buildroot/board/khadas/vim3
Antoine Coutant d6d0f73a2e board/khadas/vim3: add the path of the devicetree in extlinux.conf
Without this patch, the devicetree used by linux at runtime is
the u_boot devicetree.

While using rusticl on the khadas vim3 board with the default
extlinux.conf, mesa's panfrost driver return "gpu shed timeout"
errors. Adding "devicetree /meson-g12b-khadas-vim3.dtb" to the
extlinux.conf file solve the problem. Linux successfully boot
with and without the change but without this patch the devicetree
used by linux at runtime is the u-boot devicetree.

The differences between the u-boot devicetree and the linux
devicetree are:
-The u-boot devicetree contains two more nodes than the linux devicetree. Those nodes are:
    - smbios : compatible option is set to "u-boot,sysinfo-smbios".
    - __symbols__ : present if -@ or --symbols is used during the devicetree compilation.
-Most of u-boot devicetree nodes have a "phandle" property.
-SoC and vpu have a "u-boot,dm-pre-reloc;" property.
-Some aliases are different.
-The u-boot operating points tables contains more nodes.
The size difference between the u-boot devicetree and the linux
devicetree is approximately 3.5kB.

During runtime, the linux devicetree have the "phandle" and
"u-boot,dm-pre-reloc;" properties and the smbios node. So,
The runtime devicetree is the one from u-boot.

Signed-off-by: Antoine Coutant <antoine.coutant@smile.fr>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-11-18 16:14:45 +01:00
..
extlinux.conf board/khadas/vim3: add the path of the devicetree in extlinux.conf 2023-11-18 16:14:45 +01:00
genimage.cfg
post-build.sh
post-image.sh
readme.txt

Khadas VIM3

Description
===========

This configuration builds a complete image for the Khadas VIM3 to be flashed
on an SD-card.

How to build it
===============

Select the default configuration for the target:
$ make khadas_vim3_defconfig

Optional: modify the configuration:
$ make menuconfig

Build:
$ make

Result of the build
===================
output/images/
+-- amlogic-boot-fip
+   +-- build-fip.sh
+   +-- g12a.inc
+   `-- khadas-vim3
+       +-- acs.bin
+       +-- acs_tool.py
+       +-- aml_ddr.fw
+       +-- aml_encrypt_g12b
+       +-- bl2.bin
+       +-- bl301.bin
+       +-- bl30.bin
+       +-- bl31.bin
+       +-- bl31.img
+       +-- blx_fix.sh
+       +-- ddr3_1d.fw
+       +-- ddr4_1d.fw
+       +-- ddr4_2d.fw
+       +-- diag_lpddr4.fw
+       +-- lpddr3_1d.fw
+       +-- lpddr4_1d.fw
+       +-- lpddr4_2d.fw
+       +-- Makefile
+       `-- piei.fw
+-- boot.vfat
+-- extlinux
+   `-- extlinux.conf
+-- fip
+   +-- u-boot.bin
+   +-- u-boot.bin.sd.bin
+   +-- u-boot.bin.usb.bl2
+   `-- u-boot.bin.usb.tpl
+-- Image
+-- meson-g12b-a311d-khadas-vim3.dtb
+-- rootfs.ext2
+-- rootfs.ext4 -> rootfs.ext2
+-- rootfs.tar
+-- sdcard.img
`-- u-boot.bin

The post-image script uses the files in the amlogic-boot-fip folder to sign
the bootloader image before integrating it into the sdcard image.

To copy the image file to the sdcard use dd:
$ dd if=output/images/sdcard.img of=/dev/sdX

Tested hardware
===============
Khadas vim3 (rev. 14)