<?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>Kinetis MicrocontrollersのトピックRe: SIM_SDID reads 0 after mass erase</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/SIM-SDID-reads-0-after-mass-erase/m-p/1887257#M66436</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/234089"&gt;@bm31416&lt;/a&gt;&amp;nbsp;, &lt;BR /&gt;There is no log file of the reading process because this a tool that is directly on MCUXpresso but I can share you the erase log file, I'm using P&amp;amp;E so this log file may change.&lt;/P&gt;
&lt;LI-CODE lang="c"&gt;Executing flash operation 'Erase' (Erase flash) - Wed Jun 05 09:51:24 CST 2024
Checking MCU info...
Scanning for targets...
Executing flash action...
P&amp;amp;E GDB Server for Arm(R) devices, Version 9.45.00.00
Copyright 2018, P&amp;amp;E Microcomputer Systems Inc, All rights reserved
Loading library C:\nxp\MCUXpressoIDE_11.9.1_2170\ide\plugins\com.pemicro.debug.gdbjtag.pne_5.7.8.202404031741\win32\gdi\unit_ngs_arm_internal.dll ... Done.
Command line arguments: -device=NXP_KVx_KV31F512M12 -startserver -singlesession -serverport=7225 -gdbmiport=6225 -interface=OPENSDA -speed=5000 -port=USB1 -streamingport=10224 -configfile=C:/workspace/MCUXpresso11.9.1/.metadata/.plugins/com.pemicro.debug.gdbjtag.pne/config.ini -programmingtype=3 -flashobjectfile=C:\workspace\MCUXpresso11.9.1\frdmkv31f_led_blinky_aaaaah\Debug\frdmkv31f_led_blinky_aaaaah.axf -quitafterprogramming
Config file selected: C:/workspace/MCUXpresso11.9.1/.metadata/.plugins/com.pemicro.debug.gdbjtag.pne/config.ini
Device selected is NXP_KVx_KV31F512M12
User Specified Hardware Selection : Interface=OPENSDA and Port=USB1
Connecting to target.
Unable to load libusb0.dll
OpenSDA detected - Flash Version 1.18
Device is NXP_KVx_KV31F512M12.
Mode is In-Circuit Debug.
(C)opyright 2012, P&amp;amp;E Microcomputer Systems, Inc. (www.pemicro.com)
API version is 101
TARGET XML PATH is C:\nxp\MCUXpressoIDE_11.9.1_2170\ide\plugins\com.pemicro.debug.gdbjtag.pne_5.7.8.202404031741\supportFiles_ARM\target_v7m_vfp.xml
Server 1 running on 127.0.0.1:7225
Server 2 running on 127.0.0.1:7227
Server 3 running on 127.0.0.1:7229
Server 4 running on 127.0.0.1:7231
Server 5 running on 127.0.0.1:7233
Server 6 running on 127.0.0.1:7235
Server 7 running on 127.0.0.1:7237
Server 8 running on 127.0.0.1:7239
Server 9 running on 127.0.0.1:7241
Server 10 running on 127.0.0.1:7243
Server 11 running on 127.0.0.1:6225
Unable to load libusb0.dll
Copyright 2024 P&amp;amp;E Microcomputer Systems,Inc.
Command Line :C:\nxp\MCUXpressoIDE_11.9.1_2170\ide\plugins\com.pemicro.debug.gdbjtag.pne_5.7.8.202404031741\win32\pegdbserver_console -device=NXP_KVx_KV31F512M12 -startserver -singlesession -serverport=7225 -gdbmiport=6225 -interface=OPENSDA -speed=5000 Ð
OpenSDA detected - Flash Version 1.18
CMD&amp;gt;RE
Initializing.
Target has been RESET and is active.
CMD&amp;gt;CM C:\nxp\MCUXpressoIDE_11.9.1_2170\ide\plugins\com.pemicro.debug.gdbjtag.pne_5.7.8.202404031741\supportFiles_ARM\NXP\KVx\freescale_kv31f512m12_1x32x128k_pflash.arp
Initializing.
Initialized.
;version 1.06, 05/18/2017, Copyright 2017 P&amp;amp;E Microcomputer Systems, Inc. All rights reserved. www.pemicro.com [kv_31f512_n_pflash]
;device freescale, kv31f512m12, 1x32x128k, desc=pflash
;begin_cs device=$00000000, length=$00080000, ram=$20000000
Loading programming algorithm ...
Inaccessible blocks ...
block 0007E000-0007FFFF : Flash Access Control Enabled
Programming sequency is : erase only
CMD&amp;gt;EO
Erasing ranges ...
Range 00000000-00001FFF
Erased successfully.
CMD&amp;gt;RE
Initializing.
Target has been RESET and is active.
All Servers Running
Target Disconnected.&lt;/LI-CODE&gt;
&lt;P&gt;There is a chance where you can try to read the SIM_SDID in the way I explain before? this in order to narrow more what could be the issue.&lt;/P&gt;</description>
    <pubDate>Thu, 13 Jun 2024 18:50:28 GMT</pubDate>
    <dc:creator>Pablo_Ramos</dc:creator>
    <dc:date>2024-06-13T18:50:28Z</dc:date>
    <item>
      <title>SIM_SDID reads 0 after mass erase</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/SIM-SDID-reads-0-after-mass-erase/m-p/1874742#M66400</link>
      <description>&lt;P&gt;Hi *,&lt;/P&gt;&lt;P&gt;I am using MCU_Link and openocd to flash mkv31f devices. I've noticed that after I perform a mass erase the value of&amp;nbsp;SIM_SDID is 0.&lt;/P&gt;&lt;P&gt;I read this value using the debugger and openocd.&lt;/P&gt;&lt;P&gt;If the chip has a valid image, the expected value is read back.&lt;/P&gt;&lt;P&gt;Is this the expected behavior? Isn't this register read only?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[Update 2024-05-27]:&lt;/P&gt;&lt;P&gt;When I run the command dap info from open ocd I get the answer:&lt;/P&gt;&lt;P&gt;AP ID register 0x24770011&lt;BR /&gt;Type is MEM-AP AHB3&lt;BR /&gt;MEM-AP BASE 0xe00ff003&lt;BR /&gt;Valid ROM table present&lt;BR /&gt;Component base address 0xe00ff000&lt;BR /&gt;Can't read component, the corresponding core might be turned off&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 27 May 2024 07:40:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/SIM-SDID-reads-0-after-mass-erase/m-p/1874742#M66400</guid>
      <dc:creator>bm31416</dc:creator>
      <dc:date>2024-05-27T07:40:07Z</dc:date>
    </item>
    <item>
      <title>Re: SIM_SDID reads 0 after mass erase</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/SIM-SDID-reads-0-after-mass-erase/m-p/1880964#M66417</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/234089"&gt;@bm31416&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;I test your issue using an FRDM-KV31F and the value of the SIM_SDID isn't 0, the way I test it is the following:&lt;/P&gt;
