2331458_en-US

Yes

S32E288 secondary core flash image

Hello,

I am trying to create a bootable flash image for the S32E288-975EVB and have created several related posts about it:

I have managed to bring up the SMU core from flash with my custom BLOB and I believe I have also managed to comprehend the start sequence of secondary cores, but I am now missing a bootable flash image. I have managed to create a raw binary image by following this guide. I have also consulted AI about the topic and it is very confident in saying that even if I have the binary, that I can flash to my QSPI_flash, then I would still need a special procedure in my SMU boot core for copying it from flash to R52 bootable RAM to make sure that each section gets correctly copied to it's designated DRAM or CRAM section.

Can anyone please confirm, whether I can just "dumb copy" my entire R52_0_0 binary flash image to RAM and boot the R52 core just setting the correct entry point OR do I need to create another procedure for copying each section to it's designated RAM address as defined by the linker and/or the map file?

Re: S32E288 secondary core flash image

Hey @chenyin_h

Thanks for the initial clarification, but I think I would require a bit more specific information.

To answer your question:
Yes, the current boot sequence is:
1. I create a bootable BLOB with the S32 Design Studio IVT tool, where I use my SMU M33 project binary as the application binary.
2. The goal: The SMU core should then bring up the R52 cores (I'm testing with a single R52_0_0). I believe I have the boot sequence set up, but with no way to test, since I don't have the R52 application binary in RAM.

Could you clarify on this "it will move the secondary image from your flash to each RAM location". Who do you refer by "it", the bootROM or the SMU boot core?

Additionally, could you also describe the process of copying the code from flash to RAM, which registers should definitely be configured and which could pose problems with access errors or whatnot?

Re: S32E288 secondary core flash image

Thanks for your post.

May I know if the boot sequence is SMU--> RTU0_C0?

If yes, typically you may flash both images for SMU and RTU0_C0 to the flash, and the first image is load by the bootROM, while running your SMU application, it will move the secondary image from your flash to each RAM location, according to different RAM sections definition from the settings.

BR

Chenyin

Re: S32E288 secondary core flash image

Hello, @HiddenSquid

Thanks for your reply.

1. It here means the SMU application.

2. It is a software defined process, the SMU application would copy data as defined in different memory sections to each part, to be simple, if the RTU0 application is targeted running on 7M SRAM, then the corresponding data should be copied from Flash to the SRAM by SMU application.

I suggest directly referring to GreenVIP 1.3.1 for details, which is actually booting from SMU and then loaded images for cores in RTU0 and RTU1.

BR
Chenyin