<?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>S32KのトピックRe: Flash/CPU error on S32K1xx</title>
    <link>https://community.nxp.com/t5/S32K/Flash-CPU-error-on-S32K1xx/m-p/1230048#M9882</link>
    <description>&lt;P&gt;Hello &lt;A id="link_12" href="https://community.nxp.com/t5/user/viewprofilepage/user-id/183262" target="_self"&gt;sero&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;For all reset sources, the RESET_B pin is driven low by the MCU for at least 128 bus clock cycles and until flash memory initialization has completed.&lt;BR /&gt;After flash memory initialization has completed, the RESET_B pin is released and the internal chip reset de-asserts. Keeping the RESET_B pin asserted externally delays the negation of the internal chip reset.&lt;/P&gt;
&lt;P&gt;It could be helpful if you share with me the details of the error you had in design, also the details of the error messages could help a lot.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;This behavior could be caused because the flash got corrupted, the MCU is lockup by the Flash protection mechanism. To avoid wrong flash functionality the MCU is in a permanent reset state. Please take a look at AN12130 for more information about how to prevent this issue happen. Unfortunately, we have not scripts to recover MCU from that state. &lt;A href="https://www.nxp.com/docs/en/application-note/AN12130.pdf" target="_blank"&gt;https://www.nxp.com/docs/en/application-note/AN12130.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm looking foward to your reply, if you have more questions do not hesitate to ask me.&lt;BR /&gt;Best regards,&lt;BR /&gt;Omar&lt;/P&gt;</description>
    <pubDate>Thu, 11 Feb 2021 20:22:17 GMT</pubDate>
    <dc:creator>Omar_Anguiano</dc:creator>
    <dc:date>2021-02-11T20:22:17Z</dc:date>
    <item>
      <title>Flash/CPU error on S32K1xx</title>
      <link>https://community.nxp.com/t5/S32K/Flash-CPU-error-on-S32K1xx/m-p/1228070#M9848</link>
      <description>&lt;P&gt;Hello Together,&lt;/P&gt;&lt;P&gt;i have some problems with a S32K142&lt;/P&gt;&lt;P&gt;I was able to debug and flash the device for quite some time.&lt;/P&gt;&lt;P&gt;Now, after i had some connection problems, i can still connect to the Debug-Interface (via Segger Jlink) but it tells me that the either CPU cannot be halted or that the device is in permanent reset .&lt;BR /&gt;After connecting the reset-pin to GND and another access via Jlink, I tried to unlock the device (which was successful).&lt;/P&gt;&lt;P&gt;After this, i can - sometimes - access the memory, but it keeps changing the content which is shown.&lt;/P&gt;&lt;P&gt;erase/flash/etc. is not possible&lt;/P&gt;&lt;P&gt;I tried SWD and JTAG, i also changed the speed.&lt;/P&gt;&lt;P&gt;As far as i can see from the datasheet, the device cannot start the internal RC Oscillator to provide a clock to the CPU and the memory.&lt;/P&gt;&lt;P&gt;To give some more hint: because i had an error in the design, i provided a signal on a pin before i had a power connected. I resolved the problem, so this was not happening any more at the time the above error occured.&lt;/P&gt;&lt;P&gt;Is it possible that i ruined the port or the oscillator unit with the "supply via ESD Diode"?&lt;/P&gt;&lt;P&gt;It doesn't seem that i had a latch-up because the ports still worked fine (and the connection via SWD/JTAG is still possible).&lt;/P&gt;&lt;P&gt;Thanks for your help&lt;/P&gt;&lt;P&gt;Roland&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Feb 2021 15:28:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Flash-CPU-error-on-S32K1xx/m-p/1228070#M9848</guid>
      <dc:creator>sero</dc:creator>
      <dc:date>2021-02-08T15:28:38Z</dc:date>
    </item>
    <item>
      <title>Re: Flash/CPU error on S32K1xx</title>
      <link>https://community.nxp.com/t5/S32K/Flash-CPU-error-on-S32K1xx/m-p/1230048#M9882</link>
      <description>&lt;P&gt;Hello &lt;A id="link_12" href="https://community.nxp.com/t5/user/viewprofilepage/user-id/183262" target="_self"&gt;sero&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;For all reset sources, the RESET_B pin is driven low by the MCU for at least 128 bus clock cycles and until flash memory initialization has completed.&lt;BR /&gt;After flash memory initialization has completed, the RESET_B pin is released and the internal chip reset de-asserts. Keeping the RESET_B pin asserted externally delays the negation of the internal chip reset.&lt;/P&gt;
