LinuxBSP33 getting ATF+uboot on S32G RDB2 board

[mmatsunaga]

Hello,

I'm following the instructions on S32G2_LinuxBSP_33.0_User_Manual.pdf.

I performed the following:

1) Building uboot:

git clone https://source.codeaurora.org/external/autobsps32/u-boot
cd u-boot
git checkout bsp33.0-2020.04

make CROSS_COMPILE=<toolchain_path>/bin/aarch64-none-linux-gnu- s32g274ardb2_defconfig

make CROSS_COMPILE=<toolchain_path>/bin/aarch64-none-linux-gnu-

2) Building ATF:

(tools for fiptool already installed on my Ubuntu)

git clone https://source.codeaurora.org/external/autobsps32/arm-trusted-firmware
cd arm-trusted-firmware
git checkout bsp33.0-2.5

make CROSS_COMPILE=<toolchain_path>/bin/aarch64-none-linux-gnu- ARCH=aarch64 BL33=<uboot_path>/u-boot-nodtb.bin ARCH=aarch64 PLAT=s32g274ardb2

3) Write fip.s32 to the SDCard:

sudo dd if=build/s32g274ardb2/release/fip.s32 of=/dev/sda skip=512 seek=512 iflag=skip_bytes oflag=seek_bytes conv=fsync,notrunc

4) When I boot the board with the SDCard I get nothing on the screen.

Note: I was only able to get ATF+uboot running with the BSP28, when I had the option: CONFIG_S32_ATF_BOOT_FLOW=y when building uboot.

From what I understand this option doesn't exist anymore starting on BSP32.

More info:

when ATF finish the build, it outputs:

Image Layout
DCD: Offset: 0x200 Size: 0x1c
IVT: Offset: 0x1000 Size: 0x100
AppBootCode Header: Offset: 0x1200 Size: 0x40
Application: Offset: 0x1240 Size: 0x2ea00

IVT Location: SD/eMMC
Load address: 0x342fc6a0
Entry point: 0x34302000

And my boot_info.c contains:

const unsigned long fip_mmc_offset = 0x1240;
const unsigned long fip_qspi_offset = 0;
const unsigned long fip_mem_offset = 0;
const unsigned int fip_hdr_size = 0x0;
const unsigned int dtb_size = 0x5960;

Am I missing something?

I appreciate any help on how to proceed.

Thanks

Marcio

[hamzahfrq]

Hi,

Were you able to boot the board with/without ATF? I am facing the same issue as yours..

Thanks and best regards

[Bio_TICFSL]

Hello mmatsunaga,

There is no plan to implement the same in U-Boot/ATF. You need to do the implementation per your use-case.

Regards

[mmatsunaga]

Hi,

About the option CONFIG_S32_ATF_BOOT_FLOW=y, you mentioned that it won't be implemented for BSP32 and later. Does it mean that ATF+uboot is not supported by NXP anymore?

At least from reading the User Manual I had the impression that ATF+uboot should still work on the board.

Appreciate any feedback on this.

Thanks,

[Bio_TICFSL]

Hello,

Sorry that is correct! it won't be implemented.it should be working but we have not tested the ATF in BSP 33.

Regards

[hamzahfrq]

Hi,

When either fsl-image-auto-s32g274ardb2.sdcard (full image) or fip.s32-sdcard (ATF+u-boot) is flashed on the sd card, the board comes up with ATF+u-boot. Could you please explain why you have said that ATF+u-boot is not tested on the board?

Best regards.

[mmatsunaga]

Hello,

And just so I understand better. When you said that it should be working, do you mean that ATF+uboot should be working 'out of the box' on BSP32 or do I need to perform some custom modifications in the lines of what the option CONFIG_S32_ATF_BOOT_FLOW=y was doing for BSP28?

Thanks!

[Bio_TICFSL]

Hi,

If you made some modification probably it will be need it again, but the ATF should be working on BSP32.

Regards

[mmatsunaga]

Hi,

Thanks for the answer.

So do you have any suggestion on how to debug or what to look for? considering after following all the steps from the NXP User Manual for ATF+uboot I don't get any output (blank screen) during boot?

Thanks,

[mmatsunaga]

Hello,

Thanks for the information, but I should still be able to get ATF+uboot running on the board right?

I get no output at all on the screen after following the steps from the User Manual.

Thanks,