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
Adventurer
Adventurer
5,170 Views
Registered: ‎11-10-2017

Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

Hello,

 

I am trying to load a hello world application in ultrazed eg mpsoc via SD boot. I am using petalinux 2017.3 and created HDF via Vivado 2017.3 on Ubuntu 16.04 LTS.

 

I was able to create the images using petalinux as referred in UG1144 and UG 1156. 

 

When i load the SD card and start the board it is not able to load the root fs. When i look at the boot lok, it is still showing single partition mmcblk0p1 while i have got my SD card parted via gparted into  - BOOT and rootfs partition.

 

BOOT contains image.ub, BOOT.BIN, Image and system.dtb files and i have extracted my rootfs.cpio in the rootfs partition.

 

Bootlog of root=/dev/mmcblk0p2

 

Xilinx Zynq MP First Stage Boot Loader
Release 2017.3   Feb 15 2018  -  13:54:00
NOTICE:  ATF running on XCZU3EG/silicon v4/RTL5.1 at 0xfffea000, with PMU firmware
NOTICE:  BL31: Secure code at 0x0
NOTICE:  BL31: Non secure code at 0x8000000
NOTICE:  BL31: v1.3(release):f9b244b
NOTICE:  BL31: Built : 08:21:53, Feb 15 2018


U-Boot 2017.01 (Feb 15 2018 - 13:54:12 +0530) Xilinx ZynqMP ZCU102 revB

I2C:   ready
DRAM:  2 GiB
ERROR: usb dr_mode not found

at /home/vishal/myxprj/build/tmp/work/plnx_aarch64-xilinx-linux/u-boot-xlnx/v2017.01-xilinx-v2017.3+gitAUTOINC+da811c4511-r0/git/drivers/usb/common/common.c:32/usb_get_dr_mode()
EL Level:       EL2
Chip ID:        xczu3eg
MMC:   sdhci@ff160000: 0 (eMMC), sdhci@ff170000: 1 (SD), sdhci@ff170000: 2 (SD)
zynqmp_qspi_ofdata_to_platdata: CLK 124999999
SF: Detected n25q256a with page size 512 Bytes, erase size 128 KiB, total 64 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Bootmode: SD_MODE1
Net:   ZYNQ GEM: ff0e0000, phyaddr ffffffff, interface rgmii-id
eth0: ethernet@ff0e0000
U-BOOT for myxprj

ethernet@ff0e0000 Waiting for PHY auto negotiation to complete........ done
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10
BOOTP broadcast 11
BOOTP broadcast 12
BOOTP broadcast 13
BOOTP broadcast 14
BOOTP broadcast 15
BOOTP broadcast 16
BOOTP broadcast 17

Retry time exceeded
Hit any key to stop autoboot:  0
Device: sdhci@ff160000
Manufacturer ID: 13
OEM: 14e
Name: Q2J55
Tran Speed: 200000000
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 7.1 GiB
Bus Width: 8-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
reading image.ub
13410164 bytes read in 977 ms (13.1 MiB/s)
## Loading kernel from FIT Image at 10000000 ...
   Using 'conf@2' configuration
   Trying 'kernel@0' kernel subimage
     Description:  Linux Kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x100000d8
     Data Size:    13376000 Bytes = 12.8 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x00080000
     Entry Point:  0x00080000
     Hash algo:    sha1
     Hash value:   46ea30fd3997d54fad2ee427bac03ba37ebf93bd
   Verifying Hash Integrity ... sha1+ OK
