S32K344 BOOT to APP MATLAB generated project in Design Studio

[AJLFD]

Hello all,

I have a S32K344 bootloader application running on a custom board that I've used to jump to applications that were generated in design studio with no prior issues. I now have a MATLAB generated application that I've been trying to jump to but with no success as it keeps hitting the application's hard fault handler or the debugger crashes (J-Trace). 

Boot Flash Start: 0x00400000

App Flash Start: 0x00600000

App VTABLE: 0x0060800

App Jump: 0x00600804

*** This is how I've been jumping that has worked for me and that has appeared on other forums ***

typedef void(*voidFunPtr)(void);

void AppJump(void){

uint32_t pAppJump = (voidFunPtr)(*(uint32_t *) 0x00600804);

S32_SysTick->CSRr = 0;

S32_SCB->VTOR = (uint32_t)0x00600800;

( pAppJump )();

}

Actions I've done:

- Checked the map file generated from the application for the correct jump location, I've confirmed this through the disassembly

- Relocated the vector table to the application's table before the jump ( S32_SCB->VTOR )

- Disabled FreeRTOS and peripheral interrupts before the jump

- DeInit all active peripherals

- Disabled the Systick

- Configured the stack pointer

Are there any configurations going on with the MATLAB generated projects that I have to change? Is there some reinitialization I must do? I've searched through forum posts with boot troubles and tried their solutions but nothing has worked yet. I can jump to the application's startup_cm7.s code but I believe the fault occurs here at some point.

[rathi_tg]

Hi @lukaszadrapa  

I want to jump from application code to Boot code using matlab code. I have used custom code as follows 

if(userSP == 0xFFFFFFFF){

return;

}

/* Set up stack pointer */

__asm("msr msp, r0");

__asm("msr psp, r0");

/* Relocate vector table */

S32_SCB->VTOR = (uint32_t)BOOT_START_ADDRESS;

/* Jump to BootPC (r1) */

__asm("mov pc, r1");

But when i try to build the application i am facing issues with assemble commands. The Boot Address is 0x000000.

Regards 

Gopal

[lukaszadrapa]

Hi @AJLFD 

I'm not aware of specific difference in MATLAB project but I guess that something more needs to be deinitialized. That's the most common problem. If I'm not able to find it, I use following approach: reset the device by debugger and dump the peripheral registers to a file(s). Run the bootloader until you reach jump instruction. Now dump the registers again, compare the files and analyze the differences. Don't forget to check also core registers, especially MPU and NVIC - I would start with this.

Regards,

Lukas

[AJLFD]

There may also be a problem with FreeRTOS. In some attempts using xCreateTask() will also set the hard fault handler or crash the debugger after it has made the jump. Some variables for the pxTaskCode, pcName, pxStack are replaced with 0xA5A5A5A5.