<?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: MPC560xB - Bad RAM initialization at startup in MPC5xxx</title>
    <link>https://community.nxp.com/t5/MPC5xxx/MPC560xB-Bad-RAM-initialization-at-startup/m-p/685293#M8369</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you can. Actually it can be either 32-bit or 64-bit write with this device.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Jul 2017 07:21:24 GMT</pubDate>
    <dc:creator>davidtosenovjan</dc:creator>
    <dc:date>2017-07-12T07:21:24Z</dc:date>
    <item>
      <title>MPC560xB - Bad RAM initialization at startup</title>
      <link>https://community.nxp.com/t5/MPC5xxx/MPC560xB-Bad-RAM-initialization-at-startup/m-p/685290#M8366</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in a previous post I ask why in the following startup code&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp; &amp;nbsp;/* SRAM initialization code*/&lt;BR /&gt;&amp;nbsp; &amp;nbsp;lis r11,L2SRAM_LOCATION@h&lt;BR /&gt;&amp;nbsp; &amp;nbsp;ori r11,r11,L2SRAM_LOCATION@l&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp; &amp;nbsp;/* Loops to cover L2SRAM, stmw allows 128 bytes (32 GPRS x 4 bytes) writes */&lt;BR /&gt;&amp;nbsp; &amp;nbsp;lis r12,L2SRAM_CNT@h&lt;BR /&gt;&amp;nbsp; &amp;nbsp;ori r12,r12,L2SRAM_CNT@l&lt;BR /&gt;&amp;nbsp; &amp;nbsp;mtctr r12&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp; &amp;nbsp;init_l2sram_loop:&lt;BR /&gt;&amp;nbsp; &amp;nbsp;stmw r0, 0(r11) /* Write 32 GPRs to SRAM*/&lt;BR /&gt;&lt;STRONG style="border: 0px; font-weight: bold;"&gt;&amp;nbsp; &amp;nbsp;addi r11,r11,128 /* Inc the ram ptr; 32 GPRs * 4 bytes = 128B */&lt;/STRONG&gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp;bdnz init_l2sram_loop /* Loop for 48k of SRAM */&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;SRAM data is not initialized to value 0x00 in all bytes and you answer me that&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;" There in no need to have ram initialized with 0x0000 0000 patern.&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp; And it is also not recommended to have all 0 in SRAM.&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp; Your RAM will be initialed with R0 to R31 GPRs in 128bytes loops. And the address on R11 will be incremented by 128B. "&lt;/P&gt;&lt;P style="color: #3d3d3d;"&gt;&lt;/P&gt;&lt;P style="color: #3d3d3d;"&gt;What is the reason to avoid SRAM initialization to pattern 0x0000 0000 ?&lt;/P&gt;&lt;P style="color: #3d3d3d;"&gt;&lt;/P&gt;&lt;P style="color: #3d3d3d;"&gt;Best regards,&lt;/P&gt;&lt;P style="color: #3d3d3d;"&gt;Romain&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Jul 2017 12:52:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/MPC560xB-Bad-RAM-initialization-at-startup/m-p/685290#M8366</guid>
      <dc:creator>romainbenet</dc:creator>
      <dc:date>2017-07-05T12:52:53Z</dc:date>
    </item>
    <item>
      <title>Re: MPC560xB - Bad RAM initialization at startup</title>
      <link>https://community.nxp.com/t5/MPC5xxx/MPC560xB-Bad-RAM-initialization-at-startup/m-p/685291#M8367</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The whole SRAM needs to be written by any value. Important is that it must be 64-bit write, to completely define ECC &lt;BR /&gt;code for data unit.&lt;BR /&gt;Users sometimes use special patterns having meaning of certain opcodes as 'nop' or branch to itself, but it is not necessary, it can be cleared.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pay attention to section 1.1 of AN5200:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/docs/DOC-103300"&gt;AN5200 - Error Correcting Codes Implemented on MPC55xx and MPC56xx&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jul 2017 06:29:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/MPC560xB-Bad-RAM-initialization-at-startup/m-p/685291#M8367</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2017-07-12T06:29:30Z</dc:date>
    </item>
    <item>
      <title>Re: MPC560xB - Bad RAM initialization at startup</title>
      <link>https://community.nxp.com/t5/MPC5xxx/MPC560xB-Bad-RAM-initialization-at-startup/m-p/685292#M8368</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I read your application note section 1.1 it says that " the whole SRAM is deleted or written by any value, however it must be either 64-bit write or 32-bit write" and when I read the table 2 which indicates which component is associated to 32 or 64 bits write my target (MPC5604B) as other MPC560xB uses the ECC 32+7.&lt;/P&gt;&lt;P&gt;So is it possible that I can initialize the SRAM by 32bits access with pattern 0x0000 0000 ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Romain&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jul 2017 07:17:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/MPC560xB-Bad-RAM-initialization-at-startup/m-p/685292#M8368</guid>
      <dc:creator>romainbenet</dc:creator>
      <dc:date>2017-07-12T07:17:17Z</dc:date>
    </item>
    <item>
      <title>Re: MPC560xB - Bad RAM initialization at startup</title>
      <link>https://community.nxp.com/t5/MPC5xxx/MPC560xB-Bad-RAM-initialization-at-startup/m-p/685293#M8369</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you can. Actually it can be either 32-bit or 64-bit write with this device.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jul 2017 07:21:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/MPC560xB-Bad-RAM-initialization-at-startup/m-p/685293#M8369</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2017-07-12T07:21:24Z</dc:date>
    </item>
    <item>
      <title>Re: MPC560xB - Bad RAM initialization at startup</title>
      <link>https://community.nxp.com/t5/MPC5xxx/MPC560xB-Bad-RAM-initialization-at-startup/m-p/685294#M8370</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for your help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Romain&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jul 2017 07:26:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/MPC560xB-Bad-RAM-initialization-at-startup/m-p/685294#M8370</guid>
      <dc:creator>romainbenet</dc:creator>
      <dc:date>2017-07-12T07:26:30Z</dc:date>
    </item>
  </channel>
</rss>

