cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
gi4you
Contributor
Contributor
3,049 Views
Registered: ‎09-24-2009

zcu102 petalinux booting error

Jump to solution

 

With zcu102 rev 1.0, Vivado2019.1 and petalinux 2019.1 I found the kernel booting error. 

Does anyone have a solution?

 

[ 3.820699] can: controller area network core (rev 20170425 abi 9)
[ 3.826827] NET: Registered protocol family 29
[ 3.831215] can: raw protocol (rev 20170425)
[ 3.835452] can: broadcast manager protocol (rev 20170425 t)
[ 3.841076] can: netlink gateway (rev 20170425) max_hops=1
[ 3.846759] Bluetooth: RFCOMM TTY layer initialized
[ 3.851377] Bluetooth: RFCOMM socket layer initialized
[ 3.856490] Bluetooth: RFCOMM ver 1.11
[ 3.860197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 3.865473] Bluetooth: BNEP filters: protocol multicast
[ 3.870663] Bluetooth: BNEP socket layer initialized
[ 3.875592] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 3.881477] Bluetooth: HIDP socket layer initialized
[ 3.886523] 9pnet: Installing 9P2000 support
[ 3.890657] Key type dns_resolver registered
[ 3.895324] registered taskstats version 1
[ 3.898953] Loading compiled-in X.509 certificates
[ 3.904041] Btrfs loaded, crc32c=crc32c-generic
·r?ÂÊconsole [ttyPS0] enabledl: ttyPS0 at MMIO 0xff000000 (irq = 47, base_baud = 6249375) is a xuartps
[ 3.923089] console [ttyPS0] enabled
[ 3.926673] bootconsole [cdns0] disabled
[ 3.926673] bootconsole [cdns0] disabled
[ 3.934576] ff010000.serial: ttyPS1 at MMIO 0xff010000 (irq = 48, base_baud = 6249375) is a xuartps

 

0 Kudos
1 Solution

Accepted Solutions
gi4you
Contributor
Contributor
2,966 Views
Registered: ‎09-24-2009

Thank you so much for your support.

Solved my problem.

I changed the Root filesystem type is INITRAMFS.

And succesfully login to petalinux.

 

Starting udev
[ 5.700092] udevd[1842]: starting version 3.2.5
[ 5.704917] random: udevd: uninitialized urandom read (16 bytes read)
[ 5.711417] random: udevd: uninitialized urandom read (16 bytes read)
[ 5.717913] random: udevd: uninitialized urandom read (16 bytes read)
[ 5.728471] udevd[1843]: starting eudev-3.2.5
[ 6.195885] EXT4-fs (mmcblk0p2): recovery complete
[ 6.198880] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 6.200686] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 6.210615] [drm] Cannot find any crtc or sizes
Fri Jul 12 19:41:02 UTC 2019
Configuring packages on first boot....
(This may take several minutes. Please do not power off the machine.)
Running postinst /etc/rpm-postinsts/100-sysvinit-inittab...
update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing)
INIT: Entering runlevel: 5
Configuring network interfaces... Cannot find device "eth0"
Starting Dropbear SSH server: Generating 2048 bit rsa key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCSA+jQSxar0obuc1xPBHAMWO6Ww2z2hxCFIsBP8KAQm5Uc7DqLOAdYNNI+s4wByeo5cpplLtgmC44q3+3coB7XGj55oGamWe/52wESdZ5hB9ufehjrNfZemnhPIfa1HGAVH7qaNqmgFLZ0HNSIGpbM9pc6nNXP+pIUpJluIdloDq2v2RJCaJRNrx6FRjrbyq6CpVq/4eNhv0CTwbLMELcNKb9rqwcrTzN/4X2ngg+YTV+OTF/WlSmp15ohYhJYfI+CrJYuFwm0a1cCHMwWYISEkk+tFc2Vj1F2J1vtxJiSqnIIg3rbW+SbkvHzfB3sB76+R5et5zbcYgZU8Onl5r11 root@zcu102_dma
Fingerprint: sha1!! 80:ab:c0:1c:25:5e:83:a6:52:9b:c6:6d:d4:66:d7:92:e8:be:39:cc
dropbear.
Starting internet superserver: inetd.
Starting syslogd/klogd: done
Starting tcf-agent: OK

PetaLinux 2019.1 zcu102_dma /dev/ttyPS0

zcu102_dma login: root
Password:
root@zcu102_dma:~#

 

View solution in original post

0 Kudos
8 Replies
shirilt
Xilinx Employee
Xilinx Employee
3,010 Views
Registered: ‎05-15-2018

Hi @gi4you 

Could you modify your <petalinux-project-root>\project-spec\meta-user\recipes-bsp\device-tree\files\system-user.dtsi file as follows and then retry?

