Actions
Forum Thread Details
  • State Verified Answer
  • Replies 19 replies
  • Answers 3 answers
  • Subscribers 326 subscribers
  • Views 4225 views
  • Users 0 members are here
Related

Ultrazed-EV bootconsole [cdns0] disabled

khabnl

Hello,

 

I am testing the Ultrazed-EV board and I found bootconsole [cdns0] disabled message and stopped.

 

I added booting parameters in system-user.dtsi.

 

bootargs = "console=ttyPS0,115200 earlycon clk_ignore_unused cpuidle.off=1 root=/dev/mmcblk0p2 rw  rootfstype=ext4 rootwait";

 

 

U-Boot 2019.01 (Jul 19 2019 - 14:29:54 +0000)

 

Board: Xilinx ZynqMP

DRAM:  4 GiB

usb dr_mode not found

EL Level:       EL2

Chip ID:        zu7ev

MMC:   mmc@ff160000: 0, mmc@ff170000: 1

Loading Environment from SPI Flash... SF: Detected n25q256a with page size 512 Bytes, erase size 128 KiB, total 64 MiB

*** Warning - bad CRC, using default environment

 

In:    serial@ff000000

Out:   serial@ff000000

Err:   serial@ff000000

Board: Xilinx ZynqMP

Bootmode: SD_MODE1

Reset reason:   EXTERNAL

Net:   ZYNQ GEM: ff0e0000, phyaddr c, interface rgmii-id

eth0: ethernet@ff0e0000

U-BOOT for uzev_plinux

 

ethernet@ff0e0000 Waiting for PHY auto negotiation to complete...... done

BOOTP broadcast 1

BOOTP broadcast 2

BOOTP broadcast 3

DHCP client bound to address 192.168.0.101 (1016 ms)

Hit any key to stop autoboot:  0

Device: mmc@ff160000

Manufacturer ID: 13

OEM: 14e

Name: Q2J55

Bus Speed: 52000000

Mode : MMC High Speed (52MHz)

Rd Block Len: 512

MMC version 5.0

High Capacity: Yes

Capacity: 7.1 GiB

Bus Width: 4-bit

Erase Group Size: 512 KiB

HC WP Group Size: 8 MiB

User Capacity: 7.1 GiB WRREL

Boot Capacity: 16 MiB ENH

RPMB Capacity: 4 MiB ENH

23676020 bytes read in 1770 ms (12.8 MiB/s)

## 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:    13574656 Bytes = 12.9 MiB

     Architecture: AArch64

     OS:           Linux

     Load Address: 0x00080000

     Entry Point:  0x00080000

     Hash algo:    sha1

     Hash value:   6430bf9020db9fe81f94415ab58478ebe4154d35

   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:   0x10cfa620

     Data Size:    10066525 Bytes = 9.6 MiB

     Architecture: AArch64

     OS:           Linux

     Load Address: unavailable

     Entry Point:  unavailable

     Hash algo:    sha1

     Hash value:   21d9aa2b62261cf1213a1643c76d418b626775cb

   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:   0x10cf23d0

     Data Size:    33180 Bytes = 32.4 KiB

     Architecture: AArch64

     Hash algo:    sha1

     Hash value:   b128e977b259dd6ff89fe8d29afee83b6c64ac7b

   Verifying Hash Integrity ... sha1+ OK

   Booting using the fdt blob at 0x10cf23d0

   Loading Kernel Image ... OK

   Loading Ramdisk to 07666000, end 07fffa5d ... OK

   Loading Device Tree to 000000000765a000, end 000000000766519b ... OK

 

Starting kernel ...

 

[    0.000000] Booting Linux on physical CPU 0x0

[    0.000000] Linux version 4.9.0-xilinx-v2017.3 (avnet@ubuv1604) (gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11) ) #1 SMP Tue Feb 6 17:51:04 EST 2018

[    0.000000] Boot CPU: AArch64 Processor [410fd034]

[    0.000000] earlycon: cdns0 at MMIO 0x00000000ff000000 (options '115200n8')

[    0.000000] bootconsole [cdns0] enabled

[    0.000000] efi: Getting EFI parameters from FDT:

[    0.000000] efi: UEFI not found.

