<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Configuring KDS debug connection for Debugging code in RAM in Kinetis Design Studio</title>
    <link>https://community.nxp.com/t5/Kinetis-Design-Studio/Configuring-KDS-debug-connection-for-Debugging-code-in-RAM/m-p/309560#M188</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;The debugger should simply debug a RAM target like a FLASH target (the GDB server should know where is RAM and where is FLASH)&lt;/P&gt;&lt;P&gt;With Processor Expert I use the RAM (instead of FLASH configuration). This maps my code to the RAM space. What did not work for me (I'm using the Segger J-Link) is the source file mapping (Eclipse does not find the source file). Not sure what is causing this, any ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Erich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 11 May 2014 15:52:10 GMT</pubDate>
    <dc:creator>BlackNight</dc:creator>
    <dc:date>2014-05-11T15:52:10Z</dc:date>
    <item>
      <title>Configuring KDS debug connection for Debugging code in RAM</title>
      <link>https://community.nxp.com/t5/Kinetis-Design-Studio/Configuring-KDS-debug-connection-for-Debugging-code-in-RAM/m-p/309559#M187</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am wondering whether there is a guide to configuring a debug connection for code in SRAM?&lt;BR /&gt;The K64 has 256k of SRAM and so even quite large code can be run and debugged in it. I used an SRAM debug target in CW10.x for cases where the code was not too large to fit in say the 128k of a K60.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the KDS debug configuration there are not many options and although I have an SRAM build target I couldn't find way of configuring the debugger to run it.&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 04 May 2014 14:59:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Design-Studio/Configuring-KDS-debug-connection-for-Debugging-code-in-RAM/m-p/309559#M187</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2014-05-04T14:59:27Z</dc:date>
    </item>
    <item>
      <title>Re: Configuring KDS debug connection for Debugging code in RAM</title>
      <link>https://community.nxp.com/t5/Kinetis-Design-Studio/Configuring-KDS-debug-connection-for-Debugging-code-in-RAM/m-p/309560#M188</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;The debugger should simply debug a RAM target like a FLASH target (the GDB server should know where is RAM and where is FLASH)&lt;/P&gt;&lt;P&gt;With Processor Expert I use the RAM (instead of FLASH configuration). This maps my code to the RAM space. What did not work for me (I'm using the Segger J-Link) is the source file mapping (Eclipse does not find the source file). Not sure what is causing this, any ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Erich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 11 May 2014 15:52:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Design-Studio/Configuring-KDS-debug-connection-for-Debugging-code-in-RAM/m-p/309560#M188</guid>
      <dc:creator>BlackNight</dc:creator>
      <dc:date>2014-05-11T15:52:10Z</dc:date>
    </item>
  </channel>
</rss>