## Loading fdt from FIT Image at 10000000 ...
   Using 'conf@2' configuration
   Trying 'fdt@0' fdt subimage
     Description:  Flattened Device Tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x10cc1bd0
     Data Size:    32859 Bytes = 32.1 KiB
     Architecture: AArch64
     Hash algo:    sha1
     Hash value:   a39813bfe081edcdd567b6ccfb9d0e34d97c9a73
   Verifying Hash Integrity ... sha1+ OK
   Booting using the fdt blob at 0x10cc1bd0
   Loading Kernel Image ... OK
   Loading Device Tree to 0000000007ff4000, end 0000000007fff05a ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.9.0-xilinx-v2017.3 (vishal@vishal-VirtualBox) (gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11) ) #1 SMP Thu Feb 15 14:06:17 IST 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 1024 MiB at 0x0000000040000000
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.0 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 @ffffffc03ff7a000 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: 517120
[    0.000000] Kernel command line: earlycon earlyprintk clk_ignore_unused root=/dev/mmcblk0p2 rw rootwait uio_pdrv_genirq.of_id=generic-uio cma=1024M
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.000000] Memory: 1002760K/2097152K available (9084K kernel code, 582K rwdata, 2816K rodata, 512K init, 395K bss, 45816K reserved, 1048576K 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 - 0xffffff8008960000   (  9088 KB)
[    0.000000]     .rodata : 0xffffff8008960000 - 0xffffff8008c30000   (  2880 KB)
[    0.000000]       .init : 0xffffff8008c30000 - 0xffffff8008cb0000   (   512 KB)
[    0.000000]       .data : 0xffffff8008cb0000 - 0xffffff8008d41a00   (   583 KB)
[    0.000000]        .bss : 0xffffff8008d41a00 - 0xffffff8008da4634   (   396 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 - 0xffffffbf01c00000   (    28 MB actual)
[    0.000000]     memory  : 0xffffffc000000000 - 0xffffffc080000000   (  2048 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.008263] Console: colour dummy device 80x25
[    0.012525] console [tty0] enabled
[    0.015888] bootconsole [cdns0] disabled
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.9.0-xilinx-v2017.3 (vishal@vishal-VirtualBox) (gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11) ) #1 SMP Thu Feb 15 14:06:17 IST 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 1024 MiB at 0x0000000040000000
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.0 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 @ffffffc03ff7a000 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: 517120
[    0.000000] Kernel command line: earlycon earlyprintk clk_ignore_unused root=/dev/mmcblk0p2 rw rootwait uio_pdrv_genirq.of_id=generic-uio cma=1024M
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.000000] Memory: 1002760K/2097152K available (9084K kernel code, 582K rwdata, 2816K rodata, 512K init, 395K bss, 45816K reserved, 1048576K 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 - 0xffffff8008960000   (  9088 KB)
[    0.000000]     .rodata : 0xffffff8008960000 - 0xffffff8008c30000   (  2880 KB)
[    0.000000]       .init : 0xffffff8008c30000 - 0xffffff8008cb0000   (   512 KB)
[    0.000000]       .data : 0xffffff8008cb0000 - 0xffffff8008d41a00   (   583 KB)
[    0.000000]        .bss : 0xffffff8008d41a00 - 0xffffff8008da4634   (   396 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 - 0xffffffbf01c00000   (    28 MB actual)
[    0.000000]     memory  : 0xffffffc000000000 - 0xffffffc080000000   (  2048 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.008263] Console: colour dummy device 80x25
[    0.012525] console [tty0] enabled
[    0.015888] bootconsole [cdns0] disabled
[    0.019800] Calibrating delay loop (skipped), value calculated using timer frequency.. 199.99 BogoMIPS (lpj=399996)
[    0.019816] pid_max: default: 32768 minimum: 301
[    0.019933] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
[    0.019944] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes)
[    0.020614] ASID allocator initialised with 65536 entries
[    0.021174] zynqmp_plat_init Power management API v0.3
[    0.021259] EFI services will not be available.
[    0.021640] Detected VIPT I-cache on CPU1
[    0.021671] CPU1: Booted secondary processor [410fd034]
[    0.021962] Detected VIPT I-cache on CPU2
[    0.021981] CPU2: Booted secondary processor [410fd034]
[    0.022258] Detected VIPT I-cache on CPU3
[    0.022277] CPU3: Booted secondary processor [410fd034]
[    0.022315] Brought up 4 CPUs
[    0.022349] SMP: Total of 4 processors activated.
[    0.022358] CPU features: detected feature: 32-bit EL0 Support
[    0.022370] CPU: All CPU(s) started at EL2
[    0.022387] alternatives: patching kernel code
[    0.023192] devtmpfs: initialized
[    0.028037] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.053742] xor: measuring software checksum speed
[    0.092018]    8regs     :  2111.000 MB/sec
[    0.132050]    8regs_prefetch:  1882.000 MB/sec
[    0.172082]    32regs    :  2594.000 MB/sec
[    0.212114]    32regs_prefetch:  2180.000 MB/sec
[    0.212127] xor: using function: 32regs (2594.000 MB/sec)
[    0.212237] pinctrl core: initialized pinctrl subsystem
[    0.212995] NET: Registered protocol family 16
[    0.234160] cpuidle: using governor menu
[    0.234383] Failed to initialise IOMMU /amba/smmu@fd800000
[    0.234619] vdso: 2 pages (1 code @ ffffff8008967000, 1 data @ ffffff8008cb4000)
[    0.234647] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.235261] DMA: preallocated 256 KiB pool for atomic allocations
[    0.245799] reset_zynqmp reset-controller: Xilinx zynqmp reset driver probed
[    0.246637] ARM CCI_400_r1 PMU driver probed
[    0.250031] zynqmp-pinctrl ff180000.pinctrl: zynqmp pinctrl initialized
[    0.251426] sysfs: cannot create duplicate filename '/bus/platform/devices/ff170000.sdhci'
[    0.251466] ------------[ cut here ]------------
[    0.251491] WARNING: CPU: 2 PID: 1 at /home/vishal/myxprj/build/tmp/work-shared/plnx_aarch64/kernel-source/fs/sysfs/dir.c:31 sysfs_warn_dup+0x5c/0x78
[    0.251514] Modules linked in:
[    0.251528]
[    0.251542] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.9.0-xilinx-v2017.3 #1
[    0.251555] Hardware name: xlnx,zynqmp (DT)
[    0.251568] task: ffffffc03d866c00 task.stack: ffffffc03d868000
[    0.251584] PC is at sysfs_warn_dup+0x5c/0x78
[    0.251599] LR is at sysfs_warn_dup+0x5c/0x78
[    0.251611] pc : [<ffffff80081fed9c>] lr : [<ffffff80081fed9c>] pstate: 60000045
[    0.251631] sp : ffffffc03d86bb80
[    0.251642] x29: ffffffc03d86bb80 x28: 0000000000000000
[    0.251657] x27: 0000000000000000 x26: ffffff8008d86000
[    0.251672] x25: 0000000000000000 x24: ffffff8008d01000
[    0.251687] x23: ffffffffffffffef x22: 0000000000000001
[    0.251702] x21: ffffffc03d822ac8 x20: ffffffc03d023a80
[    0.251717] x19: ffffffc03db65000 x18: 0000000000000010
[    0.251732] x17: 0000000000000000 x16: 0000000000000000
[    0.251746] x15: 0000000000000006 x14: 2e30303030373166
[    0.251761] x13: 662f736563697665 x12: 642f6d726f667461
[    0.251776] x11: 6c702f7375622f27 x10: 000000000000005a
[    0.251791] x9 : 000000000000005e x8 : 7075642065746165
[    0.251806] x7 : 726320746f6e6e61 x6 : ffffff8008d4a235
[    0.251821] x5 : ffffff800843f498 x4 : 0000000000000000
[    0.251836] x3 : 0000000000000000 x2 : 00000000000001df
[    0.251850] x1 : ffffff8008cca9c8 x0 : 000000000000004e
[    0.251865]
[    0.251879] ---[ end trace 580fef7e4f33558c ]---
[    0.251892] Call trace:
[    0.251905] Exception stack(0xffffffc03d86b9b0 to 0xffffffc03d86bae0)
[    0.251920] b9a0:                                   ffffffc03db65000 0000008000000000
[    0.251942] b9c0: ffffffc03d86bb80 ffffff80081fed9c ffffff8008d4c5fa 000000000000004e
[    0.251964] b9e0: ffffffc03d86ba00 ffffff80080d908c ffffff8008d49c68 ffffff8008aea790
[    0.251986] ba00: ffffffc03d86baa0 ffffff80080d9364 ffffffc03db65000 ffffffc03d023a80
[    0.252008] ba20: ffffffc03d822ac8 0000000000000001 ffffffffffffffef ffffff8008d01000
[    0.252030] ba40: 0000000000000000 ffffff8008d86000 000000000000004e ffffff8008cca9c8
[    0.252052] ba60: 00000000000001df 0000000000000000 0000000000000000 ffffff800843f498
[    0.252073] ba80: ffffff8008d4a235 726320746f6e6e61 7075642065746165 000000000000005e
[    0.252095] baa0: 000000000000005a 6c702f7375622f27 642f6d726f667461 662f736563697665
[    0.252117] bac0: 2e30303030373166 0000000000000006 0000000000000000 0000000000000000
[    0.252140] [<ffffff80081fed9c>] sysfs_warn_dup+0x5c/0x78
[    0.252155] [<ffffff80081ff1f0>] sysfs_do_create_link_sd.isra.0+0xc0/0xd0
[    0.252170] [<ffffff80081ff220>] sysfs_create_link+0x20/0x40
[    0.252189] [<ffffff80085015f4>] bus_add_device+0xf4/0x198
[    0.252204] [<ffffff80084ff69c>] device_add+0x3b4/0x598
[    0.252221] [<ffffff80086f1274>] of_device_add+0x5c/0x70
[    0.252236] [<ffffff80086f1b48>] of_platform_device_create_pdata+0x90/0xf8
[    0.252252] [<ffffff80086f1cb4>] of_platform_bus_create+0xe4/0x318
[    0.252268] [<ffffff80086f2034>] of_platform_populate+0x6c/0xc0
[    0.252286] [<ffffff8008c5ebe0>] of_platform_default_populate_init+0x64/0x78
[    0.252304] [<ffffff80080830b8>] do_one_initcall+0x38/0x128
[    0.252320] [<ffffff8008c30c94>] kernel_init_freeable+0x140/0x1e0
[    0.252335] [<ffffff8008946548>] kernel_init+0x10/0x100
[    0.252350] [<ffffff8008082e80>] ret_from_fork+0x10/0x50
[    0.270462] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    0.336381] raid6: int64x1  gen()   372 MB/s
[    0.404340] raid6: int64x1  xor()   405 MB/s
[    0.472376] raid6: int64x2  gen()   618 MB/s
[    0.540418] raid6: int64x2  xor()   548 MB/s
[    0.608512] raid6: int64x4  gen()   902 MB/s
[    0.676503] raid6: int64x4  xor()   677 MB/s
[    0.744557] raid6: int64x8  gen()  1049 MB/s
[    0.812606] raid6: int64x8  xor()   684 MB/s
[    0.880727] raid6: neonx1   gen()   662 MB/s
[    0.948705] raid6: neonx1   xor()   695 MB/s
[    1.016770] raid6: neonx2   gen()  1069 MB/s
[    1.084820] raid6: neonx2   xor()   948 MB/s
[    1.152855] raid6: neonx4   gen()  1378 MB/s
[    1.220903] raid6: neonx4   xor()  1083 MB/s
[    1.288976] raid6: neonx8   gen()  1454 MB/s
[    1.356999] raid6: neonx8   xor()  1118 MB/s
[    1.357013] raid6: using algorithm neonx8 gen() 1454 MB/s
[    1.357025] raid6: .... xor() 1118 MB/s, rmw enabled
[    1.357038] raid6: using intx1 recovery algorithm
[    1.357522] GPIO IRQ not connected
[    1.357537] XGpio: /amba_pl@0/gpio@80000000: registered, base is 509
[    1.357822] GPIO IRQ not connected
[    1.357835] XGpio: /amba_pl@0/gpio@80001000: registered, base is 501
[    1.358556] SCSI subsystem initialized
[    1.358765] usbcore: registered new interface driver usbfs
[    1.358811] usbcore: registered new interface driver hub
[    1.358859] usbcore: registered new device driver usb
[    1.358951] media: Linux media interface: v0.10
[    1.358992] Linux video capture interface: v2.00
[    1.359037] pps_core: LinuxPPS API ver. 1 registered
[    1.359051] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    1.359086] PTP clock support registered
[    1.359126] EDAC MC: Ver: 3.0.0
[    1.359573] FPGA manager framework
[    1.359732] fpga-region fpga-full: FPGA Region probed
[    1.359859] Advanced Linux Sound Architecture Driver Initialized.
[    1.360218] Bluetooth: Core ver 2.22
[    1.360259] NET: Registered protocol family 31
[    1.360273] Bluetooth: HCI device and connection manager initialized
[    1.360292] Bluetooth: HCI socket layer initialized
[    1.360308] Bluetooth: L2CAP socket layer initialized
[    1.360332] Bluetooth: SCO socket layer initialized
[    1.360987] clocksource: Switched to clocksource arch_sys_counter
[    1.361102] VFS: Disk quotas dquot_6.6.0
[    1.361158] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    1.367716] NET: Registered protocol family 2
[    1.368136] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[    1.368269] TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
[    1.368579] TCP: Hash tables configured (established 16384 bind 16384)
[    1.368664] UDP hash table entries: 1024 (order: 3, 32768 bytes)
[    1.368717] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
[    1.368881] NET: Registered protocol family 1
[    1.369290] RPC: Registered named UNIX socket transport module.
[    1.369305] RPC: Registered udp transport module.
[    1.369318] RPC: Registered tcp transport module.
[    1.369330] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.369838] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[    1.370589] futex hash table entries: 1024 (order: 5, 131072 bytes)
[    1.370684] audit: initializing netlink subsys (disabled)
[    1.370720] audit: type=2000 audit(1.356:1): initialized
[    1.371323] workingset: timestamp_bits=62 max_order=19 bucket_order=0
[    1.372046] NFS: Registering the id_resolver key type
[    1.372072] Key type id_resolver registered
[    1.372085] Key type id_legacy registered
[    1.372103] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.372133] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    1.376926] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[    1.376951] io scheduler noop registered
[    1.376964] io scheduler deadline registered
[    1.377009] io scheduler cfq registered (default)
[    1.378353] xilinx-dpdma fd4c0000.dma: Xilinx DPDMA engine is probed
[    1.378663] Write failed gate address:1000f02
[    1.378770] xilinx-zynqmp-dma fd500000.dma: ZynqMP DMA driver Probe success
[    1.378913] xilinx-zynqmp-dma fd510000.dma: ZynqMP DMA driver Probe success
[    1.379059] xilinx-zynqmp-dma fd520000.dma: ZynqMP DMA driver Probe success
[    1.379203] xilinx-zynqmp-dma fd530000.dma: ZynqMP DMA driver Probe success
[    1.379346] xilinx-zynqmp-dma fd540000.dma: ZynqMP DMA driver Probe success
[    1.379489] xilinx-zynqmp-dma fd550000.dma: ZynqMP DMA driver Probe success
[    1.379635] xilinx-zynqmp-dma fd560000.dma: ZynqMP DMA driver Probe success
[    1.379779] xilinx-zynqmp-dma fd570000.dma: ZynqMP DMA driver Probe success
[    1.379997] xilinx-zynqmp-dma ffa80000.dma: ZynqMP DMA driver Probe success
[    1.380146] xilinx-zynqmp-dma ffa90000.dma: ZynqMP DMA driver Probe success
[    1.380291] xilinx-zynqmp-dma ffaa0000.dma: ZynqMP DMA driver Probe success
[    1.380438] xilinx-zynqmp-dma ffab0000.dma: ZynqMP DMA driver Probe success
[    1.380584] xilinx-zynqmp-dma ffac0000.dma: ZynqMP DMA driver Probe success
[    1.380729] xilinx-zynqmp-dma ffad0000.dma: ZynqMP DMA driver Probe success
[    1.380877] xilinx-zynqmp-dma ffae0000.dma: ZynqMP DMA driver Probe success
[    1.381045] xilinx-zynqmp-dma ffaf0000.dma: ZynqMP DMA driver Probe success
[    1.381238] zynqmp_pm firmware: Power management API v0.3
[    1.381356] xenfs: not registering filesystem on non-xen platform
[    1.413977] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    1.415456] ff000000.serial: ttyPS0 at MMIO 0xff000000 (irq = 40, base_baud = 6249999) is a xuartps
[    2.745311] console [ttyPS0] enabled
[    2.749224] ff010000.serial: ttyPS1 at MMIO 0xff010000 (irq = 41, base_baud = 6249999) is a xuartps
[    2.758423] [drm] Initialized
[    2.761687] [drm] load() is defered & will be called again
[    2.767610] xilinx-drm-dp-sub fd4aa000.dp_sub: Xilinx DisplayPort Subsystem is probed
[    2.775552] Unable to detect cache hierarchy from DT for CPU 0
[    2.786806] brd: module loaded
[    2.793034] loop: module loaded
[    2.807082] ahci-ceva fd0c0000.ahci: AHCI 0001.0301 32 slots 2 ports 6 Gbps 0x3 impl platform mode
[    2.815980] ahci-ceva fd0c0000.ahci: flags: 64bit ncq sntf pm clo only pmp fbs pio slum part ccc sds apst
[    2.826545] scsi host0: ahci-ceva
[    2.830030] scsi host1: ahci-ceva
[    2.833419] ata1: SATA max UDMA/133 mmio [mem 0xfd0c0000-0xfd0c1fff] port 0x100 irq 37
[    2.841265] ata2: SATA max UDMA/133 mmio [mem 0xfd0c0000-0xfd0c1fff] port 0x180 irq 37
[    2.849316] mtdoops: mtd device (mtddev=name/number) must be supplied
[    2.856573] m25p80 spi0.0: found n25q256a, expected n25q512a
[    2.862297] m25p80 spi0.0: n25q256a (65536 Kbytes)
[    2.867024] 3 ofpart partitions found on MTD device spi0.0
[    2.872476] Creating 3 MTD partitions on "spi0.0":
[    2.877255] 0x000000000000-0x000000100000 : "boot"
[    2.882612] 0x000000100000-0x000000140000 : "bootenv"
[    2.888119] 0x000000140000-0x000001740000 : "kernel"
[    2.894455] libphy: Fixed MDIO Bus: probed
[    2.899723] tun: Universal TUN/TAP device driver, 1.6
[    2.904711] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    2.911025] CAN device driver interface
[    2.915374] macb ff0e0000.ethernet: Not enabling partial store and forward
[    2.922733] libphy: MACB_mii_bus: probed
[    2.928958] macb ff0e0000.ethernet eth0: Could not attach to PHY
[    2.977626] usbcore: registered new interface driver asix
[    2.983000] usbcore: registered new interface driver ax88179_178a
[    2.989055] usbcore: registered new interface driver cdc_ether
[    2.994870] usbcore: registered new interface driver net1080
[    3.000511] usbcore: registered new interface driver cdc_subset
[    3.006414] usbcore: registered new interface driver zaurus
[    3.011979] usbcore: registered new interface driver cdc_ncm
[    3.017981] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    3.024434] ehci-pci: EHCI PCI platform driver
[    3.029119] usbcore: registered new interface driver uas
[    3.034392] usbcore: registered new interface driver usb-storage
[    3.040654] mousedev: PS/2 mouse device common for all mice
[    3.046617] rtc_zynqmp ffa60000.rtc: rtc core: registered ffa60000.rtc as rtc0
[    3.053803] i2c /dev entries driver
[    3.057461] cdns-i2c ff030000.i2c: 400 kHz mmio ff030000 irq 32
[    3.064370] usbcore: registered new interface driver uvcvideo
[    3.070039] USB Video Class driver (1.1.1)
[    3.074744] cdns-wdt fd4d0000.watchdog: Xilinx Watchdog Timer at ffffff8008f61000 with timeout 10s
[    3.083815] Bluetooth: HCI UART driver ver 2.3
[    3.088190] Bluetooth: HCI UART protocol H4 registered
[    3.093308] Bluetooth: HCI UART protocol BCSP registered
[    3.098601] Bluetooth: HCI UART protocol LL registered
[    3.103721] Bluetooth: HCI UART protocol ATH3K registered
[    3.109103] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    3.115393] Bluetooth: HCI UART protocol Intel registered
[    3.120774] Bluetooth: HCI UART protocol Broadcom registered
[    3.126378] Bluetooth: HCI UART protocol QCA registered
[    3.131621] usbcore: registered new interface driver bcm203x
[    3.137262] usbcore: registered new interface driver bpa10x
[    3.142819] usbcore: registered new interface driver bfusb
[    3.148285] usbcore: registered new interface driver btusb
[    3.153720] Bluetooth: Generic Bluetooth SDIO driver ver 0.1
[    3.159413] usbcore: registered new interface driver ath3k
[    3.163257] ata1: SATA link down (SStatus 0 SControl 330)
[    3.163291] ata2: SATA link down (SStatus 0 SControl 330)
[    3.175724] EDAC MC: ECC not enabled
[    3.179391] EDAC DEVICE0: Giving out device to module zynqmp-ocm-edac controller zynqmp_ocm: DEV ff960000.memory-controller (INTERRUPT)
[    3.192027] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 1099999 KHz
[    3.199411] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed to: 1199999 KHz
[    3.208284] sdhci: Secure Digital Host Controller Interface driver
[    3.214386] sdhci: Copyright(c) Pierre Ossman
[    3.218723] sdhci-pltfm: SDHCI platform and OF driver helper
[    3.269001] mmc0: SDHCI controller on ff160000.sdhci [ff160000.sdhci] using ADMA 64-bit
[    3.324996] mmc1: SDHCI controller on ff170000.sdhci [ff170000.sdhci] using ADMA 64-bit
[    3.333193] ledtrig-cpu: registered to indicate activity on CPUs
[    3.339264] usbcore: registered new interface driver usbhid
[    3.344761] usbhid: USB HID core driver
[    3.350371] fpga_manager fpga0: Xilinx ZynqMP FPGA Manager registered
[    3.357318] xilinx-dp-snd-pcm dp_snd_pcm0: Xilinx DisplayPort Sound PCM probed
[    3.364508] xilinx-dp-snd-pcm dp_snd_pcm1: Xilinx DisplayPort Sound PCM probed
[    3.372713] Write failed to divider address:fd1a00c0
[    3.377933] xilinx-dp-snd-codec dp_snd_codec0: Xilinx DisplayPort Sound Codec probed
[    3.386030] xilinx-dp-snd-card dp_snd_card: xilinx-dp-snd-codec-dai <-> xilinx-dp-snd-codec-dai mapping ok
[    3.395757] xilinx-dp-snd-card dp_snd_card: xilinx-dp-snd-codec-dai <-> xilinx-dp-snd-codec-dai mapping ok
[    3.407674] xilinx-dp-snd-card dp_snd_card: Xilinx DisplayPort Sound Card probed
[    3.407774] mmc0: new HS200 MMC card at address 0001
[    3.408068] mmcblk0: mmc0:0001 Q2J55L 7.09 GiB
[    3.408172] mmcblk0boot0: mmc0:0001 Q2J55L partition 1 16.0 MiB
[    3.408272] mmcblk0boot1: mmc0:0001 Q2J55L partition 2 16.0 MiB
[    3.408368] mmcblk0rpmb: mmc0:0001 Q2J55L partition 3 4.00 MiB
[    3.409189]  mmcblk0: p1
[    3.444712] pktgen: Packet Generator for packet performance testing. Version: 2.75
[    3.452393] Netfilter messages via NETLINK v0.30.
[    3.457155] ip_tables: (C) 2000-2006 Netfilter Core Team
[    3.462450] Initializing XFRM netlink socket
[    3.466698] NET: Registered protocol family 10
[    3.471513] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    3.476886] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    3.483126] NET: Registered protocol family 17
[    3.487510] NET: Registered protocol family 15
[    3.491934] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    3.504867] Ebtables v2.0 registered
[    3.505731] mmc1: error -110 whilst initialising SD card
[    3.513748] can: controller area network core (rev 20120528 abi 9)
[    3.519908] NET: Registered protocol family 29
[    3.524303] can: raw protocol (rev 20120528)
[    3.528554] can: broadcast manager protocol (rev 20161123 t)
[    3.534197] can: netlink gateway (rev 20130117) max_hops=1
[    3.539723] Bluetooth: RFCOMM TTY layer initialized
[    3.544531] Bluetooth: RFCOMM socket layer initialized
[    3.549653] Bluetooth: RFCOMM ver 1.11
[    3.553382] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    3.558672] Bluetooth: BNEP filters: protocol multicast
[    3.563883] Bluetooth: BNEP socket layer initialized
[    3.568827] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    3.574734] Bluetooth: HIDP socket layer initialized
[    3.579866] 9pnet: Installing 9P2000 support
[    3.584078] Key type dns_resolver registered
[    3.588825] registered taskstats version 1
[    3.593279] Btrfs loaded, crc32c=crc32c-generic
[    3.608666] PLL: shutdown
[    3.611326] [drm] load() is defered & will be called again
[    3.617439] xilinx-psgtr fd400000.zynqmp_phy: Lane:3 type:8 protocol:4 pll_locked:yes
[    3.625498] xilinx-drm-dp fd4a0000.dp: device found, version 4.010
[    3.631607] xilinx-drm-dp fd4a0000.dp: Display Port, version 1.0200 (tx)
[    3.639572] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    3.644996] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
[    3.652892] xhci-hcd xhci-hcd.0.auto: hcc params 0x0238f625 hci version 0x100 quirks 0x02010010
[    3.661547] xhci-hcd xhci-hcd.0.auto: irq 220, io mem 0xfe200000
[    3.667637] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    3.674358] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.681566] usb usb1: Product: xHCI Host Controller
[    3.686418] usb usb1: Manufacturer: Linux 4.9.0-xilinx-v2017.3 xhci-hcd
[    3.693019] usb usb1: SerialNumber: xhci-hcd.0.auto
[    3.698217] hub 1-0:1.0: USB hub found
[    3.701916] hub 1-0:1.0: 1 port detected
[    3.705986] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    3.711405] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[    3.719092] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    3.727209] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    3.733919] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.741127] usb usb2: Product: xHCI Host Controller
[    3.745980] usb usb2: Manufacturer: Linux 4.9.0-xilinx-v2017.3 xhci-hcd
[    3.752577] usb usb2: SerialNumber: xhci-hcd.0.auto
[    3.757725] hub 2-0:1.0: USB hub found
[    3.761414] hub 2-0:1.0: 1 port detected
[    3.766271] PLL: enable
[    3.768822] PLL: shutdown
[    3.771554] OF: graph: no port node found in /xilinx_drm
[    3.776788] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    3.783382] [drm] No driver support for vblank timestamp query.
[    3.813699] PLL: enable
[    3.848269] Console: switching to colour frame buffer device 160x64
[    3.865251] xilinx-drm xilinx_drm: fb0:  frame buffer device
[    3.980993] [drm] Initialized xilinx_drm 1.0.0 20130509 on minor 0
[    3.987392] rtc_zynqmp ffa60000.rtc: setting system clock to 1970-01-01 00:00:23 UTC (23)
[    3.995684] clk: Not disabling unused clocks
[    3.999954] ALSA device list:
[    4.002864]   #0: DisplayPort monitor
[    4.007157] VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2): error -6
[    4.015083] Please append a correct "root=" boot option; here are the available partitions:
[    4.023438] 0100           65536 ram0 [    4.026967]  (driver?)
[    4.029300] 0101           65536 ram1 [    4.032868]  (driver?)
[    4.035201] 0102           65536 ram2 [    4.038770]  (driver?)
[    4.041103] 0103           65536 ram3 [    4.044668]  (driver?)
[    4.047010] 0104           65536 ram4 [    4.050575]  (driver?)
[    4.052904] 0105           65536 ram5 [    4.056477]  (driver?)
[    4.058811] 0106           65536 ram6 [    4.062380]  (driver?)
[    4.064713] 0107           65536 ram7 [    4.068285]  (driver?)
[    4.070616] 0108           65536 ram8 [    4.074186]  (driver?)
[    4.076514] 0109           65536 ram9 [    4.080091]  (driver?)
[    4.082421] 010a           65536 ram10 [    4.086078]  (driver?)
[    4.088405] 010b           65536 ram11 [    4.092066]  (driver?)
[    4.094399] 010c           65536 ram12 [    4.098061]  (driver?)
[    4.100384] 010d           65536 ram13 [    4.104045]  (driver?)
[    4.106377] 010e           65536 ram14 [    4.110034]  (driver?)
[    4.112362] 010f           65536 ram15 [    4.116028]  (driver?)
[    4.118360] 1f00            1024 mtdblock0 [    4.122364]  (driver?)
[    4.124688] 1f01             256 mtdblock1 [    4.128700]  (driver?)
[    4.131033] 1f02           22528 mtdblock2 [    4.135037]  (driver?)
[    4.137365] b300         7438336 mmcblk0 [    4.141198]  driver: mmcblk
[    4.143962]   b301          250040 mmcblk0p1 00000000-01[    4.149113]
[    4.150546] b318            4096 mmcblk0rpmb [    4.154742]  (driver?)
[    4.157071] b310           16384 mmcblk0boot1 [    4.161340]  (driver?)
[    4.163666] b308           16384 mmcblk0boot0 [    4.167937]  (driver?)
[    4.170263] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
[    4.178739] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G        W       4.9.0-xilinx-v2017.3 #1
[    4.187076] Hardware name: xlnx,zynqmp (DT)
[    4.191210] Call trace:
[    4.193633] [<ffffff8008088138>] dump_backtrace+0x0/0x198
[    4.199038] [<ffffff80080882e4>] show_stack+0x14/0x20
[    4.206541] [<ffffff80083de514>] dump_stack+0x94/0xb8
[    4.214002] [<ffffff800812e9a8>] panic+0x114/0x25c
[    4.221176] [<ffffff8008c310e8>] mount_block_root+0x198/0x270
[    4.229297] [<ffffff8008c313f8>] mount_root+0x11c/0x134
[    4.236885] [<ffffff8008c3157c>] prepare_namespace+0x16c/0x1b4
[    4.245100] [<ffffff8008c30d14>] kernel_init_freeable+0x1c0/0x1e0
[    4.253575] [<ffffff8008946548>] kernel_init+0x10/0x100
[    4.261169] [<ffffff8008082e80>] ret_from_fork+0x10/0x50
[    4.268816] SMP: stopping secondary CPUs
[    4.275039] Kernel Offset: disabled
[    4.280782] Memory Limit: none
[    4.286065] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
[    4.746222] random: fast init done

 

