<?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>LayerscapeのトピックLS1046A Hard Coded RCW fail to change</title>
    <link>https://community.nxp.com/t5/Layerscape/LS1046A-Hard-Coded-RCW-fail-to-change/m-p/2045696#M15413</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;we have a custom designed board based on LS1046A and the LS1046ARDB as reference design. The custom board is "bare metal", nothing programmed on it. So we set the boot source word as 0x9F and tried to override the Hard coded RCW with the new settings in order to be able to access the QSPI flash for further programming.&amp;nbsp; The RCW override procedure works on the LS1046ARDB board but does not on the custom board, i.e. the RCW words keep the hardcoded values and they are not overridden with the new ones. Does anyone know if there is any signal or clock that must be present that we might have forgotten in our board and that allows this override procedure?&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
    <pubDate>Mon, 17 Feb 2025 17:42:49 GMT</pubDate>
    <dc:creator>DaT63</dc:creator>
    <dc:date>2025-02-17T17:42:49Z</dc:date>
    <item>
      <title>LS1046A Hard Coded RCW fail to change</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046A-Hard-Coded-RCW-fail-to-change/m-p/2045696#M15413</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;we have a custom designed board based on LS1046A and the LS1046ARDB as reference design. The custom board is "bare metal", nothing programmed on it. So we set the boot source word as 0x9F and tried to override the Hard coded RCW with the new settings in order to be able to access the QSPI flash for further programming.&amp;nbsp; The RCW override procedure works on the LS1046ARDB board but does not on the custom board, i.e. the RCW words keep the hardcoded values and they are not overridden with the new ones. Does anyone know if there is any signal or clock that must be present that we might have forgotten in our board and that allows this override procedure?&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Mon, 17 Feb 2025 17:42:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046A-Hard-Coded-RCW-fail-to-change/m-p/2045696#M15413</guid>
      <dc:creator>DaT63</dc:creator>
      <dc:date>2025-02-17T17:42:49Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046A Hard Coded RCW fail to change</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046A-Hard-Coded-RCW-fail-to-change/m-p/2050635#M15436</link>
      <description>&lt;P&gt;In CodeWarrior Target Initialization File, please configure "USE_SAFE_RCW = True", then pay attention to the following content.&lt;/P&gt;
&lt;P&gt;if USE_SAFE_RCW:&lt;BR /&gt;# Please make sure SERDES REF CLK is set to 100 MHz (SW4[1:2] = 00)&lt;BR /&gt;# Set rcw_src to the hard-coded RCW option matching the board's DIP SW&lt;BR /&gt;# regarding SYSCLK and differential/single-ended clock source&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;# use this when SYSCLK = 66 MHz, single-ended clock source&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;# TA.rcw.set_source(0x9A)&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;# use this when SYSCLK = 66 MHz, differential clock source&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;# TA.rcw.set_source(0x9B)&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;# use this when SYSCLK = 100 MHz, single-ended clock source&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;# TA.rcw.set_source(0x9E)&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;# use this when SYSCLK = 100 MHz, differential clock source&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;TA.rcw.set_source(0x9F)&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;# Activate QSPI lines&lt;BR /&gt;TA.rcw.set_data({13: 0x20124000})&lt;/P&gt;
&lt;P&gt;# add here if you need to override other particular RCW values&lt;BR /&gt;# TA.rcw.set_data({1: 0x40282830, 9: 0x00C12980, 10: 0x00002580})&lt;BR /&gt;TA.rcw.apply()&lt;/P&gt;
&lt;P&gt;If your problem persists, please capture CCS console log to me to do more investigation.&lt;/P&gt;
&lt;P&gt;When you clicking flash programming icon in CodeWarrior IDE,&amp;nbsp;the CCS console will pop up in the Windows task bar, please open it type "log v", then click flash programming icon again, the low level CCS log will be printed, please capture it to me.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Feb 2025 08:41:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046A-Hard-Coded-RCW-fail-to-change/m-p/2050635#M15436</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2025-02-25T08:41:06Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046A Hard Coded RCW fail to change</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046A-Hard-Coded-RCW-fail-to-change/m-p/2054204#M15460</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am not using&amp;nbsp; the LS1046ARDB, it is a custom board, so no dip switches to set the boot source; in any case I already said that the HRCW was set to 0x9F. I am also not using CodeWarrior but another JTAG debugger, hence I cannot follow your suggestions. I managed to find the solution to the problem: it was a missing resistor on the board.&lt;/P&gt;&lt;P&gt;Thank you anyway&lt;/P&gt;</description>
      <pubDate>Sun, 02 Mar 2025 16:54:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046A-Hard-Coded-RCW-fail-to-change/m-p/2054204#M15460</guid>
      <dc:creator>DaT63</dc:creator>
      <dc:date>2025-03-02T16:54:51Z</dc:date>
    </item>
  </channel>
</rss>

