<?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>S32 Design StudioのトピックDebug probe + S32DS: not possible to flash QSPI B chip</title>
    <link>https://community.nxp.com/t5/S32-Design-Studio/Debug-probe-S32DS-not-possible-to-flash-QSPI-B-chip/m-p/1723903#M10991</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I set up S32DS with the NXP Debug Probe, but I work with a custom S32G2 based board which has primary QSPI wired to channel B instead of channel A.&lt;BR /&gt;First problem I encountered is that I couldn't flash the QSPI chip in "normal mode". By trial and erorr I found out, that I can only flash the chip in "serial boot" mode.&lt;BR /&gt;But even then, although S32DS shows the complete flashing process and I see the probe's Tx/Rx diode flashing, I verify that the chip hasn't be flashed.&lt;/P&gt;&lt;P&gt;By further investigation I found out the problem is that Debug Probe + S32DS setup is designed specifically for the NXP's development boards.&lt;BR /&gt;This IDE assumes the primary QSPI chip is always wired to QSPI channel A, while my board boots from the QSPI B.&lt;BR /&gt;In S32DS QSPI channel is unfortunately always fixed to QSPI A, which is confirmed by the debugger script s32g2xx_flash.py.&lt;BR /&gt;Fortunately I have Lauterbach setup which allows me to flash and debug the board, so I was able to get the flashing script configuration and adapt s32g2xx_flash.py for QSPI B flashing.&lt;/P&gt;&lt;P&gt;This way I can flash the board, but still only in "serial boot" mode. When flashing in "normal" mode I get the gdb error as attached (generated with unmodified&amp;nbsp;s32g2xx_flash.py)&lt;/P&gt;&lt;P&gt;I already reported this problem to my FAE Adrian Gancev and he submitted a ticket, but I cannot access it:&lt;BR /&gt;&lt;A href="https://community.nxp.com/t5/S32-Design-Studio/S32G-QSPI-flashing-failure-when-QSPI-boot-configured/m-p/1663564#M10275" target="_blank"&gt;https://community.nxp.com/t5/S32-Design-Studio/S32G-QSPI-flashing-failure-when-QSPI-boot-configured/m-p/1663564#M10275&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I'd like to know if this problem has already been solved and I can now update S32DS to work with QSPI B.&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;Michal Matyl&lt;/P&gt;</description>
    <pubDate>Fri, 15 Sep 2023 11:33:36 GMT</pubDate>
    <dc:creator>MichalMatyl</dc:creator>
    <dc:date>2023-09-15T11:33:36Z</dc:date>
    <item>
      <title>Debug probe + S32DS: not possible to flash QSPI B chip</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/Debug-probe-S32DS-not-possible-to-flash-QSPI-B-chip/m-p/1723903#M10991</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I set up S32DS with the NXP Debug Probe, but I work with a custom S32G2 based board which has primary QSPI wired to channel B instead of channel A.&lt;BR /&gt;First problem I encountered is that I couldn't flash the QSPI chip in "normal mode". By trial and erorr I found out, that I can only flash the chip in "serial boot" mode.&lt;BR /&gt;But even then, although S32DS shows the complete flashing process and I see the probe's Tx/Rx diode flashing, I verify that the chip hasn't be flashed.&lt;/P&gt;&lt;P&gt;By further investigation I found out the problem is that Debug Probe + S32DS setup is designed specifically for the NXP's development boards.&lt;BR /&gt;This IDE assumes the primary QSPI chip is always wired to QSPI channel A, while my board boots from the QSPI B.&lt;BR /&gt;In S32DS QSPI channel is unfortunately always fixed to QSPI A, which is confirmed by the debugger script s32g2xx_flash.py.&lt;BR /&gt;Fortunately I have Lauterbach setup which allows me to flash and debug the board, so I was able to get the flashing script configuration and adapt s32g2xx_flash.py for QSPI B flashing.&lt;/P&gt;&lt;P&gt;This way I can flash the board, but still only in "serial boot" mode. When flashing in "normal" mode I get the gdb error as attached (generated with unmodified&amp;nbsp;s32g2xx_flash.py)&lt;/P&gt;&lt;P&gt;I already reported this problem to my FAE Adrian Gancev and he submitted a ticket, but I cannot access it:&lt;BR /&gt;&lt;A href="https://community.nxp.com/t5/S32-Design-Studio/S32G-QSPI-flashing-failure-when-QSPI-boot-configured/m-p/1663564#M10275" target="_blank"&gt;https://community.nxp.com/t5/S32-Design-Studio/S32G-QSPI-flashing-failure-when-QSPI-boot-configured/m-p/1663564#M10275&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I'd like to know if this problem has already been solved and I can now update S32DS to work with QSPI B.&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;Michal Matyl&lt;/P&gt;</description>
      <pubDate>Fri, 15 Sep 2023 11:33:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/Debug-probe-S32DS-not-possible-to-flash-QSPI-B-chip/m-p/1723903#M10991</guid>
      <dc:creator>MichalMatyl</dc:creator>
      <dc:date>2023-09-15T11:33:36Z</dc:date>
    </item>
  </channel>
</rss>