I have also attached boot logs for mmcblk0p0 and  mmcblk0p1 as well 

 

I tried getting info on mmc from terminal :

 

mmcinfo.JPG

 

it shows 2 listed SD partitions :

 

mmcpart.JPG

 

but during the boot finds only one :

 

[    3.413553]  mmcblk0: p1
[    4.122892] 1f02           22528 mtdblock2 [    4.126900]  (driver?)
[    4.129228] b300         7438336 mmcblk0 [    4.133062]  driver: mmcblk
[    4.135829]   b301          250040 mmcblk0p1 00000000-01[    4.140973]
[    4.142409] b318            4096 mmcblk0rpmb [    4.146605]  (driver?)

 

Settings :

Following are the petalinux settings i am using :

 

>>petalinux-config 

--Subsystem AUTO Hardware Settings --> Advance bootable images storage Settings 

--> boot image settings --> primary SD card

--> u-boot env partition --> primary flash

--> kernel image --> primary sd

--> jffs2 --> primary flash

--> dtb image settings --> from boot image (i tried it from SD but was getting unable to read system.dtb file error )



--Image Packaging Configuration

--> Root filesystem type --> SD card

 

Following are the u-boot and device-tree changes i made after i read about SD boot issues and patches:

 

zynqmp.dtsi :

mmcblkerr_1.PNG

 

platform-top.h

mmcblkerr_3.PNG

 

system-user.dtsi

 

mmcblkerr_4.PNG

and patches to device tee

mmcblkerr_5.PNG

 

Boot args 

I am either modifying the boot args via system-user.dtsi file or from uEnv.txt  or will update it during u-boot prompt.

 

Following is how i changed the boot args to check against mmcblk0p0, mmcblk0p1 and mmcblk0p2: 

 

 

bootargs 'earlycon earlyprintk clk_ignore_unused root=/dev/mmcblk0p2 rw rootwait uio_pdrv_genirq.of_id=generic-uio cma=1024M rootfstype=ext3 init=/bin/sh stdout-path = serial0:115200n8'

 

 

SD Card (via Gparted): 

 

This is how my SD card looks in Gparted 

 

Screenshot from 2018-02-16 19-17-49.png

 

 

 

Please help me out.I am stuck in this for some good time and not not able to identify the cause of this. Please let me know if there are any setting changes or patches i need to use.

 

 

0 Kudos
1 Solution

Accepted Solutions
Adventurer
Adventurer
7,611 Views
Registered: ‎11-10-2017

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

hi @trigger

 

Finaly, I was able to boot from my SD card !! YAY !! 

 

Following are the changes i made:

 

1. Enabled WP and power pins for SD1 in Vivado design

 

And this is the important one :

 

2. I was earlier using VirtualBox Ubuntu image to use petalinux and generate boot images. Now I migrated to actual ubuntu system and using the same HDF files re-created the application project in petalinux and boot images.

 

 (also to mention I updated Ubuntu 16.04.3 - using sudo apt-get update)

 

3. I made the sd card partitions in the folloing manner :

 

    4 MB - UNUSED SPACE

    450 MB - BOOT  : enabled boot and lba flags

    7 GB - ROOTFS

 

previously it was :

 

    4 MB - UNUSED SPACE

    450 MB - BOOT  : enabled boot flag

    4 MB - UNUSED SPACE

    7 GB - ROOTFS

 

and copied the boot images directly from the proj directory. Earlier i was using WinSCP to transfer files from VM to pendrive then to SD card via linux system.

 

What confuse me is what change actually affected the process to be successful and why ? 

 

Thanks for all the help and guidance. !! 

 

Regards

 

Vishal

0 Kudos
35 Replies
Explorer
Explorer
5,160 Views
Registered: ‎09-14-2016

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

Hi @vish.bh30,

 

I think your are really close to the solution,

 

[    0.000000] Kernel command line: earlycon earlyprintk clk_ignore_unused root=/dev/mmcblk0p2 rw rootwait uio_pdrv_genirq.of_id=generic-uio cma=1024M

 

rootfstype is not set in your cmd line (with p2) ,

 

According to your log file (with p1)

[    0.251632] sysfs: cannot create duplicate filename '/bus/platform/devices/ff170000.sdhci'

You should check in your kernel configuration that ext3 support is activated :

https://cateee.net/lkddb/web-lkddb/EXT3_FS.html

 

So, check your kernel configuration and set cmd line in u-boot env 

 

Cheers,

Trigger

0 Kudos
Explorer
Explorer
5,131 Views
Registered: ‎10-19-2017

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

When I do this, I make 2 partitions

>>petalinux-config 

--Subsystem AUTO Hardware Settings --> Advance bootable images storage Settings 

--> boot image settings --> primary SD card

--> u-boot env partition --> primary sd

--> kernel image --> primary sd

--> jffs2 --> primary flash

--> dtb image settings --> primary sd



--Image Packaging Configuration

--> Root filesystem type --> SD card

 

 

I make two partitions

1. FAT32 with system.dtb, image.ub and BOOT.BIN (from petalinux-package)