/include/ "system-conf.dtsi"
/ {
      chosen {
            bootargs = "console=ttyPS0,115200 earlycon clk_ignore_unused";
            stdout-path = "serial0:115200n8";
      };
};

Best,

Shiril

 

---------------------------------------------------------------------------
Don’t forget to Reply, Kudo, and Accept as Solution.
---------------------------------------------------------------------------
0 Kudos
gi4you
Contributor
Contributor
3,000 Views
Registered: ‎09-24-2009

Hi Shiril,

 

Step 1: change dtsi

bpmlab2 ~/xilinx/kiman/zcu102/dma_test/zcu102_dma/project-spec/meta-user/recipes-bsp/device-tree/files $ cat system-user.dtsi
/include/ "system-conf.dtsi"
/ {
chosen {
bootargs = "console=ttyPS0,115200 earlycon clk_ignore_unused";
stdout-path = "serial0:115200n8";
};
};

 

Step 2: clean and rebuild

petalinux-build -x distclean

petalinux-build

 

Step 3:

And copy image.ub to SDCARD

 

But still the same status.

Any missing step?

 

Thanks,

Kiman

zcu102_boot_msg.PNG
0 Kudos
shirilt
Xilinx Employee
Xilinx Employee
2,994 Views
Registered: ‎05-15-2018

Hi @gi4you 

After petalinux-build, could you package BOOT.BIN again, and copy over BOOT.BIN and image.ub to the SD card and retry?

petalinux-package --boot --format BIN --fsbl images/linux/zynqmp_fsbl.elf --u-boot images/linux/u-boot.elf --pmufw images/linux/pmufw.elf --fpga images/linux/system.bit --force

Also, in system-user.dtsi, you need to have tabs before each line within parantheses:

Capture.PNG

---------------------------------------------------------------------------
Don’t forget to Reply, Kudo, and Accept as Solution.
---------------------------------------------------------------------------
0 Kudos
gi4you
Contributor
Contributor
2,981 Views
Registered: ‎09-24-2009

Hi shirilt,

Thank you for your prompt reply.

 

I rebuild the BOOT.bin

and passed tty stop problem, but another problem is [ 5.492799] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on

This error came from my SD card partition problem?

At the petalinux-config menu I selected the Root filesystem type is SD card.

 

 

 

 

