<?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 startM7 command not working when trying to boot M7 from u-boot from .sdcard of bsp33 and any other v in S32G</title>
    <link>https://community.nxp.com/t5/S32G/startM7-command-not-working-when-trying-to-boot-M7-from-u-boot/m-p/1902478#M7641</link>
    <description>&lt;P&gt;yes, tried this bootM7 command but i didn't see that led glow, may I know mistake where I did?&lt;/P&gt;&lt;P&gt;these are the steps I followed till now&lt;/P&gt;&lt;P&gt;1)I built .bin file by following software enablement guide for blinking led. after doing configuration in IVT table I got two binaries a) Export image b) Export blob image&lt;/P&gt;&lt;P&gt;2)when I insert only "export blob image" by SD. LED turned ON. Only M7 core_0. Looks GOOD.&lt;/P&gt;&lt;P&gt;3)now I took Linux BSP 33&amp;nbsp; &amp;nbsp;.sdcard file and ported into new empty SD card.&amp;nbsp; kept this export blob Image of blinking LED. Bin in FAT partition of BSP33 SD card.&lt;/P&gt;&lt;P&gt;4)I used these commands to boot both A53 with Linux and M7 with blinking led.&lt;/P&gt;&lt;P&gt;RAM start pointer is :0x34000000&lt;/P&gt;&lt;P&gt;RAM entry pointer is:0x34207000&lt;/P&gt;&lt;P&gt;5)Is there any problem with address values in u-boot commands when compared with above values? why LED is not glowing?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;""""&lt;/P&gt;&lt;P&gt;setenv xw_file Blinking_LED_RTD_M7_0.bin&lt;BR /&gt;setenv xw_load_addr 0x80000000&lt;BR /&gt;setenv xw_sram_address_m7_0 0x34000000&lt;BR /&gt;setenv xw_file_size 0x40000&lt;BR /&gt;setenv xw_load_firmware 'dcache off'; mw.q ${xw_sram_address} 0x0 0x100000;fatlo&lt;/P&gt;&lt;P&gt;ad mmc 0:1 ${xw_load_addr} ${xw_file};cp.q ${xw_load_addr} ${xw_sram_address_m7_0} ${xw_file_size};startm7 ${xw_start_addr}'&lt;BR /&gt;setenv xw_sram_address 0x34000000&lt;BR /&gt;setenv xw_start_addr 0x34501000&lt;BR /&gt;saveenv&lt;BR /&gt;startm7 xw_load_firmware&amp;nbsp;&lt;/P&gt;&lt;P&gt;boot&lt;/P&gt;</description>
    <pubDate>Mon, 08 Jul 2024 15:24:33 GMT</pubDate>
    <dc:creator>Lee0202</dc:creator>
    <dc:date>2024-07-08T15:24:33Z</dc:date>
    <item>
      <title>startM7 command not working when trying to boot M7 from u-boot from .sdcard of bsp33 and any other v</title>
      <link>https://community.nxp.com/t5/S32G/startM7-command-not-working-when-trying-to-boot-M7-from-u-boot/m-p/1902478#M7641</link>
      <description>&lt;P&gt;yes, tried this bootM7 command but i didn't see that led glow, may I know mistake where I did?&lt;/P&gt;&lt;P&gt;these are the steps I followed till now&lt;/P&gt;&lt;P&gt;1)I built .bin file by following software enablement guide for blinking led. after doing configuration in IVT table I got two binaries a) Export image b) Export blob image&lt;/P&gt;&lt;P&gt;2)when I insert only "export blob image" by SD. LED turned ON. Only M7 core_0. Looks GOOD.&lt;/P&gt;&lt;P&gt;3)now I took Linux BSP 33&amp;nbsp; &amp;nbsp;.sdcard file and ported into new empty SD card.&amp;nbsp; kept this export blob Image of blinking LED. Bin in FAT partition of BSP33 SD card.&lt;/P&gt;&lt;P&gt;4)I used these commands to boot both A53 with Linux and M7 with blinking led.&lt;/P&gt;&lt;P&gt;RAM start pointer is :0x34000000&lt;/P&gt;&lt;P&gt;RAM entry pointer is:0x34207000&lt;/P&gt;&lt;P&gt;5)Is there any problem with address values in u-boot commands when compared with above values? why LED is not glowing?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;""""&lt;/P&gt;&lt;P&gt;setenv xw_file Blinking_LED_RTD_M7_0.bin&lt;BR /&gt;setenv xw_load_addr 0x80000000&lt;BR /&gt;setenv xw_sram_address_m7_0 0x34000000&lt;BR /&gt;setenv xw_file_size 0x40000&lt;BR /&gt;setenv xw_load_firmware 'dcache off'; mw.q ${xw_sram_address} 0x0 0x100000;fatlo&lt;/P&gt;&lt;P&gt;ad mmc 0:1 ${xw_load_addr} ${xw_file};cp.q ${xw_load_addr} ${xw_sram_address_m7_0} ${xw_file_size};startm7 ${xw_start_addr}'&lt;BR /&gt;setenv xw_sram_address 0x34000000&lt;BR /&gt;setenv xw_start_addr 0x34501000&lt;BR /&gt;saveenv&lt;BR /&gt;startm7 xw_load_firmware&amp;nbsp;&lt;/P&gt;&lt;P&gt;boot&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jul 2024 15:24:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/startM7-command-not-working-when-trying-to-boot-M7-from-u-boot/m-p/1902478#M7641</guid>
      <dc:creator>Lee0202</dc:creator>
      <dc:date>2024-07-08T15:24:33Z</dc:date>
    </item>
    <item>
      <title>Re: startM7 command not working when trying to boot M7 from u-boot from .sdcard of bsp33 and any oth</title>
      <link>https://community.nxp.com/t5/S32G/startM7-command-not-working-when-trying-to-boot-M7-from-u-boot/m-p/1905263#M8331</link>
      <description>&lt;P&gt;Hi, &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/235531"&gt;@Lee0202&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for the question&lt;/P&gt;
