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
Visitor ngc6027
Visitor
1,503 Views
Registered: ‎07-13-2018

Adding Utilities to PetaLinux Build Causes Boot Failure

Jump to solution

Hello,

 

I am trying to add some utilities to my PetaLinux build (v2018.2) on a Zedboard, including gdb, zip, and vim. I go into the configuration menu (petalinux-config -c rootfs) and select the utilities to add, save the configuration, and run petalinux-build. When I copy the resulting BOOT.BIN and image.ub files to an SD card and attempt to boot, I get a kernel panic. Xilinx UG1144 (pp. 51-52) states that if the image size changes (which I believe it must after adding all of those utilities), you should change the CONFIG_SYS_BOOTM_LEN parameter in platform-top.h to a size larger than the image size, and undefine CONFIG_SYS_BOOTMAPSZ in the same file. I didn't notice CONFIG_SYS_BOOTMAPSZ actually being defined in platform-top.h, but I threw in a #undef for it anyway. None of this worked, and the kernel still panics on boot. Below is the boot output:

 

U-Boot 2018.01 (Mar 30 2019 - 10:39:10 -0400)

Model: Zynq Zed Development Board
Board: Xilinx Zynq
Silicon: v3.1
DRAM:  ECC disabled 512 MiB
MMC:   sdhci@e0100000: 0 (SD)
SF: Detected s25fl256s_64k with page size 256 Bytes, erase size 64 KiB, total 32 MiB
*** Warning - bad CRC, using default environment

In:    serial@e0001000
Out:   serial@e0001000
Err:   serial@e0001000
Model: Zynq Zed Development Board
Board: Xilinx Zynq
Silicon: v3.1
Net:   ZYNQ GEM: e000b000, phyaddr 0, interface rgmii-id
eth0: ethernet@e000b000
U-BOOT for avnet-digilent-zedboard-2018_2

ethernet@e000b000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Hit any key to stop autoboot:  0
Device: sdhci@e0100000
Manufacturer ID: 3
OEM: 5344
Name: SS32G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 29.7 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
reading image.ub
138610792 bytes read in 7524 ms (17.6 MiB/s)
## Loading kernel from FIT Image at 10000000 ...
   Using 'conf@system-top.dtb' configuration
   Verifying Hash Integrity ... OK
   Trying 'kernel@1' kernel subimage
     Description:  Linux kernel
     Type:         Kernel Image
     Compression:  gzip compressed
     Data Start:   0x10000108
     Data Size:    3825017 Bytes = 3.6 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x00008000
     Entry Point:  0x00008000
     Hash algo:    sha1
     Hash value:   bcd4ab7a45df06f49d0d19a6a410bf10e5f84556
   Verifying Hash Integrity ... sha1+ OK
## Loading ramdisk from FIT Image at 10000000 ...
   Using 'conf@system-top.dtb' configuration
   Trying 'ramdisk@1' ramdisk subimage
     Description:  petalinux-user-image
     Type:         RAMDisk Image
     Compression:  gzip compressed
     Data Start:   0x103a99d8
     Data Size:    134768897 Bytes = 128.5 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: unavailable
     Entry Point:  unavailable
     Hash algo:    sha1
     Hash value:   f478f57bb77a16deee88c3bbbf73db0ff8ed9d81
   Verifying Hash Integrity ... sha1+ OK
## Loading fdt from FIT Image at 10000000 ...
   Using 'conf@system-top.dtb' configuration
   Trying 'fdt@system-top.dtb' fdt subimage
     Description:  Flattened Device Tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x103a5f84
     Data Size:    14739 Bytes = 14.4 KiB
     Architecture: ARM
     Hash algo:    sha1
     Hash value:   861ab5ee88e4dd3680d9941a0012c8f73a270fa5
   Verifying Hash Integrity ... sha1+ OK
   Booting using the fdt blob at 0x103a5f84
   Uncompressing Kernel Image ... OK
   Loading Ramdisk to 17293000, end 1f319901 ... OK
   Loading Device Tree to 1728c000, end 17292992 ... OK

Starting kernel ...

