cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Observer
Observer
62 Views
Registered: ‎07-24-2020

Wrong Image Format for bootm command - Petalinux Boot 2020.1

Hello,

Petalinux boot is failing,  My design is just to use the PL DDR instead of PS DDR. I have built the petalinux and I copied BOOT.BIN boot.scr image.ub system.dtb files from /image/linux directory to SD card and tried to boot on the board, below is the error what I get,

U-Boot 2020.01 (Sep 16 2020 - 09:17:15 +0000)

CPU: Zynq 7z020
Silicon: v3.1
Model: Zynq Zed Development Board
DRAM: ECC disabled 1024 MiB
Flash: 0 Bytes
NAND: 0 MiB
MMC: mmc@e0100000: 0
Loading Environment from SPI Flash... SF: Detected s25fl256s1 with page size 256 Bytes, erase size 64 KiB, total 32 MiB
*** Warning - bad CRC, using default environment

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

Warning: ethernet@e000b000 using MAC address from DT
eth0: ethernet@e000b000
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2010 bytes read in 49 ms (40 KiB/s)
## Executing script at 43000000
** Reading file would overwrite reserved memory **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
SCRIPT FAILED: continuing...
## Executing script at 43000000
** Reading file would overwrite reserved memory **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
SCRIPT FAILED: continuing...
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2010 bytes read in 49 ms (40 KiB/s)
## Executing script at 43000000
** Reading file would overwrite reserved memory **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
SCRIPT FAILED: continuing...
MMC Device 1 not found
no mmc device at slot 1
SF: Detected s25fl256s1 with page size 256 Bytes, erase size 64 KiB, total 32 MiB
device 0 offset 0xfc0000, size 0x40000
SF: 262144 bytes @ 0xfc0000 Read: OK
## Executing script at 43000000
Wrong image format for "source" command
SCRIPT FAILED: continuing...


no devices available
SCRIPT FAILED: continuing...
## Executing script at 43000000
Wrong image format for "source" command
SCRIPT FAILED: continuing...
starting USB...
Bus usb@e0002000: USB EHCI 1.00
scanning bus usb@e0002000 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device

Device 1: unknown device
ethernet@e000b000 Waiting for PHY auto negotiation to complete.......

-----------------------------------------------------------------------------------------------------

When I stop autoboot mode and When I executed bootm command manually,  I get the below log, In that load address and entry point is still pointing to PS DDR range. How to make the linux load address/entry point lies in the range of 0x4000_0000??

 

Zynq> fatload mmc 0 0x41000000 image.ub

Zynq> bootm 0x41000000

 

LOG:

U-Boot 2020.01 (Sep 18 2020 - 09:26:58 +0000)

CPU: Zynq 7z020
Silicon: v3.1
Model: Zynq Zed Development Board
DRAM: ECC disabled 256 MiB
Flash: 0 Bytes
NAND: 0 MiB
MMC: mmc@e0100000: 0
Loading Environment from SPI Flash... SF: Detected s25fl256s1 with page size 256 Bytes, erase size 64 KiB, total 32 MiB
*** Warning - bad CRC, using default environment

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

Warning: ethernet@e000b000 using MAC address from DT
eth0: ethernet@e000b000
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2010 bytes read in 17 ms (115.2 KiB/s)
## Executing script at 43000000
** Reading file would overwrite reserved memory **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
SCRIPT FAILED: continuing...
## Executing script at 43000000
** Reading file would overwrite reserved memory **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
SCRIPT FAILED: continuing...
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2010 bytes read in 17 ms (115.2 KiB/s)
## Executing script at 43000000
** Reading file would overwrite reserved memory **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
SCRIPT FAILED: continuing...
MMC Device 1 not found
no mmc device at slot 1
SF: Detected s25fl256s1 with page size 256 Bytes, erase size 64 KiB, total 32 Mi B
device 0 offset 0xfc0000, size 0x40000
SF: 262144 bytes @ 0xfc0000 Read: OK
## Executing script at 43000000
Wrong image format for "source" command
SCRIPT FAILED: continuing...


no devices available
SCRIPT FAILED: continuing...
## Executing script at 43000000
Wrong image format for "source" command
SCRIPT FAILED: continuing...
starting USB...
Bus usb@e0002000: USB EHCI 1.00
scanning bus usb@e0002000 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device

