Redlib Semihosting with LPC-link

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Redlib Semihosting with LPC-link

897 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by rjm on Mon Jan 18 05:18:59 MST 2016
Upon using redlib and LPClink on embedded artist's new LPC1549 board (and the built-in LPClink), I encounter an immediate hardFault exception related to a memset() call when __main is invoked in the startup-file, but only when "nohost" or "semihosting" is selected and on a target board with LPC8xx. With the option "none" all goes OK.
According to evalboard spec, LPC2link 2 is part of it. When the debugger is started, LPClink 1.1 is reported.

When a project using LPC1549 is debugged (whether external or the evalboard itself), redlib nohost or semihost does not result in a hardFault exception.
It must be noted that semihosting on an LPC8xx works flawliessly using RedProbe.

BTW: I found information on lpcware.com about RedProbe related to LPClink, and that LPClink with semihosting works considerably slower compared to RedProbe. On the other hand, I remember about a notice which states that Redprobe will no longer be supported upon one of next version revisions of LPCXpresso, which means that performance degradation using semihosting
0 Kudos
Reply
1 Reply

773 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Jan 19 02:03:57 MST 2016
The LPCXpresso1549 board has been available for around 2 years now and does indeed provide an LPC-Link2 debug probe - which is very different from the original LPC-Link(1).

[list]
  [*]https://www.lpcware.com/LPCXpressoV2Boards
[/list]

I suggest you post some details of what you actually see displayed in the debug log when you start a debug session to confirm that you are using LPC-Link2:

[list]
  [*]https://www.lpcware.com/content/faq/lpcxpresso/debug-log
[/list]

There should be no problems using Redlib with this board. If you are getting a hardfault in the setup code, this would indicate a problem with your project settings.  I suggest you tell us something about your project, and if possible actually post it:

https://www.lpcware.com/content/faq/lpcxpresso/how-importexport-projects

You could also try debugging the hard fault:

[list]
  [*]https://www.lpcware.com/content/faq/lpcxpresso/debugging-hard-fault
[/list]

Note that if you are using LPCOpen, then you may need to change your setup to allow semihosting to take place (rather than for printf output to be directed through the UART).  For info on this see:

[list]
  [*]https://www.lpcware.com/content/faq/lpcxpresso/using-printf
[/list]

Support for debugging via the old Red Probe+ produced by Code Red is not being removed from LPCXpresso IDE, but support for carrying out SWO trace via Red Probe+ is being discontinued in the next release : https://www.lpcware.com/content/faq/lpcxpresso/trace-overview

Semihosting performance via LPC-Link2 is not noticeably different to that with Red Probe+.

Regards,
LPCXpresso Support
0 Kudos
Reply