Flex-builder Not Creating SDBoot composite firmware images

[tmorrison]

Hi,

When I try to build a non-secure version of the composite image for a LS1043ardb

  flexbuilder -i mkfw -b sd -m ls1043ardb -a arm64' 

It builds the "ATF version" (secure version), but it then says:

  "uboot sdboot on ls1043ardb is not supported"

?

[yipingwang]

Hello Thomas Morrison,

Which version SDK are you using?

I execute the following command in LSDK 19.09, I didn't encounter any problem.

$ flex-builder -i mkfw -b sd -m ls1043ardb -a arm64

Would you please attach your whole console log to me to do more investigation?

Thanks,

Yiping

[tmorrison]

Attached is the build for LSDK 19.09. This shows it building the tfa build (bl2/bl3..etc).

Here are the last few lines of this:

    Build ATF for ls1043ardb sdboot in /home/tom/lsdk/build/firmware/atf/ls1043ardb  [Done]
    make[1]: Leaving directory '/home/tom/lsdk/packages/firmware'
    make: Leaving directory '/home/tom/lsdk'
    uboot sdboot on ls1043ardb is not supported - one2!

I figured that was coming from Flex-Builder, and put unique error phrase (e.g.: one2!)for each possible exit

It happens inside of the "generate_qoriq_composite_firmware() - on line ~142

    if [ ! -f $fipimg ] || [ ! -f $bl2img ]; then
    echo ${3} ${2}boot on $1 is not supported - one2! && exit
    fi

[yipingwang]

According to your log, files bl2_sd.pbl and fip_uboot.bin have already existed in folder build/firmware/atf/ls1043ardb/.

Did you modify file configs/board/ls1043ardb/manifest? What's your Linux distribution?

Would you please comment the following lines to check whether the SD firmware image could be generated.

# if [ ! -f $fipimg ] || [ ! -f $bl2img ]; then
# echo ${3} ${2}boot on $1 is not supported! && exit
# fi

[tmorrison]

Hi Yiping,

Performed tests, here are the results...

1) It seems builds the "secure" image - even if I don't ask for it. 

2) I have not modified the manifest

3) Ubuntu 18.04 LTS

4) Edited, and re-ran - it again just built the secure image and nothing else - BUT - I didn't get that error

It seems that the generate composite firmware image doesn't build a non-secure version? 

Questions: 

   a) Is there a way to build the composite firmware image any other way

   b) What I really need is to install Linux kernel and rootfs on the SD Card. 

        So, is there a procedure to install the Linux Image/dtb along with the rootfs

        using 'dd' commands (I am currently using this method to install uboot and

        microcode on sd card for debug).

Thanks in advance.        

[yipingwang]

Please deploy bl2_sd.pbl at block no. 0x00008 on SD card.

Please deploy fip_uboot.bin at block no. 0x00800 on SD card.

For details, please refer to section "4.2 LSDK memory layout and Userland" in LSDK1909 LSDK user manual.

[tmorrison]

so you can't use the u-boot-with-spl.bin?

[yipingwang]

bl2_sd.pbl  contains RCW+PBI+BL2

fip_uboot.bin TF-A FIP image, it contains BL31 +TEE (BL32) + U-Boot.

If ATF version firmware image, u-boot is built with configuration file  ls1043ardb_tfa_defconfig, so SD u-boot image u-boot-with-spl.bin is not used.

[tmorrison]

Thank you Yiping.

I understand what you are saying, but we are still trying to debug hardware

with u-boot. Can I use these images to debug in CodeWarrior/CodeWarrior Tap?

t

[yipingwang]

Please try to use Attach method to debug the bootloader, please refer to IDE configuration in "2. Debug u-boot with CodeWarrior for ARMv8" in https://community.nxp.com/docs/DOC-331981 to configure CodeWarrior IDE to debug the bootloader.

[tmorrison]

Unfortunately, this refers only to debugging simple u-boot, not a tfa version

t