Goldbox RDB3 S32G299 M7_0 not boot from EMMC.

[vsong]

I am following the steps in "S32G-VNP-GLDBOX3 SOFTWARE ENABLEMENT GUIDE" to 

Light Up RGB LED using S32 Real Time Drivers, from M7_0 core, boot from EMMC (a little modification instead of boot from SD card - I only have one SD card with Linux BSP.  I don't want to erase the SD card with my own binary file.  I would like to save the SD card as a recovery boot)

Code is compiled and should run, Tested with below 2 senario.

1. S32 debugger probe, and I see the RED LED lights on - again change the blue LED to red LED.

2. if I boot from SD card, then copy the "blinker.bin" from SD card(bin file is copied to SD card after compilation, before boot) to Sram at 0x3400 0000, and start_M7 at 0x3450 1000, I see the RED LED lights solid on as well. with below command after interrup the uboot: 

(note for this blinker.bin, I commented out  /*Clock_Ip_Init(Mcu_aClockConfigPB);*/ cause BSP should already init the clock)

dcach off

initsram 0x34000000 0x700000

fatload mmc 0:1 0x34000000 blinker.bin

startm7 0x34501000

__________________________________________________

Here is the issue:

If I use IVT tool to create IVT (only app_bootloader, no DCD, no other items) image, then export blob image with emmc/sd selection, I got a blob image with

0x1000 IVT table

0x1200 app_bootloader header

0x1240 blinker.bin 

Next, I choose switches:

SW 11 on - LED option on

SW 3 off - choose emmc

SW 4 only pin6/7 ON -  emmc boot

When I do flash tool, I choose: 

SW10 pin1/2 all off - serial boot

so I flash the blob.bin with emmc.bin algo into device.  after it successfully finished, I power off.

Then I choose

SW 10 pin1-on, Pn2-off for emmc boot.

power on again.

But I never see my red LED solid on.

Here is my blob binary file.

and my ram_start is at:

please help.

Thanks,

song

[vsong]

Thank you for the solution.  After I change the linker file, the RDB boot from eMMC card with Red LED solid on.  The solution works!

Still have some questions about the linker file.  The reason I didn't use the suggested linker file modification is in  "S32G-VNP-GLDBOX3 SOFTWARE ENABLEMENT GUIDE", the internal operation uses 0x3400 8000 to 3400 8200, ADMA starts 0x3400 0000 for 8k(0x0000 2000).

while in "S32G reference manual",  internal operations uses 0x3400 8000 to  0x3407 9C00, ADMA starts 0x3400 2000 for 4k (0x0000 1000)

I am not sure which one is correct.  So I choose not to change anything in the linker file.

Your solution definitely working, but now you give another internal operation address as 0x3400 8000 to 0x3407 8000, with ADMA at 0x343F F000 for 4k (0x0000 1000).

For above 3 reference, which one is correct?

Thanks,

[Daniel-Aguirre · Accepted solution]

Hi,

We understand that the problem is the following:

You are trying to boot with IVT + eMMC under the M7_0 core and cannot see it running, is this correct?

If so, we are seeing that you are not modifying the linker file as told under the "SW Enablement Guide" [Page 18, rev 2.1]:

Since you are booting through the uSDHC interface (it is shared between SD and eMMC) this is a restriction that the linker needs to comply with.

We modified our linker file and see it work no problem. Just as a note, since you are not initializing the Clock, the blink will be slower since the clocks are not being configured.

Please, let us know.