cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Visitor
Visitor
1,215 Views
Registered: ‎02-15-2017

Petalinux Ultrascale 2017.2 boot problem

Jump to solution

Hello,

I have a problem booting Petalinux from my Ultrascale.

Is somebody used to that error with **Unrecognized filesystem type**?

 

Do you think it is a problem of the custom .hdf?

 

ZynqMP> Xilinx Zynq MP First Stage Boot Loader 
Release 2017.2   Aug 27 2018  -  16:48:06
NOTICE:  ATF running on XCZU3EG/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):0d9d51a
NOTICE:  BL31: Built : 14:28:00, Aug 27 2018


U-Boot 2017.01 (Aug 27 2018 - 16:43:14 +0200) Xilinx ZynqMP ZCU102 revB

I2C:   Error, wrong i2c adapter 0 max 0 possible
Error, wrong i2c adapter 0 max 0 possible
ready
DRAM:  1 GiB
EL Level:       EL2
Chip ID:        xczu3eg
MMC:   sdhci@ff160000: 0 (eMMC), sdhci@ff170000: 1 (SD)
SF: Detected n25q256a with page size 512 Bytes, erase size 128 KiB, total 64 MiB
Error, wrong i2c adapter 0 max 0 possible
Error, wrong i2c adapter 0 max 0 possible
In:    serial
Out:   serial
Err:   serial
Net:   ZYNQ GEM: ff0e0000, phyaddr ffffffff, interface rgmii-id
eth0: ethernet@ff0e0000
Hit any key to stop autoboot:  0 
boot Petalinux
syntax error
Device: sdhci@ff160000
Manufacturer ID: 13
OEM: 14e
Name: Q2J54 
Tran Speed: 25000000
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 3.6 GiB
Bus Width: 8-bit
Erase Group Size: 512 KiB
HC WP Group Size: 8 MiB
User Capacity: 3.6 GiB WRREL
Boot Capacity: 16 MiB ENH
RPMB Capacity: 512 KiB ENH
** Unrecognized filesystem type **
ZynqMP> 

 

Thank you!

 

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Visitor
Visitor
1,163 Views
Registered: ‎02-15-2017

Re: Petalinux Ultrascale 2017.2 boot problem

Jump to solution

The Problem is solved!

The u-boot couldn't find the image.ub (kernel).

 

I had to change the environment variables directly in the u-boot terminal on startup.

 

<ZynqMP> printenv
bootcmd=run sdboot
sdboot=echo boot Petalinux; run uenvboot ; mmcinfo && fatload mmc 1 ${netstart} ${kernel_img} && bootm // changed mmc 0 (flash) to mmc 1 (sd)

Thank you for the help!

 

View solution in original post

0 Kudos
3 Replies
Highlighted
Moderator
Moderator
1,201 Views
Registered: ‎12-04-2016

Re: Petalinux Ultrascale 2017.2 boot problem

Jump to solution

Hi

 

See if this debugging steps listed in this AR helps

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

 

 

Best Regards

Shabbir

0 Kudos
Highlighted
Visitor
Visitor
1,194 Views
Registered: ‎02-15-2017

Re: Petalinux Ultrascale 2017.2 boot problem

Jump to solution

Thank you for the answer, I will try to debug.

The strange thing is that everything is working fine in Standalone OS.

 

Therefore the problem should be in Petalinux generation.

In the end of the build process there is this warning:

[fsbl_config] a53_x64 | a53_x32 | r5_single | r5_dual will be deprecated.
Please use 'destination_cpu' attribute of bootloader partition.

Could this cause the error?

 

 

Or what is the syntax error?

Hit any key to stop autoboot:  0 
boot Petalinux
syntax error
Device: sdhci@ff160000
0 Kudos
Highlighted
Visitor
Visitor
1,164 Views
Registered: ‎02-15-2017

Re: Petalinux Ultrascale 2017.2 boot problem

Jump to solution

The Problem is solved!

The u-boot couldn't find the image.ub (kernel).

 

I had to change the environment variables directly in the u-boot terminal on startup.

 

<ZynqMP> printenv
bootcmd=run sdboot
sdboot=echo boot Petalinux; run uenvboot ; mmcinfo && fatload mmc 1 ${netstart} ${kernel_img} && bootm // changed mmc 0 (flash) to mmc 1 (sd)

Thank you for the help!

 

View solution in original post

0 Kudos