S32KのトピックRe: Bootloader in S32K358

Bootloader in S32K358

CaoRq — Wed, 24 Apr 2024 07:13:59 GMT

Hi, NXP

I am doing bootloader in s32k358, but now I face a problem

the boot software is using linker_flash_c0_s32k358.ld , if the app is using linker_flash_c0_s32k358.ld , boot can jump to app successfully , but if the app uses linker_flash_s32k358.ld, it can't jump successfully and enter hardfault.

Can you tell me the reason and how to solve it

Thank you in advance.

Re: Bootloader in S32K358

VaneB — Wed, 24 Apr 2024 18:40:52 GMT

Hi @CaoRq

In S32DS, when you create a project for multicore devices using RTDs, a project is created for each core with its own Linker file, except core 0, where two Linker files are created.

In each Linker file, you will find the default definition of the memory regions of the cores, each one is independent.

Concerning the Linker file that was additionally generated, it is not usually used and can be verified in the project properties. So for greater ease, I recommend not using it.

B.R.

VaneB

Re: Bootloader in S32K358

CaoRq — Thu, 25 Apr 2024 06:42:13 GMT

Hi VaneB

Thank you for reply

I am using core0 for booloader, so I use linker_flash_c0_s32k358.ld for bootloader. Although I am using core0 app now, I need to download core0 and core2 app in 1 hex in future, so I choose linker_flash_s32k358.ld for app, boot can't jump to app successfully and enter hard fault , when I choose linker_flash_c0_s32k358.ld for test , boot jump successfully. I think it means jump process has no problem.

linker_flash_c0_s32k358.ld in bootloader has no change, the ld file in app only choose it's start address like this:

Before jumping , I deinit the peripheral , disable the systick, disable interrupts,set MSP and PSP to the top of the stack ,set S32_SCB->VTOR = 0x20000000u and set control register to 0,then jump,it enter hard fault.

I have no idea to solve it and expect your reply.

Thank you in advance.