Device 1: unknown device
ethernet@e000b000 Waiting for PHY auto negotiation to complete.....

U-Boot 2020.01 (Sep 18 2020 - 09:26:58 +0000)

CPU: Zynq 7z020
Silicon: v3.1
Model: Zynq Zed Development Board
DRAM: ECC disabled 256 MiB
Flash: 0 Bytes
NAND: 0 MiB
MMC: mmc@e0100000: 0
Loading Environment from SPI Flash... SF: Detected s25fl256s1 with page size 256 Bytes, erase size 64 KiB, total 32 MiB
*** Warning - bad CRC, using default environment

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

Warning: ethernet@e000b000 using MAC address from DT
eth0: ethernet@e000b000
Hit any key to stop autoboot: 0
Zynq> fatload mmc 0 0x43000000 uImage
Zynq> fatload mmc 0 0x1000000 image.ub
** Reading file would overwrite reserved memory **
Zynq> bootm 0x1000000
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Zynq> fatload mmc 0 0x41000001 image.ub
11505288 bytes read in 58914 ms (190.4 KiB/s)
Zynq> bootm 0x41000001
## Loading kernel from FIT Image at 41000001 ...
Using 'conf@system-top.dtb' configuration
Verifying Hash Integrity ... OK
Trying 'kernel@1' kernel subimage
Description: Linux kernel
Type: Kernel Image
Compression: uncompressed
Data Start: 0x410000f9
Data Size: 4325968 Bytes = 4.1 MiB
Architecture: ARM
OS: Linux
Load Address: 0x00200000
Entry Point: 0x00200000
Hash algo: sha256
Hash value: 87bbd46051da5f5983cccd508134478436feeee3f9b8ee22339b8ce8168b7 00f
Verifying Hash Integrity ... sha256+ OK
## Loading ramdisk from FIT Image at 41000001 ...
Using 'conf@system-top.dtb' configuration
Verifying Hash Integrity ... OK
Trying 'ramdisk@1' ramdisk subimage
Description: petalinux-image-minimal
Type: RAMDisk Image
Compression: uncompressed
Data Start: 0x41425289
Data Size: 7157387 Bytes = 6.8 MiB
Architecture: ARM
OS: Linux
Load Address: unavailable
Entry Point: unavailable
Hash algo: sha256
Hash value: d45fd3aed8ad93e13cd9a274cef373444f4f9108fb52be32e9f0f401c89c9 798
Verifying Hash Integrity ... sha256+ OK
## Loading fdt from FIT Image at 41000001 ...
Using 'conf@system-top.dtb' configuration
Verifying Hash Integrity ... OK
Trying 'fdt@system-top.dtb' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x41420455
Data Size: 19816 Bytes = 19.4 KiB
Architecture: ARM
Hash algo: sha256
Hash value: 1ee07ec62f91da104048cf5a9c068d2d7da4ae24a5efaad65d8bd7bae04e4 c97
Verifying Hash Integrity ... sha256+ OK
Booting using the fdt blob at 0x41420455
Loading Kernel Image
ERROR: Failed to allocate 0x6d368b bytes below 0x20000000.
ramdisk - allocation error
bootm - boot application image from memory

Usage:
bootm [addr [arg ...]]
- boot application image stored in memory
passing arguments 'arg ...'; when booting a Linux kernel,
'arg' can be the address of an initrd image
When booting a Linux kernel which requires a flat device-tree
a third argument is required which is the address of the
device-tree blob. To boot that kernel without an initrd image,
use a '-' for the second argument. If you do not pass a third
a bd_info struct will be passed instead

For the new multi component uImage format (FIT) addresses
must be extended to include component or configuration unit name:
addr:<subimg_uname> - direct component image specification
addr#<conf_uname> - configuration specification
Use iminfo command to get the list of existing component
images and configurations.

Sub-commands to do part of the bootm sequence. The sub-commands must be
issued in the order below (it's ok to not issue all sub-commands):
start [addr [arg ...]]
loados - load OS image
ramdisk - relocate initrd, set env initrd_start/initrd_end
fdt - relocate flat device tree
cmdline - OS specific command line processing/setup
bdt - OS specific bd_t processing
prep - OS specific prep before relocation or go
go - start OS

 

--------------------------------

 

Regards,

Prasanna

0 Kudos
0 Replies