<?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 S32K144 FLASH application problem in S32K</title>
    <link>https://community.nxp.com/t5/S32K/S32K144-FLASH-application-problem/m-p/896024#M4375</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;MCU model number: S32K144&lt;BR /&gt;Downloader: J-LINK&lt;BR /&gt;Description of the problem: After the PFlash cache is closed, there is no problem with single-step debugging. The online DEBUG fails to run at full speed, as shown in the following figure:&lt;BR /&gt;Note: When running offline, check whether it is running through the indicator in the main function. The indicator does not respond, indicating that it has not entered the main loop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;deadbef5:&amp;nbsp;&amp;nbsp; Failed to execute MI command:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; -data-disassemble -s 3735928565 -e 3735928721 -- 3&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Error message from debugger back end:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Cannot access memory at address 0xdeadbef4&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="aaaaaaaaaaa.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/79356i9CF6F3B746E088B6/image-size/large?v=v2&amp;amp;px=999" role="button" title="aaaaaaaaaaa.png" alt="aaaaaaaaaaa.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Configuration information:&lt;BR /&gt;1. Set the clock to RUN mode before configuring PFlash (normally working in HSRUN, PFlash cannot operate under high speed).&lt;BR /&gt;2. Close the PFlash cache and prefetch:&lt;BR /&gt;MSCM-&amp;gt;OCMDR[0u] |= MSCM_OCMDR_OCM1(0xFu);&lt;BR /&gt;3. Initialize PFlash; write data to PFlash.&lt;BR /&gt;4. Enable PFlash cache and prefetch.&lt;BR /&gt;5, restore the working mode to HSRUN mode (112M)&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 15 Apr 2019 12:16:51 GMT</pubDate>
    <dc:creator>liuweiliang</dc:creator>
    <dc:date>2019-04-15T12:16:51Z</dc:date>
    <item>
      <title>S32K144 FLASH application problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K144-FLASH-application-problem/m-p/896024#M4375</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;MCU model number: S32K144&lt;BR /&gt;Downloader: J-LINK&lt;BR /&gt;Description of the problem: After the PFlash cache is closed, there is no problem with single-step debugging. The online DEBUG fails to run at full speed, as shown in the following figure:&lt;BR /&gt;Note: When running offline, check whether it is running through the indicator in the main function. The indicator does not respond, indicating that it has not entered the main loop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;deadbef5:&amp;nbsp;&amp;nbsp; Failed to execute MI command:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; -data-disassemble -s 3735928565 -e 3735928721 -- 3&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Error message from debugger back end:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Cannot access memory at address 0xdeadbef4&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="aaaaaaaaaaa.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/79356i9CF6F3B746E088B6/image-size/large?v=v2&amp;amp;px=999" role="button" title="aaaaaaaaaaa.png" alt="aaaaaaaaaaa.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Configuration information:&lt;BR /&gt;1. Set the clock to RUN mode before configuring PFlash (normally working in HSRUN, PFlash cannot operate under high speed).&lt;BR /&gt;2. Close the PFlash cache and prefetch:&lt;BR /&gt;MSCM-&amp;gt;OCMDR[0u] |= MSCM_OCMDR_OCM1(0xFu);&lt;BR /&gt;3. Initialize PFlash; write data to PFlash.&lt;BR /&gt;4. Enable PFlash cache and prefetch.&lt;BR /&gt;5, restore the working mode to HSRUN mode (112M)&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Apr 2019 12:16:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K144-FLASH-application-problem/m-p/896024#M4375</guid>
      <dc:creator>liuweiliang</dc:creator>
      <dc:date>2019-04-15T12:16:51Z</dc:date>
    </item>
    <item>
      <title>Re: S32K144 FLASH application problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K144-FLASH-application-problem/m-p/896025#M4376</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Please refer to the&amp;nbsp;OCM1 description:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_2.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/75600iEF1FA4C520948D41/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;The below line should be executed from RAM to avoid these undesired results.&lt;/P&gt;&lt;P&gt;MSCM-&amp;gt;OCMDR[0u] |= MSCM_OCMDR_OCM1(0xFu);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Apr 2019 13:05:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K144-FLASH-application-problem/m-p/896025#M4376</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2019-04-15T13:05:06Z</dc:date>
    </item>
    <item>
      <title>Re: S32K144 FLASH application problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K144-FLASH-application-problem/m-p/896026#M4377</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI Daniel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;are there other scenarios possible, beside code execution from flash which would keep the flash controller busy / causing a problem?&lt;/P&gt;&lt;P&gt;Like DMA, EEE, cSEC accessing the flash?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;best regards&lt;/P&gt;&lt;P&gt;Jochen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Jul 2020 06:39:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K144-FLASH-application-problem/m-p/896026#M4377</guid>
      <dc:creator>jochengerster</dc:creator>
      <dc:date>2020-07-16T06:39:58Z</dc:date>
    </item>
    <item>
      <title>Re: S32K144 FLASH application problem</title>
      <link>https://community.nxp.com/t5/S32K/S32K144-FLASH-application-problem/m-p/1452703#M15258</link>
      <description>&lt;P&gt;I also meet the problem just like you, so, are u solve it? thank u! waiting for your reply!&lt;/P&gt;</description>
      <pubDate>Wed, 04 May 2022 12:07:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/S32K144-FLASH-application-problem/m-p/1452703#M15258</guid>
      <dc:creator>ssyyw</dc:creator>
      <dc:date>2022-05-04T12:07:10Z</dc:date>
    </item>
  </channel>
</rss>