4.890867] 0x000000140000-0x000001740000 : "kernel"
[ 4.897131] macb ff0e0000.ethernet: Not enabling partial store and forward
[ 4.904493] libphy: MACB_mii_bus: probed
[ 4.910773] macb ff0e0000.ethernet eth0: Could not attach to PHY
[ 4.947642] xilinx-axipmon ffa00000.perf-monitor: Probed Xilinx APM
[ 4.954160] xilinx-axipmon fd0b0000.perf-monitor: Probed Xilinx APM
[ 4.960633] xilinx-axipmon fd490000.perf-monitor: Probed Xilinx APM
[ 4.967115] xilinx-axipmon ffa10000.perf-monitor: Probed Xilinx APM
[ 4.973605] dwc3-of-simple ff9d0000.usb0: dwc3_simple_set_phydata: Can't find usb3-phy
[ 4.982012] dwc3 fe200000.dwc3: Failed to get clk 'ref': -2
[ 4.988247] cdns-i2c ff020000.i2c: 400 kHz mmio ff020000 irq 32
[ 4.994522] cdns-i2c ff030000.i2c: 400 kHz mmio ff030000 irq 33
[ 5.000735] cdns-wdt fd4d0000.watchdog: Xilinx Watchdog Timer at (____ptrval____) with timeout 60s
[ 5.009894] cdns-wdt ff150000.watchdog: Xilinx Watchdog Timer at (____ptrval____) with timeout 10s
[ 5.019136] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 1199880 KHz
[ 5.026575] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed to: 1199999 KHz
[ 5.066843] mmc0: SDHCI controller on ff170000.mmc [ff170000.mmc] using ADMA 64-bit
[ 5.082425] rtc_zynqmp ffa60000.rtc: setting system clock to 2019-05-31 09:44:06 UTC (1559295846)
[ 5.091303] of_cfs_init
[ 5.093750] of_cfs_init: OK
[ 5.096638] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 5.177282] ata1: SATA link down (SStatus 0 SControl 330)
[ 5.182697] ata2: SATA link down (SStatus 0 SControl 330)
[ 5.212562] mmc0: new ultra high speed SDR104 SDHC card at address 0001
[ 5.219662] mmcblk0: mmc0:0001 Team 29.1 GiB
[ 5.224873] mmcblk0: p1 p2
[ 5.235602] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 5.242127] clk: Not disabling unused clocks
[ 5.246397] ALSA device list:
[ 5.249353] #0: DisplayPort monitor
[ 5.253264] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 5.261868] cfg80211: failed to load regulatory.db
[ 5.266802] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[ 5.274284] Please append a correct "root=" boot option; here are the available partitions:
[ 5.282642] 0100 65536 ram0
[ 5.282643] (driver?)
[ 5.288741] 0101 65536 ram1
[ 5.288743] (driver?)
[ 5.294822] 0102 65536 ram2
[ 5.294824] (driver?)
[ 5.300911] 0103 65536 ram3
[ 5.300912] (driver?)
[ 5.306992] 0104 65536 ram4
[ 5.306994] (driver?)
[ 5.313081] 0105 65536 ram5
[ 5.313083] (driver?)
[ 5.319167] 0106 65536 ram6
[ 5.319168] (driver?)
[ 5.325254] 0107 65536 ram7
[ 5.325255] (driver?)
[ 5.331337] 0108 65536 ram8
[ 5.331339] (driver?)
[ 5.337423] 0109 65536 ram9
[ 5.337424] (driver?)
[ 5.343508] 010a 65536 ram10
[ 5.343509] (driver?)
[ 5.349676] 010b 65536 ram11
[ 5.349678] (driver?)
[ 5.355852] 010c 65536 ram12
[ 5.355854] (driver?)
[ 5.362020] 010d 65536 ram13
[ 5.362022] (driver?)
[ 5.368196] 010e 65536 ram14
[ 5.368198] (driver?)
[ 5.374364] 010f 65536 ram15
[ 5.374366] (driver?)
[ 5.380544] 1f00 1024 mtdblock0
[ 5.380546] (driver?)
[ 5.387065] 1f01 256 mtdblock1
[ 5.387066] (driver?)
[ 5.393584] 1f02 22528 mtdblock2
[ 5.393586] (driver?)
[ 5.400106] b300 30547968 mmcblk0
[ 5.400108] driver: mmcblk
[ 5.406883] b301 512000 mmcblk0p1 00021377-01
[ 5.406885]
[ 5.413663] b302 15879168 mmcblk0p2 00021377-02
[ 5.413664]
[ 5.420446] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 5.428699] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.19.0-xilinx-v2019.1 #1
[ 5.435909] Hardware name: xlnx,zynqmp (DT)
[ 5.440076] Call trace:
[ 5.442514] dump_backtrace+0x0/0x148
[ 5.446164] show_stack+0x14/0x20
[ 5.449464] dump_stack+0x90/0xb4
[ 5.452769] panic+0x120/0x268
[ 5.455809] mount_block_root+0x1b0/0x260
[ 5.459800] mount_root+0x11c/0x148
[ 5.463273] prepare_namespace+0x158/0x1a0
[ 5.467353] kernel_init_freeable+0x1b8/0x1d4
[ 5.471694] kernel_init+0x10/0xfc
[ 5.475079] ret_from_fork+0x10/0x18
[ 5.478639] SMP: stopping secondary CPUs
[ 5.482553] Kernel Offset: disabled
[ 5.486025] CPU features: 0x0,20802004
[ 5.489756] Memory Limit: none
[ 5.492799] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

 

0 Kudos
gi4you
Contributor
Contributor
2,967 Views
Registered: ‎09-24-2009

Thank you so much for your support.

Solved my problem.

I changed the Root filesystem type is INITRAMFS.

And succesfully login to petalinux.

 

Starting udev
[ 5.700092] udevd[1842]: starting version 3.2.5
[ 5.704917] random: udevd: uninitialized urandom read (16 bytes read)
[ 5.711417] random: udevd: uninitialized urandom read (16 bytes read)
[ 5.717913] random: udevd: uninitialized urandom read (16 bytes read)
[ 5.728471] udevd[1843]: starting eudev-3.2.5
[ 6.195885] EXT4-fs (mmcblk0p2): recovery complete
[ 6.198880] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 6.200686] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 6.210615] [drm] Cannot find any crtc or sizes
Fri Jul 12 19:41:02 UTC 2019
Configuring packages on first boot....
(This may take several minutes. Please do not power off the machine.)
Running postinst /etc/rpm-postinsts/100-sysvinit-inittab...
update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing)
INIT: Entering runlevel: 5
Configuring network interfaces... Cannot find device "eth0"
Starting Dropbear SSH server: Generating 2048 bit rsa key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCSA+jQSxar0obuc1xPBHAMWO6Ww2z2hxCFIsBP8KAQm5Uc7DqLOAdYNNI+s4wByeo5cpplLtgmC44q3+3coB7XGj55oGamWe/52wESdZ5hB9ufehjrNfZemnhPIfa1HGAVH7qaNqmgFLZ0HNSIGpbM9pc6nNXP+pIUpJluIdloDq2v2RJCaJRNrx6FRjrbyq6CpVq/4eNhv0CTwbLMELcNKb9rqwcrTzN/4X2ngg+YTV+OTF/WlSmp15ohYhJYfI+CrJYuFwm0a1cCHMwWYISEkk+tFc2Vj1F2J1vtxJiSqnIIg3rbW+SbkvHzfB3sB76+R5et5zbcYgZU8Onl5r11 root@zcu102_dma
Fingerprint: sha1!! 80:ab:c0:1c:25:5e:83:a6:52:9b:c6:6d:d4:66:d7:92:e8:be:39:cc
dropbear.
Starting internet superserver: inetd.
Starting syslogd/klogd: done
Starting tcf-agent: OK

