S32G2 BSP44 Memory map

[cf-technica]

Hi all, 

We're currently working with S32G2 BSP44 including ATF version 2.10.

Although, looking at ATF makefiles, BL2 reserved RAM memory starts at 0x34302000, for developing constraints we must set it from 0x34700000 and end it at 0x347f0000. But, when using this memory range, BL2 does just don't boot. 

We've been trying different BL2_BASE address and we've detected that, when BL2_BASE = 0x34709000 is set, then the system boots (but, unfortunately, due to our memory map we cannot extend it till 0x347f9000). 

Is there any reserved memory region that can not be mapped until 0x34709000 that explains this lack of boot?

Also, in order to fit our BL2 image from 0x34709000 to 0x347f9000, we've tried to reduce S32_IO_BUFFER_SIZE in order to fit our memory map, but, if it's modified from 0x013000 to a smaller value, then u-boot fails when booting. Is there a minimal size for S32_IO_BUFFER_SIZE?

Thanks in advance,

[chenyin_h]

Hello, @cf-technica 

Thanks for your post.

I will try reproducing the issue and then investigate on it.

1. May I know if you are working on a RDB2 or custom board?

2. SD/eMMC or QSPI boot is used during the test?

BR

Chenyin

[cf-technica]

Hi Chenyin

Thanks for your fast reply. Is currently a custom board.

In order to test it, we've changed BL2_BASE variable in bl2 Makefile. It only boots if 0x34709000 or higher (for example 0x3470A000) is set, but not for lower values like 0x34700000 or 0x34701000.

Also, we're working on an eMMC boot environment.

[chenyin_h]

Hello, @cf-technica 

Thanks for your confirmation.

I understand your memory constrains is 0x34700000 to 0x347f0000, but usually the BL2 part is not that large, so your custom constrains is for the whole TFA?(including fip part?)

BR

Chenyin

[cf-technica]

Hi,

Currently BL1 is executed on ROM, while u-boot runs over DDR. So BL2 is the only one that should be executing in that memory range. The strange thing is: why if we boot from 0x34700000 BL2 does not boot, but if we configure BL2_BASE to 0x3470A000 it boots ok?

About the size, I think the problem relies on the 0x13000 value for de S32_IO_BUFFER. If we boot from BL2 from 0x3470A000 and reduce S32_IO_BUFFER to fit 0x347f0000 as the end fro BL2 , then the next step (BL31 or u-boot I do not know) fails to boot and only show the register stack value as an error.

[chenyin_h]

Hello, @cf-technica 

Thanks for your confirmation.

I have some tests on my local RDB2 with BSP44 code base, but do not reproduce the issue you mentioned.

My test is with the following modification: BL2_BASE=0x34700000 BOOTROM_ADMA_RSRVD_BASE=0x347EF000, would you mind testing it again on your  board?

BR

Chenyin