2. ext4, with untarred rootfs (mnt /dev/sd<X> /mnt/<whatever>; cp <project>/images/linux/rootfs.tar.gz /mnt/<whatever>; cd /mnt/<whatever>; tar -zxvf rootfs.tar.gz; rm rootfs.tar.gz 

 

AND IF YOUR SD CARD HAS A READ-ONLY MECHANICAL SWITCH ON THE SIDE, MAKE SURE IT IS PUSHED ALL THE WAY UP OR TO THE NOT READ-ONLY POSITION.

 

I work with zc706, so I am not sure if it is the same for MPSoC

0 Kudos
Adventurer
Adventurer
5,078 Views
Registered: ‎11-10-2017

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

Hello @jackfrye11 @trigger

 

 

--> dtb image settings --> primary sd

If I select this setting i am getting err:

 

reading system.dtb
** Unable to read file system.dtb **

I found that there is a issue with petalinux : https://www.xilinx.com/support/answers/70304.html

 

so i did what is mentioned there... :

 

After I executed the work around given in the AR#70304 I am still not able to load root fs in the mmcblk0p1 / p2

 

this is my boot log:

 

Xilinx Zynq MP First Stage Boot Loader
Release 2017.3   Feb 19 2018  -  12:45:11
NOTICE:  ATF running on XCZU3EG/silicon v4/RTL5.1 at 0xfffea000, with PMU firmware
NOTICE:  BL31: Secure code at 0x0
NOTICE:  BL31: Non secure code at 0x8000000
NOTICE:  BL31: v1.3(release):f9b244b
NOTICE:  BL31: Built : 07:12:50, Feb 19 2018


U-Boot 2017.01 (Feb 19 2018 - 12:45:23 +0530) Xilinx ZynqMP ZCU102 revB

I2C:   ready
DRAM:  2 GiB
ERROR: usb dr_mode not found

at /home/vishal/myxprj/build/tmp/work/plnx_aarch64-xilinx-linux/u-boot-xlnx/v2017.01-xilinx-v2017.3+gitAUTOINC+da811c4511-r0/git/drivers/usb/common/common.c:32/usb_get_dr_mode()
EL Level:       EL2
Chip ID:        xczu3eg
MMC:   sdhci@ff160000: 0 (eMMC), sdhci@ff170000: 1 (SD), sdhci@ff170000: 2 (SD)
zynqmp_qspi_ofdata_to_platdata: CLK 124999999
SF: Detected n25q256a with page size 512 Bytes, erase size 128 KiB, total 64 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Bootmode: SD_MODE1
Net:   ZYNQ GEM: ff0e0000, phyaddr ffffffff, interface rgmii-id
eth0: ethernet@ff0e0000
U-BOOT for myxprj

ethernet@ff0e0000 Waiting for PHY auto negotiation to complete........ done
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10
BOOTP broadcast 11
BOOTP broadcast 12
BOOTP broadcast 13
BOOTP broadcast 14
BOOTP broadcast 15
BOOTP broadcast 16
BOOTP broadcast 17

Retry time exceeded
Hit any key to stop autoboot:  0
ZynqMP>
ZynqMP>
ZynqMP>
ZynqMP>
ZynqMP>
ZynqMP> mmc info
Device: sdhci@ff160000
Manufacturer ID: 13
OEM: 14e
Name: Q2J55
Tran Speed: 200000000
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 7.1 GiB
Bus Width: 8-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
ZynqMP>
ZynqMP> mmc list
sdhci@ff160000: 0 (eMMC)
sdhci@ff170000: 1 (SD)
sdhci@ff170000: 2 (SD)
ZynqMP>
sdhci@ff160000: 0 (eMMC)
sdhci@ff170000: 1 (SD)
sdhci@ff170000: 2 (SD)
ZynqMP>
sdhci@ff160000: 0 (eMMC)
sdhci@ff170000: 1 (SD)
sdhci@ff170000: 2 (SD)
ZynqMP>
sdhci@ff160000: 0 (eMMC)
sdhci@ff170000: 1 (SD)
sdhci@ff170000: 2 (SD)
ZynqMP>
sdhci@ff160000: 0 (eMMC)
sdhci@ff170000: 1 (SD)
sdhci@ff170000: 2 (SD)
ZynqMP>
sdhci@ff160000: 0 (eMMC)
sdhci@ff170000: 1 (SD)
sdhci@ff170000: 2 (SD)
ZynqMP>
sdhci@ff160000: 0 (eMMC)
sdhci@ff170000: 1 (SD)
sdhci@ff170000: 2 (SD)
ZynqMP>
sdhci@ff160000: 0 (eMMC)
sdhci@ff170000: 1 (SD)
sdhci@ff170000: 2 (SD)
ZynqMP> setenv bootargs 'earlycon earlyprintk clk_ignore_unused root=/dev/mmcblk0p1 rw rootfstype=ext4 uio_pdrv_genirq.of_id=generic-uio cma=1024M  console=ttyPS0,115200 stdout-path=serial0:115200n8'
ZynqMP>
ZynqMP> setenv cp_dtb2ram 'mmcinfo && fatload mmc 0:1 ${dtbnetstart} ${dtb_img}'
ZynqMP>
ZynqMP> setenv default_bootcmd 'run cp_kernel2ram && run cp_dtb2ram && booti ${netstart} - ${dtbnetstart}'
ZynqMP>
ZynqMP> boot
Device: sdhci@ff160000
Manufacturer ID: 13
OEM: 14e
Name: Q2J55
Tran Speed: 200000000
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 7.1 GiB
Bus Width: 8-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
reading image.ub
13610908 bytes read in 1002 ms (13 MiB/s)
Device: sdhci@ff160000
Manufacturer ID: 13
OEM: 14e
Name: Q2J55
Tran Speed: 200000000
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 7.1 GiB
Bus Width: 8-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
reading system.dtb
** Unable to read file system.dtb **
ZynqMP>
ZynqMP> bootm
## Loading kernel from FIT Image at 10000000 ...
   Using 'conf@2' configuration
   Trying 'kernel@0' kernel subimage
     Description:  Linux Kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x100000d8
     Data Size:    13576704 Bytes = 12.9 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x00080000
     Entry Point:  0x00080000
     Hash algo:    sha1
     Hash value:   31f41b74be76a7e384bd5151d1e9b43b4b4a85b9
   Verifying Hash Integrity ... sha1+ OK
## Loading fdt from FIT Image at 10000000 ...
   Using 'conf@2' configuration
   Trying 'fdt@0' fdt subimage
     Description:  Flattened Device Tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x10cf2bd0
     Data Size:    32899 Bytes = 32.1 KiB
     Architecture: AArch64
     Hash algo:    sha1
     Hash value:   3bc635dab2a9e8e5ce6d97d2500bf3c1b7770c17
   Verifying Hash Integrity ... sha1+ OK
   Booting using the fdt blob at 0x10cf2bd0
   Loading Kernel Image ... OK
   Loading Device Tree to 0000000007ff4000, end 0000000007fff082 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.9.0-xilinx-v2017.3 (vishal@vishal-VirtualBox) (gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11) ) #1 SMP Mon Feb 19 12:54:50 IST 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 1024 MiB at 0x0000000040000000
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.0 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 @ffffffc03ff7a000 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: 517120
[    0.000000] Kernel command line: earlycon earlyprintk clk_ignore_unused root=/dev/mmcblk0p1 rw rootfstype=ext4 uio_pdrv_genirq.of_id=generic-uio cma=1024M  console=ttyPS0,115200 stdout-path=serial0:115200n8
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.000000] Memory: 1002564K/2097152K available (9276K kernel code, 586K rwdata, 2860K rodata, 512K init, 395K bss, 46012K reserved, 1048576K 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 - 0xffffff8008990000   (  9280 KB)
[    0.000000]     .rodata : 0xffffff8008990000 - 0xffffff8008c60000   (  2880 KB)
[    0.000000]       .init : 0xffffff8008c60000 - 0xffffff8008ce0000   (   512 KB)
[    0.000000]       .data : 0xffffff8008ce0000 - 0xffffff8008d72a00   (   587 KB)
[    0.000000]        .bss : 0xffffff8008d72a00 - 0xffffff8008dd5934   (   396 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 - 0xffffffbf01c00000   (    28 MB actual)
[    0.000000]     memory  : 0xffffffc000000000 - 0xffffffc080000000   (  2048 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.000004] sched_clock: 56 bits at 99MHz, resolution 10ns, wraps every 4398046511101ns
[    0.008274] Console: colour dummy device 80x25
[    0.012548] Calibrating delay loop (skipped), value calculated using timer frequency.. 199.99 BogoMIPS (lpj=399996)
[    0.022905] pid_max: default: 32768 minimum: 301
[    0.027602] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
[    0.034157] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes)
[    0.041900] ASID allocator initialised with 65536 entries
[    0.047670] zynqmp_plat_init Power management API v0.3
[    0.052694] EFI services will not be available.
[    0.057487] Detected VIPT I-cache on CPU1
[    0.057520] CPU1: Booted secondary processor [410fd034]
[    0.057812] Detected VIPT I-cache on CPU2
[    0.057831] CPU2: Booted secondary processor [410fd034]
[    0.058108] Detected VIPT I-cache on CPU3
[    0.058127] CPU3: Booted secondary processor [410fd034]
[    0.058165] Brought up 4 CPUs
[    0.088454] SMP: Total of 4 processors activated.
[    0.093132] CPU features: detected feature: 32-bit EL0 Support
[    0.098928] CPU: All CPU(s) started at EL2
[    0.103002] alternatives: patching kernel code
[    0.108200] devtmpfs: initialized
[    0.116118] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.151276] xor: measuring software checksum speed
[    0.195959]    8regs     :  2111.000 MB/sec
[    0.235988]    8regs_prefetch:  1882.000 MB/sec
[    0.280361]    32regs    :  2594.000 MB/sec
[    0.320394]    32regs_prefetch:  2183.000 MB/sec
[    0.324822] xor: using function: 32regs (2594.000 MB/sec)
[    0.330282] pinctrl core: initialized pinctrl subsystem
[    0.336061] NET: Registered protocol family 16
[    0.356349] cpuidle: using governor menu
[    0.360294] Failed to initialise IOMMU /amba/smmu@fd800000
[    0.365851] vdso: 2 pages (1 code @ ffffff8008997000, 1 data @ ffffff8008ce4000)
[    0.373055] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.380433] DMA: preallocated 256 KiB pool for atomic allocations
[    0.396944] reset_zynqmp reset-controller: Xilinx zynqmp reset driver probed
[    0.404665] ARM CCI_400_r1 PMU driver probed[    0.412039] zynqmp-pinctrl ff180000.pinctrl: zynqmp pinctrl initialized
[    0.419849] sysfs: cannot create duplicate filename '/bus/platform/devices/ff170000.sdhci'
[    0.427924] ------------[ cut here ]------------
[    0.432498] WARNING: CPU: 2 PID: 1 at /home/vishal/myxprj/build/tmp/work-shared/plnx_aarch64/kernel-source/fs/sysfs/dir.c:31 sysfs_warn_dup+0x5c/0x78
[    0.445806] Modules linked in:
[    0.448833]
[    0.450308] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.9.0-xilinx-v2017.3 #1
[    0.457397] Hardware name: xlnx,zynqmp (DT)
[    0.461550] task: ffffffc03d866c00 task.stack: ffffffc03d868000
[    0.467433] PC is at sysfs_warn_dup+0x5c/0x78
[    0.471758] LR is at sysfs_warn_dup+0x5c/0x78
[    0.476082] pc : [<ffffff8008202564>] lr : [<ffffff8008202564>] pstate: 60000045
[    0.483434] sp : ffffffc03d86bb80
[    0.486721] x29: ffffffc03d86bb80 x28: 0000000000000000
[    0.491997] x27: 0000000000000000 x26: ffffff8008db7000
[    0.497274] x25: 0000000000000000 x24: ffffff8008d31000
[    0.502550] x23: ffffffffffffffef x22: 0000000000000001
[    0.507827] x21: ffffffc03d822ac8 x20: ffffffc03d034500
[    0.513103] x19: ffffffc03da33000 x18: 0000000000000010
[    0.518380] x17: 0000000000000000 x16: 0000000000000000
[    0.523657] x15: 0000000000000006 x14: 662f736563697665
[    0.528933] x13: 642f6d726f667461 x12: 6c702f7375622f27
[    0.534210] x11: 20656d616e656c69 x10: 0000000000000058
[    0.539486] x9 : 000000000000005e x8 : 726320746f6e6e61
[    0.544763] x7 : 63203a7366737973 x6 : ffffff8008d7b235
[    0.550039] x5 : 0000000000000006 x4 : 0000000000000000
[    0.555316] x3 : 0000000000000000 x2 : 00000000000001cf
[    0.560592] x1 : ffffff8008cfaa48 x0 : 000000000000004e
[    0.565868]
[    0.567344] ---[ end trace a02e3e94048cb8f3 ]---
[    0.571924] Call trace:
[    0.574349] Exception stack(0xffffffc03d86b9b0 to 0xffffffc03d86bae0)
[    0.580749] b9a0:                                   ffffffc03da33000 0000008000000000
[    0.588535] b9c0: ffffffc03d86bb80 ffffff8008202564 ffffff8008d7d5fa 000000000000004e
[    0.596320] b9e0: ffffffc03d86ba00 ffffff80080d908c ffffff8008d7ac68 ffffff8008b1f990
[    0.604105] ba00: ffffffc03d86baa0 ffffff80080d9364 ffffffc03da33000 ffffffc03d034500
[    0.611890] ba20: ffffffc03d822ac8 0000000000000001 ffffffffffffffef ffffff8008d31000
[    0.619675] ba40: 0000000000000000 ffffff8008db7000 000000000000004e ffffff8008cfaa48
[    0.627460] ba60: 00000000000001cf 0000000000000000 0000000000000000 0000000000000006
[    0.635245] ba80: ffffff8008d7b235 63203a7366737973 726320746f6e6e61 000000000000005e
[    0.643030] baa0: 0000000000000058 20656d616e656c69 6c702f7375622f27 642f6d726f667461
[    0.650815] bac0: 662f736563697665 0000000000000006 0000000000000000 0000000000000000
[    0.658600] [<ffffff8008202564>] sysfs_warn_dup+0x5c/0x78
[    0.663964] [<ffffff80082029b8>] sysfs_do_create_link_sd.isra.0+0xc0/0xd0
[    0.670710] [<ffffff80082029e8>] sysfs_create_link+0x20/0x40
[    0.676335] [<ffffff80085298ec>] bus_add_device+0xf4/0x198
[    0.681785] [<ffffff8008527994>] device_add+0x3b4/0x598
[    0.686975] [<ffffff8008722d8c>] of_device_add+0x5c/0x70
[    0.692250] [<ffffff8008723660>] of_platform_device_create_pdata+0x90/0xf8
[    0.699083] [<ffffff80087237cc>] of_platform_bus_create+0xe4/0x318
[    0.705225] [<ffffff8008723b4c>] of_platform_populate+0x6c/0xc0
[    0.711109] [<ffffff8008c8f134>] of_platform_default_populate_init+0x64/0x78
[    0.718115] [<ffffff80080830b8>] do_one_initcall+0x38/0x128
[    0.723650] [<ffffff8008c60c94>] kernel_init_freeable+0x140/0x1e0
[    0.729705] [<ffffff8008976500>] kernel_init+0x10/0x100
[    0.734894] [<ffffff8008082e80>] ret_from_fork+0x10/0x50
[    0.756478] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    0.827843] raid6: int64x1  gen()   377 MB/s
[    0.899946] raid6: int64x1  xor()   400 MB/s
[    0.971962] raid6: int64x2  gen()   621 MB/s
[    1.043973] raid6: int64x2  xor()   545 MB/s
[    1.116046] raid6: int64x4  gen()   901 MB/s
[    1.188079] raid6: int64x4  xor()   673 MB/s
[    1.260167] raid6: int64x8  gen()  1050 MB/s
[    1.332184] raid6: int64x8  xor()   682 MB/s
[    1.404302] raid6: neonx1   gen()   671 MB/s
[    1.476320] raid6: neonx1   xor()   691 MB/s
[    1.548386] raid6: neonx2   gen()  1079 MB/s
[    1.620400] raid6: neonx2   xor()   941 MB/s
[    1.692444] raid6: neonx4   gen()  1389 MB/s
[    1.764507] raid6: neonx4   xor()  1078 MB/s
[    1.836559] raid6: neonx8   gen()  1454 MB/s
[    1.908601] raid6: neonx8   xor()  1118 MB/s
[    1.912687] raid6: using algorithm neonx8 gen() 1454 MB/s
[    1.918046] raid6: .... xor() 1118 MB/s, rmw enabled
[    1.922976] raid6: using intx1 recovery algorithm
[    1.928113] GPIO IRQ not connected
[    1.931328] XGpio: /amba_pl@0/gpio@80000000: registered, base is 509
[    1.937854] GPIO IRQ not connected
[    1.941060] XGpio: /amba_pl@0/gpio@80001000: registered, base is 501
[    1.948162] SCSI subsystem initialized
[    1.951949] usbcore: registered new interface driver usbfs
[    1.957278] usbcore: registered new interface driver hub
[    1.962549] usbcore: registered new device driver usb
[    1.967610] media: Linux media interface: v0.10
[    1.972058] Linux video capture interface: v2.00
[    1.976644] pps_core: LinuxPPS API ver. 1 registered
[    1.981547] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    1.990640] PTP clock support registered
[    1.994542] EDAC MC: Ver: 3.0.0
[    1.998014] FPGA manager framework
[    2.001362] fpga-region fpga-full: FPGA Region probed
[    2.006350] Advanced Linux Sound Architecture Driver Initialized.
[    2.012631] Bluetooth: Core ver 2.22
[    2.016046] NET: Registered protocol family 31
[    2.020431] Bluetooth: HCI device and connection manager initialized
[    2.026749] Bluetooth: HCI socket layer initialized
[    2.031590] Bluetooth: L2CAP socket layer initialized
[    2.036618] Bluetooth: SCO socket layer initialized
[    2.042123] clocksource: Switched to clocksource arch_sys_counter
[    2.048112] VFS: Disk quotas dquot_6.6.0
[    2.051957] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    2.063911] NET: Registered protocol family 2
[    2.068472] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[    2.075612] TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
[    2.082372] TCP: Hash tables configured (established 16384 bind 16384)
[    2.088776] UDP hash table entries: 1024 (order: 3, 32768 bytes)
[    2.094714] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
[    2.101221] NET: Registered protocol family 1
[    2.105640] RPC: Registered named UNIX socket transport module.
[    2.111372] RPC: Registered udp transport module.
[    2.116039] RPC: Registered tcp transport module.
[    2.120710] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    2.127665] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[    2.135963] futex hash table entries: 1024 (order: 5, 131072 bytes)
[    2.142101] audit: initializing netlink subsys (disabled)
[    2.147417] audit: type=2000 audit(2.092:1): initialized
[    2.153192] workingset: timestamp_bits=62 max_order=19 bucket_order=0
[    2.160194] NFS: Registering the id_resolver key type
[    2.165070] Key type id_resolver registered
[    2.169205] Key type id_legacy registered
[    2.173188] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    2.179859] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    2.187037] JFS: nTxBlock = 8192, nTxLock = 65536
[    2.204022] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[    2.211234] io scheduler noop registered
[    2.215118] io scheduler deadline registered
[    2.219363] io scheduler cfq registered (default)
[    2.225413] xilinx-dpdma fd4c0000.dma: Xilinx DPDMA engine is probed
[    2.231882] Write failed gate address:1000f02
[    2.236147] xilinx-zynqmp-dma fd500000.dma: ZynqMP DMA driver Probe success
[    2.243106] xilinx-zynqmp-dma fd510000.dma: ZynqMP DMA driver Probe success
[    2.250024] xilinx-zynqmp-dma fd520000.dma: ZynqMP DMA driver Probe success
[    2.256942] xilinx-zynqmp-dma fd530000.dma: ZynqMP DMA driver Probe success
[    2.263864] xilinx-zynqmp-dma fd540000.dma: ZynqMP DMA driver Probe success
[    2.270786] xilinx-zynqmp-dma fd550000.dma: ZynqMP DMA driver Probe success
[    2.277706] xilinx-zynqmp-dma fd560000.dma: ZynqMP DMA driver Probe success
[    2.284625] xilinx-zynqmp-dma fd570000.dma: ZynqMP DMA driver Probe success
[    2.291622] xilinx-zynqmp-dma ffa80000.dma: ZynqMP DMA driver Probe success
[    2.298526] xilinx-zynqmp-dma ffa90000.dma: ZynqMP DMA driver Probe success
[    2.305437] xilinx-zynqmp-dma ffaa0000.dma: ZynqMP DMA driver Probe success
[    2.312358] xilinx-zynqmp-dma ffab0000.dma: ZynqMP DMA driver Probe success
[    2.319277] xilinx-zynqmp-dma ffac0000.dma: ZynqMP DMA driver Probe success
[    2.326207] xilinx-zynqmp-dma ffad0000.dma: ZynqMP DMA driver Probe success
[    2.333116] xilinx-zynqmp-dma ffae0000.dma: ZynqMP DMA driver Probe success
[    2.340040] xilinx-zynqmp-dma ffaf0000.dma: ZynqMP DMA driver Probe success
[    2.347008] zynqmp_pm firmware: Power management API v0.3
[    2.352324] xenfs: not registering filesystem on non-xen platform
[    2.390869] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
·r¢º²¢êconsole [ttyPS0] enabled ttyPS0 at MMIO 0xff000000 (irq = 40, base_baud = 6249999) is a xuartps
[    2.407640] console [ttyPS0] enabled
[    2.414608] bootconsole [cdns0] disabled
[    2.414608] bootconsole [cdns0] disabled
[    2.422717] ff010000.serial: ttyPS1 at MMIO 0xff010000 (irq = 41, base_baud = 6249999) is a xuartps
[    2.431886] [drm] Initialized
[    2.435183] [drm] load() is defered & will be called again
[    2.441124] xilinx-drm-dp-sub fd4aa000.dp_sub: Xilinx DisplayPort Subsystem is probed
[    2.449048] Unable to detect cache hierarchy from DT for CPU 0
[    2.460302] brd: module loaded
[    2.466621] loop: module loaded
[    2.470657] ahci-ceva fd0c0000.ahci: AHCI 0001.0301 32 slots 2 ports 6 Gbps 0x3 impl platform mode
[    2.479535] ahci-ceva fd0c0000.ahci: flags: 64bit ncq sntf pm clo only pmp fbs pio slum part ccc sds apst
[    2.490140] scsi host0: ahci-ceva
[    2.493596] scsi host1: ahci-ceva
[    2.496981] ata1: SATA max UDMA/133 mmio [mem 0xfd0c0000-0xfd0c1fff] port 0x100 irq 37
[    2.504815] ata2: SATA max UDMA/133 mmio [mem 0xfd0c0000-0xfd0c1fff] port 0x180 irq 37
[    2.512872] mtdoops: mtd device (mtddev=name/number) must be supplied
[    2.520117] m25p80 spi0.0: found n25q256a, expected n25q512a
[    2.525826] m25p80 spi0.0: n25q256a (65536 Kbytes)
[    2.530546] 3 ofpart partitions found on MTD device spi0.0
[    2.535998] Creating 3 MTD partitions on "spi0.0":
[    2.540775] 0x000000000000-0x000000100000 : "boot"
[    2.546147] 0x000000100000-0x000000140000 : "bootenv"
[    2.551639] 0x000000140000-0x000001740000 : "kernel"
[    2.558006] libphy: Fixed MDIO Bus: probed
[    2.563293] tun: Universal TUN/TAP device driver, 1.6
[    2.568264] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    2.574572] CAN device driver interface
[    2.578956] macb ff0e0000.ethernet: Not enabling partial store and forward
[    2.586315] libphy: MACB_mii_bus: probed
[    2.592519] macb ff0e0000.ethernet eth0: Could not attach to PHY
[    2.642827] usbcore: registered new interface driver asix
[    2.648198] usbcore: registered new interface driver ax88179_178a
[    2.654254] usbcore: registered new interface driver cdc_ether
[    2.660065] usbcore: registered new interface driver net1080
[    2.665707] usbcore: registered new interface driver cdc_subset
[    2.671609] usbcore: registered new interface driver zaurus
[    2.677176] usbcore: registered new interface driver cdc_ncm
[    2.683197] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.689638] ehci-pci: EHCI PCI platform driver
[    2.694344] usbcore: registered new interface driver uas
[    2.699615] usbcore: registered new interface driver usb-storage
[    2.705914] mousedev: PS/2 mouse device common for all mice
[    2.711862] rtc_zynqmp ffa60000.rtc: rtc core: registered ffa60000.rtc as rtc0
[    2.719045] i2c /dev entries driver
[    2.722707] cdns-i2c ff030000.i2c: 400 kHz mmio ff030000 irq 32
[    2.729666] usbcore: registered new interface driver uvcvideo
[    2.735331] USB Video Class driver (1.1.1)
[    2.739965] cdns-wdt fd4d0000.watchdog: Xilinx Watchdog Timer at ffffff8009559000 with timeout 10s
[    2.749014] Bluetooth: HCI UART driver ver 2.3
[    2.753377] Bluetooth: HCI UART protocol H4 registered
[    2.758494] Bluetooth: HCI UART protocol BCSP registered
[    2.763788] Bluetooth: HCI UART protocol LL registered
[    2.768908] Bluetooth: HCI UART protocol ATH3K registered
[    2.774291] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    2.780580] Bluetooth: HCI UART protocol Intel registered
[    2.785962] Bluetooth: HCI UART protocol Broadcom registered
[    2.791565] Bluetooth: HCI UART protocol QCA registered
[    2.796808] usbcore: registered new interface driver bcm203x
[    2.802448] usbcore: registered new interface driver bpa10x
[    2.808003] usbcore: registered new interface driver bfusb
[    2.813473] usbcore: registered new interface driver btusb
[    2.818908] Bluetooth: Generic Bluetooth SDIO driver ver 0.1
[    2.824603] usbcore: registered new interface driver ath3k
[    2.825259] ata1: SATA link down (SStatus 0 SControl 330)
[    2.825304] ata2: SATA link down (SStatus 0 SControl 330)
[    2.840911] EDAC MC: ECC not enabled
[    2.844578] EDAC DEVICE0: Giving out device to module zynqmp-ocm-edac controller zynqmp_ocm: DEV ff960000.memory-controller (INTERRUPT)
[    2.857191] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 1099999 KHz
[    2.864556] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed to: 1199999 KHz
[    2.873473] sdhci: Secure Digital Host Controller Interface driver
[    2.879565] sdhci: Copyright(c) Pierre Ossman
[    2.883949] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.892107] sdhci: =========== REGISTER DUMP (mmc0)===========
[    2.897856] sdhci: Sys addr: 0x00000000 | Version:  0x00001002
[    2.903668] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[    2.909483] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[    2.915299] sdhci: Present:  0x1ff70000 | Host ctl: 0x00000000
[    2.921114] sdhci: Power:    0x00000000 | Blk gap:  0x00000080
[    2.926930] sdhci: Wake-up:  0x00000000 | Clock:    0x00000000
[    2.932746] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[    2.938561] sdhci: Int enab: 0x00ff0003 | Sig enab: 0x00ff0003
[    2.944377] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[    2.950193] sdhci: Caps:     0x75ecc881 | Caps_1:   0x00002007
[    2.956008] sdhci: Cmd:      0x00000000 | Max curr: 0x00000000
[    2.961823] sdhci: Host ctl2: 0x00000000
[    2.965730] sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x0000000000000000
[    2.972239] sdhci: ===========================================
[    3.022139] mmc0: SDHCI controller on ff160000.sdhci [ff160000.sdhci] using ADMA 64-bit
[    3.031297] mmc0: mmc_rescan_try_freq: trying to init card at 400000 Hz
[    3.038944] sdhci: =========== REGISTER DUMP (mmc1)===========
[    3.044699] sdhci: Sys addr: 0x00000000 | Version:  0x00001002
[    3.050511] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[    3.056327] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[    3.062141] sdhci: Present:  0x01f70000 | Host ctl: 0x00000000
[    3.067957] sdhci: Power:    0x00000000 | Blk gap:  0x00000080
[    3.073773] sdhci: Wake-up:  0x00000000 | Clock:    0x00000000
[    3.079588] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[    3.085403] sdhci: Int enab: 0x00ff0003 | Sig enab: 0x00ff0003
[    3.091219] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[    3.097035] sdhci: Caps:     0x31ecc881 | Caps_1:   0x00002007
[    3.102850] sdhci: Cmd:      0x00000000 | Max curr: 0x00000000
[    3.108666] sdhci: Host ctl2: 0x00000000
[    3.112572] sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x0000000000000000
[    3.119081] sdhci: ===========================================
[    3.170136] mmc1: SDHCI controller on ff170000.sdhci [ff170000.sdhci] using ADMA 64-bit
[    3.178221] mmc1: mmc_rescan_try_freq: trying to init card at 400000 Hz
[    3.184785] ledtrig-cpu: registered to indicate activity on CPUs
[    3.190877] usbcore: registered new interface driver usbhid
[    3.196362] usbhid: USB HID core driver
[    3.201984] fpga_manager fpga0: Xilinx ZynqMP FPGA Manager registered
[    3.208911] xilinx-dp-snd-pcm dp_snd_pcm0: Xilinx DisplayPort Sound PCM probed
[    3.216082] xilinx-dp-snd-pcm dp_snd_pcm1: Xilinx DisplayPort Sound PCM probed
[    3.224307] Write failed to divider address:fd1a00c0
[    3.226460] mmc0: new HS200 MMC card at address 0001
[    3.226750] mmcblk0: mmc0:0001 Q2J55L 7.09 GiB
[    3.226853] mmcblk0boot0: mmc0:0001 Q2J55L partition 1 16.0 MiB
[    3.226953] mmcblk0boot1: mmc0:0001 Q2J55L partition 2 16.0 MiB
[    3.227050] mmcblk0rpmb: mmc0:0001 Q2J55L partition 3 4.00 MiB
[    3.227910]  mmcblk0: p1
[    3.259132] xilinx-dp-snd-codec dp_snd_codec0: Xilinx DisplayPort Sound Codec probed
[    3.267306] xilinx-dp-snd-card dp_snd_card: xilinx-dp-snd-codec-dai <-> xilinx-dp-snd-codec-dai mapping ok
[    3.276998] xilinx-dp-snd-card dp_snd_card: xilinx-dp-snd-codec-dai <-> xilinx-dp-snd-codec-dai mapping ok
[    3.287013] xilinx-dp-snd-card dp_snd_card: Xilinx DisplayPort Sound Card probed
[    3.294437] pktgen: Packet Generator for packet performance testing. Version: 2.75
[    3.305095] Netfilter messages via NETLINK v0.30.
[    3.311858] ip_tables: (C) 2000-2006 Netfilter Core Team
[    3.317139] Initializing XFRM netlink socket
[    3.321392] NET: Registered protocol family 10
[    3.328203] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    3.333568] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    3.339813] NET: Registered protocol family 17
[    3.344186] NET: Registered protocol family 15
[    3.348611] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    3.361534] Ebtables v2.0 registered
[    3.365138] can: controller area network core (rev 20120528 abi 9)
[    3.371298] NET: Registered protocol family 29
[    3.375686] can: raw protocol (rev 20120528)
[    3.379937] can: broadcast manager protocol (rev 20161123 t)
[    3.385581] can: netlink gateway (rev 20130117) max_hops=1
[    3.391106] Bluetooth: RFCOMM TTY layer initialized
[    3.395918] Bluetooth: RFCOMM socket layer initialized
[    3.401036] Bluetooth: RFCOMM ver 1.11
[    3.404765] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    3.410058] Bluetooth: BNEP filters: protocol multicast
[    3.415267] Bluetooth: BNEP socket layer initialized
[    3.420212] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    3.426120] Bluetooth: HIDP socket layer initialized
[    3.431238] 9pnet: Installing 9P2000 support
[    3.435436] Key type dns_resolver registered
[    3.440228] registered taskstats version 1
[    3.446267] mmc1: error -110 whilst initialising SD card
[    3.452694] Btrfs loaded, crc32c=crc32c-generic
[    3.459435] Key type encrypted registered
[    3.461174] mmc1: mmc_rescan_try_freq: trying to init card at 300000 Hz
[    3.480889] PLL: shutdown
[    3.483527] [drm] load() is defered & will be called again
[    3.489632] xilinx-psgtr fd400000.zynqmp_phy: Lane:3 type:8 protocol:4 pll_locked:yes
[    3.497682] xilinx-drm-dp fd4a0000.dp: device found, version 4.010
[    3.503781] xilinx-drm-dp fd4a0000.dp: Display Port, version 1.0200 (tx)
[    3.511777] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    3.517194] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
[    3.525101] xhci-hcd xhci-hcd.0.auto: hcc params 0x0238f625 hci version 0x100 quirks 0x02010010
[    3.533740] xhci-hcd xhci-hcd.0.auto: irq 220, io mem 0xfe200000
[    3.539827] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    3.546528] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.553730] usb usb1: Product: xHCI Host Controller
[    3.558590] usb usb1: Manufacturer: Linux 4.9.0-xilinx-v2017.3 xhci-hcd
[    3.565187] usb usb1: SerialNumber: xhci-hcd.0.auto
[    3.570385] hub 1-0:1.0: USB hub found
[    3.574065] hub 1-0:1.0: 1 port detected
[    3.578143] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    3.583551] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[    3.591233] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    3.599337] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    3.606039] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.613241] usb usb2: Product: xHCI Host Controller
[    3.618103] usb usb2: Manufacturer: Linux 4.9.0-xilinx-v2017.3 xhci-hcd
[    3.624699] usb usb2: SerialNumber: xhci-hcd.0.auto
[    3.629857] hub 2-0:1.0: USB hub found
[    3.633537] hub 2-0:1.0: 1 port detected
[    3.638398] PLL: enable
[    3.640936] PLL: shutdown
[    3.643648] OF: graph: no port node found in /xilinx_drm
[    3.648874] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    3.655467] [drm] No driver support for vblank timestamp query.
[    3.685858] PLL: enable
[    3.721399] Console: switching to colour frame buffer device 160x64
[    3.738315] xilinx-drm xilinx_drm: fb0:  frame buffer device
[    3.870132] [drm] Initialized xilinx_drm 1.0.0 20130509 on minor 0
[    3.876473] rtc_zynqmp ffa60000.rtc: setting system clock to 1970-01-01 00:37:52 UTC (2272)
[    3.884856] clk: Not disabling unused clocks
[    3.889087] ALSA device list:
[    3.891991]   #0: DisplayPort monitor
[    3.896983] List of all partitions:
[    3.900397] 0100           65536 ram0 [    3.903952]  (driver?)
[    3.906297] 0101           65536 ram1 [    3.909842]  (driver?)
[    3.912193] 0102           65536 ram2 [    3.915748]  (driver?)
[    3.918091] 0103           65536 ram3 [    3.921656]  (driver?)
[    3.923997] 0104           65536 ram4 [    3.927553]  (driver?)
[    3.929895] 0105           65536 ram5 [    3.933455]  (driver?)
[    3.935806] 0106           65536 ram6 [    3.939358]  (driver?)
[    3.941700] 0107           65536 ram7 [    3.945261]  (driver?)
[    3.947607] 0108           65536 ram8 [    3.951163]  (driver?)
[    3.953509] 0109           65536 ram9 [    3.957066]  (driver?)
[    3.959412] 010a           65536 ram10 [    3.963055]  (driver?)
[    3.965397] 010b           65536 ram11 [    3.969049]  (driver?)
[    3.971391] 010c           65536 ram12 [    3.975033]  (driver?)
[    3.977375] 010d           65536 ram13 [    3.981022]  (driver?)
[    3.983369] 010e           65536 ram14 [    3.987015]  (driver?)
[    3.989354] 010f           65536 ram15 [    3.993001]  (driver?)
[    3.995351] 1f00            1024 mtdblock0 [    3.999338]  (driver?)
[    4.001680] 1f01             256 mtdblock1 [    4.005678]  (driver?)
[    4.008021] 1f02           22528 mtdblock2 [    4.012010]  (driver?)
[    4.014356] b300         7438336 mmcblk0 [    4.018174]  driver: mmcblk
[    4.020954]   b301          250040 mmcblk0p1 00000000-01[    4.026072]
[    4.027551] b318            4096 mmcblk0rpmb [    4.031714]  (driver?)
[    4.034057] b310           16384 mmcblk0boot1 [    4.038315]  (driver?)
[    4.040654] b308           16384 mmcblk0boot0 [    4.044908]  (driver?)
[    4.047251] No filesystem could mount root, tried: [    4.051943]  ext4
[    4.053844]
[    4.055327] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,1)
[    4.063744] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G        W       4.9.0-xilinx-v2017.3 #1
[    4.072073] Hardware name: xlnx,zynqmp (DT)
[    4.076240] Call trace:
[    4.078679] [<ffffff8008088138>] dump_backtrace+0x0/0x198
[    4.084055] [<ffffff80080882e4>] show_stack+0x14/0x20
[    4.089091] [<ffffff8008406594>] dump_stack+0x94/0xb8
[    4.094126] [<ffffff800812e9a8>] panic+0x114/0x25c
[    4.098899] [<ffffff8008c6116c>] mount_block_root+0x21c/0x270
[    4.104625] [<ffffff8008c613f8>] mount_root+0x11c/0x134
[    4.109834] [<ffffff8008c6157c>] prepare_namespace+0x16c/0x1b4
[    4.115649] [<ffffff8008c60d14>] kernel_init_freeable+0x1c0/0x1e0
[    4.121726] [<ffffff8008976500>] kernel_init+0x10/0x100
[    4.126933] [<ffffff8008082e80>] ret_from_fork+0x10/0x50
[    4.132226] SMP: stopping secondary CPUs
[    4.136134] Kernel Offset: disabled
[    4.139604] Memory Limit: none
[    4.142646] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,1)
[    4.518430] random: fast init done
[  113.816954] random: crng init done

