<?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: Segger J-Flash settings with K8x and QSPI in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Segger-J-Flash-settings-with-K8x-and-QSPI/m-p/1350831#M61643</link>
    <description>&lt;P&gt;&amp;nbsp;J-Flash/J-Link V6.50a works perfectly. There's a bug in V7.45c, which I have reported to Segger.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;Update Jan 20, 2022 from Segger:&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;EM&gt;Upcoming release of Segger J-Link/J-Flash will include fix for this issue.&lt;/EM&gt;&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;EM&gt;The issue was due to a speed optimization that relied on the availability of an external reference clock, RTCK, which is not the case with many devices, including the NXP K8x.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Update Jan 25, 2022:&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Segger J-Link/J-Flash V7.60f available for download.&amp;nbsp; Fix for K8x issue included in this release.&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 25 Jan 2022 18:23:37 GMT</pubDate>
    <dc:creator>deniscollis</dc:creator>
    <dc:date>2022-01-25T18:23:37Z</dc:date>
    <item>
      <title>Segger J-Flash settings with K8x and QSPI</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Segger-J-Flash-settings-with-K8x-and-QSPI/m-p/1347064#M61577</link>
      <description>&lt;P&gt;I'm attempting to program a K81 and QSPI (Micron&amp;nbsp;MT25QL128 - 16MB, single die).&amp;nbsp; Segger J-Flash V7.54c shows error:&amp;nbsp;&lt;/P&gt;&lt;P&gt;Timeout while preparing target, RAMCode did not respond in time. (PC = 0x00000000, CPSR = 0x00000000, LR = 0x61000000)!&lt;BR /&gt;Failed to prepare RAMCode using RAM&lt;BR /&gt;Error while determining flash info (Bank 1&amp;nbsp;@ 0x68000000)&lt;BR /&gt;&lt;SPAN&gt;Failed to auto program target&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The J-Flash Project Info:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="deniscollis_0-1632774047039.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/157592i2D2092E12FF62AF9/image-size/medium?v=v2&amp;amp;px=400" role="button" title="deniscollis_0-1632774047039.png" alt="deniscollis_0-1632774047039.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Has anyone encountered this, and can figure what's going on?&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Denis&lt;/P&gt;</description>
      <pubDate>Mon, 27 Sep 2021 20:23:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Segger-J-Flash-settings-with-K8x-and-QSPI/m-p/1347064#M61577</guid>
      <dc:creator>deniscollis</dc:creator>
      <dc:date>2021-09-27T20:23:59Z</dc:date>
    </item>
    <item>
      <title>Re: Segger J-Flash settings with K8x and QSPI</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Segger-J-Flash-settings-with-K8x-and-QSPI/m-p/1347322#M61580</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When you use jFlash, you doesn't configure the QSPI. So the external ram can't be used.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have a great day,&lt;/P&gt;
&lt;P&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;
&lt;P&gt;- We are following threads for 7 days after the last post, later replies are ignored&lt;BR /&gt;Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;</description>
      <pubDate>Tue, 28 Sep 2021 06:53:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Segger-J-Flash-settings-with-K8x-and-QSPI/m-p/1347322#M61580</guid>
      <dc:creator>nxf56274</dc:creator>
      <dc:date>2021-09-28T06:53:26Z</dc:date>
    </item>
    <item>
      <title>Re: Segger J-Flash settings with K8x and QSPI</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Segger-J-Flash-settings-with-K8x-and-QSPI/m-p/1348719#M61605</link>
      <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/71004"&gt;@nxf56274&lt;/a&gt;I'm not sure what you're saying.&amp;nbsp;There is no external RAM, only the K81 with its onboard internal RAM.&lt;/P&gt;&lt;P&gt;As I understand the process, in order to write to the external QSPI flash, j-Flash/J-Link first downloads code to the MCU's internal RAM, sets the program counter and starts execution.&amp;nbsp; Thereafter, J-Link/J-Flash sends instructions and data to the RAM resident code, which relays it to the external QSPI flash.&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Denis&lt;/P&gt;</description>
      <pubDate>Tue, 05 Oct 2021 23:43:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Segger-J-Flash-settings-with-K8x-and-QSPI/m-p/1348719#M61605</guid>
      <dc:creator>deniscollis</dc:creator>
      <dc:date>2021-10-05T23:43:18Z</dc:date>
    </item>
    <item>
      <title>Re: Segger J-Flash settings with K8x and QSPI</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Segger-J-Flash-settings-with-K8x-and-QSPI/m-p/1350831#M61643</link>
      <description>&lt;P&gt;&amp;nbsp;J-Flash/J-Link V6.50a works perfectly. There's a bug in V7.45c, which I have reported to Segger.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;Update Jan 20, 2022 from Segger:&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;EM&gt;Upcoming release of Segger J-Link/J-Flash will include fix for this issue.&lt;/EM&gt;&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;EM&gt;The issue was due to a speed optimization that relied on the availability of an external reference clock, RTCK, which is not the case with many devices, including the NXP K8x.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Update Jan 25, 2022:&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Segger J-Link/J-Flash V7.60f available for download.&amp;nbsp; Fix for K8x issue included in this release.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jan 2022 18:23:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Segger-J-Flash-settings-with-K8x-and-QSPI/m-p/1350831#M61643</guid>
      <dc:creator>deniscollis</dc:creator>
      <dc:date>2022-01-25T18:23:37Z</dc:date>
    </item>
  </channel>
</rss>

