<?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>MCX Microcontrollers中的主题 Subject: MPC5605 memory-read issue at 0x00100010</title>
    <link>https://community.nxp.com/t5/MCX-Microcontrollers/Subject-MPC5605-memory-read-issue-at-0x00100010/m-p/2413089#M5916</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We have an issue with an ECU using MPC5605.&lt;/P&gt;&lt;P&gt;During an EOL memory-dump operation, our toolbox reads memory using a direct CPU byte access:&lt;/P&gt;&lt;P&gt;*((uint8_t *)address)&lt;/P&gt;&lt;P&gt;From the CAN log:&lt;/P&gt;&lt;P&gt;```text&lt;BR /&gt;Read 8 bytes from 0x00100008 -&amp;gt; successful&lt;BR /&gt;Read 8 bytes from 0x00100010 -&amp;gt; ECU stops responding and resets&lt;BR /&gt;```&lt;/P&gt;&lt;P&gt;We checked the MPC5606BK Reference Manual, `16234_MPC5606BRM`, Rev. 2:&lt;/P&gt;&lt;P&gt;- Table 3-1, page 49, shows `0x00100000 - 0x001FFFFF` as **Reserved**.&lt;BR /&gt;- Pages 871-872 describe the flash-memory map and flash-emulation mapping.&lt;/P&gt;&lt;P&gt;Could you please clarify:&lt;/P&gt;&lt;P&gt;1. Is `0x00100010` a valid/readable address for MPC5605?&lt;BR /&gt;2. If it is a reserved address, what happens when software reads it directly? Can it cause an exception or reset?&lt;BR /&gt;3. Which reference manual section should we use for the exact MPC5605 memory map?&lt;/P&gt;&lt;P&gt;We are also collecting the full MPC5605 part number and silicon revision from the ECU hardware.&lt;/P&gt;&lt;P&gt;Best regards,&lt;BR /&gt;kasirajan C&lt;/P&gt;</description>
    <pubDate>Fri, 11 Sep 2026 13:03:04 GMT</pubDate>
    <dc:creator>kasirajan</dc:creator>
    <dc:date>2026-09-11T13:03:04Z</dc:date>
    <item>
      <title>Subject: MPC5605 memory-read issue at 0x00100010</title>
      <link>https://community.nxp.com/t5/MCX-Microcontrollers/Subject-MPC5605-memory-read-issue-at-0x00100010/m-p/2413089#M5916</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We have an issue with an ECU using MPC5605.&lt;/P&gt;&lt;P&gt;During an EOL memory-dump operation, our toolbox reads memory using a direct CPU byte access:&lt;/P&gt;&lt;P&gt;*((uint8_t *)address)&lt;/P&gt;&lt;P&gt;From the CAN log:&lt;/P&gt;&lt;P&gt;```text&lt;BR /&gt;Read 8 bytes from 0x00100008 -&amp;gt; successful&lt;BR /&gt;Read 8 bytes from 0x00100010 -&amp;gt; ECU stops responding and resets&lt;BR /&gt;```&lt;/P&gt;&lt;P&gt;We checked the MPC5606BK Reference Manual, `16234_MPC5606BRM`, Rev. 2:&lt;/P&gt;&lt;P&gt;- Table 3-1, page 49, shows `0x00100000 - 0x001FFFFF` as **Reserved**.&lt;BR /&gt;- Pages 871-872 describe the flash-memory map and flash-emulation mapping.&lt;/P&gt;&lt;P&gt;Could you please clarify:&lt;/P&gt;&lt;P&gt;1. Is `0x00100010` a valid/readable address for MPC5605?&lt;BR /&gt;2. If it is a reserved address, what happens when software reads it directly? Can it cause an exception or reset?&lt;BR /&gt;3. Which reference manual section should we use for the exact MPC5605 memory map?&lt;/P&gt;&lt;P&gt;We are also collecting the full MPC5605 part number and silicon revision from the ECU hardware.&lt;/P&gt;&lt;P&gt;Best regards,&lt;BR /&gt;kasirajan C&lt;/P&gt;</description>
      <pubDate>Fri, 11 Sep 2026 13:03:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCX-Microcontrollers/Subject-MPC5605-memory-read-issue-at-0x00100010/m-p/2413089#M5916</guid>
      <dc:creator>kasirajan</dc:creator>
      <dc:date>2026-09-11T13:03:04Z</dc:date>
    </item>
    <item>
      <title>Re: Subject: MPC5605 memory-read issue at 0x00100010</title>
      <link>https://community.nxp.com/t5/MCX-Microcontrollers/Subject-MPC5605-memory-read-issue-at-0x00100010/m-p/2413595#M5920</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Address 0x00100010 belongs to the range 0x00100000-0x001FFFFF, which is marked as Reserved in the MPC560xB memory map. Reserved regions must not be accessed by application software. Accessing such locations may generate a bus-related exception or other device-specific fault response, which can result in loss of communication or a reset if the exception is not handled.&lt;/P&gt;
&lt;P&gt;Chapter 3 &lt;BR /&gt;Memory Map&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="petervlna_0-1789455244473.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/396399iFDCEE160150325BA/image-size/medium?v=v2&amp;amp;px=400" role="button" title="petervlna_0-1789455244473.png" alt="petervlna_0-1789455244473.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Peter&lt;/P&gt;</description>
      <pubDate>Tue, 15 Sep 2026 06:55:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCX-Microcontrollers/Subject-MPC5605-memory-read-issue-at-0x00100010/m-p/2413595#M5920</guid>
      <dc:creator>petervlna</dc:creator>
      <dc:date>2026-09-15T06:55:10Z</dc:date>
    </item>
    <item>
      <title>Re: Subject: MPC5605 memory-read issue at 0x00100010</title>
      <link>https://community.nxp.com/t5/MCX-Microcontrollers/Subject-MPC5605-memory-read-issue-at-0x00100010/m-p/2414679#M5932</link>
      <description>&lt;P&gt;Thanks for your reply&lt;/P&gt;</description>
      <pubDate>Sat, 19 Sep 2026 06:02:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCX-Microcontrollers/Subject-MPC5605-memory-read-issue-at-0x00100010/m-p/2414679#M5932</guid>
      <dc:creator>kasirajan</dc:creator>
      <dc:date>2026-09-19T06:02:38Z</dc:date>
    </item>
  </channel>
</rss>