&lt;P&gt;It could be helpful if you share with me the details of the error you had in design, also the details of the error messages could help a lot.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;This behavior could be caused because the flash got corrupted, the MCU is lockup by the Flash protection mechanism. To avoid wrong flash functionality the MCU is in a permanent reset state. Please take a look at AN12130 for more information about how to prevent this issue happen. Unfortunately, we have not scripts to recover MCU from that state. &lt;A href="https://www.nxp.com/docs/en/application-note/AN12130.pdf" target="_blank"&gt;https://www.nxp.com/docs/en/application-note/AN12130.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm looking foward to your reply, if you have more questions do not hesitate to ask me.&lt;BR /&gt;Best regards,&lt;BR /&gt;Omar&lt;/P&gt;</description>
      <pubDate>Thu, 11 Feb 2021 20:22:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Flash-CPU-error-on-S32K1xx/m-p/1230048#M9882</guid>
      <dc:creator>Omar_Anguiano</dc:creator>
      <dc:date>2021-02-11T20:22:17Z</dc:date>
    </item>
    <item>
      <title>Re: Flash/CPU error on S32K1xx</title>
      <link>https://community.nxp.com/t5/S32K/Flash-CPU-error-on-S32K1xx/m-p/1230696#M9890</link>
      <description>&lt;P&gt;Good Morning Omar,&lt;/P&gt;&lt;P&gt;i applied 5V (from a switch) to a GPIO, while the processor did not had a power supply. Because of it I had erratic behaviour (like GPIO toggling, PLL not working, ..)&lt;/P&gt;&lt;P&gt;After I found out, I connected the switch via a transfer gate powered by the processors power supply.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;After some flashing and debugging i was not able to connect any more. I don't use the protection flash addresses in my code.&lt;/P&gt;&lt;P&gt;Here is the jlink transceipt.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Connecting to target via JTAG&lt;BR /&gt;InitTarget() start&lt;BR /&gt;InitTarget()&lt;BR /&gt;TotalIRLen = 4, IRPrint = 0x01&lt;BR /&gt;JTAG chain detection found 1 devices:&lt;BR /&gt;#0 Id: 0x0993801D, IRLen: 04, JTAG-DP&lt;BR /&gt;InitTarget() end&lt;BR /&gt;TotalIRLen = 4, IRPrint = 0x01&lt;BR /&gt;JTAG chain detection found 1 devices:&lt;BR /&gt;#0 Id: 0x0993801D, IRLen: 04, JTAG-DP&lt;BR /&gt;DPv0 detected&lt;BR /&gt;Scanning AP map to find all available APs&lt;BR /&gt;AP[2]: Stopped AP scan as end of AP map has been reached&lt;BR /&gt;AP[0]: AHB-AP (IDR: 0x24770011)&lt;BR /&gt;AP[1]: JTAG-AP (IDR: 0x001C0000)&lt;BR /&gt;Iterating through AP map to find AHB-AP to use&lt;BR /&gt;AP[0]: Skipped. Invalid implementer code read from CPUIDVal[31:24] = 0xFF&lt;BR /&gt;AP[1]: Skipped. Not an AHB-AP&lt;BR /&gt;DPv0 detected&lt;BR /&gt;Scanning AP map to find all available APs&lt;BR /&gt;AP[2]: Stopped AP scan as end of AP map has been reached&lt;BR /&gt;AP[0]: AHB-AP (IDR: 0x24770011)&lt;BR /&gt;AP[1]: JTAG-AP (IDR: 0x001C0000)&lt;BR /&gt;Iterating through AP map to find AHB-AP to use&lt;BR /&gt;AP[0]: Core found&lt;BR /&gt;AP[0]: AHB-AP ROM base: 0xE00FF000&lt;BR /&gt;CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)&lt;BR /&gt;Found Cortex-M4 r0p1, Little endian.&lt;BR /&gt;FPUnit: 6 code (BP) slots and 2 literal slots&lt;BR /&gt;CoreSight components:&lt;BR /&gt;ROMTbl[0] @ E00FF000&lt;BR /&gt;Initializing 28672 bytes work RAM @ 0x1FFFC000&lt;BR /&gt;Reset: Halt core after reset via DEMCR.VC_CORERESET.&lt;BR /&gt;Reset: Reset device via AIRCR.SYSRESETREQ.&lt;BR /&gt;Reset: Core did not halt after reset, trying to disable WDT.&lt;BR /&gt;Reset: Halt core after reset via DEMCR.VC_CORERESET.&lt;BR /&gt;Reset: Reset device via AIRCR.SYSRESETREQ.&lt;BR /&gt;Reset: CPU did not halt after reset.&lt;BR /&gt;Reset: Using fallback: Reset pin.&lt;BR /&gt;Reset: Halt core after reset via DEMCR.VC_CORERESET.&lt;BR /&gt;Reset: Reset device via reset pin&lt;BR /&gt;T-bit of XPSR is 0 but should be 1. Changed to 1.&lt;BR /&gt;Cortex-M4 identified.&lt;BR /&gt;J-Link&amp;gt;&lt;/P&gt;&lt;P&gt;here after i tried the "unlock kinetis" command&lt;/P&gt;&lt;P&gt;J-Link&amp;gt;unlock kinetis&lt;BR /&gt;Found SWD-DP with ID 0x2BA01477&lt;BR /&gt;Unlocking device...O.K.&lt;BR /&gt;J-Link&amp;gt;unlock kinetis&lt;BR /&gt;Found SWD-DP with ID 0x2BA01477&lt;BR /&gt;Unlocking device...O.K.&lt;BR /&gt;J-Link&amp;gt;unlock kinetis&lt;BR /&gt;Found SWD-DP with ID 0x2BA01477&lt;BR /&gt;Unlocking device...O.K.&lt;BR /&gt;J-Link&amp;gt;unlock kinetis&lt;BR /&gt;Found SWD-DP with ID 0x2BA01477&lt;BR /&gt;Unlocking device...O.K.&lt;/P&gt;&lt;P&gt;J-Link&amp;gt;r&lt;/P&gt;&lt;P&gt;InitTarget() start&lt;BR /&gt;InitTarget()&lt;BR /&gt;Device will be unsecured now.&lt;BR /&gt;InitTarget() end&lt;BR /&gt;Found SW-DP with ID 0x2BA01477&lt;BR /&gt;DPv0 detected&lt;BR /&gt;AP map detection skipped. Manually configured AP map found.&lt;BR /&gt;AP[0]: AHB-AP (IDR: Not set)&lt;BR /&gt;AP[0]: Core found&lt;BR /&gt;AP[0]: AHB-AP ROM base: 0xE00FF000&lt;BR /&gt;CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)&lt;BR /&gt;Found Cortex-M4 r0p1, Little endian.&lt;BR /&gt;FPUnit: 6 code (BP) slots and 2 literal slots&lt;BR /&gt;CoreSight components:&lt;BR /&gt;ROMTbl[0] @ E00FF000&lt;BR /&gt;Reset delay: 0 ms&lt;BR /&gt;Reset type NORMAL: Resets core &amp;amp; peripherals via SYSRESETREQ &amp;amp; VECTRESET bit.&lt;BR /&gt;Reset: Halt core after reset via DEMCR.VC_CORERESET.&lt;BR /&gt;Reset: Reset device via AIRCR.SYSRESETREQ.&lt;BR /&gt;Reset: S_RESET_ST never gets cleared. CPU seems to be kept in reset forever.&lt;BR /&gt;Reset: Using fallback: Reset pin.&lt;BR /&gt;Reset: Halt core after reset via DEMCR.VC_CORERESET.&lt;BR /&gt;Reset: Reset device via reset pin&lt;BR /&gt;Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).&lt;BR /&gt;Reset: Reconnecting and manually halting CPU.&lt;BR /&gt;Found SW-DP with ID 0x2BA01477&lt;BR /&gt;DPv0 detected&lt;BR /&gt;AP map detection skipped. Manually configured AP map found.&lt;BR /&gt;AP[0]: AHB-AP (IDR: Not set)&lt;BR /&gt;AP[0]: Core found&lt;BR /&gt;AP[0]: AHB-AP ROM base: 0xE00FF000&lt;BR /&gt;CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)&lt;BR /&gt;Found Cortex-M4 r0p1, Little endian.&lt;BR /&gt;CPU could not be halted&lt;BR /&gt;Reset: Core did not halt after reset, trying to disable WDT.&lt;BR /&gt;Reset: Halt core after reset via DEMCR.VC_CORERESET.&lt;BR /&gt;Reset: Reset device via reset pin&lt;BR /&gt;T-bit of XPSR is 0 but should be 1. Changed to 1.&lt;BR /&gt;J-Link&amp;gt;&lt;/P&gt;&lt;P&gt;using SWD won't make a difference.&lt;/P&gt;&lt;P&gt;From time to time i get different behaviours, and sometimes i can read memory content. But the content changes every time i read it out.Sadly i cannot reproduce this right now but i keep trying.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 13 Feb 2021 08:15:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Flash-CPU-error-on-S32K1xx/m-p/1230696#M9890</guid>
      <dc:creator>sero</dc:creator>
      <dc:date>2021-02-13T08:15:50Z</dc:date>
    </item>
    <item>
      <title>Re: Flash/CPU error on S32K1xx</title>
      <link>https://community.nxp.com/t5/S32K/Flash-CPU-error-on-S32K1xx/m-p/1230697#M9891</link>
      <description>&lt;P&gt;But it seems i found the answer in the document you shared.&lt;/P&gt;&lt;P&gt;Page 7, on top:&lt;/P&gt;&lt;P&gt;Applying voltages to I/O pins when the processor is not powered. If the pin’s voltage level electrical specifications are violated,the processor can attempt a partial power up and/or puts the flash into an undefined state. This can lead to corruption of flashcontents, corruption of flash control logic, or corruption of device configuration and trim values which in turn can lead to theprocessor reporting as secured (locked device) or failure of the processor to respond to and complete flash commands&lt;/P&gt;</description>
      <pubDate>Sat, 13 Feb 2021 08:17:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Flash-CPU-error-on-S32K1xx/m-p/1230697#M9891</guid>
      <dc:creator>sero</dc:creator>
      <dc:date>2021-02-13T08:17:02Z</dc:date>
    </item>
    <item>
      <title>Re: Flash/CPU error on S32K1xx</title>
      <link>https://community.nxp.com/t5/S32K/Flash-CPU-error-on-S32K1xx/m-p/1231167#M9900</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;
&lt;P&gt;I agree, the 5V applied to the GPIO while the device was powered off might cause damage to your device. &lt;BR /&gt;I apologize for the inconvenience this may cause you, if you have more questions do not hesitate to ask me.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Omar&lt;/P&gt;</description>
      <pubDate>Mon, 15 Feb 2021 19:57:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Flash-CPU-error-on-S32K1xx/m-p/1231167#M9900</guid>
      <dc:creator>Omar_Anguiano</dc:creator>
      <dc:date>2021-02-15T19:57:28Z</dc:date>
    </item>
    <item>
      <title>Re: Flash/CPU error on S32K1xx</title>
      <link>https://community.nxp.com/t5/S32K/Flash-CPU-error-on-S32K1xx/m-p/1231183#M9901</link>
      <description>&lt;P&gt;After you read the jflash messages, do you find any chance to connect to the processor core/flash?&lt;/P&gt;</description>
      <pubDate>Mon, 15 Feb 2021 20:40:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Flash-CPU-error-on-S32K1xx/m-p/1231183#M9901</guid>
      <dc:creator>sero</dc:creator>
      <dc:date>2021-02-15T20:40:00Z</dc:date>
    </item>
  </channel>
</rss>

