UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Observer tkato@poc.com
Observer
290 Views
Registered: ‎09-06-2019

Updating Linux to xilinx-v2019.1

After experiancing some issues with shared MDIO and gem bring up we decided to roll to Linux version v2019.1 (from the xilinx git repo).

We've updated the paths in our buildroot project to the v2019.1 tag but when we attempt to load the new kernel image onto our board we get back a error saying that the kernel could not be loaded due to a bad fit image. What other changes need to be done in order to successfully roll our project from 2018.3 to 2019.1?

Thanks!

0 Kudos
7 Replies
Moderator
Moderator
276 Views
Registered: ‎04-24-2017

Re: Updating Linux to xilinx-v2019.1

Hi tkato@poc.com ,

Can you post the boot log?

Thanks,
Sandeep
PetaLinux Yocto | Embedded SW Support

---------------------------------------------------------------------------
Don’t forget to Reply, Kudo, and Accept as Solution.
---------------------------------------------------------------------------
0 Kudos
Scholar watari
Scholar
272 Views
Registered: ‎06-16-2013

Re: Updating Linux to xilinx-v2019.1

Hi tkato@poc.com 

 

Did you make sure the following version ?

 

- PMUFW

- ATF

 

I'm not sure, but PMUFW or ATF strictly check version number to trustly boot around 2018.x.

 

Best regards,

0 Kudos
Observer tkato@poc.com
Observer
259 Views
Registered: ‎09-06-2019

Re: Updating Linux to xilinx-v2019.1

Here is the log from the boot:

Xilinx Zynq MP First Stage Boot Loader
Release 2018.3   Mar 12 2019  -  14:10:09
NOTICE:  ATF running on XCZU7EG/EV/silicon v4/RTL5.1 at 0xfffea000
NOTICE:  BL31: Secure code at 0x0
NOTICE:  BL31: Non secure code at 0x8000000
NOTICE:  BL31: v1.5(release):xilinx-v2018.2-919-g08560c36
NOTICE:  BL31: Built : 12:45:21, Dec  6 2018
PMUFW:  v1.1


U-Boot 2019.01-06928-g86487c5ed3-dirty (Mar 15 2019 - 11:23:50 -0700)

Model: ZynqMP ZCU106 RevA
Board: Xilinx ZynqMP
DRAM:  4 GiB
EL Level:       EL2
Chip ID:        zu7
Loading Environment from SPI Flash... SF: Detected n25q1024a with page size 512 Bytes, erase size 128 KiB, total 256 MiB
OK
In:    serial@ff000000
Out:   serial@ff000000
Err:   serial@ff000000
Net:   Found GPIO reset info, GPIO6
ZYNQ GEM: ff0d0000, assign phyaddr 0, interface rgmii-id
eth0: ethernet@ff0d0000ZYNQ GEM: ff0e0000, assign phyaddr 1, interface rgmii-id
PHY is not detected
GEM PHY init failed
, eth-1: ethernet@ff0e0000
Hit any key to stop autoboot:  0
SF: Detected n25q1024a with page size 512 Bytes, erase size 128 KiB, total 256 MiB
device 0 offset 0x200000, size 0xb98622
SF: 12158498 bytes @ 0x200000 Read: OK
  design filename = "adts_video_demo;COMPRESS=TRUE;UserID=0XFFFFFFFF;Version=2018.3"
  part number = "xczu7ev-ffvc1156-2-i"
  date = "2019/10/07"
  time = "12:51:40"
  bytes in bitstream = 10271308
zynqmp_align_dma_buffer: Align buffer at 0000000001000086 to 0000000000ffffc0(swap 0)
device 0 offset 0x1200000, size 0x700000
SF: 7340032 bytes @ 0x1200000 Read: OK
## Loading kernel from FIT Image at 01000000 ...
Bad FIT kernel image format!
ERROR: can't get kernel image!