I am using a micro SD card so there is no issue of wp lock as well as i am using disable-wp  under sdhci1 in system-user.dtsi file.

 

I also checked and have enable ext3 and ext4 in kernel settings via petalinux-config -c kernel -->file systems  , as well as adding CONFIG_EXT3_FS=y and CONFIG_EXT4_FS=y in config file of kernel before build.

 

not sure whay it is still reading single partition in the card and not able to load fs.

0 Kudos
Explorer
Explorer
5,054 Views
Registered: ‎09-14-2016

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

Hi @vish.bh30,

 

Probably a stupid question but are sure about SD card ID.

 

Device: sdhci@ff160000
Manufacturer ID: 13
OEM: 14e
Name: Q2J55
Tran Speed: 200000000
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 7.1 GiB
[...]
ZynqMP>
ZynqMP> mmc list
sdhci@ff160000: 0 (eMMC)
sdhci@ff170000: 1 (SD)
sdhci@ff170000: 2 (SD)

 

Could you also double check this configuration inside peta-linux:

In petalinux-config I selected Image Packaging Configuration > SD card as the RootFS type.

 

> usb start
> fatls usb 0:1
> fatls usb 0:2
...

It's maybe a good idea to check device-tree because (i'm not sure on Ultraszed Board but Picozed uses the same bus for emmc and sd).

 

