LPC-Expresso + LPC-Link + LPC-Link 2 - which are supported?

[lpcware]

Content originally posted in LPCWare by tealok on Tue Jun 04 11:11:22 MST 2013
I have purchased the LPC433x-Explorer, a new LPC-Link 2 from mBed, and downloaded the latest v5.2.4 LPCXpresso.  I also have an older LPC-Link, separated from an LPCXpresso LPC1114 Rev A board.

My  problem is:  none of  the above will "talk" to each other.  The free version of the LPCXpresso does  not recognize either LPC-Link.

The LPC433x-Xplorer zip projects extract and compile with no errors, but when I attempt to debug the Blinky project, for example, my LPC-link is not recognized.  I read in the forum FAQ about unrecognized LPC-links, and set the preferences to recognize the LPC-Link as HID, but this did not result  in any change in behavior.  The CodeRed website clearly  shows LPC-Link (legacy, not LPC-Link-2) in its table of Features-vs-Version (http://www.code-red-tech.com/RedSuite5/lpcxpresso-5.php) in the row  "JTAG/SWD  Interfaces Supported".  In the  same   preferences dialog, there is an EMULATOR choice. When I try to configure, the GUI reports that EMULATORS are not supported in the free version, and points me to upgrade. 

So, can anyone help me with these LPC-Link & Emulator questions?

1.  How do I set up LPCXpresso (free ver) to recognize and allow flashing code with my legacy LPC-Link (from a LPC1114 Rev A LPCXpresso board)?

2.  Do I have a "bad" version (Rev A) of the LPC-Link board?

3.  When  I compile and select Debug, the IDE attempts to attach a JTAG-EMULATOR (and fails).  How does LPC-Link differ from a supported EMULATOR, yet retain its identity as a JTAG interface?  How does LPCXpresso differentiate between a JTAG emulator and a LPC-Link JTAG device?  If I cannot perform[B] full debug[/B] (ie, flash code, set breakpoints, watchpoints, display variables) [B]what is[/B] the functionality provided by LPC-Link? 

4.  Would I have any greater chance of success using LPC-Link or LPC-Link-2 if I purchase the RedSuite NXP Edition, or do I fundamentally need to purchase a non-free IDE  and a Redlink or RedProbe+ to obtain seamless behavior?

5.  Will LPC-Link-2 be supported for [B]full debug[/B] in LPCXpresso (free) IDE?  Is it  now, but  only in one of the paid versions?

6.  What is the correct, or most ideal, or known-to-work combination of LPCXpresso versions  _and_ JTAG interfaces for [B]full debug[/B] with the LPC433x-Xplorer board?

NOTE:  from the LPCXpresso IDE, I have run  "Launch Configuration -> edit  current", and tried to choose other JTAG interfaces.  I also downloaded the latest LPC-Link-2 configuration utility, image and USB drivers.  I made sure that Windows device manager was showing "LPC based  USB device" for the LPC-Link2 before launching LPCXpresso, but the debugger launch never  succeeded in  identifying ANY debugger.  I DID observe the red LED on the LPC-Link-2 and the red and  blue LED's on the Xplorer-- all were illuminated (steady) when  the J-Link-2  J2 (JTAG-SWD)  connector was attached.

ANY help will be greatly appreciated.

Tealok

[lpcware]

Content originally posted in LPCWare by tealok on Tue Jun 11 10:01:30 MST 2013
My board is in fact a 4337.

After following your suggestions,  and importing the [I][B][U]Xplorer 4337[/U] [/B][/I] projects, I am now able to ... blink LED's, set breakpoints, etc.

The zip file used in my original post was for a  4330... duh, I should have spotted that- it came from NGX at ...
   http://shop.ngxtechnologies.com/download/sample_code/LPC4330-Xplorer/LPCXpresso/lpc4330_Xplorer_LPCX...

Much better... This toolchain works great, thank you NXP, and Code Red support, for sticking with my thread request for help.

Tealok

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Tue Jun 11 05:57:47 MST 2013
Sudden thought. Can you actually double check what MCU is actually fitted to your board - is it an LPC4330 (as I assumed) or is it actually an LPC4337?

If it is an LPC4337 then the boot jumpers will be set differently as this part has internal flash. It also means that any projects you are trying to debug will need to be configured differently. Read the LPC18/43 FAQ previously referenced (plus the FAQs this then references) for details.

I suggest that you:

1) Create a new workspace ("File -> Switch workspace", then point to new/empty folder)

2) If you have an LPC4330, import the examples from:

C:\nxp\LPCXpresso_5.2.4_2122\lpcxpresso\Examples\NXP\LPC4000\LPC43xx\NGX_LPC4330-Xplorer.zip

3) If you have an LPC4337, import the examples from:

C:\nxp\LPCXpresso_5.2.4_2122\lpcxpresso\Examples\NXP\LPC4000\LPC43xx\NGX_LPC4337-Xplorer.zip

In either case report your MCU and the results of attempting to debug with the appropriate examples (including the debug log if you still see failures).