Booting Linux on physical CPU 0x0
Linux version 4.14.0-xilinx-v2018.2 (oe-user@oe-host) (gcc version 7.2.0 (GCC)) #1 PREEMPT Sat Mar 30 10:48:17 EDT 2019
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c52c79
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
OF: fdt: Machine model: Zynq Zed Development Board
bootconsole [earlycon0] enabled
Memory policy: Data cache writeback
cma: Reserved 16 MiB at 0x16000000
CPU: All CPU(s) started in SVC mode.
Built 1 zonelists, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyPS0,115200 earlyprintk
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 361536K/524288K available (6144K kernel code, 255K rwdata, 1536K rodata, 1024K init, 134K bss, 146368K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xe0800000 - 0xff800000   ( 496 MB)
    lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc0700000   (7136 kB)
      .init : 0xc0900000 - 0xc0a00000   (1024 kB)
      .data : 0xc0a00000 - 0xc0a3fd20   ( 256 kB)
       .bss : 0xc0a3fd20 - 0xc0a616bc   ( 135 kB)
Preemptible hierarchical RCU implementation.
        Tasks RCU enabled.
NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
efuse mapped to e0800000
slcr mapped to e0802000
zynq_clock_init: clkc starts at e0802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
timer #0 at e0808000, irq=17
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0x100000 - 0x100060
Hierarchical SRCU implementation.
devtmpfs: initialized
random: get_random_u32 called from bucket_table_alloc+0x12c/0x178 with crng_init=0
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 256 (order: -1, 3072 bytes)
pinctrl core: initialized pinctrl subsystem
random: fast init done
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0xe0840000
zynq-pinctrl 700.pinctrl: zynq pinctrl initialized
e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 24, base_baud = 3125000) is a xuartps
console [ttyPS0] enabled
console [ttyPS0] enabled
bootconsole [earlycon0] disabled
bootconsole [earlycon0] disabled
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
FPGA manager framework
fpga-region fpga-full: FPGA Region probed
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (write error); looks like an initrd
/initrd.image: incomplete write (-28 != 134768897)
Freeing initrd memory: 131612K
hw perfevents: no interrupt-affinity property for /pmu@f8891000, guessing.
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
workingset: timestamp_bits=30 max_order=17 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
io scheduler mq-deadline registered
io scheduler kyber registered
dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.dmac:        DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
brd: module loaded
loop: module loaded
m25p80 spi0.0: found s25fl256s1, expected n25q512a
m25p80 spi0.0: s25fl256s1 (32768 Kbytes)
4 ofpart partitions found on MTD device spi0.0
Creating 4 MTD partitions on "spi0.0":
0x000000000000-0x000000500000 : "boot"
0x000000500000-0x000000520000 : "bootenv"
0x000000520000-0x000000fa0000 : "kernel"
0x000000fa0000-0x000002000000 : "spare"
libphy: Fixed MDIO Bus: probed
CAN device driver interface
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 26 (00:0a:35:00:1e:53)
Marvell 88E1510 e000b000.ethernet-ffffffff:00: attached PHY driver [Marvell 88E1510] (mii_bus:phy_addr=e000b000.ethernet-ffffffff:00, irq=POLL)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
chipidea-usb2 e0002000.usb: e0002000.usb supply vbus not found, using dummy regulator
ULPI transceiver vendor/product ID 0x0451/0x1507
Found TI TUSB1210 ULPI transceiver.
ULPI integrity check: passed.
ci_hdrc ci_hdrc.0: EHCI Host Controller
ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
i2c /dev entries driver
IR NEC protocol handler initialized
IR RC5(x/sz) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR SANYO protocol handler initialized
IR Sharp protocol handler initialized
IR MCE Keyboard/mouse protocol handler initialized
IR XMP protocol handler initialized
cdns-wdt f8005000.watchdog: Xilinx Watchdog Timer at e0942000 with timeout 10s
EDAC MC: ECC not enabled
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.sdhci [e0100000.sdhci] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
fpga_manager fpga0: Xilinx Zynq FPGA Manager registered
mmc0: new high speed SDHC card at address aaaa
mmcblk0: mmc0:aaaa SS32G 29.7 GiB
 mmcblk0: p1 p2
NET: Registered protocol family 10
Segment Routing with IPv6
sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20170425 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20170425)
can: broadcast manager protocol (rev 20170425 t)
can: netlink gateway (rev 20170425) max_hops=1
hctosys: unable to open rtc device (rtc0)
of_cfs_init
of_cfs_init: OK
ALSA device list:
  No soundcards found.
RAMDISK: Couldn't find valid RAM disk image starting at 0.
VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
0100           16384 ram0
 (driver?)
0101           16384 ram1
 (driver?)
0102           16384 ram2
 (driver?)
0103           16384 ram3
 (driver?)
0104           16384 ram4
 (driver?)
0105           16384 ram5
 (driver?)
0106           16384 ram6
 (driver?)
0107           16384 ram7
 (driver?)
0108           16384 ram8
 (driver?)
