cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Contributor
Contributor
4,266 Views
Registered: ‎07-02-2015

ZCU102 ubuntu desktop using Petalinux 2019.1

Hi,

I am trying to do the ZCU102 ubuntu desktop available at :

https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841937/Zynq+UltraScale+MPSoC+Ubuntu+part+2+-+Building+and+Running+the+Ubuntu+Desktop+From+Sources

But I am using Petalinux 2019.1 instead of 2018.3, I followed all the steps correctly, when I use the given the given .img file the design works correctly and the ubuntu GUI desktop runs, but when i follow the steps to build the .ub and .BIN files and replace it with the files on the SD card the ubuntu desktop doesn't run, instead the Display shows linux login terminal without GUI. I have attached a picture of the booting data i get befor showing the login terrminal. Is it incompatibale with Petalinux 2019.1 or am I missing something ?

IMG_0004.jpg
0 Kudos
34 Replies
Highlighted
Voyager
Voyager
4,114 Views
Registered: ‎06-28-2018

  1. Download an Ubuntu ARM64 image from https://wiki.ubuntu.com/ARM/RaspberryPi
  2. Write the image to an SD card
  3. Create a PetaLinux project using zcu102 bsp
  4. Run petalinux-config and change rootfs type to "SD card"
  5. Build the project
  6. Create BOOT.bin and image.ub
  7. Remove everything under the boot partition of the SD card and copy these two files there, do not touch the rootfs partition
  8. To enable GUI on Ubuntu install a display manager such as lightdm
0 Kudos
Highlighted
Contributor
Contributor
4,105 Views
Registered: ‎07-02-2015

0 Kudos
Highlighted
Voyager
Voyager
4,097 Views
Registered: ‎06-28-2018

If you want to run Ubuntu on ZCU102 I have given you the steps.

0 Kudos
Highlighted
Contributor
Contributor
4,084 Views
Registered: ‎07-02-2015

Thanks a lot,

but the problem is that I am still learning so I need to follow some sort of a tutorial because there is a lot of stuff that I will be stuck in when following your procedure, for example I am dont know how should i modify the BOOTARGS and configuring the kernel in Petalinux in that case to have it running correctly. as you see I am stuck in the step by step Tutorial

0 Kudos
Highlighted
Voyager
Voyager
4,078 Views
Registered: ‎06-28-2018

You don't have to modify the bootargs or change the kernel configuration to run Ubuntu.

Once you have a working Ubuntu system you can start playing with it.

If you have trouble following the steps you can always ask.

0 Kudos
Highlighted
Contributor
Contributor
4,067 Views
Registered: ‎07-02-2015

Are you sure ? I dont even need to configure the petalinux to enable the SD card for rootfs: select ‘Image Packaging Configuration->Root file system type->SD card’?

and i dont need to set the kernelargs to

earlycon clk_ignore_unused earlyprintk root=/dev/mmcblk0p2 rw rootwait cma=1024M

 

0 Kudos
Highlighted
Voyager
Voyager
4,062 Views
Registered: ‎06-28-2018

  • petalinux-config : hardware configuration
  • petalinux-config -c kernel : kernel configuration
  • petalinux-config -c rootfs : root file system configuration

Changing rootfs type is the only thing you have to do regarding configuration.

Default bootargs will boot the system.

I always follow these steps and successfully run Ubuntu on any Xilinx device.

0 Kudos
Highlighted
Contributor
Contributor
3,942 Views
Registered: ‎07-02-2015

Hi

These steps are succesful for running Ubuntu but not for running desktop, there is still missing steps in getting the Ubuntu-desktop application to run on the ZCU102 board I hope if any one has experience in this

0 Kudos
Highlighted
Participant
Participant
3,881 Views
Registered: ‎11-12-2019

Hello, I am currently experiencing this problem. I have downloaded the latest BSP file and generated BOOT.BIN and image.ub files in the pre-build directory via petaLinux. When I copy these two files to the SD card, I then start the ZCU102 board, the screen only Display the GUI of the command line, I can't see the Ubuntu desktop. When I log in to the system with the root username and password, I find that there are a lot of commands missing, such as: apt-get, systemctl, etc. Is your problem solved?Thanks.
0 Kudos
Highlighted
Voyager
Voyager
3,873 Views
Registered: ‎06-28-2018

@vae 

You are probably booting into PetaLinux, not Ubuntu. PetaLinux does not let you add a package manager such as dpkg.

Make sure you have selected SD card as the rootfs type.

@ahmedmohamed85 

Try switching between your virtual terminals. You can switch to the 7th terminal by pressing

CTRL+ALT+F7

X server should be running on this terminal.

0 Kudos
Highlighted
Participant
Participant
3,831 Views
Registered: ‎11-12-2019

Thanks for your answer, I follow https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841937/Zynq+UltraScale+MPSoC+Ubuntu+part+2+-+Building+and+Running+the +Ubuntu+Desktop+From+Sources, but ignore the Vivado related operations, start the operation directly from the BSP creation project,use the hdf file given in the tutorial, and configure the petaLinux and kernel, and finally generate in the image/linux directory. But when I copy the file to the SD card, the board is activated, the monitor does not respond, am I missing some steps? I noticed the light next to the SD card on the board. The yellow light is always on, not blinking.I gave detailed steps in the picture.
step.png
0 Kudos
Highlighted
Voyager
Voyager
3,805 Views
Registered: ‎06-28-2018