Regards,
CodeRedSupport

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Tue Jun 11 04:27:55 MST 2013

---

Quote: tealok
Are my J4 boot-control switches set incorrectly?  (1,2,3 =  ON, 4 = OFF).

---

This certainly looks suspicious to me. All of the Xplorer-4330 / 1830 boards that I can find here have the J4 jumpers set to 1=OFF, 2,3,4=ON. In other words, holding the board with the ethernet socket on the right:

- J4-1 is in the down position
- J4-2, J4-3, J4-4 are in the up position

This should configure the board to boot from SPIFI flash (which is what this board has mounted on it).

Note that LPCXpresso 5.2.4 ships with some simple examples that have been tested here with the Xplorer-4330 board. I would suggest trying those out, as I'm not sure how up to date the examples you are using might be.

As a slight aside, for general information on using LPC18/43 parts with LPCXpresso, please see:

http://support.code-red-tech.com/CodeRedWiki/LPC1850_4350_Support

If you continue to have problems after checking your J4 jumpers, then it would perhaps be useful to see your debug log:

http://support.code-red-tech.com/CodeRedWiki/DebugLog

Regards,
CodeRedSupport

[lpcware]

Content originally posted in LPCWare by tealok on Mon Jun 10 16:03:27 MST 2013
I really appreciate the suggestions, and having experts monitor this venue. 

My system is a clean Win7 Pro, 64-bit, fully patched, running on a Dell T5500  with 8-cores and 16GB of RAM.

Since LPC-Link2 is not supported, I just abandoned (postponed)  my expectations  ;-)

The suggestion to avoid custom debug configurations (allow auto-generation) made me think maybe the Eclipse IDE is a bit "sticky", and my experiments resulted in a corrupted or incompatible config-- so I blew the workspace away and started over- including a workstation re-boot.

After importing and building all projects, I selected individual projects, and clicked "debug".  Sure enough, allowing the system to search for emulators/debuggers worked.  The IDE produced a message about the HID device being  configured, then popped a dialog with two JTAG choices.  From my work with OpenOCD on Linux, it looked like these were the M0 and M4 TAPs in the JTAG chain, so I chose the "Coresight JTAG DP".

The code then attempted to run, but produced an error: "15: target error from register access: verify population of memory and peripherals" (JPG screen-shot attached).  Since the IDE offered "help with this issue", I followed it, but the Code-Red FAQ/KB was not directly applicable, and I did not find a solution.

The  register address listed was:  0x1001 FFF8.

Do I have a bad flash device?  Is there a bug in the code?  Are my J4 boot-control switches set incorrectly?  (1,2,3 =  ON, 4 = OFF).

Any help/suggestions will be very much appreciated !!

Note:
I subsequently built, downloaded and attempted to run _each_ of the Xplorer projects.  None (I repeat, none) would run.  Those which actually loaded code (as evidenced by the LPC-Link's flashing LED, and the IDE's progress-bar during the transfer), all failed with the same error and address.

I also  observed that, after failure, it was necessary to power-off and re-connect the LPC-Link.  Otherwise, the LPC-Link would not be correctly identified or configured for the next project/test.

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Wed Jun 05 01:13:58 MST 2013
Connecting to LPC43xx from LPCXpresso IDE via LPC-Link is fully supported, and has been working for many releases now.

Connecting to LPC43xx from LPCXpresso IDE via LPC-Link2 is not yet supported, but is under active development for release in the not too distant future. Note that LPC-Link2 already supports NXP's other Cortex based parts, as per the xref'ed thread that [I]whitecoe[/I] pointed you at.

Note - when using LPC-Link2 with LPCXpresso IDE, ensure that jumper JP1 is open.

What OS are you running, and are you running natively or within a virtual machine environment?

Have you tried connecting your LPC-Link to a different USB port, or through a powered USB hub?

Did you LPCXpresso board work correctly before you disconnected the LPC-Link? Did you disconnect your LPC-Link from the target portion of your LPCXpresso board correctly? You'll find some useful links on doing this at:

http://support.code-red-tech.com/CodeRedWiki/LPCXpressoExtDebug

If you disconnect and reconnect the LPCXpresso/LPC-Link board from your PC (assuming you are running Windows), then the Device Manager should display "USB Device with DFU capabilities". Does it?

When you then try to start a debug session, the debug firmware should be downloaded to the probe, which should reenumerate as an LPC-Link. Does it?

By the way, I strongly suggest that you avoid trying to manually setup Launch configurations. Delete the ones in your existing projects and let the tools auto-create them.

Regards,
CodeRedSupport

[lpcware]

Content originally posted in LPCWare by whitecoe on Tue Jun 04 11:59:46 MST 2013
You might want to read this...

http://knowledgebase.nxp.com/showpost.php?p=24184&postcount=6

=> sounds like LPC-Link2 support for LPC43xx is still in development.

And for what it's worth, I've had no problem using the original LPC-Link under LPCXpresso with LPC4350 or LPC4357.

HTH!