<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix"><a
href="https://www.google.com/search?q=j-link+could+not+find+core+in+coresight+setup&oq=Could+not+find+core+in+Coresight+setup">www.google.com/search?q=j-link+could+not+find+core+in+coresight+setup&oq=Could+not+find+core+in+Coresight+setup</a>
-- appears to be quite a popular failure.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">it sounds like the programming chain
chain is something like Visual Studio -> platformio ->
SEGGER (driver) -> J-link -> LPC1768</div>
<p>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).</p>
<p>Maybe <a
href="https://www.segger.com/products/debug-probes/j-link/tools/j-link-commander/">https://www.segger.com/products/debug-probes/j-link/tools/j-link-commander/</a>
or similar</p>
<p>Aarg, just found <a
href="https://www.segger.com/downloads/jlink/UM08001">https://www.segger.com/downloads/jlink/UM08001</a>
462 page manual just for a programmer ?? ! -- Just spotted it
includes debugger setup...<br>
</p>
<p>Dunno if any of that is of any use.</p>
<p>-Mark</p>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 27/11/2019 7:48 PM, Peter Ellens
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:764177e9-e6b4-b799-33cc-4b668bafcbae@gmail.com">Has
anyone successfully managed to get a J-link talking to a LPC1768
under platformio (running under visual studio code for Linux)
<br>
<br>
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...
<br>
<br>
The current error is: Could not find core in Coresight setup
<br>
Full log can be found <a class="moz-txt-link-freetext" href="https://pastebin.com/PM5BseTz">https://pastebin.com/PM5BseTz</a>
<br>
<br>
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.
<br>
<br>
Any Ideas?
</blockquote>
<br>
</body>
</html>