<?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: RT117x: dual image boot order in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT117x-dual-image-boot-order/m-p/1769007#M27874</link>
    <description>&lt;P&gt;I have progressed in my knowhow. I modified my example a bit to test a theory I had.&lt;/P&gt;&lt;LI-CODE lang="c"&gt;        PRINTF("input 'y' to switch firmware to run!\r\n");
        PRINTF("input other char to stay in the current firmware!\r\n");
        ch = GETCHAR();
        PUTCHAR(ch);
        PRINTF("\r\n");
        for(uint32_t i=0;i&amp;lt;0x1000;i++);
        if(ch == 'y')
        {
          LPUART_Deinit(BOARD_DEBUG_UART_BASEADDR);
          if(firmware_index)
          {
            bl_firmware_switch(0);
          }
          else
          {
            bl_firmware_switch(1);
          }
        }
        else if(ch == '0' || ch == '1')
        {
        	int target = ch - '0';
        	PRINTF("forcing reboot from image %d\r\n", target);
        	for(uint32_t i=0;i&amp;lt;0x1000;i++);
        	LPUART_Deinit(BOARD_DEBUG_UART_BASEADDR);
        	bl_firmware_switch(target);
        }&lt;/LI-CODE&gt;&lt;P&gt;this example is inspired (or adapted) from &lt;A href="https://www.nxp.com/webapp/Download?colCode=AN12255SW" target="_self"&gt;AN12255&lt;/A&gt;'s example. The changes I made are that, in addition to 'y' (which starts the "other" image), you can press '0' or '1' to force the start of the images indicated by the character.&lt;/P&gt;&lt;P&gt;I wrote this FW in both slot 0 and 1. In slot 0 it has image version 2 (0xFFFD0002), while in slot 1 it has 1 (0xFFFE0001). So the one to start must always be slot 0.&lt;BR /&gt;&lt;BR /&gt;Effectively at reset slot 0 starts, and the "jumps" from one slot to another are consistent:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
1
forcing reboot from image 1

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
1
forcing reboot from image 1

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
0
forcing reboot from image 0

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
0
forcing reboot from image 0

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;if I swap the version numbers though (slot 1 &amp;lt;- 0xFFFE0001, slot 2 &amp;lt;- 0xFFFD0002), a strange thing happens. On reset slot 1 starts, as I expected, but it looks like the slot indexes are reversed:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
1
forcing reboot from image 1

************ Hello world! This is firmware index 1
welcome to run firmware 1!
y

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
0
forcing reboot from image 0

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
0
forcing reboot from image 0

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
1
forcing reboot from image 1

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
1
forcing reboot from image 1

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
0
forcing reboot from image 0

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
1
forcing reboot from image 1

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you explain this strange behavior? Or maybe you can point me to cove this feature/behavior is documented?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 05 Dec 2023 11:51:22 GMT</pubDate>
    <dc:creator>mastupristi</dc:creator>
    <dc:date>2023-12-05T11:51:22Z</dc:date>
    <item>
      <title>RT117x: dual image boot order</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT117x-dual-image-boot-order/m-p/1768307#M27855</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I am trying the "dual image" feature on RT117o EVK.&lt;BR /&gt;On Provisioning tool there is Image version field:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="imageVersion.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/252893iBD283DD1970BD25A/image-size/large?v=v2&amp;amp;px=999" role="button" title="imageVersion.png" alt="imageVersion.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;in the popup it says: "&lt;EM&gt;Image with the higher image version is booted first&lt;/EM&gt;".&lt;/P&gt;&lt;P&gt;This is openly at odds with flowcharts:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="flowchart.png" style="width: 904px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/252895iAC58AF458D6AC5B5/image-size/large?v=v2&amp;amp;px=999" role="button" title="flowchart.png" alt="flowchart.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;point me to the section in the Reference Manual or Security Reference Manual where this feature is detailed?&lt;/P&gt;&lt;P&gt;However, I also tried (see attached project):&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;both images have the same version&lt;/STRONG&gt;: I can jump from one to the other and it always starts image 0&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;image 0 has 0x0012FFED, image 1 has 0x0013FFEC&lt;/STRONG&gt;: both images can jump into the other, image 0 always starts&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;image 0 has 0x0013FFEC, image 1 has 0x0012FFED&lt;/STRONG&gt;: always starts image 1 and fails to jump to image 0.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="diff.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/252896iF64D047BAB29AD10/image-size/large?v=v2&amp;amp;px=999" role="button" title="diff.png" alt="diff.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Bottom line: is this feature really present on RT117x? And how is it used?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;</description>
      <pubDate>Mon, 04 Dec 2023 14:02:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT117x-dual-image-boot-order/m-p/1768307#M27855</guid>
      <dc:creator>mastupristi</dc:creator>
      <dc:date>2023-12-04T14:02:51Z</dc:date>
    </item>
    <item>
      <title>Re: RT117x: dual image boot order</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT117x-dual-image-boot-order/m-p/1769007#M27874</link>
      <description>&lt;P&gt;I have progressed in my knowhow. I modified my example a bit to test a theory I had.&lt;/P&gt;&lt;LI-CODE lang="c"&gt;        PRINTF("input 'y' to switch firmware to run!\r\n");
        PRINTF("input other char to stay in the current firmware!\r\n");
        ch = GETCHAR();
        PUTCHAR(ch);
        PRINTF("\r\n");
        for(uint32_t i=0;i&amp;lt;0x1000;i++);
        if(ch == 'y')
        {
          LPUART_Deinit(BOARD_DEBUG_UART_BASEADDR);
          if(firmware_index)
          {
            bl_firmware_switch(0);
          }
          else
          {
            bl_firmware_switch(1);
          }
        }
        else if(ch == '0' || ch == '1')
        {
        	int target = ch - '0';
        	PRINTF("forcing reboot from image %d\r\n", target);
        	for(uint32_t i=0;i&amp;lt;0x1000;i++);
        	LPUART_Deinit(BOARD_DEBUG_UART_BASEADDR);
        	bl_firmware_switch(target);
        }&lt;/LI-CODE&gt;&lt;P&gt;this example is inspired (or adapted) from &lt;A href="https://www.nxp.com/webapp/Download?colCode=AN12255SW" target="_self"&gt;AN12255&lt;/A&gt;'s example. The changes I made are that, in addition to 'y' (which starts the "other" image), you can press '0' or '1' to force the start of the images indicated by the character.&lt;/P&gt;&lt;P&gt;I wrote this FW in both slot 0 and 1. In slot 0 it has image version 2 (0xFFFD0002), while in slot 1 it has 1 (0xFFFE0001). So the one to start must always be slot 0.&lt;BR /&gt;&lt;BR /&gt;Effectively at reset slot 0 starts, and the "jumps" from one slot to another are consistent:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