Good luck,

Cheers.

Trigger

 

 

 

0 Kudos
Adventurer
Adventurer
5,042 Views
Registered: ‎11-10-2017

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

@trigger

 

I checked again in the peralinux-config :

RootFS

Image_1.PNG

 

Boot file

Image_2.PNG

 

Kernel

kernel.PNG

 

 

u-boot

u-boot.PNG

 

dtb file

dtb.PNG

 

 

If you look at the attached boot log after these config changes ,

I2C:   ready
DRAM:  2 GiB
ERROR: usb dr_mode not found

at /home/vishal/myxprj/build/tmp/work/plnx_aarch64-xilinx-linux/u-boot-xlnx/v2017.01-xilinx-v2017.3+gitAUTOINC+da811c4511-r0/git/drivers/usb/common/common.c:                                                                                32/usb_get_dr_mode()
EL Level:       EL2
Chip ID:        xczu3eg
MMC:   sdhci@ff160000: 0 (eMMC), sdhci@ff170000: 1 (SD), sdhci@ff160000: 2 (eMMC), sdhci@ff170000: 3 (SD)
reading uboot.env

** Unable to read "uboot.env" from mmc0:1 **
Using default environment

Might be coz of this that it is still not able to read sd card ???

 

to remove the error : ERROR: usb dr_mode not found...i have updated my system-user.dtsi file as well which is attached.

 

Let me know if it is done correctly. 

 

 

0 Kudos
Explorer
Explorer
5,039 Views
Registered: ‎09-14-2016

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

Hi,

 

I don't know if your conf is good or not, i don't have this board.

 

But i think there is still a trouble somewhere, according to your log file :

 

 

Manufacturer ID: 13
OEM: 14e
Name: Q2J55
Tran Speed: 200000000
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 7.1 GiB
Bus Width: 8-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
reading system.dtb
** Unable to read file system.dtb **

 

 