&lt;P&gt;From the description, I have the following suggestions:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;In your step 3, use the raw binary instead of the blob image.&lt;/LI&gt;
&lt;LI&gt;since you want to use the startm7 to boot the M core application, from BSP perspective, the clock has been initialized, as a result, you may have to remove the clock init related callings from your own M core code.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Hope it helps&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards&lt;/P&gt;
&lt;P&gt;Chenyin&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jul 2024 11:16:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/startM7-command-not-working-when-trying-to-boot-M7-from-u-boot/m-p/1905263#M8331</guid>
      <dc:creator>chenyin_h</dc:creator>
      <dc:date>2024-07-10T11:16:07Z</dc:date>
    </item>
    <item>
      <title>Re: startM7 command not working when trying to boot M7 from u-boot from .sdcard of bsp33 and any oth</title>
      <link>https://community.nxp.com/t5/S32G/startM7-command-not-working-when-trying-to-boot-M7-from-u-boot/m-p/1980553#M11411</link>
      <description>&lt;P&gt;How is the start address derived (e.g. Where does&amp;nbsp;&lt;SPAN&gt;0x34501000 come from)? Thanks!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2024 23:26:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/startM7-command-not-working-when-trying-to-boot-M7-from-u-boot/m-p/1980553#M11411</guid>
      <dc:creator>swhite39</dc:creator>
      <dc:date>2024-10-23T23:26:33Z</dc:date>
    </item>
    <item>
      <title>Re: startM7 command not working when trying to boot M7 from u-boot from .sdcard of bsp33 and any oth</title>
      <link>https://community.nxp.com/t5/S32G/startM7-command-not-working-when-trying-to-boot-M7-from-u-boot/m-p/1980563#M11412</link>
      <description>&lt;P&gt;Answered this by checking the link map in the S32DS and using the intc_vector address.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2024 00:09:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/startM7-command-not-working-when-trying-to-boot-M7-from-u-boot/m-p/1980563#M11412</guid>
      <dc:creator>swhite39</dc:creator>
      <dc:date>2024-10-24T00:09:18Z</dc:date>
    </item>
  </channel>
</rss>