0109           16384 ram9
 (driver?)
010a           16384 ram10
 (driver?)
010b           16384 ram11
 (driver?)
010c           16384 ram12
 (driver?)
010d           16384 ram13
 (driver?)
010e           16384 ram14
 (driver?)
010f           16384 ram15
 (driver?)
1f00            5120 mtdblock0
 (driver?)
1f01             128 mtdblock1
 (driver?)
1f02           10752 mtdblock2
 (driver?)
1f03           16768 mtdblock3
 (driver?)
b300        31166976 mmcblk0
 driver: mmcblk
  b301         8388608 mmcblk0p1 7d296fa6-01

  b302        22775808 mmcblk0p2 7d296fa6-02

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

I should note that if I remove all of these utilities, Petalinux boots as expected and there are no issues. It's only when I add these utilities through the petalinux-config -c rootfs command that this issue arises.

Any help in resolving this issue would be very much appreciated as I would potentially like to add even more utilities to the rootfs in the future, and this issue is preventing that.

Thank you.

0 Kudos
1 Solution

Accepted Solutions
Visitor ngc6027
Visitor
1,279 Views
Registered: ‎07-13-2018

Re: Adding Utilities to PetaLinux Build Causes Boot Failure

Jump to solution

So I think the issue (for me at least, and possibly for you) was that the rootfs was too big to fit into RAM with the added utilities. The steps below show how to put the rootfs into its own partition on an SD card. It's a summary of the information that can be found in Xilinx UG 1144 v2018.2, pp. 55-56. For me, I had 3 partitions on my SD card: BOOT, rootfs, and EXTRA, where BOOT had BOOT.bin and image.ub, and EXTRA had things that I didn't want to have to put back into the rootfs partition when rebuilding the PetaLinux project.

  • In order to add additional programs (e.g., VIM, unzip, GDB, etc.), you may need to not bundle the rootfs with image.ub file
  • In this case, ensure you have an SD card set up the following way (I recommend using gparted on your Ubuntu machine):
    • 4 MB free space before the first partition (format below: <name>; <size>; <FS>)
    • First partition: BOOT; at least 60 MB; FAT32 (my files took up 8.7 MB; I gave 1GB to this partition)
    • Second partition: rootfs; remaining size of SD card; ext4
  • Run petalinux-config
  • Under Image Packaging Configuration -> Root filesystem type, select SD card
  • Save and exit menuconfig window
  • Run petalinux-build
  • Copy <project root>/images/linux/{BOOT.BIN, image.ub} to the BOOT partition of the SD card
  • Run “sudo tar xvf <project root>/images/linux/rootfs.tar.gz -C <path to rootfs partition of SD card>”

Hope this helps.

12 Replies
Moderator
Moderator
1,436 Views
Registered: ‎02-07-2018

Re: Adding Utilities to PetaLinux Build Causes Boot Failure

Jump to solution

Hi @ngc6027 

You need to do this below chnages , it should work. 

Note: If kernel or rootfs size increases and is greater than 128 MB, you need to do the following:
1. Mention the Bootm length in platform-top.h
#define CONFIG_SYS_BOOTM_LEN <value greater then image size>
2. Undef the CONFIG_SYS_BOOTMAPSZ in platform-top.h

 

Thanks & regards

Aravind

Visitor ngc6027
Visitor
1,415 Views
Registered: ‎07-13-2018

Re: Adding Utilities to PetaLinux Build Causes Boot Failure

Jump to solution

@aravindb I noticed that line in UG1144 and did those things before making my initial post. I mentioned that there was no CONFIG_SYS_BOOTMAPSZ defined in platform-top.h, but I did a #undef for it anyway. I also increased the CONFIG_SYS_BOOTM_LEN parameter to a value greater than what I believe is the image size (I think I set it to 512 MB to be safe), but I don't know how to determine the actual image size. Is it the size of the image.ub file? The size of that file is 132 MB.

To clarify, with those changes above, I get the output copied in my initial post. Is there some other step that I'm missing? Do I need to include files other than BOOT.BIN and image.ub on the SD card?

Thanks for your response.

0 Kudos
Visitor ngc6027
Visitor
1,372 Views
Registered: ‎07-13-2018

Re: Adding Utilities to PetaLinux Build Causes Boot Failure

Jump to solution

@aravindb

Do you have any additional ideas? Or anyone else? I had already implemented the changes in @aravindb's reply before posting. I would still like to be able to add utilities to the rootfs without causing a kernel panic at boot.