PetaLinux 2019.1 zcu102_dma /dev/ttyPS0

zcu102_dma login: root
Password:
root@zcu102_dma:~#

 

View solution in original post

0 Kudos
shirilt
Xilinx Employee
Xilinx Employee
2,950 Views
Registered: ‎05-15-2018

Hi @gi4you 

I suspected that the rootfs setting in petalinux-config menu was incorrectly set. Glad to hear that it works now. In case you don't want to use the INITRAMFS filesystem extracted from image.ub and supply your own rootfs instead, here's what you can do:

Disable the INITRAMFS from kernel config as follows:

1. petalinux-config -c kernel

 General setup  --->   [ ] Initial RAM filesystem and RAM disk (initramfs/initrd) support 

(The above is enabled by default; you should unselect it. Save & exit)

2. Add the following to your bootargs argument in system-user.dtsi -- root=/dev/mmcblk0p2 rw  rootfstype=ext4 rootwait

3. petalinux-build

4. Copy BOOT.BIN and image.ub into the FAT partition of the SD card.

5. Extract rootfs.tar.gz (from images/linux) into ext4 partition of SD card -- tar -xvf  rootfs.tar.gz -C /media/rootfs/.

6. When you boot, the rootfs on ext4 partition of the SD card will be used

In any case, could you mark my post above as the solution for your original problem, so that others can refer to it if need be?

Thanks,

Shiril

---------------------------------------------------------------------------
Don’t forget to Reply, Kudo, and Accept as Solution.
---------------------------------------------------------------------------
0 Kudos
badegoke_f1
Adventurer
Adventurer
2,228 Views
Registered: ‎06-18-2019

Dear @shirilt ,
While searching for a solution to my boot error I found your comments. I sort of think my error is related to petalinux config and mmc. I can only get it past u-boot if I change the default mmc by typing "mmc dev 1 0" and running a "run bootcmd". 

However it gets stuck in the udevd section as shown in the attached log file. Looking at the logs from @gi4you it seems it canno load mmcblk ext4 which is the next stage in the log.

Please do you have any suggestion how I can work around this to load the mmcblk  ext4 partition? I use and Enclustra Mercury XU5 SoM and PE1+ carrier. 

Please also see a link to my previous post explaining my issue :previous post 

Thanks

Bade

0 Kudos
shirilt
Xilinx Employee
Xilinx Employee
2,176 Views
Registered: ‎05-15-2018

Hi @badegoke_f1 

By defualt, petalinux is configured to boot with the mmc@ff170000 (psu_sd_1). This should match with the Vivado design, and if a manual switch is required in u-boot, you might want to check your hardware design to see which SD device is enabled by default. Also, if you are creating a template petalinux project, are you providing a 'MACHINE_NAME' in petalinux-config --> DTG settings? You need to do that so petalinux pulls in the required device-tree include files for the requisite board (if using custom board, select the closest Xilinx board that matches). For more details on MACHINE_NAME, please refer to UG1144.

The linux boot getting stuck midway could be due to CPU idle power managaement feature which is enabled by default. This can be disabled by setting cpuidle.off=1 in boot arguments. When you stop at u-boot, print the bootargs variable, append cpuidle.off=1 to that variable, and save it using 'saveenv'. For other options see https://www.xilinx.com/support/answers/69143.html

Your boot process is stuck at 'udevd' portion, and you are expecting to see EXT4/MMCBLK prints after that like the OP's logs.However, I don't think your issue is related to the ext4 issue the OP was having. That issue was occurring because they had set SD card as the device for ROOTFS instead of INITRAMFS. However, since the ext4 partition of the SD card did not have a rootfs on it, it led to errors. If indeed there was an issue with this, I would expect Linux to print some verbose logs regarding that, rather than just blank out. 

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