-
Re: MicroZed TFTP boot
ldeevans Jan 7, 2021 6:11 AM (in response to ldeevans)Oh, just noticed, the boot is failing at the start anyway, maybe the boot sequence is "failing over" to try other boot sources?
So, doing:
$ petalinux-boot --jtag --prebuilt 3
boots the prebuilt images OK.
## Booting kernel from Legacy Image at 00200000 ...
Image Name: Linux-5.4.0-xilinx-v2020.1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4331152 Bytes = 4.1 MiB
Load Address: 00200000
Entry Point: 00200000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 04000000 ...
Image Name: avnet-image-minimal-mz7010-fmccc
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 7186731 Bytes = 6.9 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 00100000
Booting using the fdt blob at 0x100000
Loading Kernel Image
Loading Ramdisk to 1f925000, end 1ffff92b ... OK
Loading Device Tree to 1f91d000, end 1f924f6a ... OK
Starting kernel ...
but doing:
$ petalinux-boot --jtag --prebuilt 2
fails, with...
## Executing script at 03000000
Wrong image format for "source" command
SCRIPT FAILED: continuing...
starting USB...
and doing:
$ petalinux-boot --jtag --kernel
fails with:
## Executing script at 03000000
## Booting kernel from Legacy Image at 00200000 ...
Image Name: Linux-5.4.0-xilinx-v2020.1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4331816 Bytes = 4.1 MiB
Load Address: 00200000
Entry Point: 00200000
Verifying Checksum ... OK
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
SCRIPT FAILED: continuing...
starting USB...
There's probably a lot I've got wrong and don't know, any pointers please?
Thanks,
Dave