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: 
Contributor
Contributor
913 Views
Registered: ‎05-31-2019

SD card does not boot in ZCU104

Hi,

I am trying to boot my ZCU104 board from an SD card. I followed the instructions: on Page 38 of the Petalinux tools documentation(https://www.xilinx.com/support/documentation/sw_manuals/xilinx2018_2/ug1144-petalinux-tools-reference-guide.pdf). I copied the BOOT.bin and the image.ub files from mypetalinux-project/images/linux to the SD card directly which is partitioned fully as FAT32 and labeled BOOT. On connecting the FPGA with my PC nothing shows up in the serial console and the LED stays red.

So, I downloaded the prebuilt images for ZCU104 from here (https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/57639129/Zynq+2018.3+Release) and loaded their files on the SD card, it boots normally. The LED is green and I am able to see the boot messages on the console. 

I am not sure why when I load my BOOT.bin and image.ub from the petalinux project the console stays blank. I followed the following steps to build my project:

petalinux-config --get-hw-description=/path/system.hdf
[Change machine name to zcu104-reva and changed Root file system -> SD card]
petalinux-config -c kernel
[General setup -> cancel Initial RAM filesystem and RAM disk support]
petalinux-config -c rootfs
[Filesystem Packages–> misc, select packagegroup-core-buildessential->include all the packages]
petalinux-build
[Project builds successfully at this stage]
goto mypetalinux-project->images->linux
Execute the following command:
petalinux-package --boot --fsbl zynqmp.fsbl --fpga system.bit --pmufw pmufw.elf --u-boot

After this, I copy the generated BOOT.bin and the image.ub files to the SD card. But when I set the board to boot mode and connect to my PC nothing comes up in the console. If anyone can suggest what I am doing wrong here that will be of utmost help. Thanks!

0 Kudos
42 Replies
Scholar watari
Scholar
897 Views
Registered: ‎06-16-2013

Re: SD card does not boot in ZCU104

Hi @maju42 

 

Would you make sure boot mode (SW) on ZCU104 ?

Is it "SD boot mode" ?

 

Best regards,

0 Kudos
Contributor
Contributor
889 Views
Registered: ‎05-31-2019

Re: SD card does not boot in ZCU104

Hi @watari , Yes it is set to SD boot mode (OFF,OFF,OFF,ON)[Page 16 fn the documentation] . The issue is when I load the prebuilt BOOT.bin and image.ub to the SD card (from here), it boots successfully. But, when I load the BOOT.bin and image.ub from my own petalinux project, nothing comes up in the console. I followed the steps as I wrote above to generate these files and to configure my project.

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

Re: SD card does not boot in ZCU104

Hi @maju42 

 

Would you share boot message on serial console ?

 

Best regards,

0 Kudos
Contributor
Contributor
877 Views
Registered: ‎05-31-2019

Re: SD card does not boot in ZCU104

Hi @watari , Thank you for the quick reply. Here is what I get in the console when I put prebuilt image files:

[18:04:08:156] Xilinx Zynq MP First Stage Boot Loader ␊
[18:04:08:156] ␍Release 2018.3   Dec  6 2018  -  12:16:27␍␊
[18:04:10:028] NOTICE:  ATF running on XCZU7EV/silicon v4/RTL5.1 at 0xfffea000␍␊
[18:04:10:028] NOTICE:  BL31: Secure code at 0x0␍␊
[18:04:10:028] NOTICE:  BL31: Non secure code at 0x10080000␍␊
[18:04:10:028] NOTICE:  BL31: v1.5(release):xilinx-v2018.2-919-g08560c36␍␊
[18:04:10:044] NOTICE:  BL31: Built : 12:22:13, Dec  6 2018␍␊
[18:04:10:188] PMUFW:⇥	v1.1␍␊
[18:04:11:196] ␍␊
[18:04:11:196] ␍␊
[18:04:11:196] U-Boot 2018.01 (Dec 06 2018 - 12:13:16 +0000) Xilinx ZynqMP ZCU104 revC␍␊
[18:04:11:212] ␍␊
[18:04:11:212] I2C:   ready␍␊
[18:04:11:212] DRAM:  2 GiB␍␊
[18:04:11:404] EL Level:⇥	EL2␍␊
[18:04:11:420] Chip ID:⇥	zu7ev␍␊
[18:04:11:436] MMC:   mmc@ff170000: 0 (SD)␍␊
[18:04:11:532] SF: Detected n25q512a with page size 256 Bytes, erase size 64 KiB, total 64 MiB␍␊
[18:04:11:580] *** Warning - bad CRC, using default environment␍␊
[18:04:11:580] ␍␊
[18:04:11:580] In:    serial@ff000000␍␊
[18:04:11:580] Out:   serial@ff000000␍␊
[18:04:11:580] Err:   serial@ff000000␍␊
[18:04:11:580] Model: ZynqMP ZCU104 RevC␍␊
[18:04:11:596] Board: Xilinx ZynqMP␍␊
[18:04:11:596] Bootmode: LVL_SHFT_SD_MODE1␍␊
[18:04:11:596] Net:   ZYNQ GEM: ff0e0000, phyaddr c, interface rgmii-id␍␊
[18:04:11:612] eth0: ethernet@ff0e0000␍␊
[18:04:11:612] U-BOOT for xilinx-zcu104-2018_3␍␊
[18:04:11:612] ␍␊
[18:04:11:612] ethernet@ff0e0000 Waiting for PHY auto negotiation to complete......................................... TIMEOUT !␍␊
[18:04:32:076] Hit any key to stop autoboot:  4 <0x08><0x08><0x08> 3 <0x08><0x08><0x08> 2 <0x08><0x08><0x08> 1 <0x08><0x08><0x08> 0 ␍␊
[18:04:36:092] Device: mmc@ff170000␍␊
[18:04:36:092] Manufacturer ID: 3␍␊
[18:04:36:092] OEM: 5344␍␊
[18:04:36:108] Name: SC16G ␍␊
[18:04:36:108] Tran Speed: 50000000␍␊
[18:04:36:108] Rd Block Len: 512␍␊
[18:04:36:108] SD version 3.0␍␊
[18:04:36:108] High Capacity: Yes␍␊
[18:04:36:108] Capacity: 14.8 GiB␍␊
[18:04:36:108] Bus Width: 4-bit␍␊
[18:04:36:108] Erase Group Size: 512 Bytes␍␊
[18:04:36:124] reading image.ub␍␊
[18:04:42:044] 90713504 bytes read in 5916 ms (14.6 MiB/s)␍␊
[18:04:42:044] ## Loading kernel from FIT Image at 10000000 ...␍␊
[18:04:42:044]    Using 'conf@system-top.dtb' configuration␍␊
[18:04:42:044]    Trying 'kernel@1' kernel subimage␍␊
[18:04:42:060]      Description:  Linux kernel␍␊
[18:04:42:060]      Type:         Kernel Image␍␊
[18:04:42:060]      Compression:  gzip compressed␍␊
[18:04:42:060]      Data Start:   0x10000108␍␊
[18:04:42:060]      Data Size:    7083898 Bytes = 6.8 MiB␍␊
[18:04:42:060]      Architecture: AArch64␍␊
[18:04:42:076]      OS:           Linux␍␊
[18:04:42:076]      Load Address: 0x00080000␍␊
[18:04:42:076]      Entry Point:  0x00080000␍␊
[18:04:42:076]      Hash algo:    sha1␍␊
[18:04:42:076]      Hash value:   86126070cbc7d02bdb428991e0aebcc66089189c␍␊
[18:04:42:092]    Verifying Hash Integrity ... sha1+ OK␍␊
[18:04:42:172] ## Loading ramdisk from FIT Image at 10000000 ...␍␊
[18:04:42:172]    Using 'conf@system-top.dtb' configuration␍␊
[18:04:42:188]    Trying 'ramdisk@1' ramdisk subimage␍␊
[18:04:42:188]      Description:  petalinux-user-image␍␊
[18:04:42:188]      Type:         RAMDisk Image␍␊
[18:04:42:188]      Compression:  gzip compressed␍␊
[18:04:42:204]      Data Start:   0x106cb58c␍␊
[18:04:42:204]      Data Size:    83587714 Bytes = 79.7 MiB␍␊
[18:04:42:204]      Architecture: AArch64␍␊
[18:04:42:204]      OS:           Linux␍␊
[18:04:42:204]      Load Address: unavailable␍␊
[18:04:42:204]      Entry Point:  unavailable␍␊
[18:04:42:220]      Hash algo:    sha1␍␊
[18:04:42:220]      Hash value:   4a5485346e9506f0a2526457abf1dc42b5055f9a␍␊
[18:04:42:220]    Verifying Hash Integrity ... sha1+ OK␍␊
[18:04:43:228] ## Loading fdt from FIT Image at 10000000 ...␍␊
[18:04:43:228]    Using 'conf@system-top.dtb' configuration␍␊
[18:04:43:228]    Trying 'fdt@system-top.dtb' fdt subimage␍␊
[18:04:43:244]      Description:  Flattened Device Tree blob␍␊
[18:04:43:244]      Type:         Flat Device Tree␍␊
[18:04:43:244]      Compression:  uncompressed␍␊
[18:04:43:244]      Data Start:   0x106c1988␍␊
[18:04:43:244]      Data Size:    39741 Bytes = 38.8 KiB␍␊
[18:04:43:260]      Architecture: AArch64␍␊
[18:04:43:260]      Hash algo:    sha1␍␊
[18:04:43:260]      Hash value:   c7a49ba70341800ad4f8f2319d00a96c89f19155␍␊
[18:04:43:260]    Verifying Hash Integrity ... sha1+ OK␍␊
[18:04:43:260]    Booting using the fdt blob at 0x106c1988␍␊
[18:04:43:276]    Uncompressing Kernel Image ... OK␍␊
[18:04:43:516]    Loading Ramdisk to 03048000, end 07fff282 ... OK␍␊
[18:04:43:884]    Loading Device Tree to 000000000303b000, end 0000000003047b3c ... OK␍␊
[18:04:43:900] ␍␊
[18:04:43:900] Starting kernel ...␍␊
[18:04:43:900] ␍␊
[18:04:43:916] [    0.000000] Booting Linux on physical CPU 0x0␍␊
[18:04:43:916] [    0.000000] Linux version 4.14.0-xilinx-v2018.3 (oe-user@oe-host) (gcc version 7.3.0 (GCC)) #1 SMP Thu Dec 6 12:13:44 UTC 2018␍␊
[18:04:43:932] [    0.000000] Boot CPU: AArch64 Processor [410fd034]␍␊
[18:04:43:932] [    0.000000] Machine model: ZynqMP ZCU104 RevC␍␊
[18:04:43:948] [    0.000000] earlycon: cdns0 at MMIO 0x00000000ff000000 (options '115200n8')␍␊
[18:04:43:948] [    0.000000] bootconsole [cdns0] enabled␍␊
[18:04:43:948] [    0.000000] efi: Getting EFI parameters from FDT:␍␊
[18:04:43:964] [    0.000000] efi: UEFI not found.␍␊
[18:04:43:964] [    0.000000] cma: Reserved 1000 MiB at 0x0000000041400000␍␊
[18:04:43:996] [    0.000000] psci: probing for conduit method from DT.␍␊
[18:04:43:996] [    0.000000] psci: PSCIv1.1 detected in firmware.␍␊
[18:04:44:012] [    0.000000] psci: Using standard PSCI v0.2 function IDs␍␊
[18:04:44:012] [    0.000000] psci: MIGRATE_INFO_TYPE not supported.␍␊
[18:04:44:012] [    0.000000] percpu: Embedded 21 pages/cpu @ffffffc07fe6a000 s46488 r8192 d31336 u86016␍␊
[18:04:44:028] [    0.000000] Detected VIPT I-cache on CPU0␍␊
[18:04:44:028] [    0.000000] CPU features: enabling workaround for ARM erratum 845719␍␊
[18:04:44:028] [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 516867␍␊
[18:04:44:044] [    0.000000] Kernel command line: earlycon console=ttyPS0,115200 clk_ignore_unused␍␊
[18:04:44:044] [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)␍␊
[18:04:44:060] [    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)␍␊
[18:04:44:060] [    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)␍␊
[18:04:44:092] [    0.000000] Memory: 941336K/2096128K available (10108K kernel code, 664K rwdata, 3224K rodata, 512K init, 2167K bss, 130792K reserved, 1024000K cma-reserved)␍␊
[18:04:44:107] [    0.000000] Virtual kernel memory layout:␍␊
[18:04:44:107] [    0.000000]     modules : 0xffffff8000000000 - 0xffffff8008000000   (   128 MB)␍␊
[18:04:44:107] [    0.000000]     vmalloc : 0xffffff8008000000 - 0xffffffbebfff0000   (   250 GB)␍␊
[18:04:44:123] [    0.000000]       .text : 0xffffff8008080000 - 0xffffff8008a60000   ( 10112 KB)␍␊
[18:04:44:123] [    0.000000]     .rodata : 0xffffff8008a60000 - 0xffffff8008d90000   (  3264 KB)␍␊
[18:04:44:139] [    0.000000]       .init : 0xffffff8008d90000 - 0xffffff8008e10000   (   512 KB)␍␊
[18:04:44:139] [    0.000000]       .data : 0xffffff8008e10000 - 0xffffff8008eb6200   (   665 KB)␍␊
[18:04:44:156] [    0.000000]        .bss : 0xffffff8008eb6200 - 0xffffff80090d40b0   (  2168 KB)␍␊
[18:04:44:156] [    0.000000]     fixed   : 0xffffffbefe7fd000 - 0xffffffbefec00000   (  4108 KB)␍␊
[18:04:44:172] [    0.000000]     PCI I/O : 0xffffffbefee00000 - 0xffffffbeffe00000   (    16 MB)␍␊
[18:04:44:172] [    0.000000]     vmemmap : 0xffffffbf00000000 - 0xffffffc000000000   (     4 GB maximum)␍␊
[18:04:44:188] [    0.000000]               0xffffffbf00000000 - 0xffffffbf01bfc800   (    27 MB actual)␍␊
[18:04:44:188] [    0.000000]     memory  : 0xffffffc000000000 - 0xffffffc07ff00000   (  2047 MB)␍␊
[18:04:44:204] [    0.000000] Hierarchical RCU implementation.␍␊
[18:04:44:204] [    0.000000] ⇥	RCU event tracing is enabled.␍␊
[18:04:44:204] [    0.000000] ⇥	RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.␍␊
[18:04:44:204] [    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4␍␊
[18:04:44:220] [    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0␍␊
[18:04:44:220] [    0.000000] GIC: Adjusting CPU interface base to 0x00000000f902f000␍␊
[18:04:44:235] [    0.000000] GIC: Using split EOI/Deactivate mode␍␊
[18:04:44:235] [    0.000000] arch_timer: cp15 timer(s) running at 100.00MHz (phys).␍␊
[18:04:44:235] [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x171024e7e0, max_idle_ns: 440795205315 ns␍␊
[18:04:44:252] [    0.000003] sched_clock: 56 bits at 100MHz, resolution 10ns, wraps every 4398046511100ns␍␊
[18:04:44:252] [    0.008390] Console: colour dummy device 80x25␍␊
[18:04:44:268] [    0.012474] Calibrating delay loop (skipped), value calculated using timer frequency.. 200.00 BogoMIPS (lpj=400000)␍␊
[18:04:44:268] [    0.022841] pid_max: default: 32768 minimum: 301␍␊
[18:04:44:284] [    0.027520] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)␍␊
[18:04:44:284] [    0.034092] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes)␍␊
[18:04:44:284] [    0.041789] ASID allocator initialised with 65536 entries␍␊
[18:04:44:300] [    0.046592] Hierarchical SRCU implementation.␍␊
[18:04:44:300] [    0.051188] EFI services will not be available.␍␊
[18:04:44:300] [    0.055384] zynqmp_plat_init Platform Management API v1.1␍␊
[18:04:44:316] [    0.060729] zynqmp_plat_init Trustzone version v1.0␍␊
[18:04:44:316] [    0.065669] smp: Bringing up secondary CPUs ...␍␊
[18:04:44:316] [    0.070314] Detected VIPT I-cache on CPU1␍␊
[18:04:44:332] [    0.070343] CPU1: Booted secondary processor [410fd034]␍␊
[18:04:44:332] [    0.070612] Detected VIPT I-cache on CPU2␍␊
[18:04:44:332] [    0.070630] CPU2: Booted secondary processor [410fd034]␍␊
[18:04:44:332] [    0.070890] Detected VIPT I-cache on CPU3␍␊
[18:04:44:348] [    0.070908] CPU3: Booted secondary processor [410fd034]␍␊
[18:04:44:348] [    0.070949] smp: Brought up 1 node, 4 CPUs␍␊
[18:04:44:348] [    0.101642] SMP: Total of 4 processors activated.␍␊
[18:04:44:364] [    0.106314] CPU features: detected feature: 32-bit EL0 Support␍␊
[18:04:44:364] [    0.112112] CPU: All CPU(s) started at EL2␍␊
[18:04:44:364] [    0.116184] alternatives: patching kernel code␍␊
[18:04:44:364] [    0.121280] devtmpfs: initialized␍␊
[18:04:44:380] [    0.127851] random: get_random_u32 called from bucket_table_alloc+0x108/0x260 with crng_init=0␍␊
[18:04:44:380] [    0.132604] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns␍␊
[18:04:44:396] [    0.142135] futex hash table entries: 1024 (order: 5, 131072 bytes)␍␊
[18:04:44:412] [    0.166882] xor: measuring software checksum speed␍␊
[18:04:44:444] [    0.204483]    8regs     :  2303.000 MB/sec␍␊
[18:04:44:492] [    0.244512]    8regs_prefetch:  2053.000 MB/sec␍␊
[18:04:44:524] [    0.284541]    32regs    :  2830.000 MB/sec␍␊
[18:04:44:572] [    0.324572]    32regs_prefetch:  2379.000 MB/sec␍␊
[18:04:44:572] [    0.324600] xor: using function: 32regs (2830.000 MB/sec)␍␊
[18:04:44:572] [    0.328976] pinctrl core: initialized pinctrl subsystem␍␊
[18:04:44:588] [    0.329110] random: fast init done␍␊
[18:04:44:588] [    0.337956] NET: Registered protocol family 16␍␊
[18:04:44:588] [    0.342635] cpuidle: using governor menu␍␊
[18:04:44:604] [    0.346244] vdso: 2 pages (1 code @ ffffff8008a66000, 1 data @ ffffff8008e14000)␍␊
[18:04:44:604] [    0.353139] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.␍␊
[18:04:44:604] [    0.360407] DMA: preallocated 256 KiB pool for atomic allocations␍␊
[18:04:44:635] [    0.387347] reset_zynqmp reset-controller: Xilinx zynqmp reset driver probed␍␊
[18:04:44:635] [    0.389349] ARM CCI_400_r1 PMU driver probed␍␊
[18:04:44:635] [    0.393947] zynqmp-pinctrl ff180000.pinctrl: zynqmp pinctrl initialized␍␊
[18:04:44:651] [    0.408252] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages␍␊
[18:04:44:716] [    0.474260] raid6: int64x1  gen()   401 MB/s␍␊
[18:04:44:780] [    0.542331] raid6: int64x1  xor()   446 MB/s␍␊
[18:04:44:860] [    0.610389] raid6: int64x2  gen()   688 MB/s␍␊
[18:04:44:924] [    0.678413] raid6: int64x2  xor()   603 MB/s␍␊
[18:04:44:988] [    0.746459] raid6: int64x4  gen()  1042 MB/s␍␊
[18:04:45:052] [    0.814495] raid6: int64x4  xor()   740 MB/s␍␊
[18:04:45:132] [    0.882576] raid6: int64x8  gen()   980 MB/s␍␊
[18:04:45:196] [    0.950607] raid6: int64x8  xor()   743 MB/s␍␊
[18:04:45:260] [    1.018670] raid6: neonx1   gen()   726 MB/s␍␊
[18:04:45:324] [    1.086698] raid6: neonx1   xor()   853 MB/s␍␊
[18:04:45:404] [    1.154773] raid6: neonx2   gen()  1170 MB/s␍␊
[18:04:45:468] [    1.222784] raid6: neonx2   xor()  1207 MB/s␍␊
[18:04:45:532] [    1.290837] raid6: neonx4   gen()  1506 MB/s␍␊
[18:04:45:596] [    1.358869] raid6: neonx4   xor()  1441 MB/s␍␊
[18:04:45:676] [    1.426914] raid6: neonx8   gen()  1651 MB/s␍␊
[18:04:45:740] [    1.494970] raid6: neonx8   xor()  1532 MB/s␍␊
[18:04:45:740] [    1.494997] raid6: using algorithm neonx8 gen() 1651 MB/s␍␊
[18:04:45:755] [    1.498963] raid6: .... xor() 1532 MB/s, rmw enabled␍␊
[18:04:45:755] [    1.503892] raid6: using neon recovery algorithm␍␊
[18:04:45:755] [    1.509328] SCSI subsystem initialized␍␊
[18:04:45:755] [    1.512357] usbcore: registered new interface driver usbfs␍␊
[18:04:45:771] [    1.517676] usbcore: registered new interface driver hub␍␊
[18:04:45:771] [    1.522951] usbcore: registered new device driver usb␍␊
[18:04:45:771] [    1.528001] media: Linux media interface: v0.10␍␊
[18:04:45:787] [    1.532456] Linux video capture interface: v2.00␍␊
[18:04:45:787] [    1.537054] pps_core: LinuxPPS API ver. 1 registered␍␊
[18:04:45:787] [    1.541953] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>␍␊
[18:04:45:804] [    1.551045] PTP clock support registered␍␊
[18:04:45:804] [    1.554942] EDAC MC: Ver: 3.0.0␍␊
[18:04:45:804] [    1.558330] zynqmp-ipi ff9905c0.mailbox: Probed ZynqMP IPI Mailbox driver.␍␊
[18:04:45:819] [    1.565042] FPGA manager framework␍␊
[18:04:45:819] [    1.568361] fpga-region fpga-full: FPGA Region probed␍␊
[18:04:45:819] [    1.573397] Advanced Linux Sound Architecture Driver Initialized.␍␊
[18:04:45:836] [    1.579560] Bluetooth: Core ver 2.22␍␊
[18:04:45:836] [    1.582887] NET: Registered protocol family 31␍␊
[18:04:45:836] [    1.587280] Bluetooth: HCI device and connection manager initialized␍␊
[18:04:45:852] [    1.593596] Bluetooth: HCI socket layer initialized␍␊
[18:04:45:852] [    1.598439] Bluetooth: L2CAP socket layer initialized␍␊
[18:04:45:852] [    1.603464] Bluetooth: SCO socket layer initialized␍␊
[18:04:45:852] [    1.608788] clocksource: Switched to clocksource arch_sys_counter␍␊
[18:04:45:868] [    1.614429] VFS: Disk quotas dquot_6.6.0␍␊
[18:04:45:868] [    1.618285] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)␍␊
[18:04:45:868] [    1.628923] NET: Registered protocol family 2␍␊
[18:04:45:883] [    1.629686] TCP established hash table entries: 16384 (order: 5, 131072 bytes)␍␊
[18:04:45:883] [    1.636687] TCP bind hash table entries: 16384 (order: 6, 262144 bytes)␍␊
[18:04:45:900] [    1.643360] TCP: Hash tables configured (established 16384 bind 16384)␍␊
[18:04:45:900] [    1.649707] UDP hash table entries: 1024 (order: 3, 32768 bytes)␍␊
[18:04:45:900] [    1.655650] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)␍␊
[18:04:45:916] [    1.662126] NET: Registered protocol family 1␍␊
[18:04:45:916] [    1.666527] RPC: Registered named UNIX socket transport module.␍␊
[18:04:45:916] [    1.672226] RPC: Registered udp transport module.␍␊
[18:04:45:932] [    1.676893] RPC: Registered tcp transport module.␍␊
[18:04:45:932] [    1.681563] RPC: Registered tcp NFSv4.1 backchannel transport module.␍␊
[18:04:45:932] [    1.688065] Trying to unpack rootfs image as initramfs...␍␊
[18:04:49:548] [    5.305333] Freeing initrd memory: 81628K␍␊
[18:04:49:548] [    5.306029] hw perfevents: no interrupt-affinity property for /pmu, guessing.␍␊
[18:04:49:564] [    5.310964] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available␍␊
[18:04:49:564] [    5.319194] audit: initializing netlink subsys (disabled)␍␊
[18:04:49:580] [    5.323934] audit: type=2000 audit(5.264:1): state=initialized audit_enabled=0 res=1␍␊
[18:04:49:580] [    5.324260] workingset: timestamp_bits=62 max_order=19 bucket_order=0␍␊
[18:04:49:596] [    5.338596] NFS: Registering the id_resolver key type␍␊
[18:04:49:596] [    5.342994] Key type id_resolver registered␍␊
[18:04:49:596] [    5.347132] Key type id_legacy registered␍␊
[18:04:49:596] [    5.351115] nfs4filelayout_init: NFSv4 File Layout Driver Registering...␍␊
[18:04:49:612] [    5.357783] jffs2: version 2.2. (NAND) <0xc2><0xa9> 2001-2006 Red Hat, Inc.␍␊
[18:04:49:628] [    5.390288] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)␍␊
[18:04:49:644] [    5.392031] io scheduler noop registered␍␊
[18:04:49:644] [    5.395932] io scheduler deadline registered␍␊
[18:04:49:644] [    5.400178] io scheduler cfq registered (default)␍␊
[18:04:49:660] [    5.404837] io scheduler mq-deadline registered␍␊
[18:04:49:660] [    5.409334] io scheduler kyber registered␍␊
[18:04:49:660] [    5.414605] xilinx-dpdma fd4c0000.dma: Xilinx DPDMA engine is probed␍␊
[18:04:49:676] [    5.419982] xilinx-zynqmp-dma fd500000.dma: ZynqMP DMA driver Probe success␍␊
[18:04:49:676] [    5.426691] xilinx-zynqmp-dma fd510000.dma: ZynqMP DMA driver Probe success␍␊
[18:04:49:692] [    5.433609] xilinx-zynqmp-dma fd520000.dma: ZynqMP DMA driver Probe success␍␊
[18:04:49:692] [    5.440526] xilinx-zynqmp-dma fd530000.dma: ZynqMP DMA driver Probe success␍␊
[18:04:49:692] [    5.447449] xilinx-zynqmp-dma fd540000.dma: ZynqMP DMA driver Probe success␍␊
[18:04:49:708] [    5.454371] xilinx-zynqmp-dma fd550000.dma: ZynqMP DMA driver Probe success␍␊
[18:04:49:708] [    5.461288] xilinx-zynqmp-dma fd560000.dma: ZynqMP DMA driver Probe success␍␊
[18:04:49:723] [    5.468208] xilinx-zynqmp-dma fd570000.dma: ZynqMP DMA driver Probe success␍␊
[18:04:49:723] [    5.475193] xilinx-zynqmp-dma ffa80000.dma: ZynqMP DMA driver Probe success␍␊
[18:04:49:740] [    5.482047] xilinx-zynqmp-dma ffa90000.dma: ZynqMP DMA driver Probe success␍␊
[18:04:49:740] [    5.488963] xilinx-zynqmp-dma ffaa0000.dma: ZynqMP DMA driver Probe success␍␊
[18:04:49:740] [    5.495887] xilinx-zynqmp-dma ffab0000.dma: ZynqMP DMA driver Probe success␍␊
[18:04:49:756] [    5.502806] xilinx-zynqmp-dma ffac0000.dma: ZynqMP DMA driver Probe success␍␊
[18:04:49:756] [    5.509732] xilinx-zynqmp-dma ffad0000.dma: ZynqMP DMA driver Probe success␍␊
[18:04:49:772] [    5.516650] xilinx-zynqmp-dma ffae0000.dma: ZynqMP DMA driver Probe success␍␊
[18:04:49:772] [    5.523571] xilinx-zynqmp-dma ffaf0000.dma: ZynqMP DMA driver Probe success␍␊
[18:04:49:788] [    5.530540] xilinx-frmbuf a0000000.v_frmbuf_rd: Probe deferred due to GPIO reset defer␍␊
[18:04:49:788] [    5.538258] xilinx-frmbuf a0010000.v_frmbuf_wr: Probe deferred due to GPIO reset defer␍␊
[18:04:49:819] [    5.570669] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled␍␊
[18:04:49:819] [    5.574634] cacheinfo: Unable to detect cache hierarchy for CPU 0␍␊
[18:04:49:836] [    5.581398] brd: module loaded␍␊
[18:04:49:836] [    5.584705] loop: module loaded␍␊
[18:04:49:836] [    5.585608] ahci-ceva fd0c0000.ahci: couldn't get PHY in node ahci: -517␍␊
[18:04:49:836] [    5.590395] mtdoops: mtd device (mtddev=name/number) must be supplied␍␊
[18:04:49:852] [    5.597685] m25p80 spi0.0: n25q512a (65536 Kbytes)␍␊
[18:04:49:852] [    5.601421] 4 ofpart partitions found on MTD device spi0.0␍␊
[18:04:49:852] [    5.606849] Creating 4 MTD partitions on "spi0.0":␍␊
[18:04:49:867] [    5.611619] 0x000000000000-0x000001e00000 : "boot"␍␊
[18:04:49:867] [    5.616808] 0x000001e00000-0x000001e40000 : "bootenv"␍␊
[18:04:49:867] [    5.621754] 0x000001e40000-0x000004000000 : "kernel"␍␊
[18:04:49:883] [    5.626674] 0x000004000000-0x000004000000 : "spare"␍␊
[18:04:49:883] [    5.631157] mtd: partition "spare" is out of reach -- disabled␍␊
[18:04:49:883] [    5.638134] libphy: Fixed MDIO Bus: probed␍␊
[18:04:49:883] [    5.641948] tun: Universal TUN/TAP device driver, 1.6␍␊
[18:04:49:899] [    5.646189] CAN device driver interface␍␊
[18:04:49:899] [    5.652053] macb ff0e0000.ethernet: Not enabling partial store and forward␍␊
[18:04:49:899] [    5.657073] libphy: MACB_mii_bus: probed␍␊
[18:04:49:916] [    5.662568] macb ff0e0000.ethernet eth0: Cadence GEM rev 0x50070106 at 0xff0e0000 irq 31 (00:0a:35:00:22:01)␍␊
[18:04:49:916] [    5.670353] TI DP83867 ff0e0000.ethernet-ffffffff:0c: attached PHY driver [TI DP83867] (mii_bus:phy_addr=ff0e0000.ethernet-ffffffff:0c, irq=POLL)␍␊
[18:04:49:932] [    5.683959] usbcore: registered new interface driver asix␍␊
[18:04:49:932] [    5.688724] usbcore: registered new interface driver ax88179_178a␍␊
[18:04:49:948] [    5.694755] usbcore: registered new interface driver cdc_ether␍␊
[18:04:49:948] [    5.700549] usbcore: registered new interface driver net1080␍␊
[18:04:49:964] [    5.706172] usbcore: registered new interface driver cdc_subset␍␊
[18:04:49:964] [    5.712055] usbcore: registered new interface driver zaurus␍␊
[18:04:49:964] [    5.717597] usbcore: registered new interface driver cdc_ncm␍␊
[18:04:49:979] [    5.723478] xilinx-axipmon ffa00000.perf-monitor: Probed Xilinx APM␍␊
[18:04:49:979] [    5.730876] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver␍␊
[18:04:49:979] [    5.735908] ehci-pci: EHCI PCI platform driver␍␊
[18:04:49:996] [    5.740598] usbcore: registered new interface driver uas␍␊
[18:04:49:996] [    5.745626] usbcore: registered new interface driver usb-storage␍␊
[18:04:49:996] [    5.752042] rtc_zynqmp ffa60000.rtc: rtc core: registered ffa60000.rtc as rtc0␍␊
[18:04:50:012] [    5.758792] i2c /dev entries driver␍␊
[18:04:50:012] [    5.762858] IR NEC protocol handler initialized␍␊
[18:04:50:012] [    5.766702] IR RC5(x/sz) protocol handler initialized␍␊
[18:04:50:028] [    5.771716] IR RC6 protocol handler initialized␍␊
[18:04:50:028] [    5.776214] IR JVC protocol handler initialized␍␊
[18:04:50:028] [    5.780712] IR Sony protocol handler initialized␍␊
[18:04:50:044] [    5.785299] IR SANYO protocol handler initialized␍␊
[18:04:50:044] [    5.789967] IR Sharp protocol handler initialized␍␊
[18:04:50:044] [    5.794638] IR MCE Keyboard/mouse protocol handler initialized␍␊
[18:04:50:044] [    5.800434] IR XMP protocol handler initialized␍␊
[18:04:50:060] [    5.806288] usbcore: registered new interface driver uvcvideo␍␊
[18:04:50:060] [    5.810643] USB Video Class driver (1.1.1)␍␊
[18:04:50:060] [    5.815240] cdns-wdt fd4d0000.watchdog: Xilinx Watchdog Timer at ffffff800915d000 with timeout 60s␍␊
[18:04:50:076] [    5.823787] cdns-wdt ff150000.watchdog: Xilinx Watchdog Timer at ffffff8009165000 with timeout 10s␍␊
[18:04:50:076] [    5.832713] Bluetooth: HCI UART driver ver 2.3␍␊
[18:04:50:092] [    5.836942] Bluetooth: HCI UART protocol H4 registered␍␊
[18:04:50:092] [    5.842041] Bluetooth: HCI UART protocol BCSP registered␍␊
[18:04:50:092] [    5.847340] Bluetooth: HCI UART protocol LL registered␍␊
[18:04:50:108] [    5.852422] Bluetooth: HCI UART protocol ATH3K registered␍␊
[18:04:50:108] [    5.857784] Bluetooth: HCI UART protocol Three-wire (H5) registered␍␊
[18:04:50:108] [    5.864049] Bluetooth: HCI UART protocol Intel registered␍␊
[18:04:50:124] [    5.869376] Bluetooth: HCI UART protocol QCA registered␍␊
[18:04:50:124] [    5.874594] usbcore: registered new interface driver bcm203x␍␊
[18:04:50:124] [    5.880220] usbcore: registered new interface driver bpa10x␍␊
[18:04:50:140] [    5.885749] usbcore: registered new interface driver bfusb␍␊
[18:04:50:140] [    5.891198] usbcore: registered new interface driver btusb␍␊
[18:04:50:140] [    5.896624] Bluetooth: Generic Bluetooth SDIO driver ver 0.1␍␊
[18:04:50:156] [    5.902291] usbcore: registered new interface driver ath3k␍␊
[18:04:50:156] [    5.907817] EDAC MC: ECC not enabled␍␊
[18:04:50:156] [    5.911401] EDAC DEVICE0: Giving out device to module zynqmp-ocm-edac controller zynqmp_ocm: DEV ff960000.memory-controller (INTERRUPT)␍␊
[18:04:50:172] [    5.924203] sdhci: Secure Digital Host Controller Interface driver␍␊
[18:04:50:188] [    5.929495] sdhci: Copyright(c) Pierre Ossman␍␊
[18:04:50:188] [    5.933817] sdhci-pltfm: SDHCI platform and OF driver helper␍␊
[18:04:50:236] [    5.984798] mmc0: SDHCI controller on ff170000.mmc [ff170000.mmc] using ADMA 64-bit␍␊
[18:04:50:236] [    5.992695] ledtrig-cpu: registered to indicate activity on CPUs␍␊
[18:04:50:236] [    5.993190] usbcore: registered new interface driver usbhid␍␊
[18:04:50:252] [    5.998590] usbhid: USB HID core driver␍␊
[18:04:50:252] [    6.004229] fpga_manager fpga0: Xilinx ZynqMP FPGA Manager registered␍␊
[18:04:50:252] [    6.010151] usbcore: registered new interface driver snd-usb-audio␍␊
[18:04:50:268] [    6.015684] pktgen: Packet Generator for packet performance testing. Version: 2.75␍␊
[18:04:50:268] [    6.024657] Netfilter messages via NETLINK v0.30.␍␊
[18:04:50:283] [    6.027255] ip_tables: (C) 2000-2006 Netfilter Core Team␍␊
[18:04:50:283] [    6.032535] Initializing XFRM netlink socket␍␊
[18:04:50:283] [    6.036705] NET: Registered protocol family 10␍␊
[18:04:50:283] [    6.041466] Segment Routing with IPv6␍␊
[18:04:50:299] [    6.044728] ip6_tables: (C) 2000-2006 Netfilter Core Team␍␊
[18:04:50:299] [    6.050176] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver␍␊
[18:04:50:299] [    6.056238] NET: Registered protocol family 17␍␊
[18:04:50:315] [    6.060360] NET: Registered protocol family 15␍␊
[18:04:50:315] [    6.064773] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.␍␊
[18:04:50:332] [    6.077654] Ebtables v2.0 registered␍␊
[18:04:50:332] [    6.081286] can: controller area network core (rev 20170425 abi 9)␍␊
[18:04:50:332] [    6.087367] NET: Registered protocol family 29␍␊
[18:04:50:348] [    6.091759] can: raw protocol (rev 20170425)␍␊
[18:04:50:348] [    6.095988] can: broadcast manager protocol (rev 20170425 t)␍␊
[18:04:50:348] [    6.101613] can: netlink gateway (rev 20170425) max_hops=1␍␊
[18:04:50:364] [    6.107252] Bluetooth: RFCOMM TTY layer initialized␍␊
[18:04:50:364] [    6.111911] Bluetooth: RFCOMM socket layer initialized␍␊
[18:04:50:364] [    6.117030] Bluetooth: RFCOMM ver 1.11␍␊
[18:04:50:364] [    6.120105] mmc0: new high speed SDHC card at address aaaa␍␊
[18:04:50:380] [    6.120284] mmcblk0: mmc0:aaaa SC16G 14.8 GiB ␍␊
[18:04:50:380] [    6.122381]  mmcblk0: p1␍␊
[18:04:50:380] [    6.133102] Bluetooth: BNEP (Ethernet Emulation) ver 1.3␍␊
[18:04:50:395] [    6.138374] Bluetooth: BNEP filters: protocol multicast␍␊
[18:04:50:395] [    6.143567] Bluetooth: BNEP socket layer initialized␍␊
[18:04:50:395] [    6.148495] Bluetooth: HIDP (Human Interface Emulation) ver 1.2␍␊
[18:04:50:412] [    6.154378] Bluetooth: HIDP socket layer initialized␍␊
[18:04:50:412] [    6.159434] 9pnet: Installing 9P2000 support␍␊
[18:04:50:412] [    6.163560] Key type dns_resolver registered␍␊
[18:04:50:412] [    6.168128] registered taskstats version 1␍␊
[18:04:50:428] [    6.172178] Btrfs loaded, crc32c=crc32c-generic␍␊
[18:04:50:428] [    6.180927] ff000000.serial: ttyPS0 at MMIO 0xff000000 (irq = 41, base_baud = 6249999) is a xuartps␍<0xb7><0x05>⇥	⇥	<0x12><0x92><0x93>)S<0x82><0xc2><0xca><0xb2><0xea><0x05><0x1a><0xbd><0xb9><0xcd><0xbd><0xb1><0x95><0x81><0xda><0xd1><0xd1><0xe5>AM<0xc1><0xea><0x81>*<0xb9><0x85><0x89><0xb1><0x95><0x91>5R<0xda><0x05><0x02><0x02><0x02><0xb2>r<0x8a><0xca><0x82><0xc2><0xca><0xb2><0xea><0x05><0x1a><0xbd><0xb9><0xcd><0xbd><0xb1><0x95><0x81><0xda><0xd1><0xd1><0xe5>AM<0xc1><0xea><0x81>*<0xb9><0x85><0x89><0xb1><0x95><0x91>5R<0xda><0x05><0x02><0x02><0x02><0xb2>r<0x8a><0xca><0xa2><0xa2><0xc2><0xa2><0xea><0x05><0x12><0xbd><0xbd><0xd1><0x8d><0xbd><0xb9><0xcd><0xbd><0xb1><0x95><0x81><0xda><0x8d><0x91><0xb9><0xcd><0xc1><0xea><0x81>"<0xa5><0xcd><0x85><0x89><0xb1><0x95><0x91>5R<0xda><0x05><0x02><0x02><0x02><0xb2>r<0x8a><0xca><0xa2><0xa2><0xc2><0xa2><0xea><0x05><0x12><0xbd><0xbd><0xd1><0x8d><0xbd><0xb9><0xcd><0xbd><0xb1><0x95><0x81><0xda><0x8d><0x91><0xb9><0xcd><0xc1><0xea><0x81>"<0xa5><0xcd><0x85><0x89><0xb1><0x95><0x91>5R<0xda><0x05><0x02><0x02><0x02><0xb2>r<0x92><0x82><0x92><0xb2><0xba><0x92><0xea><0x05>2<0x99><0xc1><0x8a><0x82><0x82><0x82><0x82>r<0x9a><0x95><0xc9><0xa5><0x85><0xb1><0xe9><0x02><0xa2><0xd1><0xe5>AM<0xc5><0x02>␊
[18:04:50:460] <0xd1><0x81>j5%=<0x81><0x82><0xc2><0x99><0x99><0xc1><0x8a><0x82><0x82><0x82><0x82><0x02>BJ<0xc9><0xc5><0x81><0xea><0x02><0xa2><0x92>b<0x02><0x12><0x85><0xcd><0x95>}<0x89><0x85><0xd5><0x91><0x81><0xea><0x02><0xb2><0x92><0xa2><0xca><0xca><0xca><0xca>J<0x02>J<0xcd><0x81>␊
[18:04:50:460] <0x81><0xc2><0xd5><0x85><0xc9><0xd1><0xc1><0xcd>5R<0xfe>[    6.215899] xilinx-frmbuf a0000000.v_frmbuf_rd: Xilinx AXI frmbuf DMA_MEM_TO_DEV␍␊
[18:04:50:476] [    6.223361] xilinx-frmbuf a0000000.v_frmbuf_rd: Xilinx AXI FrameBuffer Engine Driver Probed!!␍␊
[18:04:50:476] [    6.231998] xilinx-frmbuf a0010000.v_frmbuf_wr: Xilinx AXI frmbuf DMA_DEV_TO_MEM␍␊
[18:04:50:492] [    6.239441] xilinx-frmbuf a0010000.v_frmbuf_wr: Xilinx AXI FrameBuffer Engine Driver Probed!!␍␊
[18:04:50:492] [    6.248285] xilinx-psgtr fd400000.zynqmp_phy: Lane:1 type:8 protocol:4 pll_locked:yes␍␊
[18:04:50:508] [    6.256421] PLL: shutdown␍␊
[18:04:50:508] [    6.259130] PLL: shutdown␍␊
[18:04:50:508] [    6.262118] PLL: enable␍␊
[18:04:50:508] [    6.264655] PLL: shutdown␍␊
[18:04:50:508] [    6.268211] PLL: enable␍␊
[18:04:50:508] [    6.270748] xilinx-dp-snd-codec fd4a0000.zynqmp-display:zynqmp_dp_snd_codec0: Xilinx DisplayPort Sound Codec probed␍␊
[18:04:50:524] [    6.281421] xilinx-dp-snd-pcm zynqmp_dp_snd_pcm0: Xilinx DisplayPort Sound PCM probed␍␊
[18:04:50:540] [    6.289456] xilinx-dp-snd-pcm zynqmp_dp_snd_pcm1: Xilinx DisplayPort Sound PCM probed␍␊
[18:04:50:540] [    6.297752] xilinx-dp-snd-card fd4a0000.zynqmp-display:zynqmp_dp_snd_card: xilinx-dp-snd-codec-dai <-> xilinx-dp-snd-codec-dai mapping ok␍␊
[18:04:50:556] [    6.310174] xilinx-dp-snd-card fd4a0000.zynqmp-display:zynqmp_dp_snd_card: xilinx-dp-snd-codec-dai <-> xilinx-dp-snd-codec-dai mapping ok␍␊
[18:04:50:572] [    6.322844] xilinx-dp-snd-card fd4a0000.zynqmp-display:zynqmp_dp_snd_card: Xilinx DisplayPort Sound Card probed␍␊
[18:04:50:572] [    6.333015] OF: graph: no port node found in /amba/zynqmp-display@fd4a0000␍␊
[18:04:50:588] [    6.339998] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).␍␊
[18:04:50:588] [    6.346600] [drm] No driver support for vblank timestamp query.␍␊
[18:04:50:604] [    6.352578] xlnx-drm xlnx-drm.0: bound fd4a0000.zynqmp-display (ops 0xffffff8008b17868)␍␊
[18:04:51:676] [    7.436799] [drm] Cannot find any crtc or sizes␍␊
[18:04:51:692] [    7.441545] [drm] Initialized xlnx 1.0.0 20130509 for fd4a0000.zynqmp-display on minor 0␍␊
[18:04:51:692] [    7.449648] zynqmp-display fd4a0000.zynqmp-display: ZynqMP DisplayPort Subsystem driver probed␍␊
[18:04:51:707] [    7.458603] xilinx-psgtr fd400000.zynqmp_phy: Lane:3 type:3 protocol:2 pll_locked:yes␍␊
[18:04:51:723] [    7.476544] ahci-ceva fd0c0000.ahci: AHCI 0001.0301 32 slots 2 ports 6 Gbps 0x3 impl platform mode␍␊
[18:04:51:723] [    7.485501] ahci-ceva fd0c0000.ahci: flags: 64bit ncq sntf pm clo only pmp fbs pio slum part ccc sds apst ␍␊
[18:04:51:739] [    7.495794] scsi host0: ahci-ceva␍␊
[18:04:51:739] [    7.499288] scsi host1: ahci-ceva␍␊
[18:04:51:739] [    7.502694] ata1: SATA max UDMA/133 mmio [mem 0xfd0c0000-0xfd0c1fff] port 0x100 irq 39␍␊
[18:04:51:755] [    7.510598] ata2: SATA max UDMA/133 mmio [mem 0xfd0c0000-0xfd0c1fff] port 0x180 irq 39␍␊
[18:04:51:772] [    7.520443] xilinx-psgtr fd400000.zynqmp_phy: Lane:2 type:0 protocol:3 pll_locked:yes␍␊
[18:04:51:772] [    7.530499] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller␍␊
[18:04:51:787] [    7.535989] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1␍␊
[18:04:51:787] [    7.543841] xhci-hcd xhci-hcd.0.auto: hcc params 0x0238f625 hci version 0x100 quirks 0x22010810␍␊
[18:04:51:803] [    7.552564] xhci-hcd xhci-hcd.0.auto: irq 51, io mem 0xfe200000␍␊
[18:04:51:803] [    7.558602] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002␍␊
[18:04:51:803] [    7.565380] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1␍␊
[18:04:51:819] [    7.572590] usb usb1: Product: xHCI Host Controller␍␊
[18:04:51:819] [    7.577459] usb usb1: Manufacturer: Linux 4.14.0-xilinx-v2018.3 xhci-hcd␍␊
[18:04:51:835] [    7.584150] usb usb1: SerialNumber: xhci-hcd.0.auto␍␊
[18:04:51:835] [    7.589288] hub 1-0:1.0: USB hub found␍␊
[18:04:51:835] [    7.593051] hub 1-0:1.0: 1 port detected␍␊
[18:04:51:835] [    7.597130] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller␍␊
[18:04:51:851] [    7.602615] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2␍␊
[18:04:51:851] [    7.610379] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003␍␊
[18:04:51:867] [    7.617165] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1␍␊
[18:04:51:867] [    7.624374] usb usb2: Product: xHCI Host Controller␍␊
[18:04:51:867] [    7.629243] usb usb2: Manufacturer: Linux 4.14.0-xilinx-v2018.3 xhci-hcd␍␊
[18:04:51:883] [    7.635935] usb usb2: SerialNumber: xhci-hcd.0.auto␍␊
[18:04:51:883] [    7.641025] hub 2-0:1.0: USB hub found␍␊
[18:04:51:883] [    7.644772] hub 2-0:1.0: 1 port detected␍␊
[18:04:51:899] [    7.649751] pca953x 0-0021: 0-0021 supply vcc not found, using dummy regulator␍␊
[18:04:51:899] [    7.657051] pca953x 0-0021: failed reading register␍␊
[18:04:51:915] [    7.662784] at24 2-0054: 1024 byte 24c08 EEPROM, writable, 1 bytes/write␍␊
[18:04:51:915] [    7.669510] i2c i2c-0: Added multiplexed i2c bus 2␍␊
[18:04:51:915] [    7.674476] i2c i2c-0: Added multiplexed i2c bus 3␍␊
[18:04:51:931] [    7.679509] i2c i2c-0: Added multiplexed i2c bus 4␍␊
[18:04:51:931] [    7.684892] ina2xx 5-0040: power monitor ina226 (Rshunt = 5000 uOhm)␍␊
[18:04:51:931] [    7.691263] i2c i2c-0: Added multiplexed i2c bus 5␍␊
[18:04:51:947] [    7.696164] i2c i2c-0: Added multiplexed i2c bus 6␍␊
[18:04:51:947] [    7.701093] i2c i2c-0: Added multiplexed i2c bus 7␍␊
[18:04:51:947] [    7.706015] i2c i2c-0: Added multiplexed i2c bus 8␍␊
[18:04:51:963] [    7.710933] i2c i2c-0: Added multiplexed i2c bus 9␍␊
[18:04:51:963] [    7.715717] pca954x 0-0074: registered 8 multiplexed busses for I2C switch pca9548␍␊
[18:04:51:963] [    7.723297] cdns-i2c ff030000.i2c: 400 kHz mmio ff030000 irq 33␍␊
[18:04:51:979] [    7.729938] rtc_zynqmp ffa60000.rtc: setting system clock to 2018-12-06 16:15:00 UTC (1544112900)␍␊
[18:04:51:979] [    7.738807] of_cfs_init␍␊
[18:04:51:979] [    7.741257] of_cfs_init: OK␍␊
[18:04:51:995] [    7.744150] clk: Not disabling unused clocks␍␊
[18:04:51:995] [    7.748644] ALSA device list:␍␊
[18:04:51:995] [    7.751605]   #0: DisplayPort monitor␍␊
[18:04:52:075] [    7.830991] ata1: SATA link down (SStatus 0 SControl 330)␍␊
[18:04:52:075] [    7.836404] ata2: SATA link down (SStatus 0 SControl 330)␍␊
[18:04:52:091] [    7.841924] Freeing unused kernel memory: 512K␍␊
[18:04:52:091] ␍INIT: version 2.88 booting␍␍␊
[18:04:52:172] Starting udev␍␊
[18:04:52:187] [    7.947447] udevd[1802]: starting version 3.2.2␍␊
[18:04:52:203] [    7.957131] udevd[1803]: starting eudev-3.2.2␍␊
[18:04:52:251] [    8.008318] mali: loading out-of-tree module taints kernel.␍␊
[18:04:52:539] [    8.296174] xilinx-vcu xilinx-vcu: Could not get core_enc clock␍␊
[18:04:52:555] [    8.306157] xilinx-vcu xilinx-vcu: failed to set logicoreIP refclk rate -22␍␊
[18:04:52:555] [    8.313250] VCU PLL: enable␍␊
[18:04:52:555] [    8.317349] xilinx-vcu xilinx-vcu: xvcu_probe: Probed successfully␍␊
[18:04:52:588] [    8.336952] al5e a0100000.al5e: l2 prefetch size:12451840 (bits), l2 color bitdepth:10␍␊
[18:04:52:603] [    8.357085] al5d a0120000.al5d: l2 prefetch size:12451840 (bits), l2 color bitdepth:10␍␊
[18:04:52:779] [    8.540823] [drm] Cannot find any crtc or sizes␍␊
[18:04:52:971] Starting internet superserver: inetd.␍␍␊
[18:04:52:987] Configuring packages on first boot....␍␍␊
[18:04:52:987]  (This may take several minutes. Please do not power off the machine.)␍␍␊
[18:04:52:987] Running postinst /etc/rpm-postinsts/100-sysvinit-inittab...␍␍␊
[18:04:53:019] update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing)␍␍␊
[18:04:53:019]  Removing any s␍INIT: Entering runlevel: 5␍␍␍␊
[18:04:53:035] Configuring network interfaces... [    8.826268] pps pps0: new PPS source ptp0␍␊
[18:04:53:067] [    8.830283] macb ff0e0000.ethernet: gem-ptp-timer ptp clock registered.␍␊
[18:04:53:084] [    8.836956] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready␍␊
[18:04:53:099] udhcpc (v1.24.1) started␍␍␊
[18:04:53:131] Sending discover...␍␍␊
[18:04:56:171] Sending discover...␍␍␊
[18:04:59:211] Sending discover...␍␍␊
[18:05:02:251] No lease, forking to background␍␍␊
[18:05:02:251] done.␍␍␊
[18:05:02:267] Starting system message bus: dbus.␍␍␊
[18:05:02:283] Starting Xserver␍␍␊
[18:05:02:299] ␍␍␊
[18:05:02:299] Starting Dropbear SSH server: ␍␍␊
[18:05:02:299] X.Org X Server 1.19.3␍␍␊
[18:05:02:299] Release Date: 2017-03-15␍␍␊
[18:05:02:315] X Protocol Version 11, Revision 0␍␍␊
[18:05:02:315] Build Operating System: Linux 3.10.0-327.el7.x86_64 x86_64 ␍␍␊
[18:05:02:315] Current Operating System: Linux xilinx-zcu104-2018_3 4.14.0-xilinx-v2018.3 #1 SMP Thu Dec 6 12:13:44 UTC 2018 aarch64␍␍␊
[18:05:02:331] Kernel command line: earlycon console=ttyPS0,115200 clk_ignore_unused␍␍␊
[18:05:02:331] Generating key, this may take a while...␍␍␊
[18:05:02:331] Build Date: 03 December 2018  09:43:45PM␍␍␊
[18:05:02:347]  ␍␍␊
[18:05:02:347] Current version of pixman: 0.34.0␍␍␊
[18:05:02:347] ⇥	Before reporting problems, check http://wiki.x.org␍␍␊
[18:05:02:347] ⇥	to make sure that you have the latest version.␍␍␊
[18:05:02:347] Markers: (--) probed, (**) from config file, (==) default setting,␍␍␊
[18:05:02:363] ⇥	(++) from command line, (!!) notice, (II) informational,␍␍␊
[18:05:02:363] ⇥	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.␍␍␊
[18:05:02:363] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec  6 16:15:10 2018␍␍␊
[18:05:02:379] (==) Using config file: "/etc/X11/xorg.conf"␍␍␊
[18:05:02:379] (==) Using system config directory "/usr/share/X11/xorg.conf.d"␍␍␊
[18:05:04:619] D-BUS per-session daemon address is: unix:abstract=/tmp/dbus-7yJBPBwV1t,guid=3efc305860e93734e54d0a9c5c094b10␍␍␊
[18:05:04:683] matchbox: Cant find a keycode for keysym 269025056␍␍␊
[18:05:04:683] matchbox: ignoring key shortcut XF86Calendar=!$contacts␍␍␊
[18:05:04:699] ␍␍␊
[18:05:04:699] matchbox: Cant find a keycode for keysym 2809␍␍␊
[18:05:04:699] matchbox: ignoring key shortcut telephone=!$dates␍␍␊
[18:05:04:699] ␍␍␊
[18:05:04:699] matchbox: Cant find a keycode for keysym 269025050␍␍␊
[18:05:04:715] matchbox: ignoring key shortcut XF86Start=!matchbox-remote -desktop␍␍␊
[18:05:04:715] ␍␍␊
[18:05:04:715] [settings daemon] Forking. run with -n to prevent fork␍␍␊
[18:05:04:715] Error: No calibratable devices found.␍␍␊
[18:05:04:731] Activating service name='org.a11y.atspi.Registry'␍␍␊
[18:05:04:747] Successfully activated service 'org.a11y.atspi.Registry'␍␍␊
[18:05:04:747] SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry␍␍␊
[18:05:04:891] ␍␍␊
[18:05:04:891] ** (matchbox-panel:2391): <0x1b>[1;33mWARNING<0x1b>[0m **: Failed to load applet "battery" (/usr/lib/matchbox-panel/libbattery.so: cannot open shared object file: No such file or directory).␍␍␊
[18:05:06:283] Public key portion is:␍␍␊
[18:05:06:283] ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCY7dEievoRvwyVhJZpD4RbWWVzxKWA0yAJf2CXxW/VOCPuUQ6hQHuR3Tv7I/FnBLKAL2hhg6+OnHB+QUrIudP7ezBetRwx771dcHFzHV6fiZ8utBRS8QDG7msDqtTw0yZJ+BNU0O7OgBCaHTlmI3+qydcmDy0ThpLqpAAbMbEh+R+jptfa97TrpTKzyuowCujsisfc8AW28hz6bKDILFY9FMaX6jUNq2tautiRMZ8JbhnThWvaHeG27HRJCuMEITD9ul4UOgZinXHaijk+XS0pJyMN650BdXfUmBu1KXEW25bsi20+c0s3pa1PcdvEwljJ6ETf/9wWbnb5p72JOe0J root@xilinx-zcu104-2018_3␍␍␊
[18:05:06:315] Fingerprint: md5 89:ed:e8:13:30:12:c7:30:d0:a0:a2:f8:fe:1c:b7:23␍␍␊
[18:05:06:315] dropbear.␍␍␊
[18:05:06:315] Starting syslogd/klogd: done␍␍␊
[18:05:06:331] Starting tcf-agent: OK␍␊
[18:05:06:443] ␍␍␊
[18:05:06:443] PetaLinux 2018.3 xilinx-zcu104-2018_3 /dev/ttyPS0␍␊
[18:05:06:443] ␍␍␊
[18:05:06:443] ␍xilinx-zcu104-2018_3 login: root␍␊
[18:07:19:081] Password: ␍␊
[18:07:20:473] <0x1b>7<0x1b>[r<0x1b>[999;999H<0x1b>[6nroot@xilinx-zcu104-2018_3:~# ␍␊
[18:07:26:840] root@xilinx-zcu104-2018_3:~# ␍␊
[18:07:27:145] root@xilinx-zcu104-2018_3:~# ␍␊
[18:07:27:401] root@xilinx-zcu104-2018_3:~# ␍␊
[18:07:27:593] root@xilinx-zcu104-2018_3:~# ␍␊
[18:07:27:785] root@xilinx-zcu104-2018_3:~# ␍␊

[Basically booting up and I can issue commands now. All the LEDs are green as well.]

Here is what I get when I load the image files from my petalinux project:

Screenshot from 2019-10-07 19-21-37.pngThe console remains empty and nothing shows up, while the done LEDs go red.

I feel like I am doing something wrong in configuring my petalinux project but I'm not sure.

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

Re: SD card does not boot in ZCU104

Hi @maju42 

 

What's the problem ?

I'm sure that your linux already booted with ramdisk image as rootfs from first partition on SD card.

What do you wand to do ?

Do you want to use rootfs as second partition on SD card ?

Do you want to automatically mount second partition on SD card after starting linux ?

 

Best regards,

0 Kudos
Contributor
Contributor
859 Views
Registered: ‎05-31-2019

Re: SD card does not boot in ZCU104

Hi @watari , My problem is the following: After building my petalinux project (from a hdf file which I generated through Vivado), I copy the BOOT.bin and image.ub from petalinux-project/images/linux to the SD card. When I try to start the FPGA, setting it to sd boot mode the console stays empty and the LEDs are red as well. I want the FPGA to boot up properly with the image files from my project.

[Just as a test to check if the FPGA works or not, I loaded some prebuilt image files from this website. It works when I load the files from there. (As I showed in the logs.)]

I want to know why nothing is showing up in the console when I put image files from my own petalinux project. Thank you so much!

 

 

 

 

 

 

 

 

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

Re: SD card does not boot in ZCU104

Hi @maju42 

 

Would you make sure the output message by the following command ?

 

$ dumpimage -l <your boot.bin>

 

You can see detail information on your boot.bin.

 

Best regards,

0 Kudos
Contributor
Contributor
839 Views
Registered: ‎05-31-2019

Re: SD card does not boot in ZCU104

Hi @watari , This is what I am getting when I run the above command:

maju42@csdnc2d:~/SWpart6/nvdla/images/linux$ dumpimage -l BOOT.BIN 
Image Type   : Xilinx ZynqMP Boot Image support
Image Offset : 0x00002800
Image Size   : 103312 bytes (103312 bytes packed)
PMUFW Size   : 129760 bytes (129760 bytes packed)
Image Load   : 0xfffc0000
Checksum     : 0xfd170f61
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 none (PL):
    Offset     : 0x0003b680
    Size       : 36343112 (0x22a8d48) bytes
    Load       : 0xffffffff (entry=0x00000000)
    Attributes : EL3 
    Checksum   : 0xfe5f2192
FSBL payload on CPU a5x-0 (PS):
    Offset     : 0x022e4400
    Size       : 51064 (0xc778) bytes
    Load       : 0xfffea000
    Attributes : EL3 secure 
    Checksum   : 0xff76917b
FSBL payload on CPU a5x-0 (PS):
    Offset     : 0x022f0b80
    Size       : 829808 (0xca970) bytes
    Load       : 0x08000000
    Attributes : EL2 
    Checksum   : 0xef6aba83
0 Kudos
Scholar watari
Scholar
820 Views
Registered: ‎06-16-2013

Re: SD card does not boot in ZCU104

Hi @maju42 

 

Would you make sure the followings ?

 

- Make sure version number between workspace and petalinux and vivado.

- Make sure fpga binary file whether there is not any errors or not.

 

If you can not find any problem, would you do the follwoing commands ?

You can find some information.

 

$ file <your FPGA binary file>

$ dumpimage -l <your FPGA binary file>

 

Best regards,

0 Kudos
Contributor
Contributor
603 Views
Registered: ‎05-31-2019

Re: SD card does not boot in ZCU104

Hi @watari ,  I am using version 2019.1 for both Vivado and petalinux.

On your previous edit to the above, I got an error when I ran petalinux-build -c bootloader -x mrproper

[INFO] building bootloader
[INFO] generating Kconfig for project
[INFO] silentconfig project
[INFO] sourcing bitbake
[INFO] generating plnxtool conf
[INFO] generating meta-plnx-generated layer
[INFO] generating machine configuration
[INFO] generating bbappends for project . This may take time ! 
[INFO] generating u-boot configuration files
[INFO] generating kernel configuration files
[INFO] generating user layers
[INFO] generating kconfig for Rootfs
[INFO] silentconfig rootfs
[INFO] generating petalinux-user-image.bb
INFO: bitbake virtual/fsbl -c mrproper
Parsing recipes: 100% |##########################################| Time: 0:00:41
Parsing of 2777 .bb files complete (0 cached, 2777 parsed). 3812 targets, 150 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Task do_mrproper does not exist for target virtual/fsbl (/opt/pkg/petalinux/2019.1/components/yocto/source/aarch64/layers/meta-xilinx-tools/recipes-bsp/fsbl/fsbl_git.bb:do_mrproper)
ERROR: Command execution failed: 1

Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
ERROR: Failed to build bootloader

 

The command: petalinux-build -c bootloader runs fine.

[INFO] building bootloader
[INFO] sourcing bitbake
[INFO] generating user layers
INFO: bitbake virtual/fsbl
Loading cache: 100% |############################################| Time: 0:00:00
Loaded 3811 entries from dependency cache.
Parsing recipes: 100% |##########################################| Time: 0:00:02
Parsing of 2777 .bb files complete (2775 cached, 2 parsed). 3812 targets, 150 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Initialising tasks: 100% |#######################################| Time: 0:00:00
Checking sstate mirror object availability: 100% |###############| Time: 0:00:01
Sstate summary: Wanted 148 Found 126 Missed 44 Current 0 (85% match, 0% complete)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 624 tasks of which 533 didn't need to be rerun and all succeeded.
INFO: Copying Images from deploy to images
INFO: Creating images/linux directory
NOTE: Failed to copy built images to tftp dir:  /tftpboot
[INFO] successfully built bootloader

 

Running-

$ file <your FPGA binary file>

$ dumpimage -l <your FPGA binary file>

maju42@cse-dnc6d:~/SWpart7/nvdla/images/linux$ file BOOT.BIN 
BOOT.BIN: data
maju42@cse-dnc6d:~/SWpart7/nvdla/images/linux$ dumpimage -l BOOT.BIN
Image Type : Xilinx ZynqMP Boot Image support Image Offset : 0x00002800 Image Size : 103312 bytes (103312 bytes packed) PMUFW Size : 129760 bytes (129760 bytes packed) Image Load : 0xfffc0000 Checksum : 0xfd170f61 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 none (PL): Offset : 0x0003b680 Size : 36343112 (0x22a8d48) bytes Load : 0xffffffff (entry=0x00000000) Attributes : EL3 Checksum : 0xfe5f2192 FSBL payload on CPU a5x-0 (PS): Offset : 0x022e4400 Size : 51064 (0xc778) bytes Load : 0xfffea000 Attributes : EL3 secure Checksum : 0xff76917b FSBL payload on CPU a5x-0 (PS): Offset : 0x022f0b80 Size : 829808 (0xca970) bytes Load : 0x08000000 Attributes : EL2 Checksum : 0xef6aba83
0 Kudos
Contributor
Contributor
800 Views
Registered: ‎05-31-2019

Re: SD card does not boot in ZCU104

Hi @watari , I am using version 2019.1 for both Vivado and Petalinux.

Running -

$ file <your FPGA binary file>

$ dumpimage -l <your FPGA binary file>

maju42a@cse-dn6d:~/SWpart7/nvdla/images/linux$ file BOOT.BIN 
BOOT.BIN: data

maju42a@cse-dn6d:~/SWpart7/nvdla/images/linux$ dumpimage -l BOOT.BIN 
Image Type   : Xilinx ZynqMP Boot Image support
Image Offset : 0x00002800
Image Size   : 103312 bytes (103312 bytes packed)
PMUFW Size   : 129760 bytes (129760 bytes packed)
Image Load   : 0xfffc0000
Checksum     : 0xfd170f61
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 none (PL):
    Offset     : 0x0003b680
    Size       : 36343112 (0x22a8d48) bytes
    Load       : 0xffffffff (entry=0x00000000)
    Attributes : EL3 
    Checksum   : 0xfe5f2192
FSBL payload on CPU a5x-0 (PS):
    Offset     : 0x022e4400
    Size       : 51064 (0xc778) bytes
    Load       : 0xfffea000
    Attributes : EL3 secure 
    Checksum   : 0xff76917b
FSBL payload on CPU a5x-0 (PS):
    Offset     : 0x022f0b80
    Size       : 829808 (0xca970) bytes
    Load       : 0x08000000
    Attributes : EL2 
    Checksum   : 0xef6aba83
0 Kudos
Scholar watari
Scholar
772 Views
Registered: ‎06-16-2013

Re: SD card does not boot in ZCU104

Hi @maju42 

 

I suspect that fpga binary image file is wrong format or something.

So, would you execute the following command ?

 

$ file <your fpga binary image file>

$ dumpimage -l <your fpga binary image file>

 

ex)

$ file system.bit

system.bit: Xilinx BIT data - from vcu_trd_wrapper;UserID=0XFFFFFFFF;Version=2019.1 - for xczu7ev-ffvc1156-2-e - built 2019/05/25(10:45:51) -data length 0x126a9f4

$ dumpimage -l system.bit

GP Header: Size 90ff0 LoadAddr ff00ff0

 

Best regards,

0 Kudos
Contributor
Contributor
769 Views
Registered: ‎05-31-2019

Re: SD card does not boot in ZCU104

Hi @watari , Thanks for your reply. This is what I get:

$ file system.bit
system.bit: Xilinx BIT data - from design_1_wrapper;UserID=0XFFFFFFFF;Version=2019.1 - for xczu19eg-ffve1924-1LV-i - built 2019/09/20(14:32:21) - data length 0x22a8d48

$ dumpimage -l system.bit
GP Header: Size 90ff0 LoadAddr ff00ff0

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

Re: SD card does not boot in ZCU104

Hi @maju42 

 

Here is the route cause.

$ file system.bit
system.bit: Xilinx BIT data - from design_1_wrapper;UserID=0XFFFFFFFF;Version=2019.1 - for xczu19eg-ffve1924-1LV-i - built 2019/09/20(14:32:21) - data length 0x22a8d48

 

Would you rebuild FPGA image file by vivado after selecting correct device name ?

The fpga device name on ZCU104 is "XCZU7EV-2FFVC1156 MPSoC".

 

Best regards,

0 Kudos
Contributor
Contributor
744 Views
Registered: ‎05-31-2019

Re: SD card does not boot in ZCU104

Hi @watari Do you mean change the device in Vivado itself over here:

ezgif.com-crop.png

And run synthesis, implementation, generate .bit and hdf files, then configure the petalinux project?

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

Re: SD card does not boot in ZCU104

Hi @maju42 

 

Yes.

ZCU104 could not boot with fpga binary image.

Because your fpga binary image is wrong device for ZCU104.

 

So, unfortunately you must change project device name from wrong device name to correct device name and run synthesis, implementation, generate .bit file (correct FPGA binary image) and rebuild BOOT.BIN with this correct fpga binary image.

 

[note]

The reason is as below.

 

Arm trusted firmware and FPGA (*1) check whether all contents of BOOT.BIN are correct or not.

In this case, ATF, PMUFW and FSBL are correct code. But fpga binary file (bit file) is wrong.

So, you can see red led on ZCU104.

 

*1)

FPGA has a mechanism to load fpga binary by itself and so on.

 

[18:04:08:156] Xilinx Zynq MP First Stage Boot Loader ␊
[18:04:08:156] ␍Release 2018.3   Dec  6 2018  -  12:16:27␍␊
[18:04:10:028] NOTICE:  ATF running on XCZU7EV/silicon v4/RTL5.1 at 0xfffea000␍␊
[18:04:10:028] NOTICE:  BL31: Secure code at 0x0␍␊
[18:04:10:028] NOTICE:  BL31: Non secure code at 0x10080000␍␊
[18:04:10:028] NOTICE:  BL31: v1.5(release):xilinx-v2018.2-919-g08560c36␍␊
[18:04:10:044] NOTICE:  BL31: Built : 12:22:13, Dec  6 2018␍␊
[18:04:10:188] PMUFW:⇥	v1.1␍␊

 

Best regards,

Contributor
Contributor
699 Views
Registered: ‎05-31-2019

Re: SD card does not boot in ZCU104

Hi, @watari I changed the board device name in my vivado project. I ran the commands again and this is what I get:

$ dumpimage -l system.bit
GP Header: Size 90ff0 LoadAddr ff00ff0


$ file system.bit
system.bit: Xilinx BIT data - from design_1_wrapper;UserID=0XFFFFFFFF;Version=2019.1 - for xczu7ev-ffvc1156-2-e - built 2019/10/07(22:52:13) - data length 0x126a9f4

 

Now I tried to boot again with the modified image files but still, I am facing the same issue. The serial console is blank with no messages showing up.

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

Re: SD card does not boot in ZCU104

Hi @maju42 

 

Would you refer the following AR even if your board is ZCU104 ?

 

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

 

Best regards,

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

Re: SD card does not boot in ZCU104

Hi @maju42 

 

Unfortunetly, it might be something broken.

I encounter similer phenomenon in ZCU106.

Would you refer the following AR and run BIST ?

 

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

 

Best regards,

0 Kudos
Contributor
Contributor
447 Views
Registered: ‎05-31-2019

Re: SD card does not boot in ZCU104

@watari In my case, all the 4 LEDs are glowing green when running the built-in tests but the pmod test fails in the serial console. How did you fix the problem in your ZCU106  board? 

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

Re: SD card does not boot in ZCU104

Hi @maju42 

 

In my case, it was power controller issue.

So, I rewrite this firmware.

 

But, in your case, it seems fine.

I only suggest you to change SD card to tested SD card. Refer the following URL.

 

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

 

Best regards,

0 Kudos
Contributor
Contributor
407 Views
Registered: ‎05-31-2019

Re: SD card does not boot in ZCU104

Hi @watari , I don't think it is a problem with my SD card, as it seems to work fine if I run the official zcu104 bsp from the Xilinx website. Can you tell me what are changes you did while issuing the command: petalinux-config --get-hw-description=./ , i.e in this screen-

ezgif.com-crop.png

I am changing the MACHINE_NAME to zcu104-revc in DTG settings and choosing SD card in Image Packaging Configuration. Are you making any other changes?

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

Re: SD card does not boot in ZCU104

Hi @maju42 

 

I suspected the followings.

 

1. Wrong FPGA binary data and/or format

=> That's true. So you already modified it. But, not work fine yet.

2. DRAM issue (AR #71961/https://www.xilinx.com/support/answers/71961.html)

=> Use Vivado 2019.1. Not applicable.

3. Mismatch version between ATF, PMUFW and FSBL

=> Allow correct flow. Not applicable.

4. Has a problem on power lane.

=> As you mentioned about the result of BIST on ZCU104, there was not any problem.

It's similer my issue on ZCU106.

5. There are something wrong sectors or pages on SD card.

=> Not make sure it yet.

If it's true, some design work fine, but some design malfunction malfunction.

 

That's my opinion.

If they are wrong, I suggest you to make sure booting procedure by oscilloscope and system debugger.

It is hard to debug boot procedure between PoR and FSBL.

At least, your issue is relevant loading FPGA bit stream.

 

Best regards,

0 Kudos
Contributor
Contributor
366 Views
Registered: ‎08-23-2018

Re: SD card does not boot in ZCU104

Regarding your first post, the only issues I can see is your commands for updating the project BSP and the way you create the BOOT.bin

1) petalinux-config --get-hw-description=/path/to/the/bin/directory

It does not contain the *.bit filename, just put the directory path where it is located.

2) BOOT.BIN creation is a bit odd, but this may be for the zcu104 (I use the zcu102). 

For the zcu102 anyways the program files are all .elf files and have that name eg,
petalinux-package --boot --format BIN --fsbl zynqmp_fsbl.elf --u-boot u-boot.elf --pmufw pmufw.elf --fpga system.bit --force

3) You are removing the initrd and ramfs from the image.ub file but are not putting a filesystem into another second partition on the sdacrd... what is Linux going to use for a filesystem? 

I would recommend leaving the initrd and ramfs in initially then you only need to copy over the BOOT.BIN and the image.ub files to the BOOT partition.

 

Regarding the BOOT partition, its probably OK if you can take other pre-built BOOT.BIN & image.ub files and use them sucessfully on the same partition. There are some cautions on reserving some space at the start of the SDCard but that would not be an issue if existing files work on the same SDCard.

 

If the SDCard is good then the culprit is the FSBL as it is the first to load. It is either not packages right or there is a problem wit hthe compile. If FSBL starts up then it will print a header to your serial terminal prior to attempting to load a FPGA image. If it hangs after the POST line then there is an issue with the FPGA bit file.

 

Note: If you have no special Linux drivers enabled that expect FPGA elements in the PL then it would be safe to just leave out the .bit file from the BOOT.BIN file and see if that loads.

 

 - Richard

 

0 Kudos
Contributor
Contributor
358 Views
Registered: ‎05-31-2019

Re: SD card does not boot in ZCU104

Hi @rwillis , Thank you for your suggestions. I read somewhere that because the rootfs is configured to the SD boot, then the RAM initial of the kernel must be canceled. Otherwise, in the boot phase, the kernel cannot find the symbolic image of the rootfs in the memory, and an error will occur. But I will follow your instructions and leave it as it is. Apart from this is it okay to select [Filesystem Packages–> misc, select packagegroup-core-buildessential->include all the packages] in petalinux-config -c rootfs stage? Or do I need to add more packages? Sorry I am fairly new to this field.

 

0 Kudos
Observer tejaallani
Observer
339 Views
Registered: ‎05-08-2018

Re: SD card does not boot in ZCU104

@maju42  please check these:

https://forums.xilinx.com/t5/Embedded-Linux/Microzed-xc7z020-unable-to-see-prints-on-UART1/m-p/1002307#M35529

https://forums.xilinx.com/t5/ACAP-and-SoC-Boot-and/Microzed-xc7z020-FSBL-UNDEFINED-HANDLER-when-booting-from-SD/m-p/1001760/thread-id/3224/highlight/false#M3239

You can enable debug prints in fsbl and check where is it going wrong. If your fsbl is getting stuck in the same spot as shown in above link, then your vivado configuration maybe wrong.

0 Kudos
Contributor
Contributor
280 Views
Registered: ‎08-23-2018

Re: SD card does not boot in ZCU104

@maju42 

As @tejaallani said in his last post, concentrate on getting the FSBL working. Only then can you start to look at the u-boot and linux boot phases.

Go over your build method for the FSBL very carefully. 

NOTE - This may or may not apply to the zcu104. In the zcu102 board Xilinx made a change in its choice of processor RAM but did not change the board's revision. This caused quite a lot of problems as the board's FSBL was not capable of initializing the RAM correctly. Xilinx released a patch for the FSBL and this had to be added to the petalinux recipe for the FSBL in order to fix it. The patches were made available in Releases 2018.2 and 2018.3 (maybe 2018.1). Release 2019.1 seems to have the FSBL source pre-patched. I would suggest looking over the release notes on your board if you have a more recent one (bought after January of this year) and try to determine if the RAM part number was changed. The change involves moving to non ECC DDR DRAM.

I added in this note as the problem with the RAM caused the FSBL to freeze and not generate a POST line in the serial console, similar to your problems.

Also look for reported problems with the FSBL, an example is this bug (https://github.com/antmicro/zynq-mkbootimage/issues/6) it may not be related to your issue but it is a good idea to see if others are having the same problems with the FSBL on the zcu104 (Google zcu104 FSBL, possibly add RAM)

 - Richard

 

 

0 Kudos
Contributor
Contributor
275 Views
Registered: ‎08-23-2018

Re: SD card does not boot in ZCU104

FYI, the Xilinx Wiki page for the FSBL (release notes, building it from SDK etc)

https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18842019/FSBL

 

And I noticed that your are building with Petalinux 2018.2 but testing prebuilt images from 2018.3

You may want to switch to 2018.3 if there were RAM changes as I stated in my last post. I am basing this off of my experiences with the zcu102 so it may not apply to the zcu104. I had better luck dealing with the board hardware changes in 2018.3.

 - Richard

 

0 Kudos
Contributor
Contributor
269 Views
Registered: ‎05-31-2019

Re: SD card does not boot in ZCU104

 

Hi @rwillis @tejaallani , I noticed that, but currently, I am using Petalinux v2019.1 and building the BSP with the same version, as 2018.3 is not supported in Ubuntu 18.04. Also, I believe this is due to an issue with improper FSBL. In my case, I am not making any changes to it. I am generating the bit file from Vivado. When I open my project in Vivado SDK, it generates the hdf file as well which I am later using to build the Petalinux project. 

Is it okay to use the FSBL after compiling the ZynqMP FSBL from the git repository: https://github.com/Xilinx/embeddedsw/tree/release-2019.1/lib/sw_apps/zynqmp_fsbl/misc? The makefile seems to have support only for zcu102 boards.

0 Kudos