S32 Customer Bootloader

NP1 — Tue, 04 Oct 2022 05:40:39 GMT

Anyone can explain the booting process ?

Can anyone look into below statement and correct if my understanding is wrong ?

Initially we need to select the Boot Mode using RCON or Fuse Configuration .

It will decide the location of IVT from where the Boot Manager is to be loaded.

If it's QSPI Load(Loading from NORFLASH) we need to place IVT at 0th Address, If it's any MMC device it should be at offset 0x1000.

The BootROM is the first sw that run after any reset.

It is placed in Internal ROM and is executed by M7 Core.

BootROM will load the IVT to SRAM (I need clarification of this) also since it contain location of the Bootmanager(BM) for M7 Core it will load that BM to SARM and run it from SRAM.

This BM will help in the peripheral /clock initializations. Later BM of M7 will help to Copy the BM of A53 from NORFlash or EMMC devices to SRAM and run from SRAM.

Later this will help to Copy the Customer Application or Linux to SRAM or DDR and will pass control to the Application .

Then Application began execution . After a Power ON Reset , the control directly comes to application only.

Please correct me if I'm wrong regarding the about flow.

NXP documents wasn't giving me a clear picture regarding the same .

(mainly regarding

> where the IVT will be copied by BootROM ? without peripheral init. how the copy of the to external memory take place (since SRAM is external for S32G2) ?

> Will BootManager for M7 will copy to SRAM by BootROM only ?

>Will peripheral init. clock init take place with the help of BM only?

> After Power on reset where the control will go if the program is currently running in application ? Should it follow the boot process again ? )

Re: S32 Customer Bootloader

Bio_TICFSL — Tue, 04 Oct 2022 13:48:08 GMT

Hello NP1,

Typically for a S32G virgin device, the device must be setup to Serial Boot mode.
Key steps for booting up the device:
1. Ensure power supply on the board
2. Ensure correct BMODE settings (set to Serial boot if setting A or D as explained below, follow Table 1)
3. Lauterbach (LTB) and T32 support for S32G
4. Steps in case BootROM is kept in serial mode and direct application is required to be run on CM7_0:
a. T32 Script to attach to S32G CM7_0
b. Small application (constraint – SRAM size of 8M)
c. T32 Script to configure and enable the CM7_0
5. Steps if Serial boot required:
a. Application binary to download (Constraint – SRAM size of 8K)
b. Tool to transfer binary on Serial (UART/CAN/ETHERNET) port
c. Hardware bus connection for the serial interface to S32GEVB
6. Steps if required boot from QSPI:
a. Configure BMODE to ‘10’
b. Scripts to program QSPI flash
7. Steps if required boot from SD/MMC:
a. Configure BMODE to ‘10’
b. Scripts/Tools to program SD/MMC

And boot!!!

Regards

topic S32 Customer Bootloader in S32G

S32 Customer Bootloader

Re: S32 Customer Bootloader