@vae 

Maybe the DisplayPort or HDMI is not enabled in the HDF you are using. Maybe the OS is not even booting. Can you share the boot log (connect a UART cable between your board and PC).

0 Kudos
Highlighted
Teacher
Teacher
3,799 Views
Registered: ‎06-16-2013

Hi @vae 

 

Would you share the following result, if you can use serial console ?

You can investigate route cause of DisplayPort or/and HDMI issue.

 

$ ls /sys/devices/platform/amba_pl@0/

$ ls /sys/devices/platform/amba/

 

Best regards,

 

0 Kudos
Highlighted
Participant
Participant
3,773 Views
Registered: ‎11-12-2019

After I connect using PUTTY, I start the board. The black window only displays "!!Press ESC enter system control mode". I did it, but it didn't work.

When I use other SD cards that can be started normally, the terminal has information output and the Ubuntu desktop is displayed normally.

So I suspect that the system I configured is not started at all.

I noticed that the last step in the tutorial is to copy the BOOT.BIN and image.ub files to the boot partition of the SD card, but my approach is: just pass another Win10 computer open SD card, then ctrl-c, ctrl-v.... system can not be started for this reason?

If so, then I should know what to do next. Because my operation should have no other problems from beginning to end; if it is not for this reason, what should I do to correctly display the relevant log information on the PUTTY terminal?

Thank you very much!

0 Kudos
Highlighted
Participant
Participant
3,771 Views
Registered: ‎11-12-2019

Thanks,some new problems have been found in my previous reply message.Can you give me some advice?

0 Kudos
Highlighted
Teacher
Teacher
3,730 Views
Registered: ‎06-16-2013

Hi @vae 

 

Would you do the followings to clear what is occuring at your side ?

 

- Make sure file system to investigate whether partition issue or not on ubuntu.

$ df -T -k

- What kind of SD card are you using ? Clear capacity (ex. 4GB), compatibility (ex. SDXC), interface standard (ex. UGH-I) and so on,

- Try to repair failed sector by using "chkdsk" on Windows, if necessary or want to make sure quality of SD card.

=> I suspect your SD card is something wrong, like there are some failed sector...

 

Best regards,

0 Kudos
Highlighted
Participant
Participant
3,695 Views
Registered: ‎11-12-2019

In win10 through the chkdsk command, the SD card is no problem.

When I specify the boot and root partitions through the fdisk command in Linux, then copy the file, connect the serial port, start the board, and the black window of PUTTY finally has the output information.

The information has been attached to the file. Although I don't know the specific content, I can obviously see:

Unable to handle kernel NULL pointer dereference at virtual address 00000000

so what should I do next? Looking forward to your reply!

0 Kudos
Highlighted
Teacher
Teacher
3,661 Views
Registered: ‎06-16-2013

Hi @vae 

 

How and what do you describe kernel arguments ?

It seems that there is something wrong on kernel arguments.

 

Best regards,

0 Kudos
Highlighted
Participant
Participant
3,639 Views
Registered: ‎11-12-2019

I followed the tutorial to configure the kernel, just added more network-related kernel parameters.

I tried to copy the root and boot partitions of another normal system and the system could start normally. But the kernel parameters I need don't seem to be turned on on this system.

In fact, I just need to execute the command: iptables -t nat -L, but the cmd prompt:
Can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.


I have already looked up a lot of relevant information before, and I finally suspect that the kernel lacks the relevant configuration, so this series of operations will be available.


I am still trying to configure the kernel so that the Ubuntu desktop can be displayed.

0 Kudos
Highlighted
Participant
Participant
3,599 Views
Registered: ‎11-12-2019

 

The kernel boot issue has been resolved because copying: root=/dev/mmcblk0p2 has two more spaces in the middle. . .

After recompiling, I copied the BOOT.BIN and image.ub files to the boot partition of the SD card, but I emptied the root partition. In this case, the system is started, and the black window finally displays:


End Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.


Next, I downloaded the arm version of the archive from http://cdimage.ubuntu.com/ubuntu-base/releases/16.04/release/, extracted it to the root partition, started it again, and the black window stopped:

Started Update UTMP about System Runlevel Changes.

What should I do next?

0 Kudos
Highlighted
Teacher
Teacher
3,588 Views
Registered: ‎06-16-2013

Hi @vae 

 

Would you share console log message or boot log ?

 

Best regards,

 

0 Kudos
Highlighted
Participant
Participant
3,569 Views
Registered: ‎11-12-2019

This is empty root

0 Kudos
Highlighted
Participant
Participant
3,565 Views
Registered: ‎11-12-2019

This is the log information that the system starts after decompressing to the root partition.

0 Kudos
Highlighted
Adventurer
Adventurer
3,541 Views
Registered: ‎05-08-2018

@vae The ZCU102 board has a x4 UART to USB ftdi chip on it. One of the uart port is connected to psuart0 (the linux console), two more are connected to PL ios (if I recall correctly), and the last one to the TI MSP430 micrcontroller onboard. I never quite understood what that uc was doing in particular.. some board level power management of some kind, I suppose. Nevertheless, the output you have is the output of the uart of the MSP430. Try opening one of the other 3 remaining com ports and you'll pick the zynq ps one

