[chbot] J-link under platformio for LPC1768

[Mark Atherton]

www.google.com/search?q=j-link+could+not+find+core+in+coresight+setup&oq=Could+not+find+core+in+Coresight+setup 
<https://www.google.com/search?q=j-link+could+not+find+core+in+coresight+setup&oq=Could+not+find+core+in+Coresight+setup> 
-- appears to be quite a popular failure.

it sounds like the programming chain chain is something like Visual 
Studio -> platformio -> SEGGER (driver) -> J-link -> LPC1768

Are there any CLI tools that allow you to break this chain, firstly to 
confirm that you can talk to J-link, then you should be able to find 
device ID for the LPC1768 (RAM, FLASH size).

Maybe 
https://www.segger.com/products/debug-probes/j-link/tools/j-link-commander/ 
or similar

Aarg, just found https://www.segger.com/downloads/jlink/UM08001 462 page 
manual just for a programmer ?? ! -- Just spotted it includes debugger 
setup...

Dunno if any of that is of any use.

-Mark




On 27/11/2019 7:48 PM, Peter Ellens wrote:
> Has anyone successfully managed to get a J-link talking to a LPC1768 
> under platformio (running under visual studio code for Linux)
>
> I just can't seem to get it to work...  Sadly i'm not experienced 
> enough with J-links to know if its something I am doing wrong or 
> something else...
>
> The current error is: Could not find core in Coresight setup
> Full log can be found https://pastebin.com/PM5BseTz
>
> Initially I did have issues with the SEGGER software detecting my 
> j-link as a clone and it wiped the J-Links firmware. But I was able to 
> put the firmware back and update it to the latest available version 
> and it hasn't given any weird errors since.
>
> Any Ideas? 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ourshack.com/pipermail/chchrobotics/attachments/20191127/635e6e8b/attachment.html>