Bumping up this thread.
I see Neil have pushed a patch to fix the green screen issue here
I started testing it by moving back to the old boot scripts which I have been using from balbes work but now I am stuck with text_offset so after doing some more search I found that text_offset patch is still being maintained by Khadas team here
Chainloader method shared above have been used since then but it does not fulfil all the use case of booting like if image is flashed to emmc then it cannot boot over emmc and in some case if USB drive is connected then it fails to boot over sd card.
Is there any other way to fix text_offset ? As I think with green screen issue fixed we should be able to move back to old boot script method.
Stuck with this
reading Image
31267328 bytes read in 1710 ms (17.4 MiB/s)
reading uInitrd
8139419 bytes read in 442 ms (17.6 MiB/s)
reading uEnv.ini
268 bytes read in 2 ms (130.9 KiB/s)
reading /dtbs/amlogic/meson-gxm-khadas-vim2.dtb
41606 bytes read in 11 ms (3.6 MiB/s)
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
[rsvmem] fdt get prop fail.
## Loading init Ramdisk from Legacy Image at 04080000 ...
Image Name: uInitrd Image
Image Type: AArch64 Linux RAMDisk Image (uncompressed)
Data Size: 8139355 Bytes = 7.8 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
load dtb from 0x20000000 ......
ERROR: Did not find a cmdline Flattened Device Tree
load dtb from 0x0 ......
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
Please advice @hyphop @chewitt
Update I updated the boot script by following the odroid method and now it gets stuck while loading the kernel.
# Flattened Device Tree blob at 20000000
Booting using the fdt blob at 0x20000000
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
[rsvmem] fdt get prop fail.
Loading Ramdisk to b36fb000, end b3ebe25b ... OK
Loading Device Tree to 000000001fff2000, end 000000001ffff285 ... OK
fdt_instaboot: no instaboot image
Starting kernel ...
uboot time: 104587001 us
[ 0.769378] hub 2-0:1.0: config failed, hub doesn't have any ports! (err -19)
domain-0 init dvfs: 4
domain-1 init dvfs: 4
Both ways it is not able to load dtb.