0 Kudos
Highlighted
Participant
Participant
3,498 Views
Registered: ‎11-12-2019

I didn't understand what you mean. Now the serial port is working normally. After the board is started, the system related information is already displayed on the screen. The black window of putty also displays the same information. The details have been given in the previous comments. Can you give me some more comments? Thank you very much!
0 Kudos
Highlighted
Adventurer
Adventurer
2,949 Views
Registered: ‎11-05-2018

Hi @baltintop,

In your steps for booting Ubuntu, can the Ubuntu image be on the same bootable partition on SD card that has BOOT.BIN and image.ub. Any constraints on what to the name the non-boot partition etc. Trying to figure out, how u-boot knows where to load the kernel from without these details mattering.

Thanks

0 Kudos
Highlighted
Adventurer
Adventurer
2,933 Views
Registered: ‎11-05-2018

Hi @baltintop ,

When I change rootfs to SD card in petalinux-config, I get the following error message.

My SD card

.069329] 1f03 65280 mtdblock3
[ 3.069331] (driver?)
[ 3.075839] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 3.084082] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.14.0 #4
[ 3.089981] Hardware name: xlnx,zynqmp (DT)
[ 3.094148] Call trace:
[ 3.096586] [<ffffff8008088c58>] dump_backtrace+0x0/0x368
[ 3.101962] [<ffffff8008088fd4>] show_stack+0x14/0x20
[ 3.106997] [<ffffff80089e45f8>] dump_stack+0x9c/0xbc
[ 3.112031] [<ffffff800809b308>] panic+0x11c/0x274
[ 3.116805] [<ffffff8008d21124>] mount_block_root+0x1a8/0x27c
[ 3.122533] [<ffffff8008d21430>] mount_root+0x11c/0x134
[ 3.127741] [<ffffff8008d215b4>] prepare_namespace+0x16c/0x1b4
[ 3.133557] [<ffffff8008d20d44>] kernel_init_freeable+0x1b8/0x1d8
[ 3.139633] [<ffffff80089f6960>] kernel_init+0x10/0x100
[ 3.144841] [<ffffff8008084a90>] ret_from_fork+0x10/0x18
[ 3.150136] SMP: stopping secondary CPUs
[ 3.154090] Kernel Offset: disabled
[ 3.157512] CPU features: 0x002004
[ 3.160896] Memory Limit: none
[ 3.163938] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

 

0 Kudos
Highlighted
Voyager
Voyager
2,888 Views
Registered: ‎06-28-2018

Hi @chintan_asi 

I think the following settings tell u-boot where to look for the Linux kernel and tell the kernel where to look for the root filesystem.

Screenshot from 2020-01-11 14-38-35.pngScreenshot from 2020-01-11 14-37-45.png

The labels of the partitions are not important but the filesystem architecture should be FAT or EXT because u-boot can only load from FAT and EXT as far as I know. You can boot into u-boot environment and type help to see all available u-boot commands.

You can load a kernel image from the first partition (formatted as FAT) on the SD card to a specific address in the memory using fatload command like this

fatload mmc 0:1 0x3000000 uImage

then boot the Linux kernel by running this

bootm 0x3000000

 For your other question can you please share the full boot log?

0 Kudos
Highlighted
Adventurer
Adventurer
2,820 Views
Registered: ‎11-05-2018

Hi @baltintop 

Pasted in the log on the serial port.

Let me know if you can think of what could be going on. I have highlighted the portions that seem to point to the root cause in red.

Any insights you can offer are much appreciated.

 

sdhci@ff160000: 0 (SD)
*** Warning - bad CRC, using default environment

In: serial@ff000000
Out: serial@ff000000
Err: serial@ff000000
Board: Xilinx ZynqMP
Bootmode: SD_MODE
Net: ZYNQ GEM: ff0d0000, phyaddr ffffffff, interface sgmii
i2c_mux_set: could not set mux: id: 5 chip: 74 channel: 0
I2C EEPROM MAC address read failed
eth0: ethernet@ff0d0000Device 'ethernet@ff0e0000': seq 0 is in use by 'ethernet@ ff0d0000'
ZYNQ GEM: ff0e0000, phyaddr 1, interface rgmii-id
I2C EEPROM MAC address read failed

Warning: ethernet@ff0e0000 (eth1) using random MAC address - be:7f:a5:2f:08:6a
, eth1: ethernet@ff0e0000
U-BOOT for vp430

