https://community.nxp.com/t5/S32K/Can-the-BootLoader-based-on-RTD2-0-work-properly-with-the-APP/m-p/2261144#M55338 <P>Hello&nbsp;<a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/213974">@FrankLiu2019</a>&nbsp;,</P> <DIV> <DIV> <P>Any application built on RTD 2.0 is generally <STRONG>not compatible by default</STRONG> with an application built on RTD 6.0. It is up to the user to validate and adapt the integration, as there are no official NXP examples for mixing these versions.</P> <P>BootLoader using <STRONG>LLD</STRONG> and APP using <STRONG>MCAL</STRONG> might work if the BootLoader leaves the system in a clean state (interrupts off, clocks/watchdog handled) and the APP reinitializes its own drivers.</P> </DIV> </DIV> <P>Best regards,</P> <P>Pavel</P> Fri, 12 Dec 2025 11:03:02 GMT PavelL 2025-12-12T11:03:02Z https://community.nxp.com/t5/S32K/Can-the-BootLoader-based-on-RTD2-0-work-properly-with-the-APP/m-p/2260562#M55320 <P>The current version of the BootLoader I am using is based on RTD2.0 <A href="https://community.nxp.com/t5/S32K-Knowledge-Base/Unified-bootloader-Demo/ta-p/1423099" target="_self">Obtained from this link</A>&nbsp;, and it can function properly with the RTD2.0 APP. After I upgraded the APP to version RTD6.0, it crashed immediately after the upgrade.</P><P><STRONG>Can the BootLoader based on RTD2.0 work properly with the APP based on RTD6.0?</STRONG></P><P>There is another question, based on the same version. When the BootLoader uses <STRONG>LLD</STRONG> and the APP uses <STRONG>MCAL</STRONG>, will they be able to function properly?</P><P>These are two versions of the ld file and the memory data that has been read. The jump address from the BootLoader is 0x00441421.</P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="LD_compare.png" style="width: 999px;"><img src="https://community.nxp.com/t5/image/serverpage/image-id/369612iFDEC8A9BA26D9BDA/image-size/large?v=v2&amp;px=999" role="button" title="LD_compare.png" alt="LD_compare.png" /><span class="lia-inline-image-caption" onclick="event.preventDefault();">LD_compare.png</span></span><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="READ_FLASH.png" style="width: 641px;"><img src="https://community.nxp.com/t5/image/serverpage/image-id/369613iF9F49309C9E97D20/image-size/large?v=v2&amp;px=999" role="button" title="READ_FLASH.png" alt="READ_FLASH.png" /><span class="lia-inline-image-caption" onclick="event.preventDefault();">READ_FLASH.png</span></span></P> Fri, 12 Dec 2025 01:31:12 GMT https://community.nxp.com/t5/S32K/Can-the-BootLoader-based-on-RTD2-0-work-properly-with-the-APP/m-p/2260562#M55320 FrankLiu2019 2025-12-12T01:31:12Z https://community.nxp.com/t5/S32K/Can-the-BootLoader-based-on-RTD2-0-work-properly-with-the-APP/m-p/2261144#M55338 <P>Hello&nbsp;<a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/213974">@FrankLiu2019</a>&nbsp;,</P> <DIV> <DIV> <P>Any application built on RTD 2.0 is generally <STRONG>not compatible by default</STRONG> with an application built on RTD 6.0. It is up to the user to validate and adapt the integration, as there are no official NXP examples for mixing these versions.</P> <P>BootLoader using <STRONG>LLD</STRONG> and APP using <STRONG>MCAL</STRONG> might work if the BootLoader leaves the system in a clean state (interrupts off, clocks/watchdog handled) and the APP reinitializes its own drivers.</P> </DIV> </DIV> <P>Best regards,</P> <P>Pavel</P> Fri, 12 Dec 2025 11:03:02 GMT https://community.nxp.com/t5/S32K/Can-the-BootLoader-based-on-RTD2-0-work-properly-with-the-APP/m-p/2261144#M55338 PavelL 2025-12-12T11:03:02Z