[ 4.085664] mmc0: new HS200 MMC card at address 0001 [ 4.086359] mmcblk0: mmc0:0001 Q2J55L 7.09 GiB [ 4.086466] mmcblk0boot0: mmc0:0001 Q2J55L partition 1 16.0 MiB [ 4.088590] mmcblk0boot1: mmc0:0001 Q2J55L partition 2 16.0 MiB [ 4.088699] mmcblk0rpmb: mmc0:0001 Q2J55L partition 3 4.00 MiB [ 4.090964] mmcblk0: p1 [ 4.097907] mmc1: error -110 whilst initialising SD card [ 4.103280] mmc1: mmc_rescan_try_freq: trying to init card at 300000 Hz

 

 

Your SD Card size isn't 8Go right? I think you are not loading the kernel from sd card but emmc. You can try to boot without sd card just to be sure ( if the kernel is loaded without SD card, you are booting from an other place :) )

 

you can also try to add this part in your system :

 

&sdhci1 {
    status = "okay";
    disable-wp;
}; 

 Cheers,

Trigger

0 Kudos
Adventurer
Adventurer
5,012 Views
Registered: ‎11-10-2017

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

@trigger

 

Yes i am using a 8 G micro SD card

 

I have already included  disable-wp in system-user dtsi file

 

Can you please check the file attached above ... Alsi o for so.e reason i am not able to do add in device tree with below mentio ed format

 

&sdhci1{
....
..
};
0 Kudos
Explorer
Explorer
5,004 Views
Registered: ‎09-14-2016

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

@vish.bh30

 

Could you please give us u-boot .config file ?

 

I think you should try commands bellow (inside u-boot prompt):

U-Boot# mmc part
...
U-Boot # mmc dev 0
... U-Boot # mmc rescan
... U-Boot # mmc dev 1
...

 

Cheers,

Trigger

0 Kudos
Adventurer
Adventurer
4,949 Views
Registered: ‎11-10-2017

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

@trigger

 

this what i got 

 

ZynqMP>
ZynqMP> mmc part

Partition Map for MMC device 0  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     16              500080          00000000-01     83
ZynqMP>

Partition Map for MMC device 0  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     16              500080          00000000-01     83
ZynqMP> mmc dev 0
switch to partitions #0, OK
mmc0(part 0) is current device
ZynqMP>
ZynqMP> mmc rescan
ZynqMP>
ZynqMP> mmc dev 1
switch to partitions #0, OK
mmc1 is current device
ZynqMP>

 

i have attached the config files  .. (uboot : config.cfg, complete one is config . also added kernel config if required)

 

In platform-auto.h file i found that : 

 

/* sdio - psu_sd_1 */
....
#define CONFIG_SUPPORT_EMMC_BOOT

Doesn't it needs to be for SD card : VFAT/EXT3/EXT4 instead of EMMC ?? i checked online under spl_mmc.c

 

it has CONFIG_SPL_FAT_SUPPORT or CONFIG_SPL_EXT_SUPPORT  required for boot mode to be FS

 

link: https://github.com/LeMaker/u-boot/blob/master/common/spl/spl_mmc.c

 

Do i need to update the config file ? If so with what variable/value ?

 

 

 

 

 

 

 

0 Kudos
Explorer
Explorer
3,951 Views
Registered: ‎09-14-2016

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

hi @vish.bh30

 

Looks like you got 2 devices ( emmc and sd card ? )

 

To be sure you can use ext4ls command in order to list device's content and be sure which device you have to use :)

 

Cheers,

Trigger

0 Kudos
Adventurer
Adventurer
3,946 Views
Registered: ‎11-10-2017

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

@trigger

 

it says : 

 

ZynqMP> ext4ls mmc 1
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
ZynqMP> ext4ls mmc 0
Failed to mount ext2 filesystem...
** Unrecognized filesystem type ***

I did selected ext2 /3 and 4 and Jffs2 type under petalinux-config -c kernel --> file systems

 

also added CONFIG_EXT3_FS=y, CONFIG_EXT4_FS=y,  under plnx_kernel.cfg file ???? and i made the rootfs filesystem type as EXT4 using Gparted ... 

0 Kudos
Explorer
Explorer
3,935 Views
Registered: ‎09-14-2016

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

OK @vish.bh30,

 

First of all this thread is a little mess...

 

1. Describe emmc and sd card format.

  1. How many partitions?

  2. Partition format ( ext2, ext3, ext4 vfat, exfat ...)

 

I'm not about this part but I think you have to select the device before try to list the content.

 

ZynqMP> mmc dev 1
...
...
ZynqMP> ext4ls mmc 1
...
ZynqMP> ext4ls mmc 0
...
...
ZynqMP> mmc dev 0
...
...
ZynqMP> ext4ls mmc 1
...
ZynqMP> ext4ls mmc 0

 With the correct "ls" command according to your partition format

 

Trigger

0 Kudos
Adventurer
Adventurer
3,925 Views
Registered: ‎11-10-2017

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

hi  @trigger

 

Not sure on emmc format.

 

I made 2 partitions on my SD card : 

1. FAT32 - "BOOT" >> boot.bin, image.ub, system.dtb, Image files 

2. EXT4 - "ROOTFS" >> extracted rootfs.tar.gz in this .

 

ext4ls is not working even in the order you gave so i tried looking it up.. i tried the same with fatls  and fatload :

 

ZynqMP> mmc dev 1
switch to partitions #0, OK
mmc1 is current device
ZynqMP>
ZynqMP>
ZynqMP>
ZynqMP> ext4ls mmc 1
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
ZynqMP>
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
ZynqMP> fatls mmc 1
 19941788   boot.bin
 13411932   image.ub
    32578   system.dtb
 13378048   image

4 file(s), 0 dir(s)

ZynqMP>
 19941788   boot.bin
 13411932   image.ub
    32578   system.dtb
 13378048   image

4 file(s), 0 dir(s)

ZynqMP> fatls mmc 0
 26582120   image.ub

1 file(s), 0 dir(s)

ZynqMP>
 26582120   image.ub

1 file(s), 0 dir(s)

ZynqMP> fatload mmc 1
** No boot file defined **
ZynqMP>
ZynqMP>

 

0 Kudos
Explorer
Explorer
3,918 Views
Registered: ‎09-14-2016

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

Hi @vish.bh30,

 

 

Ok so it's cool you have what you want :)

 

 

Try that:

 

Zynq-Bulls> fatls mmc 1:1
3643224 uimage
30655 sun7i-a20-olinuxino-micro.dtb
499 boot.scr
48 image-version-info
33554432 rootfs.ubi.img
5 file(s), 0 dir(s)
Zynq-Bulls> ext4ls mmc 1:2
<DIR> 1024 .
<DIR> 1024 ..
<DIR> 12288 lost+found
<DIR> 1024 home
<DIR> 1024 boot
<DIR> 2048 sbin
<DIR> 1024 usr
<DIR> 1024 media
<DIR> 2048 lib
<DIR> 1024 sys
<DIR> 2048 etc
<DIR> 1024 mnt
<DIR> 1024 proc
<SYM> 8 tmp
<DIR> 2048 bin
<DIR> 1024 dev
<DIR> 1024 var
<DIR> 1024 run
<DIR> 1024 instrument
Zynq-Bulls>

 You should be able to see all your stuff (normally).

 

 

After that, if you choose the good device before boot your kernel you should be able to load the rootfs :)

 

Trigger

0 Kudos
Adventurer
Adventurer
3,916 Views
Registered: ‎11-10-2017

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

@trigger

 

Just a additional info to my previous reply :

 

ZynqMP> fatload mmc 1 0x1000000 BOOT.bin 19941788
reading BOOT.bin
** BOOT.bin shorter than offset + len **
19941788 bytes read in 1466 ms (13 MiB/s)
ZynqMP>
ZynqMP> boot
.
.
...........

[    3.553331] xilinx-drm xilinx_drm: fb0:  frame buffer device
[    3.665081] [drm] Initialized xilinx_drm 1.0.0 20130509 on minor 0
[    3.671490] rtc_zynqmp ffa60000.rtc: setting system clock to 1970-01-01 01:14:23 UTC (4463)
[    3.679946] clk: Not disabling unused clocks
[    3.684219] ALSA device list:
[    3.687134]   #0: DisplayPort monitor
[    3.691417] VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2): error -6
[    3.699335] Please append a correct "root=" boot option; here are the available partitions:
[    3.707694] 0100           65536 ram0 [    3.711218]  (driver?)
[    3.713552] 0101           65536 ram1 [    3.717121]  (driver?)
[    3.719447] 0102           65536 ram2 [    3.723024]  (driver?)
[    3.725356] 0103           65536 ram3 [    3.728920]  (driver?)
[    3.731259] 0104           65536 ram4 [    3.734827]  (driver?)
[    3.737161] 0105           65536 ram5 [    3.740724]  (driver?)
[    3.743063] 0106           65536 ram6 [    3.746633]  (driver?)
[    3.748960] 0107           65536 ram7 [    3.752534]  (driver?)
[    3.754869] 0108           65536 ram8 [    3.758438]  (driver?)
[    3.760765] 0109           65536 ram9 [    3.764340]  (driver?)
[    3.766673] 010a           65536 ram10 [    3.770331]  (driver?)
[    3.772656] 010b           65536 ram11 [    3.776319]  (driver?)
[    3.778653] 010c           65536 ram12 [    3.782308]  (driver?)
[    3.784635] 010d           65536 ram13 [    3.788297]  (driver?)
[    3.790629] 010e           65536 ram14 [    3.794288]  (driver?)
[    3.796613] 010f           65536 ram15 [    3.800276]  (driver?)
[    3.802611] 1f00            1024 mtdblock0 [    3.806616]  (driver?)
[    3.808939] 1f01             256 mtdblock1 [    3.812953]  (driver?)
[    3.815284] 1f02           22528 mtdblock2 [    3.819289]  (driver?)
[    3.821617] b300         7438336 mmcblk0 [    3.825452]  driver: mmcblk
[    3.828214]   b301          250040 mmcblk0p1 00000000-01[    3.833362]
[    3.834797] b318            4096 mmcblk0rpmb [    3.838994]  (driver?)
[    3.841322] b310           16384 mmcblk0boot1 [    3.845592]  (driver?)
[    3.847913] b308           16384 mmcblk0boot0 [    3.852188]  (driver?)
[    3.854515] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
[    3.862990] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.9.0-xilinx-v2017.3 #1
[    3.870100] Hardware name: xlnx,zynqmp (DT)
[    3.874238] Call trace:
[    3.876660] [<ffffff8008088138>] dump_backtrace+0x0/0x198
[    3.882065] [<ffffff80080882e4>] show_stack+0x14/0x20
[    3.889571] [<ffffff80083e5114>] dump_stack+0x94/0xb8
[    3.897033] [<ffffff800812e9a8>] panic+0x114/0x25c
[    3.904211] [<ffffff8008c310e8>] mount_block_root+0x198/0x270
[    3.912342] [<ffffff8008c313f8>] mount_root+0x11c/0x134
[    3.919940] [<ffffff8008c3157c>] prepare_namespace+0x16c/0x1b4
[    3.928165] [<ffffff8008c30d14>] kernel_init_freeable+0x1c0/0x1e0
[    3.936641] [<ffffff800894c148>] kernel_init+0x10/0x100
[    3.944239] [<ffffff8008082e80>] ret_from_fork+0x10/0x50
[    3.951886] SMP: stopping secondary CPUs
[    3.958113] Kernel Offset: disabled
[    3.963858] Memory Limit: none
[    3.969133] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)

still getting same error .. 

 

Edited: 

 

@trigger Saw your reply after i posted this .. 

 

ZynqMP>
ZynqMP>
ZynqMP> fatls mmc 1:1
 19941788   boot.bin
 13411932   image.ub
    32578   system.dtb
 13378048   image

4 file(s), 0 dir(s)

ZynqMP>
 19941788   boot.bin
 13411932   image.ub
    32578   system.dtb
 13378048   image

4 file(s), 0 dir(s)

ZynqMP> ext4ls mmc1:2
** No device specified **
ZynqMP>
** No device specified **
ZynqMP>

for some reason it does not identifies my 2nd partition in SD card

 

 

Just a missing space in the command :

 

ZynqMP> ext4ls mmc 1:2
<DIR>       4096 .
<DIR>       4096 ..
<DIR>      16384 lost+found
<DIR>       4096 home
<DIR>       4096 var
<DIR>       4096 lib
<DIR>       4096 sys
<DIR>       4096 proc
<DIR>       4096 dev
<DIR>       4096 usr
<DIR>       4096 sbin
<DIR>       4096 bin
<DIR>       4096 etc
<DIR>       4096 run
<DIR>       4096 boot
<DIR>       4096 media
<DIR>       4096 mnt
<DIR>       4096 tmp
ZynqMP>
<DIR>       4096 .
<DIR>       4096 ..
<DIR>      16384 lost+found
<DIR>       4096 home
<DIR>       4096 var
<DIR>       4096 lib
<DIR>       4096 sys
<DIR>       4096 proc
<DIR>       4096 dev
<DIR>       4096 usr
<DIR>       4096 sbin
<DIR>       4096 bin
<DIR>       4096 etc
<DIR>       4096 run
<DIR>       4096 boot
<DIR>       4096 media
<DIR>       4096 mnt
<DIR>       4096 tmp
ZynqMP>

So able to see my folder now.... 

how do i load them ?? 

 

fatload mmc 1:2 ??

 

 

0 Kudos
Explorer
Explorer
3,901 Views
Registered: ‎09-14-2016

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

Ok @vish.bh30,

 

Next step : 

ZynqMP> mmc dev 1

 to choose the correct device.

 

Update cmd line :

 

