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