Search Results

Search results 1-11 of 11.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • LPC1100L Support

    ktownsend - - J-Link/Flasher related

    Post

    Does the J-Link support the new LPC1100L chips? I'm using the latest beta SW (v425k) and also tried 4.24 (release) and it won't recognize the LPC1114L (/302). Kevin

  • I just built a new board with a 3.3V supply and I get the same results ... The error message is typically "parity error (Data = 0xFFFFFFFF, Received Parity=1)". I'm sure the footprints are OK, and I've checked the board under a microscope looking for unplated vias, etc., but out of 4 boards I've assembled they all have the same result with the QFN part. I've attached the schematic, though it's the exact same SWD interface I'm using on some QFP-based 1114 boards with no problems. I could probably…

  • The board runs at 2.0V, though I've also replaced everything to run at 3.3V with similar results. Perhaps I'll try making an entirely new board, but I've triple checked everything and I'm 99% confident that the board itself is good. Out of curiousity, what is the lowest you can go with the J-Link? I'd like to be abe to use 1.8V logic (LPC1114 supports this) but I'm not sure if the J-Link is able?

  • While I haven't had any problems with the QFP LPC1114 and the J-Link I haven't been able to connect since switching to QFN (LPC1114FHN33/301,5). J-Link Commander shows the following: SEGGER J-Link Commander V4.14a ('?' for help) Compiled Apr 21 2010 20:54:48 DLL version V4.14a, compiled Apr 21 2010 20:54:28 Firmware: J-Link ARM V8 compiled Dec 1 2009 11:42:48 Hardware: V8.00 S/N : 58001768 Feature(s) : FlashBP, FlashDL, GDB Info: Could not measure total IR len. TDO is constant high. WARNING: No …

  • It seems that you can add "-if SWD" when starting up the J-Link GDB server to force SWD mode, and it at least connects now but still lists the CoreID as 0x00000000. Shouldn't I be expecting to see a specific CoreID for the LPC1343 for example? It might be nice to enable SWD or JTAG as a menu or dropdown-box option in a future release as well, since the command-line approach isn't terribly practical or obvious, though it's obviously better than nothing.

  • I was interested in testing GDB Server to write a tutorial on how to use it, but have been unable to get it to connect to an LPC1343 board that works with other J-Link software an in Crossworks for ARM. It seems that the target can not be properly identified, but there doesn't seem to be any way to indicate what the exact core of processor is (unlike, for example, J-Flash ARM where I can specify the device being used and then connect). I'm using v 4.12 of the software and v8 firmware. Am I missi…

  • Just an update that Keil sent me a fix for this, which I imagine will make it's way into the next update. Thanks for the assistance, though.

  • Do you have any experience with Keil to guess how long oit normally takes them to put out big fixes, etc.? Obviously it's beyond your own control, but when I see the last update is from October, I'm hoping it's not every 6 months.

  • Rolf: Thanks for the update. I just tried the new drivers but still have the same problem in uVision 4.0.1, and still need to manually select the device in "J-Flash ARM" ... it doesn't seem to recognise it automatically. Kevin.

  • Just an update that when I go into J-Flash 4.09R and manually selected LPC1114 as the device in the CPU tab of Project Settings, it seems to connect and displays the same core ID as Keil (0x0BB11477), but I'm not able to manually select the device in the Keil interface (it display the same IDCODE but says no SW-DP found beside it, and it the entire SW Device section is grayed out). I've tried to attach a screenshot from Keil but had to compress the crap out of it and resize it to get it below th…

  • I noticed that the LPC1112/4 is apparently supported with the new beta firmware (4.09r), but I've been unable to connect to an LPC1114 (LPC1114FBD48/301 which is the QFP 8KB/32KB version). J-Link Commander recognizes that an M0 chip is connected, but I'm unable to properly download to flash or debug in Keil. I thought it might be an issue with the ID number not being recognised? I'd attach some screenshots, but the 20KB limit is a bit too small to upload anything useful. J-Link commander and the…