cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
evatrostaz
Participant
Participant
1,908 Views
Registered: ‎07-13-2020

Petalinux 2020.1 U-Boot wrong image format

Jump to solution

Hi,

I'm trying to boot PetaLinux which i created with avnet-digilent-zedboard-2020.1.bsp and followed this:
https://forums.xilinx.com/t5/AI-and-Vitis-AI/Petalinux-does-not-boot-All-steps-inside/td-p/973671

I copied BOOT.BIN and image.ub to SD Card.

Here is log from PuTTy:

 

U-Boot 2020.01 (Jul 13 2020 - 09:50:54 +0000)

CPU:   Zynq 7z020
Silicon: v3.1
Model: Zynq Zed Development Board
DRAM:  ECC disabled 512 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
OK
In:    serial@e0001000
Out:   serial@e0001000
Err:   serial@e0001000
Net:
ZYNQ GEM: e000b000, mdio bus e000b000, phyaddr 0, interface rgmii-id
eth0: ethernet@e000b000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
## Executing script at 03000000
Wrong image format for "source" command
SCRIPT FAILED: continuing...
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
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 03000000
Wrong image format for "source" command
SCRIPT FAILED: continuing...


no devices available
SCRIPT FAILED: continuing...
## Executing script at 03000000
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

What does "Wrong image format for "source" command" mean?
Anyone have idea what to do?
BTW I did run Getting Started for ZedBoard successfully.

 

 

 

 

1 Solution

Accepted Solutions
evatrostaz
Participant
Participant
1,738 Views
Registered: ‎07-13-2020

I did clear new project with this for embedded accel platform, and used boot.scr generated by petalinux-build. Works fine now.

Make sure your sd card is partitioned properly and is not locked with mechanical switch

Copy BOOT.BIN, image.ub and boot.scr to SDcard_boot_dir and set 'run mmc_boot' as bootcmd.

View solution in original post

5 Replies
sulcas.mindaugas
Observer
Observer
1,870 Views
Registered: ‎05-17-2018

I have same issue with ultra96v1 board. I created petalinux project using zynqmp template. Image created with same flow using petalinux 2018.3 works just fine.

0 Kudos
Reply
evatrostaz
Participant
Participant
1,815 Views
Registered: ‎07-13-2020

Thanks for answer!
But unfortunately i wanted to try Vitis Libraries so maybe i will try my luck with 2019 version.

0 Kudos
Reply
jwoeber
Participant
Participant
1,795 Views
Registered: ‎04-04-2019

Hi,

I am having the same issues with the ZCU102 Board and petalinux 2020.1.

Created a BOOT.BIN with the hdf File from the official repo and I am also getting the Wrong image format for "source" command Error.

I cant use the previous petalinux version because I need a linux kernel version > 5.0.

 

petalinux-create -t project -s ~/Downloads/xilinx-zcu102-v2020.1-final.bsp
cd xilinx-zcu102-v2020.1
cp ~/Downloads/system.xsa .
petalinux-config --get-hw-description=.
petalinux-config
petalinux-config -c kernel
petalinux-build
petalinux-package --boot --u-boot --format BIN

 

 

0 Kudos
Reply
evatrostaz
Participant
Participant
1,739 Views
Registered: ‎07-13-2020

I did clear new project with this for embedded accel platform, and used boot.scr generated by petalinux-build. Works fine now.

Make sure your sd card is partitioned properly and is not locked with mechanical switch

Copy BOOT.BIN, image.ub and boot.scr to SDcard_boot_dir and set 'run mmc_boot' as bootcmd.

View solution in original post

jwoeber
Participant
Participant
1,726 Views
Registered: ‎04-04-2019

Thanks,

after copying boot.scr to the sd card as well it all worked.