Image generated, failed to boot (u-boot dtb issue)

If you use the original embedded-me meta-project, you will find the dtb file path in /boot/uEnv.txt in the wic image is not configured correctly. After flashing the image to sd-card and boot the device, you will get the following error.
U-Boot 2019.07 (Jul 20 2023 - 09:26:11 +0000)

CPU:   Zynq 7z010
Silicon: v3.1
DRAM:  ECC disabled 256 MiB
MMC:   mmc@e0100000: 0
Loading Environment from SPI Flash... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment

In:    serial@e0001000
Out:   serial@e0001000
Err:   serial@e0001000
Net:   ZYNQ GEM: e000b000, phyaddr 0, interface rgmii-id

Warning: ethernet@e000b000 (eth0) using random MAC address - 02:ef:31:36:51:ea
eth0: ethernet@e000b000
554 bytes read in 11 ms (48.8 KiB/s)
Importing environment from SD ...
Hit any key to stop autoboot:  0 
gpio: pin 20 (gpio 20) value is 0
Device: mmc@e0100000
Manufacturer ID: fe
OEM: 3432
Name: SD16G 
Bus Speed: 20000000
Mode: SD High Speed (50MHz)
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 58.2 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
gpio: pin 54 (gpio 54) value is 0
gpio: pin 55 (gpio 55) value is 0
554 bytes read in 11 ms (48.8 KiB/s)
Loaded environment from uEnv.txt
Importing environment from SD ...
Copying Linux from SD to RAM...
4297336 bytes read in 463 ms (8.9 MiB/s)
** No boot file defined **
Handoff to Linux kernel...
## Booting kernel from Legacy Image at 02080000 ...
   Image Name:   Linux-4.19.0-xilinx-v2019.2
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4297272 Bytes = 4.1 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
## Error: "bootcmd_mmc" not defined
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Invalid bus 0 (err=-19)
Failed to initialize SPI flash at 0:0 (error -19)
SCRIPT FAILED: continuing...
starting USB...
No working controllers found
USB is stopped. Please issue 'usb start' first.
starting USB...
No working controllers found
ethernet@e000b000 Waiting for PHY auto negotiation to complete.. done
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 10.0.1.17 (253 ms)
*** Warning: no boot file name; using '0A000111.img'
Using ethernet@e000b000 device
TFTP from server 10.0.1.1; our IP address is 10.0.1.17
Filename '0A000111.img'.
Load address: 0x0
Loading: *
TFTP server died; starting again
missing environment variable: pxefile_addr_r
starting USB...
No working controllers found
BOOTP broadcast 1
DHCP client bound to address 10.0.1.17 (4 ms)
Using ethernet@e000b000 device
TFTP from server 10.0.1.1; our IP address is 10.0.1.17
Filename 'boot.scr.uimg'.
Load address: 0x0
Loading: *
TFTP server died; starting again
BOOTP broadcast 1
DHCP client bound to address 10.0.1.17 (4 ms)
Using ethernet@e000b000 device
TFTP from server 10.0.1.1; our IP address is 10.0.1.17
Filename 'boot.scr.uimg'.
Load address: 0x0
Loading: *
TFTP server died; starting again
Device: mmc@e0100000
Manufacturer ID: fe
OEM: 3432
Name: SD16G 
Bus Speed: 20000000
Mode: SD High Speed (50MHz)
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 58.2 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
gpio: pin 54 (gpio 54) value is 0
gpio: pin 55 (gpio 55) value is 0
554 bytes read in 11 ms (48.8 KiB/s)
Loaded environment from uEnv.txt
Importing environment from SD ...
Copying Linux from SD to RAM...
4297336 bytes read in 463 ms (8.9 MiB/s)
Handoff to Linux kernel...
## Booting kernel from Legacy Image at 02080000 ...
   Image Name:   Linux-4.19.0-xilinx-v2019.2
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4297272 Bytes = 4.1 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
ebaz4205>
jiangqucheng / EBAZ4205-Linux

Image generated, failed to boot (u-boot dtb issue) #2