&lt;P&gt;Use the erase flash action that MCUXpresso have (I use PEMicro because of the bootloader please check which one do you have)&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Pablo_Ramos_0-1717535948179.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/282483i3A6FFF6D64F913A2/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Pablo_Ramos_0-1717535948179.png" alt="Pablo_Ramos_0-1717535948179.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Once the flash is erased use the Attach to running target option.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Pablo_Ramos_2-1717535977989.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/282485iDF5FFEF28ADE9C15/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Pablo_Ramos_2-1717535977989.png" alt="Pablo_Ramos_2-1717535977989.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;With this you should be able to see the memory via MCUXpresso even though the flash is empty.&lt;/P&gt;
&lt;P&gt;Search the SIM_SDID with the address of the Reference Manual&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Pablo_Ramos_3-1717535984937.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/282486iC6712CDA4F7BAED4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Pablo_Ramos_3-1717535984937.png" alt="Pablo_Ramos_3-1717535984937.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Knowing that I was using an MKV31F512 the lasts bits match the register of the SIM_SDID&lt;BR /&gt;0011 0001 0110 or 316&lt;/P&gt;
&lt;DIV id="tinyMceEditorPablo_Ramos_4" class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Pablo_Ramos_5-1717536023801.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/282488i20F0D2404D912495/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Pablo_Ramos_5-1717536023801.png" alt="Pablo_Ramos_5-1717536023801.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Try this method.&lt;BR /&gt;Hope it help you!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jun 2024 21:21:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/SIM-SDID-reads-0-after-mass-erase/m-p/1880964#M66417</guid>
      <dc:creator>Pablo_Ramos</dc:creator>
      <dc:date>2024-06-04T21:21:23Z</dc:date>
    </item>
    <item>
      <title>Re: SIM_SDID reads 0 after mass erase</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/SIM-SDID-reads-0-after-mass-erase/m-p/1881258#M66419</link>
      <description>Thanks for the support here.&lt;BR /&gt;&lt;BR /&gt;I see two main differences between the two setups: Debugger and Software. I don't know the details of how openOcd erases the memory, but I do know it is erased afterwards.&lt;BR /&gt;&lt;BR /&gt;My assumption is that MCUExpresso sets some other HW registers which allow/activate the reading of the SIM_ID.&lt;BR /&gt;&lt;BR /&gt;Would be possible to share the logfile of the reading process from the MCUExpresso... maybe there is listed all the necessary steps.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance</description>
      <pubDate>Wed, 05 Jun 2024 06:48:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/SIM-SDID-reads-0-after-mass-erase/m-p/1881258#M66419</guid>
      <dc:creator>bm31416</dc:creator>
      <dc:date>2024-06-05T06:48:16Z</dc:date>
    </item>
    <item>
      <title>Re: SIM_SDID reads 0 after mass erase</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/SIM-SDID-reads-0-after-mass-erase/m-p/1887257#M66436</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/234089"&gt;@bm31416&lt;/a&gt;&amp;nbsp;, &lt;BR /&gt;There is no log file of the reading process because this a tool that is directly on MCUXpresso but I can share you the erase log file, I'm using P&amp;amp;E so this log file may change.&lt;/P&gt;
