Hi,
I am using flex-builder to build a u-boot image (that I'm trying to customize).
from the ls1043ardb build - we have a custom LS1043a-RGW board - that
I was hoping that would boot without any big issues.
My developer "gave me" a Image/Image.gz that runs on a "regular" LS1043a-RGW
board (Image, Image.gz, and fsl-ls1043a-rgw-sdk.dtb) as well as a rootfs
(openwrt_xxxx-ls1043ardb-rootfs.tar.gz)
1) First I built a "standard" ls1043a-rdb boot_partition and installed it on my SD Card.
flex-builder -a arm64 -m ls1043ardb -b sd
2) I used flex-installer to create the partitions and load the rootfs and this boot partition on sd card
sudo flex-installer -b bootpartition_LS_arm64_lts_4.19.tgz -r openwrt-layerscape-armv8_64b-device-ls1043ardb-rootfs.tar.gz -d /dev/sde
3) I used the following procedure to update the kernel/device tree (with Image/Image.gz and the dtb to
all of the associated fsl-ls1043a-rdb-xxx.dtb)
LS1043ARDB - How to update Linux kernel and device tree on SD card
3) After that - because I don't have a proper firmware image built (Build composite uboot image),
I flash the u-boot, iram and fsl_fman code - using this procedure:
dd if=u.bin of=/dev/mmcblk0 bs=512 seek=8 && sync
dd if=fsl_fman_ucode_t2080_r1.1_108_4_5.bin of=/dev/mmcblk0 bs=512 seek=18432 && sync
dd if=iram_Type_A_LS1021a_r1.0.bin of=/dev/mmcblk0 bs=512 seek=18944 && sync
4) I put the SD Card into our custom board, and start to boot
(see attached file for total log).
5) it seems that the first line of starting the kernel indicates that it is something built on Monday - which is likely
something I built in step #1
[ 0.000000] Linux version 4.19.68-00019-ga5c3ba83fc17 (tom@newSNIPC) (gcc version 7.5.0 (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04)) #1 SMP PREEMPT Mon Mar 30 14:
is this procedure still valid?
what am I doing wrong?
Tom