0 Kudos
Explorer
Explorer
1,288 Views
Registered: ‎10-18-2017

Re: Adding Utilities to PetaLinux Build Causes Boot Failure

Jump to solution

I am seeing same issue after adding OpenCV. Anyone fixed this yet?

0 Kudos
Visitor ngc6027
Visitor
1,280 Views
Registered: ‎07-13-2018

Re: Adding Utilities to PetaLinux Build Causes Boot Failure

Jump to solution

So I think the issue (for me at least, and possibly for you) was that the rootfs was too big to fit into RAM with the added utilities. The steps below show how to put the rootfs into its own partition on an SD card. It's a summary of the information that can be found in Xilinx UG 1144 v2018.2, pp. 55-56. For me, I had 3 partitions on my SD card: BOOT, rootfs, and EXTRA, where BOOT had BOOT.bin and image.ub, and EXTRA had things that I didn't want to have to put back into the rootfs partition when rebuilding the PetaLinux project.

  • In order to add additional programs (e.g., VIM, unzip, GDB, etc.), you may need to not bundle the rootfs with image.ub file
  • In this case, ensure you have an SD card set up the following way (I recommend using gparted on your Ubuntu machine):
    • 4 MB free space before the first partition (format below: <name>; <size>; <FS>)
    • First partition: BOOT; at least 60 MB; FAT32 (my files took up 8.7 MB; I gave 1GB to this partition)
    • Second partition: rootfs; remaining size of SD card; ext4
  • Run petalinux-config
  • Under Image Packaging Configuration -> Root filesystem type, select SD card
  • Save and exit menuconfig window
  • Run petalinux-build
  • Copy <project root>/images/linux/{BOOT.BIN, image.ub} to the BOOT partition of the SD card
  • Run “sudo tar xvf <project root>/images/linux/rootfs.tar.gz -C <path to rootfs partition of SD card>”

Hope this helps.

Explorer
Explorer
1,274 Views
Registered: ‎10-18-2017

Re: Adding Utilities to PetaLinux Build Causes Boot Failure

Jump to solution
@ngc6027 That was going to be my choice if all else failed. I'm glad to hear it works according to directions in UG, because I was struggling with putting it on the second partition. Thanks
0 Kudos
Visitor ngc6027
Visitor
1,272 Views
Registered: ‎07-13-2018

Re: Adding Utilities to PetaLinux Build Causes Boot Failure

Jump to solution

@johnfrye11 Shoot me a message if you need any additional help with that. The summary I posted here is also part of a tutorial I’m writing for my research lab, so if something is unclear, I’d like to update the instructions.

0 Kudos
Moderator
Moderator
1,270 Views
Registered: ‎04-24-2017

Re: Adding Utilities to PetaLinux Build Causes Boot Failure

Jump to solution

Hi @johnfrye11 , @ngc6027 ,

If the INITRAMFS image size is larger then it is recommeded to use with ext4 filesystem not FIT image(image.ub)

Based on it is visible that the most likely there is no enough space in shmem that's why it is failing.

For smaller rootfs sizes it can fit that's why no message is shown.

In failure case, its using tmpfs and in working case its using ramfs.

This means it works without root= as long as the root filesystem can fit in tmpfs. In this case, when you increase the filesystem size which can't fit in tmpfs and hence root=/dev/ram option is needed in order to let linux use ramfs instead of tmpfs.

You can try adding this option in device-tree

chosen {
    bootargs = "console=ttyPS0,115200 earlyprintk root=/dev/ram";
    stdout-path = "serial0:115200n8";
};

Note: This is not a perfect solution and do not to use in production.

Thanks,
Sandeep
PetaLinux Yocto | Embedded SW Support

---------------------------------------------------------------------------
Don’t forget to Reply, Kudo, and Accept as Solution.
---------------------------------------------------------------------------
0 Kudos
Explorer
Explorer
1,250 Views
Registered: ‎10-18-2017

Re: Adding Utilities to PetaLinux Build Causes Boot Failure

Jump to solution

@ngc6027 

I am still getting a very similar error message.