1
forcing reboot from image 1

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
1
forcing reboot from image 1

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
0
forcing reboot from image 0

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
0
forcing reboot from image 0

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;if I swap the version numbers though (slot 1 &amp;lt;- 0xFFFE0001, slot 2 &amp;lt;- 0xFFFD0002), a strange thing happens. On reset slot 1 starts, as I expected, but it looks like the slot indexes are reversed:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
1
forcing reboot from image 1

************ Hello world! This is firmware index 1
welcome to run firmware 1!
y

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
y

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
0
forcing reboot from image 0

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
0
forcing reboot from image 0

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
1
forcing reboot from image 1

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
1
forcing reboot from image 1

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
0
forcing reboot from image 0

************ Hello world! This is firmware index 1
welcome to run firmware 1!
please input char for switching firmware, current count: 1
HADDRSTART  30000001
HADDREND    30200000
HADDROFFSET   200000
input 'y' to switch firmware to run!
input other char to stay in the current firmware!
1
forcing reboot from image 1

@@@@@@@@@@@@ Hello world! This is firmware image 0
Firmware 0 start to run!
please input char for switching firmware, current count: 1
HADDRSTART         0
HADDREND           0
HADDROFFSET        0
input 'y' to switch firmware to run!
input other char to stay in the current firmware!&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you explain this strange behavior? Or maybe you can point me to cove this feature/behavior is documented?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Dec 2023 11:51:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT117x-dual-image-boot-order/m-p/1769007#M27874</guid>
      <dc:creator>mastupristi</dc:creator>
      <dc:date>2023-12-05T11:51:22Z</dc:date>
    </item>
    <item>
      <title>Re: RT117x: dual image boot order</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT117x-dual-image-boot-order/m-p/1769223#M27879</link>
      <description>&lt;P class="lia-align-justify"&gt;Hello &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/124967"&gt;@mastupristi&lt;/a&gt;,&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;Could you please take a look at the &lt;A href="https://www.nxp.com/products/processors-and-microcontrollers/arm-microcontrollers/i-mx-rt-crossover-mcus/i-mx-rt1170-1-ghz-crossover-mcu-with-arm-cortex-cores:i.MX-RT1170#documentation" target="_self"&gt;i.MX RT1170 Processor Reference Manual&lt;/A&gt;. Section 10.13.3 Enter Bootloader API or &lt;A href="https://www.nxp.com/products/processors-and-microcontrollers/arm-microcontrollers/i-mx-rt-crossover-mcus/i-mx-rt1170-1-ghz-crossover-mcu-with-arm-cortex-cores:i.MX-RT1170#documentation" target="_self"&gt;Security Reference Manual for the i.MX RT1170 Processor&lt;/A&gt;. Section 2.13.3 Enter Bootloader API. There is the ARG definition table, which explains about the Boot image selection?&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;Warm regards, Raul.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Dec 2023 18:35:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT117x-dual-image-boot-order/m-p/1769223#M27879</guid>
      <dc:creator>RaRo</dc:creator>
      <dc:date>2023-12-05T18:35:53Z</dc:date>
    </item>
    <item>
      <title>Re: RT117x: dual image boot order</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT117x-dual-image-boot-order/m-p/1769563#M27890</link>
      <description>&lt;P&gt;I got the point (I had missed it on a first reading)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="expla.png" style="width: 855px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/253165iACB4F11C001FCA54/image-size/large?v=v2&amp;amp;px=999" role="button" title="expla.png" alt="expla.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Dec 2023 07:44:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/RT117x-dual-image-boot-order/m-p/1769563#M27890</guid>
      <dc:creator>mastupristi</dc:creator>
      <dc:date>2023-12-06T07:44:17Z</dc:date>
    </item>
  </channel>
</rss>