Hit any key to stop autoboot: 0
Device: sdhci@ff160000
Manufacturer ID: 27
OEM: 5048
Name: SD32G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 29 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
reading image.ub
6803260 bytes read in 505 ms (12.8 MiB/s)
## Loading kernel from FIT Image at 10000000 ...
Using 'conf@system-top.dtb' configuration
Trying 'kernel@1' kernel subimage
Description: Linux kernel
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x100000f0
Data Size: 6766928 Bytes = 6.5 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x00080000
Entry Point: 0x00080000
Hash algo: sha1
Hash value: 6e965d266c89e6ce3b164b1d3f9e0bc2c23e24a4
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: 0x10674344
Data Size: 34435 Bytes = 33.6 KiB
Architecture: AArch64
Hash algo: sha1
Hash value: 254d7d95f539146f65852c969ee4c8df80d0c8bf
Verifying Hash Integrity ... sha1+ OK
Booting using the fdt blob at 0x10674344
Uncompressing Kernel Image ... OK
Loading Device Tree to 0000000007ff4000, end 0000000007fff682 ... OK

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.14.0 (oe-user@oe-host) (gcc version 7.2.0 (GCC)) #1 SMP Sat Jan 11 01:34:02 EST 2020
[ 0.000000] Boot CPU: AArch64 Processor [410fd034]
[ 0.000000] Machine model: xlnx,zynqmp
[ 0.000000] earlycon: cdns0 at MMIO 0x00000000ff000000 (options '115200n8')
[ 0.000000] bootconsole [cdns0] enabled
[ 0.000000] efi: Getting EFI parameters from FDT:
[ 0.000000] efi: UEFI not found.
[ 0.000000] cma: Reserved 256 MiB at 0x000000006fc00000
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv1.1 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: MIGRATE_INFO_TYPE not supported.
[ 0.000000] random: fast init done
[ 0.000000] percpu: Embedded 21 pages/cpu @ffffffc87ff75000 s45080 r8192 d327 44 u86016
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: enabling workaround for ARM erratum 845719
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 1033987
[ 0.000000] Kernel command line: console=ttyPS0,115200 earlycon clk_ignore_un used earlyprintk uio_pdrv_genirq.of_id=generic-uio
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes )
[ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 0.000000] software IO TLB [mem 0x6bc00000-0x6fc00000] (64MB) mapped at [fff fffc06bc00000-ffffffc06fbfffff]
[ 0.000000] Memory: 3784952K/4193280K available (9724K kernel code, 630K rwda ta, 3068K rodata, 448K init, 2157K bss, 146184K reserved, 262144K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] modules : 0xffffff8000000000 - 0xffffff8008000000 ( 128 M B)
[ 0.000000] vmalloc : 0xffffff8008000000 - 0xffffffbebfff0000 ( 250 G B)
[ 0.000000] .text : 0xffffff8008080000 - 0xffffff8008a00000 ( 9728 K B)
[ 0.000000] .rodata : 0xffffff8008a00000 - 0xffffff8008d10000 ( 3136 K B)
[ 0.000000] .init : 0xffffff8008d10000 - 0xffffff8008d80000 ( 448 K B)
[ 0.000000] .data : 0xffffff8008d80000 - 0xffffff8008e1da00 ( 631 K B)
[ 0.000000] .bss : 0xffffff8008e1da00 - 0xffffff8009039130 ( 2158 K B)
[ 0.000000] fixed : 0xffffffbefe7fd000 - 0xffffffbefec00000 ( 4108 K B)
[ 0.000000] PCI I/O : 0xffffffbefee00000 - 0xffffffbeffe00000 ( 16 M B)
[ 0.000000] vmemmap : 0xffffffbf00000000 - 0xffffffc000000000 ( 4 G B maximum)
[ 0.000000] 0xffffffbf00000000 - 0xffffffbf1dc00000 ( 476 M B actual)
[ 0.000000] memory : 0xffffffc000000000 - 0xffffffc880000000 ( 34816 M B)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU event tracing is enabled.
[ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[ 0.000000] GIC: Adjusting CPU interface base to 0x00000000f902f000
[ 0.000000] GIC: Using split EOI/Deactivate mode
[ 0.000000] arch_timer: cp15 timer(s) running at 50.00MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xb8812736b, max_idle_ns: 440795202655 ns
[ 0.000003] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 43980 46511100ns
[ 0.008248] Console: colour dummy device 80x25
[ 0.012518] Calibrating delay loop (skipped), value calculated using timer fr equency.. 100.00 BogoMIPS (lpj=200000)
[ 0.022884] pid_max: default: 32768 minimum: 301
[ 0.027562] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.034137] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.041794] ASID allocator initialised with 65536 entries
[ 0.047046] Hierarchical SRCU implementation.
[ 0.051600] EFI services will not be available.
[ 0.055962] zynqmp_plat_init Platform Management API v1.0
[ 0.061308] zynqmp_plat_init Trustzone version v1.0
[ 0.066244] smp: Bringing up secondary CPUs ...
[ 0.070891] Detected VIPT I-cache on CPU1
[ 0.070918] CPU1: Booted secondary processor [410fd034]
[ 0.071189] Detected VIPT I-cache on CPU2
[ 0.071207] CPU2: Booted secondary processor [410fd034]
[ 0.071470] Detected VIPT I-cache on CPU3
[ 0.071488] CPU3: Booted secondary processor [410fd034]
[ 0.071529] smp: Brought up 1 node, 4 CPUs
[ 0.102938] SMP: Total of 4 processors activated.
[ 0.107612] CPU features: detected feature: 32-bit EL0 Support
[ 0.113409] CPU: All CPU(s) started at EL2
[ 0.117480] alternatives: patching kernel code
[ 0.122572] devtmpfs: initialized
[ 0.129339] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, ma x_idle_ns: 7645041785100000 ns
[ 0.138881] futex hash table entries: 1024 (order: 5, 131072 bytes)
[ 0.150486] xor: measuring software checksum speed
[ 0.195137] 8regs : 2303.000 MB/sec
[ 0.235166] 8regs_prefetch: 2053.000 MB/sec
[ 0.279536] 32regs : 2830.000 MB/sec
[ 0.319568] 32regs_prefetch: 2381.000 MB/sec
[ 0.323989] xor: using function: 32regs (2830.000 MB/sec)
[ 0.329413] pinctrl core: initialized pinctrl subsystem
[ 0.335016] NET: Registered protocol family 16
[ 0.339829] cpuidle: using governor menu
[ 0.343934] vdso: 2 pages (1 code @ ffffff8008a06000, 1 data @ ffffff8008d840 00)
[ 0.351131] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.358314] DMA: preallocated 256 KiB pool for atomic allocations
[ 0.393879] reset_zynqmp reset-controller: Xilinx zynqmp reset driver probed
[ 0.401188] ARM CCI_400_r1 PMU driver probed
[ 0.405799] zynqmp-pinctrl ff180000.pinctrl: zynqmp pinctrl initialized
[ 0.423755] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.494827] raid6: int64x1 gen() 395 MB/s
[ 0.566772] raid6: int64x1 xor() 437 MB/s
[ 0.638830] raid6: int64x2 gen() 677 MB/s
[ 0.710928] raid6: int64x2 xor() 594 MB/s
[ 0.782986] raid6: int64x4 gen() 1033 MB/s
[ 0.855015] raid6: int64x4 xor() 735 MB/s
[ 0.927062] raid6: int64x8 gen() 975 MB/s
[ 0.999129] raid6: int64x8 xor() 742 MB/s
[ 1.071214] raid6: neonx1 gen() 717 MB/s
[ 1.143249] raid6: neonx1 xor() 833 MB/s
[ 1.215308] raid6: neonx2 gen() 1156 MB/s
[ 1.287355] raid6: neonx2 xor() 1187 MB/s
[ 1.359438] raid6: neonx4 gen() 1497 MB/s
[ 1.431465] raid6: neonx4 xor() 1428 MB/s
[ 1.503548] raid6: neonx8 gen() 1645 MB/s
[ 1.575582] raid6: neonx8 xor() 1526 MB/s
[ 1.579658] raid6: using algorithm neonx8 gen() 1645 MB/s
[ 1.585020] raid6: .... xor() 1526 MB/s, rmw enabled
[ 1.589950] raid6: using neon recovery algorithm
[ 1.595323] SCSI subsystem initialized
[ 1.599040] usbcore: registered new interface driver usbfs
[ 1.604366] usbcore: registered new interface driver hub
[ 1.609641] usbcore: registered new device driver usb
[ 1.614681] media: Linux media interface: v0.10
[ 1.619148] Linux video capture interface: v2.00
[ 1.623743] pps_core: LinuxPPS API ver. 1 registered
[ 1.628643] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giome tti <giometti@linux.it>
[ 1.637734] PTP clock support registered
[ 1.641632] EDAC MC: Ver: 3.0.0
[ 1.645016] zynqmp-ipi ff9905c0.mailbox: Probed ZynqMP IPI Mailbox driver.
[ 1.651872] FPGA manager framework
[ 1.655190] fpga-region fpga-full: FPGA Region probed
[ 1.660198] Advanced Linux Sound Architecture Driver Initialized.
[ 1.666395] Bluetooth: Core ver 2.22
[ 1.669801] NET: Registered protocol family 31
[ 1.674195] Bluetooth: HCI device and connection manager initialized
[ 1.680511] Bluetooth: HCI socket layer initialized
[ 1.685353] Bluetooth: L2CAP socket layer initialized
[ 1.690378] Bluetooth: SCO socket layer initialized
[ 1.695729] clocksource: Switched to clocksource arch_sys_counter
[ 1.701694] VFS: Disk quotas dquot_6.6.0
[ 1.705550] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 1.716230] NET: Registered protocol family 2
[ 1.720678] TCP established hash table entries: 32768 (order: 6, 262144 bytes )
[ 1.727907] TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
[ 1.734705] TCP: Hash tables configured (established 32768 bind 32768)
[ 1.741091] UDP hash table entries: 2048 (order: 4, 65536 bytes)
[ 1.747070] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
[ 1.753546] NET: Registered protocol family 1
[ 1.757905] RPC: Registered named UNIX socket transport module.
[ 1.763630] RPC: Registered udp transport module.
[ 1.768300] RPC: Registered tcp transport module.
[ 1.772969] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 1.779724] hw perfevents: no interrupt-affinity property for /pmu, guessing.
[ 1.786817] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters av ailable
[ 1.795005] audit: initializing netlink subsys (disabled)
[ 1.800273] audit: type=2000 audit(1.744:1): state=initialized audit_enabled= 0 res=1
[ 1.800571] workingset: timestamp_bits=62 max_order=20 bucket_order=0
[ 1.814958] NFS: Registering the id_resolver key type
[ 1.819832] Key type id_resolver registered
[ 1.823972] Key type id_legacy registered
[ 1.827954] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 1.834621] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 1.865007] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 2 46)
[ 1.872207] io scheduler noop registered
[ 1.876094] io scheduler deadline registered
[ 1.880345] io scheduler cfq registered (default)
[ 1.885004] io scheduler mq-deadline registered
[ 1.889501] io scheduler kyber registered
[ 1.894613] xilinx-zynqmp-dma fd500000.dma: ZynqMP DMA driver Probe success
[ 1.901532] xilinx-zynqmp-dma fd510000.dma: ZynqMP DMA driver Probe success
[ 1.908438] xilinx-zynqmp-dma fd520000.dma: ZynqMP DMA driver Probe success
[ 1.915354] xilinx-zynqmp-dma fd530000.dma: ZynqMP DMA driver Probe success
[ 1.922276] xilinx-zynqmp-dma fd540000.dma: ZynqMP DMA driver Probe success
[ 1.929197] xilinx-zynqmp-dma fd550000.dma: ZynqMP DMA driver Probe success
[ 1.936122] xilinx-zynqmp-dma fd560000.dma: ZynqMP DMA driver Probe success
[ 1.943033] xilinx-zynqmp-dma fd570000.dma: ZynqMP DMA driver Probe success
[ 1.950038] xilinx-zynqmp-dma ffa80000.dma: ZynqMP DMA driver Probe success
[ 1.956934] xilinx-zynqmp-dma ffa90000.dma: ZynqMP DMA driver Probe success
[ 1.963858] xilinx-zynqmp-dma ffaa0000.dma: ZynqMP DMA driver Probe success
[ 1.970774] xilinx-zynqmp-dma ffab0000.dma: ZynqMP DMA driver Probe success
[ 1.977693] xilinx-zynqmp-dma ffac0000.dma: ZynqMP DMA driver Probe success
[ 1.984617] xilinx-zynqmp-dma ffad0000.dma: ZynqMP DMA driver Probe success
[ 1.991534] xilinx-zynqmp-dma ffae0000.dma: ZynqMP DMA driver Probe success
[ 1.998454] xilinx-zynqmp-dma ffaf0000.dma: ZynqMP DMA driver Probe success
[ 2.030292] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 2.039140] cacheinfo: Unable to detect cache hierarchy for CPU 0
[ 2.049230] brd: module loaded
[ 2.055332] loop: module loaded
[ 2.058919] mtdoops: mtd device (mtddev=name/number) must be supplied
[ 2.066043] m25p80 spi0.0: found n25q00, expected m25p80
[ 2.071636] m25p80 spi0.0: n25q00 (131072 Kbytes)
[ 2.076176] 5 ofpart partitions found on MTD device spi0.0
[ 2.081603] Creating 5 MTD partitions on "spi0.0":
[ 2.086362] 0x000000000000-0x000002000000 : "boot"
[ 2.091545] 0x000002000000-0x000002040000 : "bootenv"
[ 2.096779] 0x000002040000-0x000004040000 : "kernel"
[ 2.101653] PLL: shutdown
[ 2.104574] 0x000004040000-0x000008000000 : "jffs2"
[ 2.109633] 0x000008000000-0x000008000000 : "spare"
[ 2.114329] mtd: partition "spare" is out of reach -- disabled
[ 2.121323] libphy: Fixed MDIO Bus: probed
[ 2.126167] tun: Universal TUN/TAP device driver, 1.6
[ 2.131148] CAN device driver interface
[ 2.135234] zynqmp_gpd_attach_dev error -13, node 31
[ 2.140017] macb ff0d0000.ethernet: failed to add to PM domain pd-eth2: -13
[ 2.148942] macb ff0e0000.ethernet: Not enabling partial store and forward
[ 2.156141] libphy: MACB_mii_bus: probed
[ 2.231985] macb ff0e0000.ethernet eth0: Cadence GEM rev 0x50070106 at 0xff0e 0000 irq 31 (00:0a:35:00:22:01)
[ 2.241618] Marvell 88E1510 ff0e0000.ethernet-ffffffff:01: attached PHY drive r [Marvell 88E1510] (mii_bus:phy_addr=ff0e0000.ethernet-ffffffff:01, irq=POLL)
[ 2.255973] usbcore: registered new interface driver asix
[ 2.261233] usbcore: registered new interface driver ax88179_178a
[ 2.267266] usbcore: registered new interface driver cdc_ether
[ 2.273062] usbcore: registered new interface driver net1080
[ 2.278681] usbcore: registered new interface driver cdc_subset
[ 2.284565] usbcore: registered new interface driver zaurus
[ 2.290110] usbcore: registered new interface driver cdc_ncm
[ 2.295952] xilinx-axipmon ffa00000.perf-monitor: Probed Xilinx APM
[ 2.303780] zynqmp_gpd_attach_dev error -13, node 22
[ 2.308568] dwc3-of-simple ff9d0000.usb0: failed to add to PM domain pd-usb0: -13
[ 2.316269] usbcore: registered new interface driver uas
[ 2.321424] usbcore: registered new interface driver usb-storage
[ 2.327834] rtc_zynqmp ffa60000.rtc: rtc core: registered ffa60000.rtc as rtc 0
[ 2.334906] i2c /dev entries driver
[ 2.338813] cdns-i2c ff020000.i2c: 400 kHz mmio ff020000 irq 33
[ 2.345071] cdns-i2c ff030000.i2c: 100 kHz mmio ff030000 irq 34
[ 2.351144] pca954x 1-0070: probe failed
[ 2.354957] IR NEC protocol handler initialized
[ 2.359385] IR RC5(x/sz) protocol handler initialized
[ 2.364398] IR RC6 protocol handler initialized
[ 2.368898] IR JVC protocol handler initialized
[ 2.373395] IR Sony protocol handler initialized
[ 2.377979] IR SANYO protocol handler initialized
[ 2.382650] IR Sharp protocol handler initialized
[ 2.387321] IR MCE Keyboard/mouse protocol handler initialized
[ 2.393115] IR XMP protocol handler initialized
[ 2.398280] usbcore: registered new interface driver uvcvideo
[ 2.403835] USB Video Class driver (1.1.1)
[ 2.408524] Bluetooth: HCI UART driver ver 2.3
[ 2.412791] Bluetooth: HCI UART protocol H4 registered
[ 2.417890] Bluetooth: HCI UART protocol BCSP registered
[ 2.423184] Bluetooth: HCI UART protocol LL registered
[ 2.428270] Bluetooth: HCI UART protocol ATH3K registered
[ 2.433632] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 2.439893] Bluetooth: HCI UART protocol Intel registered
[ 2.445225] Bluetooth: HCI UART protocol QCA registered
[ 2.450444] usbcore: registered new interface driver bcm203x
[ 2.456061] usbcore: registered new interface driver bpa10x
[ 2.461596] usbcore: registered new interface driver bfusb
[ 2.467048] usbcore: registered new interface driver btusb
[ 2.472472] Bluetooth: Generic Bluetooth SDIO driver ver 0.1
[ 2.478135] usbcore: registered new interface driver ath3k
[ 2.483657] EDAC MC: ECC not enabled
[ 2.487287] EDAC DEVICE0: Giving out device to module zynqmp-ocm-edac control ler zynqmp_ocm: DEV ff960000.memory-controller (INTERRUPT)
[ 2.499699] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 1200000 KHz
[ 2.506912] cpu cpu0: dev_pm_opp_set_rate: failed to find current OPP for fre q 1200000000 (-34)
[ 2.515644] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed to: 1199999 KHz
[ 2.524044] cpu cpu0: dev_pm_opp_set_rate: failed to find current OPP for fre q 1200000000 (-34)
[ 2.533090] sdhci: Secure Digital Host Controller Interface driver
[ 2.539078] sdhci: Copyright(c) Pierre Ossman
[ 2.543401] sdhci-pltfm: SDHCI platform and OF driver helper
[ 2.549296] PLL: enable
[ 2.595743] mmc0: SDHCI controller on ff160000.sdhci [ff160000.sdhci] using A DMA 64-bit
[ 2.603788] ledtrig-cpu: registered to indicate activity on CPUs
[ 2.609719] usbcore: registered new interface driver usbhid
[ 2.615134] usbhid: USB HID core driver
[ 2.620651] fpga_manager fpga0: Xilinx ZynqMP FPGA Manager registered
[ 2.628183] pktgen: Packet Generator for packet performance testing. Version: 2.75
[ 2.635819] Netfilter messages via NETLINK v0.30.
[ 2.640439] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 2.645732] Initializing XFRM netlink socket
[ 2.649898] NET: Registered protocol family 10
[ 2.654641] Segment Routing with IPv6
[ 2.658153] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 2.663569] /home/chintan/chintan/projects/RFSOC/BLT/CodeDrops/2019-06-12_1G_ Real_Sandbox/VP430_2018.1/components/ext_sources/linux-xlnx-xilinx-v2018.1/drive rs/mmc/core/sd.c:890 SD card mmc0 force write-enable
[ 2.682168] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[ 2.688259] NET: Registered protocol family 17
[ 2.692526] NET: Registered protocol family 15
[ 2.696938] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 2.709817] Ebtables v2.0 registered
[ 2.713436] can: controller area network core (rev 20170425 abi 9)
[ 2.719532] NET: Registered protocol family 29
[ 2.723918] can: raw protocol (rev 20170425)
[ 2.728154] can: broadcast manager protocol (rev 20170425 t)
[ 2.733779] can: netlink gateway (rev 20170425) max_hops=1
[ 2.739281] Bluetooth: RFCOMM TTY layer initialized
[ 2.743734] sdhci-arasan ff160000.sdhci: : Timeout for Buffer Read Ready inte rrupt, back to fixed sampling clock
[ 2.743738] mmc0: tuning execution failed: -5
[ 2.743743] mmc0: error -5 whilst initialising SD card
[ 2.763621] Bluetooth: RFCOMM socket layer initialized
[ 2.768727] Bluetooth: RFCOMM ver 1.11
[ 2.772444] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 2.777717] Bluetooth: BNEP filters: protocol multicast
[ 2.782909] Bluetooth: BNEP socket layer initialized
[ 2.787838] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 2.793722] Bluetooth: HIDP socket layer initialized
[ 2.798750] 9pnet: Installing 9P2000 support
[ 2.802904] Key type dns_resolver registered
[ 2.807480] registered taskstats version 1
[ 2.811684] Btrfs loaded, crc32c=crc32c-generic
[ 2.820997] ff000000.serial: ttyPS0 at MMIO 0xff000000 (irq = 41, base_baud = 6250000) is a xuartps
[ 2.825762] /home/chintan/chintan/projects/RFSOC/BLT/CodeDrops/2019-06-12_1G_ Real_Sandbox/VP430_2018.1/components/ext_sources/linux-xlnx-xilinx-v2018.1/drive ہ 2.848527] console [ttyPS0] enabledforce write-enable
[ 2.848527] console [ttyPS0] enabled
[ 2.855490] bootconsole [cdns0] disabled
[ 2.855490] bootconsole [cdns0] disabled
[ 2.863742] ff010000.serial: ttyPS1 at MMIO 0xff010000 (irq = 42, base_baud = 6250000) is a xuartps
[ 2.873686] zynqmp_gpd_attach_dev error -13, node 31
[ 2.878569] macb ff0d0000.ethernet: failed to add to PM domain pd-eth2: -13
[ 2.883734] sdhci-arasan ff160000.sdhci: : Timeout for Buffer Read Ready inte rrupt, back to fixed sampling clock
[ 2.883737] mmc0: tuning execution failed: -5
[ 2.883741] mmc0: error -5 whilst initialising SD card
[ 2.906030] zynqmp_gpd_attach_dev error -13, node 22
[ 2.910915] dwc3-of-simple ff9d0000.usb0: failed to add to PM domain pd-usb0: -13
[ 2.919084] rtc_zynqmp ffa60000.rtc: setting system clock to 1970-01-01 00:02 :17 UTC (137)
[ 2.927371] clk: Not disabling unused clocks
[ 2.931584] ALSA device list:
[ 2.934504] No soundcards found.
[ 2.938295] VFS: Cannot open root device "(null)" or unknown-block(0,0): erro r -6
[ 2.945707] Please append a correct "root=" boot option; here are the availab le partitions:
[ 2.954038] 0100 65536 ram0
[ 2.954040] (driver?)
[ 2.960098] 0101 65536 ram1
[ 2.960100] (driver?)
[ 2.966170] 0102 65536 ram2
[ 2.966171] (driver?)
[ 2.972250] 0103 65536 ram3
[ 2.972251] (driver?)
[ 2.978322] 0104 65536 ram4
[ 2.978323] (driver?)
[ 2.984402] 0105 65536 ram5
[ 2.984403] (driver?)
[ 2.990474] 0106 65536 ram6
[ 2.990475] (driver?)
[ 2.996554] 0107 65536 ram7
[ 2.996555] (driver?)
[ 3.002626] 0108 65536 ram8
[ 3.002627] (driver?)
[ 3.008707] 0109 65536 ram9
[ 3.008708] (driver?)
[ 3.014778] 010a 65536 ram10
[ 3.014779] (driver?)
[ 3.020945] 010b 65536 ram11
[ 3.020946] (driver?)
[ 3.027103] 010c 65536 ram12
[ 3.027105] (driver?)
[ 3.033270] 010d 65536 ram13
[ 3.033272] (driver?)
[ 3.039429] 010e 65536 ram14
[ 3.039430] (driver?)
[ 3.045596] 010f 65536 ram15
[ 3.045597] (driver?)
[ 3.051762] 1f00 32768 mtdblock0
[ 3.051764] (driver?)
[ 3.058264] 1f01 256 mtdblock1
[ 3.058266] (driver?)
[ 3.064779] 1f02 32768 mtdblock2
[ 3.064780] (driver?)
[ 3.071284] 1f03 65280 mtdblock3
[ 3.071286] (driver?)
[ 3.077799] Kernel panic - not syncing: VFS: Unable to mount root fs on unkno wn-block(0,0)
[ 3.086041] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.14.0 #1
[ 3.091940] Hardware name: xlnx,zynqmp (DT)
[ 3.096107] Call trace:
[ 3.098545] [<ffffff8008088bd0>] dump_backtrace+0x0/0x368
[ 3.103922] [<ffffff8008088f4c>] show_stack+0x14/0x20
[ 3.108957] [<ffffff80089ddf78>] dump_stack+0x9c/0xbc
[ 3.113991] [<ffffff800809b308>] panic+0x11c/0x274
[ 3.118765] [<ffffff8008d110a8>] mount_block_root+0x1a8/0x27c
[ 3.124492] [<ffffff8008d113b4>] mount_root+0x11c/0x134
[ 3.129700] [<ffffff8008d1152c>] prepare_namespace+0x160/0x1a8
[ 3.135516] [<ffffff8008d10cc8>] kernel_init_freeable+0x1b8/0x1d8
[ 3.141593] [<ffffff80089f02e0>] kernel_init+0x10/0x100
[ 3.146800] [<ffffff8008084a08>] ret_from_fork+0x10/0x18
[ 3.152095] SMP: stopping secondary CPUs
[ 3.156001] Kernel Offset: disabled
[ 3.159472] CPU features: 0x002004
[ 3.162856] Memory Limit: none
[ 3.165898] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

0 Kudos