I am developing the bootloader of s32k312, I plan to use the official bootloader(developed based on RTD200), my APP is developed based on RTD300.
I found that the program can not jump from boot to app, I did a simple comparative test, and built two projects(zip file) s32k312_rtd200_uart and s32k312_rtd300_uart, their function is to use the serial port to send information, respectively "s32k312_rtd200_uart_app" and "s32k312_rtd300_uart_app", I directly modified the jump code of S32K312_CAN_bootloader_RTD2d0, specifying the jump to reset_handler (the two app projects are configured as the same reset_handler by .ld file)



it turns out:
S32K312_CAN_bootloader_RTD2d0->s32k312_rtd200_uart_app pass
S32K312_CAN_bootloader_RTD2d0->s32k312_rtd300_uart_app fail
The boot process of the chip should look different in RTD200 and RTD300 environments, how to fix this problem? Since some modules only support RTD300, such as FREERTOS, BMS_SDK, etc., it is not possible to downgrade an APP to RTD200
#S32K3