[    4.025642] VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2): error -30
[    4.033639] Please append a correct "root=" boot option; here are the available partitions:
[    4.041996] 0100           65536 ram0
[    4.041998]  (driver?)
[    4.048090] 0101           65536 ram1
[    4.048091]  (driver?)
[    4.054179] 0102           65536 ram2
[    4.054180]  (driver?)
[    4.060259] 0103           65536 ram3
[    4.060260]  (driver?)
[    4.066347] 0104           65536 ram4
[    4.066348]  (driver?)
[    4.072432] 0105           65536 ram5
[    4.072434]  (driver?)
[    4.078517] 0106           65536 ram6
[    4.078519]  (driver?)
[    4.084602] 0107           65536 ram7
[    4.084603]  (driver?)
[    4.090684] 0108           65536 ram8
[    4.090685]  (driver?)
[    4.096773] 0109           65536 ram9
[    4.096774]  (driver?)
[    4.102851] 010a           65536 ram10
[    4.102853]  (driver?)
[    4.109027] 010b           65536 ram11
[    4.109028]  (driver?)
[    4.115194] 010c           65536 ram12
[    4.115196]  (driver?)
[    4.121370] 010d           65536 ram13
[    4.121372]  (driver?)
[    4.127537] 010e           65536 ram14
[    4.127539]  (driver?)
[    4.133713] 010f           65536 ram15
[    4.133715]  (driver?)
[    4.139883] 1f00            1024 mtdblock0
[    4.139884]  (driver?)
[    4.146403] 1f01             256 mtdblock1
[    4.146405]  (driver?)
[    4.152925] 1f02           22528 mtdblock2
[    4.152927]  (driver?)
[    4.159436] b300         7639040 mmcblk0
[    4.159438]  driver: mmcblk
[    4.166221]   b301         1048576 mmcblk0p1 7539477a-01
[    4.166222]
[    4.172999]   b302         6589440 mmcblk0p2 7539477a-02
[    4.173001]
[    4.179773] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
[    4.188194] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.14.0-xilinx-v2018.3 #8
[    4.195395] Hardware name: xlnx,zynqmp (DT)
[    4.199562] Call trace:
[    4.202001] [<ffffff8008088c58>] dump_backtrace+0x0/0x368
[    4.207385] [<ffffff8008088fd4>] show_stack+0x14/0x20
[    4.212421] [<ffffff8008a3f7f8>] dump_stack+0x9c/0xbc
[    4.217463] [<ffffff800809bdc0>] panic+0x11c/0x274
[    4.222246] [<ffffff8008d91124>] mount_block_root+0x1a8/0x27c
[    4.227973] [<ffffff8008d91430>] mount_root+0x11c/0x134
[    4.233181] [<ffffff8008d915b4>] prepare_namespace+0x16c/0x1b4
[    4.238996] [<ffffff8008d90d44>] kernel_init_freeable+0x1b8/0x1d8
[    4.245073] [<ffffff8008a51b48>] kernel_init+0x10/0x100
[    4.250281] [<ffffff8008084a90>] ret_from_fork+0x10/0x18
[    4.255576] SMP: stopping secondary CPUs
[    4.259482] Kernel Offset: disabled
[    4.262952] CPU features: 0x002004

I guess it is not reading the rootfs off the SD properly?
What are your configs under

 

misc/config System Config→ Subsystem AUTO Hardware Settings → Advanced bootable images storage Settings
0 Kudos
Moderator
Moderator
1,244 Views
Registered: ‎04-24-2017

Re: Adding Utilities to PetaLinux Build Causes Boot Failure

Jump to solution

Hi @johnfrye11 ,

Do you see the command line bootargs in boot logs?

I'm not using FIT due to this issue in kernel hence we go with ext4 filesystem on SD.

Thanks,
Sandeep
PetaLinux Yocto | Embedded SW Support

---------------------------------------------------------------------------
Don’t forget to Reply, Kudo, and Accept as Solution.
---------------------------------------------------------------------------
0 Kudos
Explorer
Explorer
1,237 Views
Registered: ‎10-18-2017

Re: Adding Utilities to PetaLinux Build Causes Boot Failure

Jump to solution

@sandeepg 

I sent you my whole bootlogs but I think this is what you want.

[    0.000000] Kernel command line: earlycon console=ttyPS0,115200 clk_ignore_unused root=/dev/mmcblk0p2 rw rootwait

Not sure where I would need to change PetaLinux, quite how it relates to this log, but let me know any suggestion and I can try it? Should I use different PetaLinux-generated file instead of image.ub?

0 Kudos
Explorer
Explorer
1,208 Views
Registered: ‎10-18-2017

Re: Adding Utilities to PetaLinux Build Causes Boot Failure

Jump to solution

@sandeepg 

I also tried what the guide says to do

Problem Description: This message indicates that the Linux kernel is unable to mount EXT4 File System and unable to find working init.

Solution: Extract RootFS in rootfs partition of SD card. For more information, see the Copying Image Files.

 

I still get the same error on boot.

0 Kudos