[    0.000000] cma: Reserved 256 MiB at 0x000000006fc00000

[    0.000000] psci: probing for conduit method from DT.

[    0.000000] psci: PSCIv1.1 detected in firmware.

[    0.000000] psci: Using standard PSCI v0.2 function IDs

[    0.000000] psci: MIGRATE_INFO_TYPE not supported.

[    0.000000] percpu: Embedded 21 pages/cpu @ffffffc87ff78000 s48152 r8192 d29672 u86016

[    0.000000] Detected VIPT I-cache on CPU0

[    0.000000] CPU features: enabling workaround for ARM erratum 845719

[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 1033987

[    0.000000] Kernel command line: earlycon clk_ignore_unused

[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)

[    0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)

[    0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)

[    0.000000] software IO TLB [mem 0x6bc00000-0x6fc00000] (64MB) mapped at [ffffffc06bc00000-ffffffc06fbfffff]

[    0.000000] Memory: 3777580K/4193280K available (9212K kernel code, 584K rwdata, 2884K rodata, 512K init, 397K bss, 153556K reserved, 262144K cma-reserved)

[    0.000000] Virtual kernel memory layout:

[    0.000000]     modules : 0xffffff8000000000 - 0xffffff8008000000   (   128 MB)

[    0.000000]     vmalloc : 0xffffff8008000000 - 0xffffffbebfff0000   (   250 GB)

[    0.000000]       .text : 0xffffff8008080000 - 0xffffff8008980000   (  9216 KB)

[    0.000000]     .rodata : 0xffffff8008980000 - 0xffffff8008c60000   (  2944 KB)

[    0.000000]       .init : 0xffffff8008c60000 - 0xffffff8008ce0000   (   512 KB)

[    0.000000]       .data : 0xffffff8008ce0000 - 0xffffff8008d72200   (   585 KB)

[    0.000000]        .bss : 0xffffff8008d72200 - 0xffffff8008dd5634   (   398 KB)

[    0.000000]     fixed   : 0xffffffbefe7fd000 - 0xffffffbefec00000   (  4108 KB)

[    0.000000]     PCI I/O : 0xffffffbefee00000 - 0xffffffbeffe00000   (    16 MB)

[    0.000000]     vmemmap : 0xffffffbf00000000 - 0xffffffc000000000   (     4 GB maximum)

[    0.000000]               0xffffffbf00000000 - 0xffffffbf1dc00000   (   476 MB actual)

[    0.000000]     memory  : 0xffffffc000000000 - 0xffffffc880000000   ( 34816 MB)

[    0.000000] Hierarchical RCU implementation.

[    0.000000]  Build-time adjustment of leaf fanout to 64.

[    0.000000]  RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.

[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4

[    0.000000] NR_IRQS:64 nr_irqs:64 0

[    0.000000] GIC: Adjusting CPU interface base to 0x00000000f902f000

[    0.000000] GIC: Using split EOI/Deactivate mode

[    0.000000] arm_arch_timer: Architected cp15 timer(s) running at 99.99MHz (phys).

[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x171015c90f, max_idle_ns: 440795203080 ns

[    0.000003] sched_clock: 56 bits at 99MHz, resolution 10ns, wraps every 4398046511101ns

[    0.008221] Console: colour dummy device 80x25

[    0.012480] console [tty0] enabled

[    0.015846] bootconsole [cdns0] disabled

  • 0 in reply to jafoste4

    Hi Josh,

     

    No, I create a new BOOT.bin and image.ub from the Vivado 2019.1.

     

    I had similar problem at Xilinx zcu102 board and it fixed by adding below parameter.

           chosen {

                bootargs = "console=ttyPS0,115200 earlycon clk_ignore_unused cpuidle.off=1 root=/dev/mmcblk0p2 rw  rootfstype=ext4 rootwait";

    stdout-path = "serial0:115200n8";

          };

     

    But Ultrazed-EV dose not help.

     

     

    Thanks,

    Kiman

  • 0

    Hi Kiman,

     

    The last boot message you see here ("bootconsole [cdns0] disabled") usually has nothing to do with the bootconsole being disabled.  This message just happens to be the spot where the kernel boot got hung up.  Because of the way STDIO messages are buffered to the UART during boot, this is the last message that is seen by the user.  The problem is somewhere else.  The u-boot messages indicate this is a kernel that expects a RAMdisk rootfs (“## Loading ramdisk from FIT Image at 10000000 ...”), but the bootargs in the system-user.dtsi file indicate a rootfs on the SD card (“root=/dev/mmcblk0p2 rw  rootfstype=ext4 rootwait”).  These settings re inconsistent.  I would expect the bootargs for a kernel mounting a RAMdisk to look much simpler (“bootargs = "earlycon clk_ignore_unused"”).  If there truly is a rootfs on the mmcblk0p2 partition then PetaLinux also needs to be configured (and thus u-boot) for that.  I believe Xilinx UG1144 describes this (https://www.xilinx.com/support/documentation/sw_manuals/xilinx2019_1/ug1144-petalinux-tools-reference-guide.pdf ).

     

    --Tom

  • 0 in reply to narrucmot

    Hi Tom,

     

    Thank you for your response.

     

    Actually I tried to simple way but I got the same result.

    bootargs = "console=ttyPS0,115200 earlycon clk_ignore_unused";

    stdout-path = "serial0:115200n8";

     

    I need the SD card /dev/mmcblk0p2 partition for the Debian rootfs.

     

    Thanks,

    Kiman

  • 0 in reply to khabnl

    I create image.ub using petalinux version 2019.1

    But the kernel image log file shows "Linux version 4.9.0-xilinx-v2017.3 (avnet@ubuv1604) (gcc version 6.2.1 20161016"

     

    I think this is something wrong, image.ub booting from existing avnet image instead of the SD card?

    Starting kernel ...

     

     

    [    0.000000]
    Linux version 4.9.0-xilinx-v2017.3 (avnet@ubuv1604) (gcc version 6.2.1 20161016     (Linaro GCC 6.2-2016.11) ) #1 SMP Tue Feb 6 17:51:04
    EST 2018

  • 0 in reply to khabnl

    Hi there,

     

    It sounds like you might be booting from the onboard EEPROM or other memory.  Check your boot switch configuration to ensure that you are targeting booting from the SDCARD.

     

    --Dan

  • 0 in reply to drozwood90

    Hi Dan,

     

    Yes, I configured booting from the SD card, and  I confirmed several times.

    Avnet default is QSPI (OFF,ON,ON,ON).

    The SD card booting is (OFF, ON, OFF, ON).

    If remove SDCARD there is no serial console message.

     

    If you see U-Boot message it indicate on Jul 19 2019, but Kernel is not 2019.1

     

     

    U-Boot 2019.01 (Jul 19 2019 - 14:29:54 +0000)

     

    Board: Xilinx ZynqMP

    DRAM:  4 GiB

    usb dr_mode not found

    EL Level:       EL2

    Chip ID:        zu7ev

    MMC:   mmc@ff160000: 0, mmc@ff170000: 1

    Loading Environment from SPI Flash... SF: Detected n25q256a with page size 512 Bytes, erase size 128 KiB, total 64 MiB

    *** Warning - bad CRC, using default environment

     

     

    Thanks,

    Kiman

  • 0 in reply to khabnl

    Hi Kiman,

     

    Is there a specific reason why 2019.1 is needed for your application?

     

    We have not done any BSP work with 2019.1 yet but we have two very stable 2018.2 BSPs posted on the UltraZed-EV page:  UltraZed-EV

     

    image

     

    I would suggest starting with one of these first before diving into 2019.1 tools as there were a lot of changes to the Xilinx tools for 2019.1 release.

     

    Best Regards,

     

    -Kevin

  • 0 in reply to zedhed

    Hi Kevin,

     

    Because our team switched to VV2019.1 for zynq ultrascal+ platform that's why I test with the latest petalinux,

    But it's Okay test with petalinux 2018.2.

     

    I download the uz7ev_evcc_sd_oob_2018_2.bsp file for UltrascalZed-EV board test.

     

    I did test two step:

    step 1 is no external rootfs    : booting fine

    step 2 is with external rootfs  : end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,10)

     

     

    My application is always configured to Root filesystem type -> SC card.

     

     

    ############

    Step 1 BSP test :

    ############

     

    1) download and unzip 2018.2 bsp project

    uz7ev_evcc_sd_oob_2018_2.bsp

     

    2) Creat project

    petalinux-create -t project --template zynqMP -s uz7ev_evcc_sd_oob_2018_2.bsp -n uz7ev_evcc

     

     

    3) Copy BOOT.bin and image.ub to SD card.

    ../pre-built/linux/images

    BOOT_SD.bin -> BOOT.bin

    image.ub

     

     

    4) SD card booting message

    Xilinx Zynq MP First Stage Boot Loader

    Release 2018.2   Sep  8 2018  -  01:31:09

    NOTICE:  ATF running on XCZU7EV/silicon v4/RTL5.1 at 0xfffea000

    NOTICE:  BL31: Secure code at 0x0

    NOTICE:  BL31: Non secure code at 0x8000000

    NOTICE:  BL31: v1.4(release):xilinx-v2018.1-4-g93a69a5a

    NOTICE:  BL31: Built : 05:27:34, Sep  8 2018

    PMUFW:  v1.0

     

     

    U-Boot 2018.01 (Sep 08 2018 - 01:27:49 -0400) Xilinx ZynqMP ZCU102 rev1.0

     

    :

    :

     

    Starting kernel ...

     

    [    0.000000] Booting Linux on physical CPU 0x0

    [    0.000000] Linux version 4.14.0-xilinx-v2018.2 (oe-user@oe-host) (gcc version 7.2.0 (GCC)) #1 SMP Sat Sep 8 01:43:06 EDT 2018

     

    :

    :

     

    root@uz7ev-evcc-sd-oob-2018-2:~# df

    Filesystem     1K-blocks   Used Available Use% Mounted on

    rootfs           1871852 127652   1744200   7% /

    devtmpfs         1871852      0   1871852   0% /dev

    tmpfs            2023532    140   2023392   1% /run

    tmpfs            2023532     84   2023448   1% /var/volatile

     

     

     

     

    ############

    Step 2 BSP test for rootfs booting from Ext4:

    ############

     

    1) petalinux-config

       Change Image Packaging Configuration -> Root filesystem type -> SC card

         

    2) petalinux-build

     

    3) 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

     

    4) Copy BOOT.bin and image.ub to SD card

     

     

    5) SD card booting message

     

    Xilinx Zynq MP First Stage Boot Loader

    Release 2018.2   Jul 23 2019  -  12:08:22

    NOTICE:  ATF running on XCZU7EV/silicon v4/RTL5.1 at 0xfffea000

    NOTICE:  BL31: Secure code at 0x0

    NOTICE:  BL31: Non secure code at 0x8000000

    NOTICE:  BL31: v1.4(release):xilinx-v2018.1-4-g93a69a5a

    NOTICE:  BL31: Built : 16:06:08, Jul 23 2019

    PMUFW:  v1.0

     

     

    U-Boot 2018.01 (Jul 23 2019 - 12:06:10 -0400) Xilinx ZynqMP ZCU102 rev1.0

     

     

    Starting kernel ...

     

    [    0.000000] Booting Linux on physical CPU 0x0

    [    0.000000] Linux version 4.14.0-xilinx-v2018.2 (oe-user@oe-host) (gcc version 7.2.0 (GCC)) #1 SMP Tue Jul 23 12:14:41 EDT 2019

    :

    :

    :

     

    [    3.760906] rtc_zynqmp ffa60000.rtc: setting system clock to 2038-01-22 04:37:01 UTC (2147747821)

    [    3.769816] clk: Not disabling unused clocks

    [    3.774050] ALSA device list:

    [    3.776960]   #0: DisplayPort monitor

    [    3.781065] VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,10): error -6

    [    3.789000] Please append a correct "root=" boot option; here are the available partitions:

    [    3.797331] 0100           65536 ram0

    [    3.797333]  (driver?)

    [    3.803395] 0101           65536 ram1

    [    3.803396]  (driver?)

    [    3.809475] 0102           65536 ram2

    [    3.809477]  (driver?)

    [    3.815546] 0103           65536 ram3

    [    3.815548]  (driver?)

    [    3.821626] 0104           65536 ram4

    [    3.821628]  (driver?)

    [    3.827698] 0105           65536 ram5

    [    3.827699]  (driver?)

    [    3.833778] 0106           65536 ram6

    [    3.833780]  (driver?)

    [    3.839850] 0107           65536 ram7

    [    3.839852]  (driver?)

    [    3.845930] 0108           65536 ram8

    [    3.845932]  (driver?)

    [    3.852002] 0109           65536 ram9

    [    3.852004]  (driver?)

    [    3.858083] 010a           65536 ram10

    [    3.858084]  (driver?)

    [    3.864241] 010b           65536 ram11

    [    3.864243]  (driver?)

    [    3.870408] 010c           65536 ram12

    [    3.870410]  (driver?)

    [    3.876567] 010d           65536 ram13

    [    3.876568]  (driver?)

    [    3.882734] 010e           65536 ram14

    [    3.882736]  (driver?)

    [    3.888893] 010f           65536 ram15

    [    3.888894]  (driver?)

    [    3.895062] 1f00           19840 mtdblock0

    [    3.895064]  (driver?)

    [    3.901570] 1f01             256 mtdblock1

    [    3.901572]  (driver?)

    [    3.908076] 1f02           23552 mtdblock2

    [    3.908077]  (driver?)

    [    3.914590] b300        30547968 mmcblk1

    [    3.914592]  driver: mmcblk

    [    3.921362]   b301         1047552 mmcblk1p1 561ae528-01

    [    3.921363]

    [    3.928126]   b302        29499392 mmcblk1p2 561ae528-02

    [    3.928128]

    [    3.934897] b308         7438336 mmcblk0

    [    3.934899]  driver: mmcblk

    [    3.941672]   b309          250040 mmcblk0p1 00000000-01

    [    3.941674]

    [    3.948438] b320            4096 mmcblk0rpmb

    [    3.948440]  (driver?)

    [    3.955126] b318           16384 mmcblk0boot1

    [    3.955128]  (driver?)

    [    3.961897] b310           16384 mmcblk0boot0

    [    3.961898]  (driver?)

    [    3.968662] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,10)

    [    3.977174] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 4.14.0-xilinx-v2018.2 #1

    [    3.984375] Hardware name: xlnx,zynqmp (DT)

    [    3.988539] Call trace:

    [    3.990976] [<ffffff8008088c58>] dump_backtrace+0x0/0x368

    [    3.996355] [<ffffff8008088fd4>] show_stack+0x14/0x20

    [    4.001389] [<ffffff8008a361f8>] dump_stack+0x9c/0xbc

    [    4.006424] [<ffffff800809bdc0>] panic+0x11c/0x274

    [    4.011198] [<ffffff8008d81124>] mount_block_root+0x1a8/0x27c

    [    4.016926] [<ffffff8008d81430>] mount_root+0x11c/0x134

    [    4.022133] [<ffffff8008d815b4>] prepare_namespace+0x16c/0x1b4

    [    4.027949] [<ffffff8008d80d44>] kernel_init_freeable+0x1b8/0x1d8

    [    4.034026] [<ffffff8008a48560>] kernel_init+0x10/0x100

    [    4.039233] [<ffffff8008084a90>] ret_from_fork+0x10/0x18

    [    4.044527] SMP: stopping secondary CPUs

    [    4.048433] Kernel Offset: disabled

    [    4.051904] CPU features: 0x002004

    [    4.055288] Memory Limit: none

    [    4.058330] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,10)

  • 0 in reply to khabnl

    Hi Kiman,

     

    Thanks for posting the steps you followed, that makes it much easier to understand where you are getting stuck.

     

    I do not see any instructions that you've listed for extracting the ROOTFS to the external file system.  Usually, this is done by creating a second EXT4 partition on the SD card like this:

     

    image

     

    Once you have the second partition in place, you can extract the packed ROOTFS tarball from PetaLinux to this partition.  When Linux boots on UltraZed, it will attempt to mount the EXT4 partition on the SD card and use its contents as the persistent root filesystem.

     

    image

     

    Further details are available for you in the Xilinx UG1144 reference guide:

     

    https://www.xilinx.com/support/documentation/sw_manuals/xilinx2018_2/ug1144-petalinux-tools-reference-guide.pdf

     

    Best Regards,

     

    -Kevin