Our design utilizes a u-boot built separately. I believe they used 2018.3 for this looking at the boot message. Would we have a create a new u boot image to boot 2019.1? Or is there a work around?

I'm also unclear what it means when it prints that the FIT kernel image is in a bad format.

0 Kudos
Scholar watari
Scholar
246 Views
Registered: ‎06-16-2013

Re: Updating Linux to xilinx-v2019.1

Hi tkato@poc.com 

 

Would you share the following results ?

 

$ dumpimage -l <your boot.bin file>

$ dumpimage -l <your fit image file name>

 

Best regards,

0 Kudos
Observer tkato@poc.com
Observer
237 Views
Registered: ‎09-06-2019

Re: Updating Linux to xilinx-v2019.1

Here are the results:

$ dumpimage -l uboot.bin :

Image Type   : Xilinx ZynqMP Boot Image support
Image Offset : 0x00002800
Image Size   : 86696 bytes (86696 bytes packed)
PMUFW Size   : 129760 bytes (129760 bytes packed)
Image Load   : 0xfffc0000
Checksum     : 0xfd179131
Modified Interrupt Vector Address [0]: 0x14000000
Modified Interrupt Vector Address [1]: 0x14000000
Modified Interrupt Vector Address [2]: 0x14000000
Modified Interrupt Vector Address [3]: 0x14000000
Modified Interrupt Vector Address [4]: 0x14000000
Modified Interrupt Vector Address [5]: 0x14000000
Modified Interrupt Vector Address [6]: 0x14000000
Modified Interrupt Vector Address [7]: 0x14000000
FSBL payload on CPU a5x-0 (PS):
    Offset     : 0x000375c0
    Size       : 51744 (0xca20) bytes
    Load       : 0xfffea000
    Attributes : EL2 
    Checksum   : 0x00014331
FSBL payload on CPU a5x-0 (PS):
    Offset     : 0x00044000
    Size       : 571128 (0x8b6f8) bytes
    Load       : 0x08000000
    Attributes : EL2 
    Checksum   : 0xeff8634e

$ dumpimage -l Image.itb :

FIT description: ARM Zynqmp FIT (Flattened Image Tree)
Created:         Tue Oct 15 17:36:12 2019
 Image 0 (kernel@1)
  Description:  POC based on ARM Xilinx Zynq ZCU106 Linux-4.x
  Created:      Tue Oct 15 17:36:12 2019
  Type:         Kernel Image
  Compression:  gzip compressed
  Data Size:    7862316 Bytes = 7678.04 KiB = 7.50 MiB
  Architecture: AArch64
  OS:           Linux
  Load Address: 0x00080000
  Entry Point:  0x00080000
  Hash algo:    crc32
  Hash value:   a61185d8
  Hash algo:    sha1
  Hash value:   3ca6fe8f481fa49d44b4eee4b4fee55db6b08806
 Image 1 (fdt@1)
  Description:  Zynqmp POC device tree blob
  Created:      Tue Oct 15 17:36:12 2019
  Type:         Flat Device Tree
  Compression:  uncompressed
  Data Size:    45352 Bytes = 44.29 KiB = 0.04 MiB
  Architecture: AArch64
  Hash algo:    crc32
  Hash value:   d22ca30d
  Hash algo:    sha1
  Hash value:   3bd1b54b2567f0c605a4fb195b469455060c1112
 Default Configuration: 'config@1'
 Configuration 0 (config@1)
  Description:  Zynqmp
  Kernel:       kernel@1
  FDT:          fdt@1

Thanks

0 Kudos
Observer tkato@poc.com
Observer
154 Views
Registered: ‎09-06-2019

Re: Updating Linux to xilinx-v2019.1

Does the FSBL also need to be built in 2019.1?

0 Kudos
Scholar watari
Scholar
151 Views
Registered: ‎06-16-2013

Re: Updating Linux to xilinx-v2019.1

Hi tkato@poc.com 

 

I'm not sure.

But I recommend it.

 

Best regards,

0 Kudos