<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SES Debug not working with CLI example in nRF52 DK</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/47483/ses-debug-not-working-with-cli-example-in-nrf52-dk</link><description>I have a strange problem running the CLI example in the DK on the Nordic dev board with SES: It works fine with build/run, but when trying to debug it pops up a message that it cant find a variety of files. See attached screenshot. 
 I notice that the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 22 May 2019 00:46:50 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/47483/ses-debug-not-working-with-cli-example-in-nrf52-dk" /><item><title>RE: SES Debug not working with CLI example in nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/188386?ContentTypeID=1</link><pubDate>Wed, 22 May 2019 00:46:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7544bd10-19e6-489e-826f-c377e2093854</guid><dc:creator>Jchristf</dc:creator><description>&lt;p&gt;Perfect, that works. thx.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SES Debug not working with CLI example in nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/188140?ContentTypeID=1</link><pubDate>Tue, 21 May 2019 08:23:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:af1bbe94-307a-4e63-ad4c-0753bc962bf3</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;You get this warning because the debugger is trying to locate the source files for the prebuild NFC T2T library, to allow you to debug these files as well. Since this library is not delivered in source code, you will not be able to debug it. Removing the checkmark next to &amp;quot;Show this dialog next time&amp;quot; and selecting Yes should allow you to continue the debug session.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SES Debug not working with CLI example in nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/188028?ContentTypeID=1</link><pubDate>Mon, 20 May 2019 16:41:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d79ea06f-4b75-4344-bc9b-11586838a3ae</guid><dc:creator>Jchristf</dc:creator><description>&lt;p&gt;PS: grepping the NRF5_SDK dir for the strange path, I get these hits:&lt;/p&gt;
&lt;p&gt;Binary file components/nfc/t2t_lib/nfc_t2t_lib_gcc.a matches&lt;br /&gt;Binary file components/nfc/t2t_lib/nfc_t2t_lib_gcc_no_fpu.a matches&lt;br /&gt;Binary file components/nfc/t2t_lib/nfc_t2t_lib_iar.a matches&lt;br /&gt;Binary file components/nfc/t4t_lib/nfc_t4t_lib_gcc.a matches&lt;br /&gt;Binary file components/nfc/t4t_lib/nfc_t4t_lib_gcc_no_fpu.a matches&lt;br /&gt;Binary file components/nfc/t4t_lib/nfc_t4t_lib_iar.a matches&lt;br /&gt;Binary file examples/ble_central_and_peripheral/experimental/ble_app_interactive/pca10040/s132/ses/Output/Release/Exe/ble_app_interactive_s132_pca10040.elf matches&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Looks like problem is the NFC library source information, not available where it expects?&lt;/p&gt;
&lt;p&gt;I looked at excluding NFC from project, which would be fine for me, but there are just too many references across the CLI project to make that feasible...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SES Debug not working with CLI example in nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/188026?ContentTypeID=1</link><pubDate>Mon, 20 May 2019 16:22:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1db96e14-71d2-4e3b-a472-021e4e1a7e6c</guid><dc:creator>Jchristf</dc:creator><description>&lt;p&gt;Im working today at my main office, which is a different DK, PC etc.&amp;nbsp; Im now getting the same error message as original stated, but a rebuild does NOT fix.&amp;nbsp; &amp;nbsp;I&amp;#39;m adding screenshot of the secondary popup I receive as well. I receive both message for a lot of files.&amp;nbsp; As mentioned that path (C:/build/.. etc) does not make any sense on my PC, so must be a fossil from the project/SES?&amp;nbsp; )&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/4786.Capture2.PNG" /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SES Debug not working with CLI example in nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/188014?ContentTypeID=1</link><pubDate>Mon, 20 May 2019 15:02:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6adbb378-a6ca-44ac-b090-3085643c656e</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;What kind of event handler are you not able to single step inside? Are you using softdevice in your application?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SES Debug not working with CLI example in nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/188005?ContentTypeID=1</link><pubDate>Mon, 20 May 2019 14:36:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:661efcc2-7d3e-4fec-8626-d651bf18a7e9</guid><dc:creator>Jchristf</dc:creator><description>&lt;p&gt;I was able to solve this specific issue &amp;nbsp;by cleaning and rebuilding. I still have a problem that it doesn&amp;rsquo;t seem to be able to single step inside event handlers - quickly ends up in the assembly code only. Is there a know trick / setting to allow this? Thx&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>