&lt;LI-CODE lang="c"&gt;Executing flash operation 'Erase' (Erase flash) - Wed Jun 05 09:51:24 CST 2024
Checking MCU info...
Scanning for targets...
Executing flash action...
P&amp;amp;E GDB Server for Arm(R) devices, Version 9.45.00.00
Copyright 2018, P&amp;amp;E Microcomputer Systems Inc, All rights reserved
Loading library C:\nxp\MCUXpressoIDE_11.9.1_2170\ide\plugins\com.pemicro.debug.gdbjtag.pne_5.7.8.202404031741\win32\gdi\unit_ngs_arm_internal.dll ... Done.
Command line arguments: -device=NXP_KVx_KV31F512M12 -startserver -singlesession -serverport=7225 -gdbmiport=6225 -interface=OPENSDA -speed=5000 -port=USB1 -streamingport=10224 -configfile=C:/workspace/MCUXpresso11.9.1/.metadata/.plugins/com.pemicro.debug.gdbjtag.pne/config.ini -programmingtype=3 -flashobjectfile=C:\workspace\MCUXpresso11.9.1\frdmkv31f_led_blinky_aaaaah\Debug\frdmkv31f_led_blinky_aaaaah.axf -quitafterprogramming
Config file selected: C:/workspace/MCUXpresso11.9.1/.metadata/.plugins/com.pemicro.debug.gdbjtag.pne/config.ini
Device selected is NXP_KVx_KV31F512M12
User Specified Hardware Selection : Interface=OPENSDA and Port=USB1
Connecting to target.
Unable to load libusb0.dll
OpenSDA detected - Flash Version 1.18
Device is NXP_KVx_KV31F512M12.
Mode is In-Circuit Debug.
(C)opyright 2012, P&amp;amp;E Microcomputer Systems, Inc. (www.pemicro.com)
API version is 101
TARGET XML PATH is C:\nxp\MCUXpressoIDE_11.9.1_2170\ide\plugins\com.pemicro.debug.gdbjtag.pne_5.7.8.202404031741\supportFiles_ARM\target_v7m_vfp.xml
Server 1 running on 127.0.0.1:7225
Server 2 running on 127.0.0.1:7227
Server 3 running on 127.0.0.1:7229
Server 4 running on 127.0.0.1:7231
Server 5 running on 127.0.0.1:7233
Server 6 running on 127.0.0.1:7235
Server 7 running on 127.0.0.1:7237
Server 8 running on 127.0.0.1:7239
Server 9 running on 127.0.0.1:7241
Server 10 running on 127.0.0.1:7243
Server 11 running on 127.0.0.1:6225
Unable to load libusb0.dll
Copyright 2024 P&amp;amp;E Microcomputer Systems,Inc.
Command Line :C:\nxp\MCUXpressoIDE_11.9.1_2170\ide\plugins\com.pemicro.debug.gdbjtag.pne_5.7.8.202404031741\win32\pegdbserver_console -device=NXP_KVx_KV31F512M12 -startserver -singlesession -serverport=7225 -gdbmiport=6225 -interface=OPENSDA -speed=5000 Ð
OpenSDA detected - Flash Version 1.18
CMD&amp;gt;RE
Initializing.
Target has been RESET and is active.
CMD&amp;gt;CM C:\nxp\MCUXpressoIDE_11.9.1_2170\ide\plugins\com.pemicro.debug.gdbjtag.pne_5.7.8.202404031741\supportFiles_ARM\NXP\KVx\freescale_kv31f512m12_1x32x128k_pflash.arp
Initializing.
Initialized.
;version 1.06, 05/18/2017, Copyright 2017 P&amp;amp;E Microcomputer Systems, Inc. All rights reserved. www.pemicro.com [kv_31f512_n_pflash]
;device freescale, kv31f512m12, 1x32x128k, desc=pflash
;begin_cs device=$00000000, length=$00080000, ram=$20000000
Loading programming algorithm ...
Inaccessible blocks ...
block 0007E000-0007FFFF : Flash Access Control Enabled
Programming sequency is : erase only
CMD&amp;gt;EO
Erasing ranges ...
Range 00000000-00001FFF
Erased successfully.
CMD&amp;gt;RE
Initializing.
Target has been RESET and is active.
All Servers Running
Target Disconnected.&lt;/LI-CODE&gt;
&lt;P&gt;There is a chance where you can try to read the SIM_SDID in the way I explain before? this in order to narrow more what could be the issue.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jun 2024 18:50:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/SIM-SDID-reads-0-after-mass-erase/m-p/1887257#M66436</guid>
      <dc:creator>Pablo_Ramos</dc:creator>
      <dc:date>2024-06-13T18:50:28Z</dc:date>
    </item>
  </channel>
</rss>

