S32G3 bootloader jump to M7 app failed, when resolving clock conflicts

superyyf — Tue, 21 Nov 2023 10:05:25 GMT

Dear NXP,

I'm trying to resolve time conflicts in multicore booting S32G399A_RDB3. According to the document "S32G_Supplemental_documentation_on_resolving_clock_conflicts_V1-2023.07.03.pdf", the Bootloader is responsible for most of clock configurations, and I've realized the Bootloader boot atf, but there is a problem when the bootloader boots the M7_0 app. While debugging the Bootloader, hardfault occured when executing the jump instruction as follows:

if I hit a breakpoint before the jump instruction and execute it in single step I can jump to the reset_handler function of the m7_app without any problem. This confused me.

version information:

1. Integration_Reference_Examples_S32G3_2023_02

2. SW32_RTD_4.4_4.0.0

3. EB tresos 27.1

I made the following modifications to the bootloader：

1. remove Mcu_init in SysDal Deinit List

2. change some clock config in Mcu module to keep the same clock config with atf

topic S32G3 bootloader jump to M7 app failed, when resolving clock conflicts in S32G

S32G3 bootloader jump to M7 app failed, when resolving clock conflicts