cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Explorer
Explorer
1,758 Views
Registered: ‎12-20-2017

ZCU102 QSPI Boot of petalinux

Jump to solution

I have a zcu102 that I am able to boot petalinux 2017.3 from the SD card.  I'd like to boot from the QSPI.

I can boot from the QSPI, but something in the error messages tells me I'm not doing something right.  

Can anyone please advise?

 

Here's what I've done:

I ran petalinux-config to indicate that all of the boot images and such were coming from the "primary flash"...

 

Subsystem AUTO Hardware Settings ->  Advanced bootable images storage Settings ->  

-> boot image settings (changed from primary flash)

->  u-boot env partition settings (changed from primary sd to primary flash)

-> kernel image settings (changed from primary sd to primary flash)

 

(I don't know if I had to do the above, but it was a switch that seemed like it matched what I wanted to do)

 

I booted via the SD card, then used flashcp to copy the BOOT.BIN into mtd0 and image.ub into mtd2.

 

Then I configured SW6[4:1] to ON,ON,OFF,ON

 

When I boot, it appears to be looking for the SD card first, then falling back to the SPI.  The red text below seems like an error, and I'd like to know if I'm doing something wrong.  For instance, was I supposed to do something with a "bif" file?

 

Release 2017.3 Aug 29 2018 - 14:27:26
NOTICE: ATF running on XCZU9EG/silicon v4/RTL5.1 at 0xfffea000, with PMU firmware
NOTICE: BL31: Secure code at 0x0
NOTICE: BL31: Non secure code at 0x8000000
NOTICE: BL31: v1.3(release):f9b244b
NOTICE: BL31: Built : 18:23:11, Aug 29 2018


U-Boot 2017.01 (Aug 29 2018 - 14:27:35 -0400) Xilinx ZynqMP ZCU102 rev1.0

I2C: ready
DRAM: 4 GiB
EL Level: EL2
Chip ID: xczu9eg
MMC: sdhci_send_command: MMC: 0 busy timeout increasing to: 200 ms.
sdhci_send_command: MMC: 0 busy timeout increasing to: 400 ms.
sdhci_send_command: MMC: 0 busy timeout increasing to: 800 ms.
sdhci_send_command: MMC: 0 busy timeout increasing to: 1600 ms.
sdhci_send_command: MMC: 0 busy timeout increasing to: 3200 ms.
sdhci_send_command: MMC: 0 busy timeout.
sdhci_send_command: MMC: 0 busy timeout.
sdhci@ff170000 - probe failed: -70
sdhci_send_command: MMC: 0 busy timeout.
sdhci_send_command: MMC: 0 busy timeout.

zynqmp_qspi_ofdata_to_platdata: CLK 124999999
SF: Detected n25q512a with page size 512 Bytes, erase size 128 KiB, total 128 MiB
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Bootmode: QSPI_MODE
Net: ZYNQ GEM: ff0e0000, phyaddr c, interface rgmii-id

Warning: ethernet@ff0e0000 MAC addresses don't match:
Address in SROM is 01:02:03:04:05:06
Address in environment is 00:0a:35:00:22:01
eth0: ethernet@ff0e0000
U-BOOT for xilinx-zcu102-2017_3

Hit any key to stop autoboot: 0
SF: Detected n25q512a with page size 512 Bytes, erase size 128 KiB, total 128 MiB
device 0 offset 0x1e40000, size 0x3dc0000
SF: 64749568 bytes @ 0x1e40000 Read: OK
## Loading kernel from FIT Image at 10000000 ...
Using 'conf@1' configuration
Trying 'kernel@0' kernel subimage
Description: Linux Kernel
Type: Kernel Image
Compression: uncompressed
Data Start: 0x100000d8
Data Size: 12769792 Bytes = 12.2 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x00080000
Entry Point: 0x00080000
Hash algo: sha1
Hash value: 822c048ad582f2b4da126e508ca84ccf9b3f888e
Verifying Hash Integrity ... sha1+ OK
## Loading ramdisk from FIT Image at 10000000 ...
Using 'conf@1' configuration
Trying 'ramdisk@0' ramdisk subimage
Description: ramdisk
Type: RAMDisk Image
Compression: uncompressed
Data Start: 0x10c3b4f0
Data Size: 45860280 Bytes = 43.7 MiB
Architecture: AArch64
OS: Linux
Load Address: unavailable
Entry Point: unavailable
Hash algo: sha1
Hash value: a680a09167fae0bb096e04fc2f1826113cecc3b2
Verifying Hash Integrity ... sha1+ OK
## Loading fdt from FIT Image at 10000000 ...
Using 'conf@1' configuration
Trying 'fdt@0' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x10c2dbd0
Data Size: 55403 Bytes = 54.1 KiB
Architecture: AArch64
Hash algo: sha1
Hash value: 7c720de7b339f7a7a34ea0b75ac38dee8dd903ba
Verifying Hash Integrity ... sha1+ OK
Booting using the fdt blob at 0x10c2dbd0
Loading Kernel Image ... OK
Loading Ramdisk to 05443000, end 07fff5b8 ... OK
Loading Device Tree to 0000000005432000, end 000000000544286a ... OK

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0
[

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Moderator
Moderator
1,734 Views
Registered: ‎04-24-2017

Re: ZCU102 QSPI Boot of petalinux

Jump to solution

Hi @aaron_b1,

 

This is a know issue and we have a CR to fix this one. Right now you can ignore this message.

 

FYI we have two known issues for QSPI JFFS2 refer this AR.

 

https://www.xilinx.com/support/answers/71114.html

https://www.xilinx.com/support/answers/71439.html

 

Thanks,
Sandeep
PetaLinux Yocto | Embedded SW Support

---------------------------------------------------------------------------
Don’t forget to Reply, Kudo, and Accept as Solution.
---------------------------------------------------------------------------

View solution in original post

Tags (1)
1 Reply
Highlighted
Moderator
Moderator
1,735 Views
Registered: ‎04-24-2017

Re: ZCU102 QSPI Boot of petalinux

Jump to solution

Hi @aaron_b1,

 

This is a know issue and we have a CR to fix this one. Right now you can ignore this message.

 

FYI we have two known issues for QSPI JFFS2 refer this AR.

 

https://www.xilinx.com/support/answers/71114.html

https://www.xilinx.com/support/answers/71439.html

 

Thanks,
Sandeep
PetaLinux Yocto | Embedded SW Support

---------------------------------------------------------------------------
Don’t forget to Reply, Kudo, and Accept as Solution.
---------------------------------------------------------------------------

View solution in original post

Tags (1)