<?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: Does anyone have the flash programmer .xml files for S25FS128S QSPI part? in CodeWarrior for QorIQ</title>
    <link>https://community.nxp.com/t5/CodeWarrior-for-QorIQ/Does-anyone-have-the-flash-programmer-xml-files-for-S25FS128S/m-p/815488#M6645</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;A _jive_internal="true" data-content-finding="Community" data-userid="316926" data-username="timhammer" href="https://community.nxp.com/people/timhammer"&gt;Tim Hammer,&lt;/A&gt; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;The flash algorithm runs in OCRAM, the parameter --waddress and --wsize are specified as OCRAM start address and OCRAM size. This setting can avoid the trouble for configuring DDR controller during custom boards bringing up. The parameter --geometry specifies QSPI works in 8 bit mode.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;In addition, please refer to the file CW4NET_v2018.01\CW_ARMv8\Config\flash\algorithms\params\S25FS256S_QSPI_64.xml to create the parameters configuration for S25FS128S according to the datasheet, which will be imported in CW4NET_v2018.01\CW_ARMv8\Config\flash\algorithms\S25FS256S.xml.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 27 Aug 2018 04:04:51 GMT</pubDate>
    <dc:creator>yipingwang</dc:creator>
    <dc:date>2018-08-27T04:04:51Z</dc:date>
    <item>
      <title>Does anyone have the flash programmer .xml files for S25FS128S QSPI part?</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-QorIQ/Does-anyone-have-the-flash-programmer-xml-files-for-S25FS128S/m-p/815486#M6643</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am about to work on them, so figured I would ask.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My CW4NET_v2018.01/CW_ARMv8/Config/flash/ directories have files for S25FS&lt;EM&gt;256&lt;/EM&gt;S,&amp;nbsp;&lt;SPAN&gt;S25FS&lt;EM&gt;512&lt;/EM&gt;S, and&amp;nbsp;S25F&lt;EM&gt;L&lt;/EM&gt;128S.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Maybe I am the first to use the S25FS128S?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;.Tim&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Aug 2018 14:18:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-QorIQ/Does-anyone-have-the-flash-programmer-xml-files-for-S25FS128S/m-p/815486#M6643</guid>
      <dc:creator>timhammer</dc:creator>
      <dc:date>2018-08-23T14:18:31Z</dc:date>
    </item>
    <item>
      <title>Re: Does anyone have the flash programmer .xml files for S25FS128S QSPI part?</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-QorIQ/Does-anyone-have-the-flash-programmer-xml-files-for-S25FS128S/m-p/815487#M6644</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After a quick review of data sheets, I could not find any difference between the S25FS256S and S25FS128S, so I just switched to that configuration and it seems to be working.&lt;/P&gt;&lt;P&gt;However, I am interested in the rest of the parameters to fl_device and have not found any information on them. The LS1012A_FRDM_init.py sets up the flash device with:&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;gdb.execute("fl_device --alias qspi --name S25FS512S --address 0x40000000 --waddress 0x10000000 --wsize 0x1FFFF --geometry 8x1 --controller QSPI")&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I simply changed the name to S25FS256S and the programming seemed to succeed (better than with the 512 version anyway!). I am pretty confident that the address parameter is correct (address where QSPI is mapped). But I&amp;nbsp;am not 100% sure I understand waddress and wsize refer to- the address and size seem to match the OCRAM, so I am guessing that the rest of the flash code uses that as the write area?&lt;/P&gt;&lt;P&gt;Also, I did not find anything in the datasheets for the S25FS...S parts that state the geometry of the chip. Does anyone know where this value came from and how I can verifiy it is correct for my part change?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;.Tim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Aug 2018 16:13:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-QorIQ/Does-anyone-have-the-flash-programmer-xml-files-for-S25FS128S/m-p/815487#M6644</guid>
      <dc:creator>timhammer</dc:creator>
      <dc:date>2018-08-23T16:13:23Z</dc:date>
    </item>
    <item>
      <title>Re: Does anyone have the flash programmer .xml files for S25FS128S QSPI part?</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-QorIQ/Does-anyone-have-the-flash-programmer-xml-files-for-S25FS128S/m-p/815488#M6645</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;A _jive_internal="true" data-content-finding="Community" data-userid="316926" data-username="timhammer" href="https://community.nxp.com/people/timhammer"&gt;Tim Hammer,&lt;/A&gt; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;The flash algorithm runs in OCRAM, the parameter --waddress and --wsize are specified as OCRAM start address and OCRAM size. This setting can avoid the trouble for configuring DDR controller during custom boards bringing up. The parameter --geometry specifies QSPI works in 8 bit mode.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;In addition, please refer to the file CW4NET_v2018.01\CW_ARMv8\Config\flash\algorithms\params\S25FS256S_QSPI_64.xml to create the parameters configuration for S25FS128S according to the datasheet, which will be imported in CW4NET_v2018.01\CW_ARMv8\Config\flash\algorithms\S25FS256S.xml.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Aug 2018 04:04:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-QorIQ/Does-anyone-have-the-flash-programmer-xml-files-for-S25FS128S/m-p/815488#M6645</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2018-08-27T04:04:51Z</dc:date>
    </item>
  </channel>
</rss>

