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
Contributor
Contributor
116 Views
Registered: ‎09-24-2009

Avnet Ultrazed-EV booting stopped after bootconsole [cdns0] disabled

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. but still the same problem.

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 Kudos
1 Reply
Newbie drozwood90
Newbie
76 Views
Registered: ‎06-05-2014

Re: Avnet Ultrazed-EV booting stopped after bootconsole [cdns0] disabled

Hi there,

We have a similar thread going on Element 14.  You might want to jump on there and see if we can get everyone all set!

https://www.element14.com/community/thread/73139/l/ultrazed-ev-bootconsole-cdns0-disabled

--Dan

0 Kudos