setenv bootargs earlycon earlyprintk clk_ignore_unused root=/dev/mmcblk1p2 rw rootwait uio_pdrv_genirq.of_id=generic-uio cma=1024M
saveenv

 

boot

 

ZynqMP> fatload mmc 0:1 0x3000000 uImage.ub
ZynqMP> fatload mmc 0:1 0x2A00000 system.dtb
ZynqMP> bootm 0x3000000 - 0x2A00000

 

Cheers,

 

Trigger

0 Kudos
Adventurer
Adventurer
3,893 Views
Registered: ‎11-10-2017

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

Hello @trigger

 

Glad there is some progress .. 

 

i am getting error : unable to read system.dtb file if i do fatload mmc 0:1 0x2A00000 system.dtb.. I tried doing fatload mmc 1:1  but got a ramdisk error : 

 

Boot Log:

 

ZynqMP> mmc dev 1
switch to partitions #0, OK
mmc1 is current device
ZynqMP>
ZynqMP> setenv bootargs 'earlycon earlyprintk clk_ignore_unused root=/dev/mmcblk1p1 rw rootfstype=ext4 uio_pdrv_genirq.of_id=generic-uio cma=1024M stdout-pat                                                                                h=serial0:115200n8'
ZynqMP>
ZynqMP> saveenv
Saving Environment to SPI Flash...
SF: Detected n25q256a with page size 512 Bytes, erase size 128 KiB, total 64 MiB
Erasing SPI flash...Writing to SPI flash...done
ZynqMP>
ZynqMP> fatload mmc 0:1 0x3000000 image.ub
reading image.ub
26582120 bytes read in 1920 ms (13.2 MiB/s)
ZynqMP>
ZynqMP> fatload mmc 0:1 0x2A00000 system.dtb
reading system.dtb
** Unable to read file system.dtb **
ZynqMP>
ZynqMP> fatload mmc 1:1 0x2A00000 system.dtb
reading system.dtb
32578 bytes read in 15 ms (2.1 MiB/s)
ZynqMP>
ZynqMP> fatload mmc 1:1 0x3000000 image.ub
reading image.ub
13411932 bytes read in 978 ms (13.1 MiB/s)
ZynqMP>
ZynqMP> bootm 0x3000000 - 0x2A00000
## Loading kernel from FIT Image at 03000000 ...
   Using 'conf@2' configuration
   Trying 'kernel@0' kernel subimage
     Description:  Linux Kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x030000d8
     Data Size:    13378048 Bytes = 12.8 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x00080000
     Entry Point:  0x00080000
     Hash algo:    sha1
     Hash value:   8fde8339990e747a01bca65b2e8d3b3b846c941c
   Verifying Hash Integrity ... sha1+ OK
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
ZynqMP>
## Loading kernel from FIT Image at 03000000 ...
   Using 'conf@2' configuration
   Trying 'kernel@0' kernel subimage
     Description:  Linux Kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x030000d8
     Data Size:    13378048 Bytes = 12.8 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x00080000
     Entry Point:  0x00080000
     Hash algo:    sha1
     Hash value:   8fde8339990e747a01bca65b2e8d3b3b846c941c
   Verifying Hash Integrity ... sha1+ OK
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
ZynqMP>

Thanks  for the help so far !! 

 

Please let me know what i need to correct for system.dtb error.. 

 

Regards ,

Vishal

0 Kudos
Explorer
Explorer
3,890 Views
Registered: ‎09-14-2016

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution
try with : root=/dev/mmcblk1p2
0 Kudos
Adventurer
Adventurer
3,886 Views
Registered: ‎11-10-2017

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

@trigger

 

Still getting Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

 

Attached the boot log 

0 Kudos
Explorer
Explorer
3,820 Views
Registered: ‎09-14-2016

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

I don't understand where is the issue, but you are close...

 

you can try (if you have a compressed rootfs) :

 

ZynqMP> fatload mmc 0:1 0x3000000 uImage.ub
ZynqMP> fatload mmc 0:1 0x2A00000 system.dtb
ZynqMP> fatload mmc 0:1 0x2000000 uramdisk.image.gz
ZynqMP> bootm 0x3000000 0x2000000 0x2A00000

 

 Trigger

0 Kudos
Explorer
Explorer
3,819 Views
Registered: ‎09-14-2016

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

more info about the trouble:

 

 

[ 2.952997] mmc0: SDHCI controller on ff160000.sdhci [ff160000.sdhci] using ADMA 64-bit
[ 3.008996] mmc1: SDHCI controller on ff170000.sdhci [ff170000.sdhci] using ADMA 64-bit
[ 3.017174] ledtrig-cpu: registered to indicate activity on CPUs
[ 3.023245] usbcore: registered new interface driver usbhid
[ 3.028739] usbhid: USB HID core driver
[ 3.034334] fpga_manager fpga0: Xilinx ZynqMP FPGA Manager registered
[ 3.041277] xilinx-dp-snd-pcm dp_snd_pcm0: Xilinx DisplayPort Sound PCM probed
[ 3.048468] xilinx-dp-snd-pcm dp_snd_pcm1: Xilinx DisplayPort Sound PCM probed
[ 3.056691] Write failed to divider address:fd1a00c0
[ 3.058973] mmc0: new HS200 MMC card at address 0001
[ 3.059265] mmcblk0: mmc0:0001 Q2J55L 7.09 GiB
[ 3.059372] mmcblk0boot0: mmc0:0001 Q2J55L partition 1 16.0 MiB
[ 3.059473] mmcblk0boot1: mmc0:0001 Q2J55L partition 2 16.0 MiB
[ 3.059572] mmcblk0rpmb: mmc0:0001 Q2J55L partition 3 4.00 MiB
[ 3.060394] mmcblk0: p1

 

Both (emmc and sd card are discovered) but onlu mmc0 seems work...

[ 3.056691] Write failed to divider address:fd1a00c0

 

Are you sure JP2 is not connected?

 

jp2.jpg

0 Kudos
Explorer
Explorer
3,808 Views
Registered: ‎09-14-2016

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

If you take a look here: http://zedboard.org/content/using-displayport-tutorial-compatability-red-ultrazed-boards

 

You can what the bootlog should be :)

 

[    5.740756] mmc0: SDHCI controller on ff160000.sdhci [ff160000.sdhci] using ADMA 64-bit
[    5.796752] mmc1: SDHCI controller on ff170000.sdhci [ff170000.sdhci] using ADMA 64-bit
[    5.804924] ledtrig-cpu: registered to indicate activity on CPUs
[    5.813010] usbcore: registered new interface driver usbhid
[    5.818509] usbhid: USB HID core driver
[    5.824572] fpga_manager fpga0: Xilinx ZynqMP FPGA Manager registered
[    5.831445] xilinx-dp-snd-pcm amba:dp_snd_pcm0: Xilinx DisplayPort Sound PCM probed
[    5.839073] xilinx-dp-snd-pcm amba:dp_snd_pcm1: Xilinx DisplayPort Sound PCM probed
[    5.855332] Write failed to divider address:fd1a007c
[    5.858372] mmc0: new HS200 MMC card at address 0001
[    5.858647] mmcblk0: mmc0:0001 Q2J55L 7.09 GiB
[    5.858748] mmcblk0boot0: mmc0:0001 Q2J55L partition 1 16.0 MiB
[    5.858854] mmcblk0boot1: mmc0:0001 Q2J55L partition 2 16.0 MiB
[    5.858951] mmcblk0rpmb: mmc0:0001 Q2J55L partition 3 4.00 MiB
[    5.859789]  mmcblk0: p1
[    5.886769] mmc1: new high speed SDHC card at address aaaa
[    5.886984] mmcblk1: mmc1:aaaa SL08G 7.40 GiB (ro)
[    5.887920]  mmcblk1: p1
0 Kudos
Explorer
Explorer
3,803 Views
Registered: ‎09-14-2016

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

last chance for you @vish.bh30 :)

 

According to our previous chare, you should:

 

1. Check Jumpers/boot mode switch on the board is set to SD1 (OFF-ON-OFF-ON)

2. Update your device tree to disable emmc and enable sd card: 

 

&sdhci0 {
   status = "disabled";
};

&sdhci1 {
   status = "okay";
    disable-wp;
};

3. Check this option "Device node SD device" in petalinux-config. Should set on  /dev/mmcblk1p2.

 

4. Rebuild petalinux after checking boot configuration!

 

5. Try to boot again ( with loading with fatload cmd NOT boot cmd)

 

6. Cross your fingers :)

 

Tip: take a look -> http://zedboard.org/content/ultrazed-production-som-doesnt-boot

 

Cheers,

Trigger

0 Kudos
Adventurer
Adventurer
3,758 Views
Registered: ‎11-10-2017

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

Hello @trigger

 

There is some good progress from our yesterday's discussion.

 

I am able to see the SD card getting booted by default now .. 

 

U-Boot 2017.01 (Feb 22 2018 - 00:17:03 +0530) Xilinx ZynqMP ZCU102 revB

I2C:   ready
DRAM:  2 GiB
ERROR: usb dr_mode not found

at /home/vishal/mxprjOne/build/tmp/work/plnx_aarch64-xilinx-linux/u-boot-xlnx/v2017.01-xilinx-v2017.3+gitAUTOINC+da811c4511-r0/git/drivers/usb/common/common.c:32/usb_get_dr_mode()
EL Level:       EL2
Chip ID:        xczu3eg
MMC:   sdhci@ff170000: 0 (SD)
zynqmp_qspi_ofdata_to_platdata: CLK 124999999
SF: Detected n25q256a with page size 512 Bytes, erase size 128 KiB, total 64 MiB
In:    serial
Out:   serial
Err:   serial
Net:   ZYNQ GEM: ff0e0000, phyaddr ffffffff, interface rgmii-id
eth0: ethernet@ff0e0000
Hit any key to stop autoboot:  0
Device: sdhci@ff170000

 

But after all the methods to load the files into memory and load using bootm command i am getting this error :

 

sched_clock: 56 bits at 99MHz, resolution 10ns, wraps every 4398046511101ns
Console: colour dummy device 80x25
console [tty0] enabled
bootconsole [cdns0] disabled

 

these were the files / changes i made :

 

1. /dev/mmcblk1p2 in petalinux-config -->image packaging

 

2.changed system-user.dtsi file (attached)

 

3. update the platform-top.h file for CONFIG_EXTRA_ENV_SETTINGS variable (attached)

 

 

0 Kudos
Explorer
Explorer
3,765 Views
Registered: ‎09-14-2016

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

Hi@vish.bh30,

 

Any news?  I thought I saw that you have posted a message but I cannot find him? deleted post maybe?

 

Cheers,

Trigger

0 Kudos
Explorer
Explorer
3,747 Views
Registered: ‎09-14-2016

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

Hi @vish.bh30

 

You should try to add console=ttyPS0,115200 in bootargs node ( system-user.dtsi) in order to tell to the Kernel which stdout should be used :)

 

Cheers,

Trigger

0 Kudos
Adventurer
Adventurer
3,734 Views
Registered: ‎11-10-2017

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

Hi @trigger

 

still getting the kernel panic  - unable to load root fs on block - error 

 


NET: Registered protocol family 10
sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
NET: Registered protocol family 17
Key type encrypted registered
cdns-i2c ff030000.i2c: input clock not found.
hctosys: unable to open rtc device (rtc0)
clk: Not disabling unused clocks
Warning: unable to open an initial console.
VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.0-xilinx-v2017.3 #2
Hardware name: xlnx,zynqmp (DT)
Call trace:
[<ffffff80080854e8>] dump_backtrace+0x0/0x198
[<ffffff8008085694>] show_stack+0x14/0x20
[<ffffff8008232284>] dump_stack+0x94/0xb8
[<ffffff80080ef298>] panic+0x114/0x25c
[<ffffff80084e11ac>] mount_block_root+0x214/0x2b4
[<ffffff80084e12c0>] mount_root+0x74/0x84
[<ffffff80084e13fc>] prepare_namespace+0x12c/0x168
[<ffffff80084e0e18>] kernel_init_freeable+0x1c0/0x1e0
[<ffffff8008401b20>] kernel_init+0x10/0x100
[<ffffff8008082330>] ret_from_fork+0x10/0x20
SMP: stopping secondary CPUs
Kernel Offset: disabled
Memory Limit: none
---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

used mmcblk0p2 as with mmcblk1p2 it is giving - Bad mm 1 - error  after i switched off the emmc in device tree.

 

Is it possible that the Boot is missing some link or patch to link boot and rootfs files ??

 

 

Regards,

 

Vishal

 

 

0 Kudos
Explorer
Explorer
3,728 Views
Registered: ‎09-14-2016

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

Hi @vish.bh30,

 

You should pay attention ;)

 

ZynqMP> fatload mmc 0:1 0x3000000 image.ub
reading image.ub
5100460 bytes read in 358 ms (13.6 MiB/s)
ZynqMP>
ZynqMP> fatload mmc 0:1 0x2A00000 system.dtb
reading system.dtb
32395 bytes read in 16 ms (1.9 MiB/s)
ZynqMP>
ZynqMP> fatload mmc 0:1 0x2000000 uramdisk.image.gz

Why do you want to load ramdisk if your rootfs is on the sd card...

 

Cheers,
Trigger

 

 

0 Kudos
Adventurer
Adventurer
3,714 Views
Registered: ‎11-10-2017

Re: Not able to mount root fs during SD boot in Ultrazed MPSoC

Jump to solution

@trigger

 

I was trying to load filesystem by having two separate partitions..but it was not loading it and i was getting the same error, so i tried using just one partition of fat32 and loading these files...

0 Kudos