linux is not booting on the zedboard

100aditya over 9 years ago

Hi,

I have done first partition of mine Zedbaord and given it name Boot and i copied following things here:-

BOOT.bin

uEnv.txt

devicetree.dtb

uImage

uramdisk.image.gz

Now i am trying to boot it from SD card but it is not happening and i am getting the following message. In this message i have highlighted the error message specially along with other relevant message that i have got in mine tty terminal.

U-Boot 2014.01 (Oct 08 2016 - 12:33:09)

I2C: ready

Memory: ECC disabled

DRAM: 512 MiB

MMC: zynq_sdhci: 0

SF: Detected S25FL256S_64K with page size 256 Bytes, erase size 64 KiB, total 32 MiB

*** Warning - bad CRC, using default environment

In: serial

Out: serial

Err: serial

Net: Gem.e000b000

Hit any key to stop autoboot: 3 2 1 0

Device: zynq_sdhci

Manufacturer ID: 27

OEM: 5048

Name: SD04G

Tran Speed: 50000000

Rd Block Len: 512

SD version 3.0

High Capacity: Yes

Capacity: 3.7 GiB

Bus Width: 4-bit

reading uEnv.txt

226 bytes read in 7 ms (31.3 KiB/s)

Loaded environment from uEnv.txt

Importing environment from SD ...

Running uenvcmd ...

Device: zynq_sdhci

Manufacturer ID: 27

OEM: 5048

Name: SD04G

Tran Speed: 50000000

Rd Block Len: 512

SD version 3.0

High Capacity: Yes

Capacity: 3.7 GiB

Bus Width: 4-bit

reading uImage

4150864 bytes read in 399 ms (9.9 MiB/s)

reading devicetree.dtb

9275 bytes read in 16 ms (565.4 KiB/s)

reading uramdisk.image.gz

18047061 bytes read in 1698 ms (10.1 MiB/s)

Wrong Image Format for bootm command

ERROR: can't get kernel image!

Copying Linux from SD to RAM...

reading uImage

4150864 bytes read in 399 ms (9.9 MiB/s)

reading devicetree.dtb

9275 bytes read in 16 ms (565.4 KiB/s)

reading uramdisk.image.gz

18047061 bytes read in 1698 ms (10.1 MiB/s)

Wrong Image Format for bootm command

ERROR: can't get kernel image!

zynq-uboot>

The content of mine uenv.txt file is as follows:-

boot_Zed=mmcinfo;fatload mmc 0 0x3000000 ${kernel_image}; fatload mmc 0 0x2A00000 ${devicetree_image}; fatload mmc 0 0x2000000 ${ramdisk_image}; bootm 0x3000000 0x2000000 0x2A00000

uenvcmd=run boot_Zed

I have created the ramdiskimage by following command:-

mkimage -A ARM -T ramdisk -C gzip -n 'ZED filesystem' -d ramdisk.image.gz uramdisk.image.gz

Upon execution of above command i got the following message:-

Image Name: ZED filesystem

Created: Mon Oct 24 10:40:13 2016

Image Type: ARM Linux RAMDisk Image (gzip compressed)

Data Size: 18046997 Bytes = 17624.02 kB = 17.21 MB

Load Address: 00000000

Entry Point: 00000000

So based on mine above information please can u please tell/suggest me the solution of mine problem.

Regards

Aditya

0 zedhed over 9 years ago

Hi Aditya,

I ran into similar problems when we started using larger RAMdisk images on ZedBoard. I found that my problem was related to copying files over the top of each other in memory when U-Boot is loading components from the SD card.

Something similar may be happening to you here, take a look at your RAMdisk image which advertises itself as 18046997 bytes (which is 0x1136015 bytes) long. Since you are loading this to 0x2000000 in memory, it occupies 0x2000000 to 0x3136015 (which is 0x2000000 + 0x1136015) which stomps over the top of your devicetree which you loaded to 0x2A00000 AND over your kernel which you loaded to 0x3000000.

Overwriting either the kernel and devicetree with over data would prevent you from successfully booting Linux. I suggest you go back and evaluate where these Linux components can be loaded into memory so that they do not overlap.

Another alternative to managing all of this on your own would be to switch over to using either Xilinx PetaLinux Tools or Wind River Pulsar Linux to help you get your design up and running faster.

Regards,

-Kevin
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 100aditya over 9 years ago in reply to zedhed

Hi Kevin,
First of all thanks for such a great reply as myself would have never figured it out as i am very new to such kind of Linux development environment on SoC boards. I will look into this and come back to u. The addresses that i am using,i have got from http://architechboards-zedboard.readthedocs.org/en/latest/quick.html webpage and also this matches with U-boot/ zed_common.h file. So i thought that it is standard thing.
So what you told seems to me logical also. So i will change the addresses. I have total address 0x20000000 .So one thing that::-
1- is it that , at each address only one byte is stored?????Why i am asking this because from some tutorials i got this thing(may be i understood wrong) that at each address two bytes(16 bit) are stored.
2- So i will change accordingly in mine uenv.txt file , then do i also need to change something in mine U-boot/ zed_common.h(which basically contains the setenv variables definitions at the boot time).
lastely, Nice suggestion by you:- "Another alternative to managing all of this on your own would be to switch over to using either Xilinx PetaLinux Tools or Wind River Pulsar Linux to help you get your design up and running faster."
But right now i am in not in a situation to jump into this. I have posted many questions on this forum and As you can see that i am on this work since last one and half months because i started following the webpage http://zedboard.org/product/wilink-8-adaptor which suggested to me to use http://architechboards-zedboard.readthedocs.org/en/latest/quick.html.That is why i could not use PetaLinux etc and now i have come very far.
Thanks you guys always guiding me and helping me all the time. As i have come so far, so let me try this the last hurdle also.
Please keep on guiding me.
Regards
Aditya
Cancel
Vote Up 0 Vote Down

Sign in to reply

Reject Answer

Cancel
0 100aditya over 9 years ago in reply to 100aditya

Hi Kevin,
Please see mine previous reply against your reply(if seen already it is ok and you can read this now). Then this is the uenv.txt file that have changed as per mine advertised address:-
boot_Zed=mmcinfo;fatload mmc 0 0x3300000 ${kernel_image}; fatload mmc 0 0x3200000 ${devicetree_image}; fatload mmc 0 0x200000 ${ramdisk_image}; bootm 0x3300000 0x2000000 0x3200000
uenvcmd=run boot_Zed
1- So is it ok now??.
2- Now also i have used printenv command to list the setenv variables which is as follows.Please have a quick look and suggest me if anything need to be modified here,since i am going to change mine uenv.txt file. But as per mine thinking since i am using uenv.txt file so in that case nothing need to be modified here.
zynq-uboot> printenv
baudrate=115200
bitstream_image=system.bit.bin
boot_image=BOOT.bin
boot_size=0xF00000
bootcmd=run $modeboot
bootdelay=3
bootenv=uEnv.txt
devicetree_image=devicetree.dtb
devicetree_size=0x20000
ethact=Gem.e000b000
ethaddr=00:0a:35:00:01:22
fdt_high=0x20000000
importbootenv=echo Importing environment from SD ...; env import -t ${loadbootenv_addr} $filesize
initrd_high=0x20000000
ipaddr=10.10.70.102
jtagboot=echo TFTPing Linux to RAM... && tftpboot 0x3000000 ${kernel_image} && tftpboot 0x2A00000 ${devicetree_image} && tftpboot 0x2000000 ${ramdisk_image} && bootm 0x3000000 0x2000000 0x2A00000
kernel_image=uImage
kernel_size=0x500000
loadbit_addr=0x100000
loadbootenv=fatload mmc 0 ${loadbootenv_addr} ${bootenv}
loadbootenv_addr=0x2000000
mmc_loadbit_fat=echo Loading bitstream from SD/MMC/eMMC to RAM.. && mmcinfo && fatload mmc 0 ${loadbit_addr} ${bitstream_image} && fpga load 0 ${loadbit_addr} ${filesize}
modeboot=sdboot
nandboot=echo Copying Linux from NAND flash to RAM... && nand read 0x3000000 0x100000 ${kernel_size} && nand read 0x2A00000 0x600000 ${devicetree_size} && echo Copying ramdisk... && nand read 0x2000000 0x620000 ${ramdisk_size} && bootm 0x3000000 0x2000000 0x2A00000
norboot=echo Copying Linux from NOR flash to RAM... && cp.b 0xE2100000 0x3000000 ${kernel_size} && cp.b 0xE2600000 0x2A00000 ${devicetree_size} && echo Copying ramdisk... && cp.b 0xE2620000 0x2000000 ${ramdisk_size} && bootm 0x3000000 0x2000000 0x2A00000
qspiboot=echo Copying Linux from QSPI flash to RAM... && sf probe 0 0 0 && sf read 0x3000000 0x100000 ${kernel_size} && sf read 0x2A00000 0x600000 ${devicetree_size} && echo Copying ramdisk... && sf read 0x2000000 0x620000 ${ramdisk_size} && bootm 0x3000000 0x2000000 0x2A00000
ramdisk_image=uramdisk.image.gz
ramdisk_size=0x5E0000
rsa_jtagboot=echo TFTPing Image to RAM... && tftpboot 0x100000 ${boot_image} && zynqrsa 0x100000 && bootm 0x3000000 0x2000000 0x2A00000
rsa_nandboot=echo Copying Image from NAND flash to RAM... && nand read 0x100000 0x0 ${boot_size} && zynqrsa 0x100000 && bootm 0x3000000 0x2000000 0x2A00000
rsa_norboot=echo Copying Image from NOR flash to RAM... && cp.b 0xE2100000 0x100000 ${boot_size} && zynqrsa 0x100000 && bootm 0x3000000 0x2000000 0x2A00000
rsa_qspiboot=echo Copying Image from QSPI flash to RAM... && sf probe 0 0 0 && sf read 0x100000 0x0 ${boot_size} && zynqrsa 0x100000 && bootm 0x3000000 0x2000000 0x2A00000
rsa_sdboot=echo Copying Image from SD to RAM... && fatload mmc 0 0x100000 ${boot_image} && zynqrsa 0x100000 && bootm 0x3000000 0x2000000 0x2A00000
sdboot=if mmcinfo; then run uenvboot; echo Copying Linux from SD to RAM... && fatload mmc 0 0x3000000 ${kernel_image} && fatload mmc 0 0x2A00000 ${devicetree_image} && fatload mmc 0 0x2000000 ${ramdisk_image} && bootm 0x3000000 0x2000000 0x2A00000; fi
serverip=10.10.70.101
stderr=serial
stdin=serial
stdout=serial
uenvboot=if run loadbootenv; then echo Loaded environment from ${bootenv}; run importbootenv; fi; if test -n $uenvcmd; then echo Running uenvcmd ...; run uenvcmd; fi
usbboot=if usb start; then run uenvboot; echo Copying Linux from USB to RAM... && fatload usb 0 0x3000000 ${kernel_image} && fatload usb 0 0x2A00000 ${devicetree_image} && fatload usb 0 0x2000000 ${ramdisk_image} && bootm 0x3000000 0x2000000 0x2A00000; fi

Please suggest me.

Regards
Aditya
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 100aditya over 9 years ago in reply to 100aditya

Hi Kevin,
Please read mine previous reply to u before reading this and if you have alreday read then it is ok. So i have changed mine uEnv.txt filewhich is as follows and as per mine advertised address that you have noticed alreday.
boot_Zed=mmcinfo;fatload mmc 0 0x3300000 ${kernel_image}; fatload mmc 0 0x3200000 ${devicetree_image}; fatload mmc 0 0x200000 ${ramdisk_image}; bootm 0x3300000 0x2000000 0x3200000
uenvcmd=run boot_Zed

1- So it seems to me ok. is it????

2- Also i used the printenv command and list the setenv variables during boot time. Please have a quick look on this and suggest me that any thing that need to be modified here also as i have changed mine uEnv.txt file. But as for as i think it does not need any kind of modification. Am i right????

zynq-uboot> printenv

baudrate=115200

bitstream_image=system.bit.bin

boot_image=BOOT.bin

boot_size=0xF00000

bootcmd=run $modeboot

bootdelay=3

bootenv=uEnv.txt

devicetree_image=devicetree.dtb

devicetree_size=0x20000

ethact=Gem.e000b000

ethaddr=00:0a:35:00:01:22

fdt_high=0x20000000

importbootenv=echo Importing environment from SD ...; env import -t ${loadbootenv_addr} $filesize

initrd_high=0x20000000

ipaddr=10.10.70.102

jtagboot=echo TFTPing Linux to RAM... && tftpboot 0x3000000 ${kernel_image} && tftpboot 0x2A00000 ${devicetree_image} && tftpboot 0x2000000 ${ramdisk_image} && bootm 0x3000000 0x2000000 0x2A00000

kernel_image=uImage

kernel_size=0x500000

loadbit_addr=0x100000

loadbootenv=fatload mmc 0 ${loadbootenv_addr} ${bootenv}

loadbootenv_addr=0x2000000

mmc_loadbit_fat=echo Loading bitstream from SD/MMC/eMMC to RAM.. && mmcinfo && fatload mmc 0 ${loadbit_addr} ${bitstream_image} && fpga load 0 ${loadbit_addr} ${filesize}

modeboot=sdboot

nandboot=echo Copying Linux from NAND flash to RAM... && nand read 0x3000000 0x100000 ${kernel_size} && nand read 0x2A00000 0x600000 ${devicetree_size} && echo Copying ramdisk... && nand read 0x2000000 0x620000 ${ramdisk_size} && bootm 0x3000000 0x2000000 0x2A00000

norboot=echo Copying Linux from NOR flash to RAM... && cp.b 0xE2100000 0x3000000 ${kernel_size} && cp.b 0xE2600000 0x2A00000 ${devicetree_size} && echo Copying ramdisk... && cp.b 0xE2620000 0x2000000 ${ramdisk_size} && bootm 0x3000000 0x2000000 0x2A00000

qspiboot=echo Copying Linux from QSPI flash to RAM... && sf probe 0 0 0 && sf read 0x3000000 0x100000 ${kernel_size} && sf read 0x2A00000 0x600000 ${devicetree_size} && echo Copying ramdisk... && sf read 0x2000000 0x620000 ${ramdisk_size} && bootm 0x3000000 0x2000000 0x2A00000

ramdisk_image=uramdisk.image.gz

ramdisk_size=0x5E0000

rsa_jtagboot=echo TFTPing Image to RAM... && tftpboot 0x100000 ${boot_image} && zynqrsa 0x100000 && bootm 0x3000000 0x2000000 0x2A00000

rsa_nandboot=echo Copying Image from NAND flash to RAM... && nand read 0x100000 0x0 ${boot_size} && zynqrsa 0x100000 && bootm 0x3000000 0x2000000 0x2A00000

rsa_norboot=echo Copying Image from NOR flash to RAM... && cp.b 0xE2100000 0x100000 ${boot_size} && zynqrsa 0x100000 && bootm 0x3000000 0x2000000 0x2A00000

rsa_qspiboot=echo Copying Image from QSPI flash to RAM... && sf probe 0 0 0 && sf read 0x100000 0x0 ${boot_size} && zynqrsa 0x100000 && bootm 0x3000000 0x2000000 0x2A00000

rsa_sdboot=echo Copying Image from SD to RAM... && fatload mmc 0 0x100000 ${boot_image} && zynqrsa 0x100000 && bootm 0x3000000 0x2000000 0x2A00000

sdboot=if mmcinfo; then run uenvboot; echo Copying Linux from SD to RAM... && fatload mmc 0 0x3000000 ${kernel_image} && fatload mmc 0 0x2A00000 ${devicetree_image} && fatload mmc 0 0x2000000 ${ramdisk_image} && bootm 0x3000000 0x2000000 0x2A00000; fi

serverip=10.10.70.101

stderr=serial

stdin=serial

stdout=serial

uenvboot=if run loadbootenv; then echo Loaded environment from ${bootenv}; run importbootenv; fi; if test -n $uenvcmd; then echo Running uenvcmd ...; run uenvcmd; fi

usbboot=if usb start; then run uenvboot; echo Copying Linux from USB to RAM... && fatload usb 0 0x3000000 ${kernel_image} && fatload usb 0 0x2A00000 ${devicetree_image} && fatload usb 0 0x2000000 ${ramdisk_image} && bootm 0x3000000 0x2000000 0x2A00000; fi

Please suggest me.

Regards

Aditya
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 100aditya over 9 years ago in reply to 100aditya

Hi Kevin,
Actually i have modified mine uEnv.txt file and now that problem has gone but now i am getting kernel panic messsage. Can you please advice for this. Here i am again dumping the serial terminal dump:-

U-Boot 2014.01 (Oct 08 2016 - 12:33:09)
I2C: ready
Memory: ECC disabled
DRAM: 512 MiB
MMC: zynq_sdhci: 0
SF: Detected S25FL256S_64K with page size 256 Bytes, erase size 64 KiB, total 32 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: Gem.e000b000
Hit any key to stop autoboot: 0
Device: zynq_sdhci
Manufacturer ID: 27
OEM: 5048
Name: SD04G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 3.7 GiB
Bus Width: 4-bit
reading uEnv.txt
203 bytes read in 8 ms (24.4 KiB/s)
Loaded environment from uEnv.txt
Importing environment from SD ...
Running uenvcmd ...
Device: zynq_sdhci
Manufacturer ID: 27
OEM: 5048
Name: SD04G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 3.7 GiB
Bus Width: 4-bit
reading uImage
4150864 bytes read in 399 ms (9.9 MiB/s)
reading devicetree.dtb
9275 bytes read in 17 ms (532.2 KiB/s)
reading uramdisk.image.gz
18047061 bytes read in 1697 ms (10.1 MiB/s)
## Booting kernel from Legacy Image at 03300000 ...
Image Name: Linux-3.14.0-xilinx-dirty
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4150800 Bytes = 4 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02000000 ...
Image Name: ZED filesystem
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 18046997 Bytes = 17.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 03200000
Booting using the fdt blob at 0x3200000
Loading Kernel Image ... OK
Loading Ramdisk to 1e9f9000, end 1fb2f015 ... OK
Loading Device Tree to 1e9f3000, end 1e9f843a ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.14.0-xilinx-dirty (architech@architech) (gcc version 4.9.1 (GCC) ) #1 SMP PREEMPT Fri Oct 21 18:51:05 BST 2016
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Xilinx Zynq
[ 0.000000] bootconsole [earlycon0] enabled
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] PERCPU: Embedded 8 pages/cpu @dfbdd000 s10752 r8192 d13824 u32768
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
[ 0.000000] Kernel command line: console=ttyPS0,115200 root=/dev/ram rw earlyprintk
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Memory: 488452K/524288K available (5670K kernel code, 348K rwdata, 1964K rodata, 206K init, 5340K bss, 35836K reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc077ca60 (7635 kB)
[ 0.000000] .init : 0xc077d000 - 0xc07b0a00 ( 207 kB)
[ 0.000000] .data : 0xc07b2000 - 0xc08092b8 ( 349 kB)
[ 0.000000] .bss : 0xc08092c4 - 0xc0d404a0 (5341 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU lockdep checking is enabled.
[ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] ps7-slcr mapped to e0802000
[ 0.000000] clkc: failed to get resource
[ 0.000000] ------------[ cut here ]------------
[ 0.000000] kernel BUG at drivers/clk/zynq/clkc.c:675!
[ 0.000000] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
[ 0.000000] Modules linked in:
[ 0.000000] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.14.0-xilinx-dirty #1
[ 0.000000] task: c07bd6f0 ti: c07b2000 task.ti: c07b2000
[ 0.000000] PC is at zynq_clock_init+0x84/0xa4
[ 0.000000] LR is at zynq_clock_init+0x84/0xa4
[ 0.000000] pc : [<c079ae58>] lr : [<c079ae58>] psr: 600000d3
[ 0.000000] sp : c07b3f90 ip : 00000001 fp : 00000000
[ 0.000000] r10: dfffce00 r9 : c07a5e58 r8 : ffffffff
[ 0.000000] r7 : c07b2000 r6 : c07ba3c0 r5 : 00000001 r4 : dfbf29c0
[ 0.000000] r3 : c07bd6f0 r2 : 00000000 r1 : 00000001 r0 : 0000001c
[ 0.000000] Flags: nZCv IRQs off FIQs off Mode SVC_32 ISA ARM Segment kernel
[ 0.000000] Control: 18c5387d Table: 0000404a DAC: 00000015
[ 0.000000] Process swapper/0 (pid: 0, stack limit = 0xc07b2240)
[ 0.000000] Stack: (0xc07b3f90 to 0xc07b4000)
[ 0.000000] 3f80: c0809808 c0785650 c06a9b04 dfbf2904
[ 0.000000] 3fa0: e0802000 e0802000 c07a2718 c0809300 c0809300 c0785510 c07a2718 c077d9a4
[ 0.000000] 3fc0: ffffffff ffffffff c077d584 00000000 00000000 c07a5e58 18c5387d c07ba40c
[ 0.000000] 3fe0: c07a5e54 c07bedfc 0000406a 413fc090 00000000 00008074 00000000 00000000
[ 0.000000] [<c079ae58>] (zynq_clock_init) from [<c0785510>] (zynq_timer_init+0xc/0x1c)
[ 0.000000] [<c0785510>] (zynq_timer_init) from [<c077d9a4>] (start_kernel+0x1fc/0x37c)
[ 0.000000] [<c077d9a4>] (start_kernel) from [<00008074>] (0x8074)
[ 0.000000] Code: e8bd8010 e59f0020 e5941000 ebf70335 (e7f001f2)
[ 0.000000] ---[ end trace 3406ff24bd97382e ]---
[ 0.000000] Kernel panic - not syncing: Attempted to kill the idle task!

Also i am sharing mine device tree:-

/dts-v1/;

/ {
#address-cells = <1>;
#size-cells = <1>;
compatible = "xlnx,zynq-7000";
model = "Xilinx Zynq";
aliases {
ethernet0 = &ps7_ethernet_0;
serial0 = &ps7_uart_1;
spi0 = &ps7_qspi_0;
} ;
chosen {
bootargs = "console=ttyPS0,115200 root=/dev/ram rw earlyprintk";
linux,stdout-path = "/amba@0/serial@e0001000";
} ;
cpus {
#address-cells = <1>;
#size-cells = <0>;
ps7_cortexa9_0: cpu@0 {
bus-handle = <&ps7_axi_interconnect_0>;
clock-latency = <0x3e8>;
clocks = <&clkc 0x3>;
compatible = "arm,cortex-a9";
d-cache-line-size = <0x20>;
d-cache-size = <0x8000>;
device_type = "cpu";
i-cache-line-size = <0x20>;
i-cache-size = <0x8000>;
interrupt-handle = <&ps7_scugic_0>;
reg = <0x0>;
} ;
ps7_cortexa9_1: cpu@1 {
bus-handle = <&ps7_axi_interconnect_0>;
clock-latency = <0x3e8>;
clocks = <&clkc 0x3>;
compatible = "arm,cortex-a9";
d-cache-line-size = <0x20>;
d-cache-size = <0x8000>;
device_type = "cpu";
i-cache-line-size = <0x20>;
i-cache-size = <0x8000>;
interrupt-handle = <&ps7_scugic_0>;
reg = <0x1>;
} ;
} ;
pmu {
compatible = "arm,cortex-a9-pmu";
interrupt-parent = <&ps7_scugic_0>;
interrupts = <0 5 4>, <0 6 4>;
reg = <0xf8891000 0x1000>, <0xf8893000 0x1000>;
reg-names = "cpu0", "cpu1";
} ;
ps7_ddr_0: memory@0 {
device_type = "memory";
reg = <0x0 0x20000000>;
} ;
wlcore {
compatible = "ti,wlcore";
interrupt-parent = <0x3>;
irq = <0x0>;
platform-quirks = <0x1>;
board-ref-clock = <0x4>;
};

fixedregulator@1 {
compatible = "regulator-fixed";
regulator-name = "wlan-en-regulator";
regulator-min-microvolt = <0x325aa0>;
regulator-max-microvolt = <0x325aa0>;
gpio = <0x4 0x9 0x4>;
startup-delay-us = <0x11170>;
enable-active-high;
linux,phandle = <0x6>;
phandle = <0x6>;
};
ps7_axi_interconnect_0: amba@0 {
#address-cells = <1>;
#size-cells = <1>;
compatible = "xlnx,ps7-axi-interconnect-1.00.a", "simple-bus";
ranges ;
ps7_afi_0: ps7-afi@f8008000 {
compatible = "xlnx,ps7-afi-1.00.a";
reg = <0xf8008000 0x1000>;
} ;
ps7_afi_1: ps7-afi@f8009000 {
compatible = "xlnx,ps7-afi-1.00.a";
reg = <0xf8009000 0x1000>;
} ;
ps7_afi_2: ps7-afi@f800a000 {
compatible = "xlnx,ps7-afi-1.00.a";
reg = <0xf800a000 0x1000>;
} ;
ps7_afi_3: ps7-afi@f800b000 {
compatible = "xlnx,ps7-afi-1.00.a";
reg = <0xf800b000 0x1000>;
} ;
ps7_ddrc_0: ps7-ddrc@f8006000 {
compatible = "xlnx,ps7-ddrc-1.00.a", "xlnx,ps7-ddrc";
reg = <0xf8006000 0x1000>;
xlnx,has-ecc = <0x0>;
} ;
ps7-coresight-comp@f8800000 {
compatible = "xlnx,ps7-coresight-comp-1.00.a";
reg = <0xf8800000 0x100000>;
};
ps7_dev_cfg_0: ps7-dev-cfg@f8007000 {
clock-names = "ref_clk", "fclk0", "fclk1", "fclk2", "fclk3";
clocks = <&clkc 12>, <&clkc 15>, <&clkc 16>, <&clkc 17>, <&clkc 18>;
compatible = "xlnx,ps7-dev-cfg-1.00.a";
interrupt-parent = <&ps7_scugic_0>;
interrupts = <0 8 4>;
reg = <0xf8007000 0x100>;
} ;
ps7_dma_s: ps7-dma@f8003000 {
#dma-cells = <1>;
#dma-channels = <8>;
#dma-requests = <4>;
arm,primecell-periphid = <0x41330>;
clock-names = "apb_pclk";
clocks = <&clkc 27>;
compatible = "xlnx,ps7-dma-1.00.a", "arm,primecell", "arm,pl330";
interrupt-names = "abort", "dma0", "dma1", "dma2", "dma3", "dma4", "dma5", "dma6", "dma7";
interrupt-parent = <&ps7_scugic_0>;
interrupts = <0 13 4>, <0 14 4>, <0 15 4>, <0 16 4>, <0 17 4>, <0 40 4>, <0 41 4>, <0 42 4>, <0 43 4>;
reg = <0xf8003000 0x1000>;
} ;
ps7_ethernet_0: ps7-ethernet@e000b000 {
#address-cells = <1>;
#size-cells = <0>;
clock-names = "ref_clk", "aper_clk";
clocks = <&clkc 13>, <&clkc 30>;
compatible = "xlnx,ps7-ethernet-1.00.a";
interrupt-parent = <&ps7_scugic_0>;
interrupts = <0 22 4>;
local-mac-address = [00 0a 35 00 00 00];
phy-handle = <&phy0>;
phy-mode = "rgmii-id";
reg = <0xe000b000 0x1000>;
xlnx,enet-reset = <0xffffffff>;
xlnx,eth-mode = <0x1>;
xlnx,has-mdio = <0x1>;
xlnx,ptp-enet-clock = <111111115>;
mdio {
#address-cells = <1>;
#size-cells = <0>;
phy0: phy@7 {
compatible = "marvell,88e1510";
device_type = "ethernet-phy";
marvell,reg-init = <0x3 0x10 0xff00 0x1e 0x3 0x11 0xfff0 0x0>;
reg = <0>;
} ;
} ;
} ;
ps7-globaltimer@f8f00200 {
clocks = <0x2 0x4>;
compatible = "arm,cortex-a9-global-timer";
interrupt-parent = <0x3>;
interrupts = <0x1 0xb 0x301>;
reg = <0xf8f00200 0x100>;
};
ps7_gpio_0: ps7-gpio@e000a000 {
#gpio-cells = <2>;
clocks = <&clkc 42>;
compatible = "xlnx,ps7-gpio-1.00.a";
emio-gpio-width = <64>;
gpio-controller ;
gpio-mask-high = <0x00000>;
gpio-mask-low = <0x5600>;
interrupt-parent = <&ps7_scugic_0>;
interrupts = <0 20 4>;
reg = <0xe000a000 0x1000>;
linux,phandle = <0x4>;
phandle = <0x4>;
} ;
ps7_iop_bus_config_0: ps7-iop-bus-config@e0200000 {
compatible = "xlnx,ps7-iop-bus-config-1.00.a";
reg = <0xe0200000 0x1000>;
} ;
ps7-ocmc@f800c000 {
compatible = "xlnx,zynq-ocmc-1.0";
interrupt-parent = <0x3>;
interrupts = <0x0 0x3 0x4>;
reg = <0xf800c000 0x1000>;
};
ps7_pl310_0: ps7-pl310@f8f02000 {
arm,data-latency = <3 2 2>;
arm,tag-latency = <2 2 2>;
cache-level = <2>;
cache-unified ;
compatible = "xlnx,ps7-pl310-1.00.a", "arm,pl310-cache";
interrupt-parent = <&ps7_scugic_0>;
interrupts = <0 2 4>;
reg = <0xf8f02000 0x1000>;
} ;
ps7_qspi_0: ps7-qspi@e000d000 {
clock-names = "ref_clk", "aper_clk";
clocks = <&clkc 10>, <&clkc 43>;
compatible = "xlnx,ps7-qspi-1.00.a";
interrupt-parent = <&ps7_scugic_0>;
interrupts = <0 19 4>;
is-dual = <0>;
num-chip-select = <1>;
reg = <0xe000d000 0x1000>;
xlnx,fb-clk = <0x1>;
xlnx,qspi-mode = <0x0>;
#address-cells = <1>;
#size-cells = <0>;
flash@0 {
compatible = "n25q128";
reg = <0x0>;
spi-max-frequency = <50000000>;
#address-cells = <1>;
#size-cells = <1>;
partition@qspi-fsbl-uboot {
label = "qspi-fsbl-uboot";
reg = <0x0 0x100000>;
};
partition@qspi-linux {
label = "qspi-linux";
reg = <0x100000 0x500000>;
};
partition@qspi-device-tree {
label = "qspi-device-tree";
reg = <0x600000 0x20000>;
};
partition@qspi-rootfs {
label = "qspi-rootfs";
reg = <0x620000 0x5E0000>;
};
partition@qspi-bitstream {
label = "qspi-bitstream";
reg = <0xC00000 0x400000>;
};
};

} ;
ps7_qspi_linear_0: ps7-qspi-linear@fc000000 {
clock-names = "ref_clk", "aper_clk";
clocks = <&clkc 10>, <&clkc 43>;
compatible = "xlnx,ps7-qspi-linear-1.00.a";
reg = <0xfc000000 0x1000000>;
} ;
ps7_ram_0: ps7-ram@0 {
compatible = "xlnx,ps7-ram-1.00.a", "xlnx,ps7-ocm";
interrupt-parent = <&ps7_scugic_0>;
interrupts = <0 3 4>;
reg = <0xfffc0000 0x40000>;
} ;
ps7_scugic_0: ps7-scugic@f8f01000 {
#address-cells = <2>;
#interrupt-cells = <3>;
#size-cells = <1>;
compatible = "xlnx,ps7-scugic-1.00.a", "arm,cortex-a9-gic", "arm,gic";
interrupt-controller ;
num_cpus = <2>;
num_interrupts = <96>;
reg = <0xf8f01000 0x1000>, <0xf8f00100 0x100>;
} ;
ps7-scuc@f8f00000 {
compatible = "xlnx,ps7-scuc-1.00.a";
reg = <0xf8f00000 0xfd>;
};
ps7_scutimer_0: ps7-scutimer@f8f00600 {
clocks = <&clkc 4>;
compatible = "xlnx,ps7-scutimer-1.00.a", "arm,cortex-a9-twd-timer";
interrupt-parent = <&ps7_scugic_0>;
interrupts = <1 13 0x301>;
reg = <0xf8f00600 0x20>;
} ;
ps7_scuwdt_0: ps7-scuwdt@f8f00620 {
clocks = <&clkc 4>;
compatible = "xlnx,ps7-scuwdt-1.00.a";
device_type = "watchdog";
interrupt-parent = <&ps7_scugic_0>;
interrupts = <1 14 0x301>;
reg = <0xf8f00620 0xe0>;
} ;
ps7_sd_0: ps7-sdio@e0100000 {
clock-frequency = <50000000>;
clock-names = "ref_clk", "aper_clk";
clocks = <&clkc 21>, <&clkc 32>;
compatible = "xlnx,ps7-sdio-1.00.a", "generic-sdhci", "arasan,sdhci-8.9a";
interrupt-parent = <&ps7_scugic_0>;
interrupts = <0 24 4>;
reg = <0xe0100000 0x1000>;
xlnx,has-cd = <0x1>;
xlnx,has-power = <0x0>;
xlnx,has-wp = <0x1>;
xlnx,sdio-clk-freq-hz = <0x2faf080>;
} ;
ps7_sd_1: ps7-sdio@e0101000 {
clock-frequency = <50000000>;
clock-names = "clk_xin", "clk_ahb";
clocks = <&clkc 22>, <&clkc 33>;
compatible = "xlnx,ps7-sdio-1.00.a", "generic-sdhci", "arasan,sdhci-8.9a";
interrupt-parent = <&ps7_scugic_0>;
interrupts = <0 47 4>;
reg = <0xe0101000 0x1000>;
xlnx,has-cd = <0x1>;
xlnx,has-power = <0x0>;
xlnx,has-wp = <0x0>;
vmmc-supply = <0x6>;
cap-power-off-card;
} ;
ps7_slcr_0: ps7-slcr@f8000000 {
compatible = "xlnx,ps7-slcr-1.00.a", "xlnx,zynq-slcr", "syscon";
reg = <0xf8000000 0x1000>;
clocks {
#address-cells = <1>;
#size-cells = <0>;
clkc: clkc {
#clock-cells = <1>;
clock-output-names = "armpll", "ddrpll", "iopll", "cpu_6or4x", "cpu_3or2x",
"cpu_2x", "cpu_1x", "ddr2x", "ddr3x", "dci",
"lqspi", "smc", "pcap", "gem0", "gem1",
"fclk0", "fclk1", "fclk2", "fclk3", "can0",
"can1", "sdio0", "sdio1", "uart0", "uart1",
"spi0", "spi1", "dma", "usb0_aper", "usb1_aper",
"gem0_aper", "gem1_aper", "sdio0_aper", "sdio1_aper", "spi0_aper",
"spi1_aper", "can0_aper", "can1_aper", "i2c0_aper", "i2c1_aper",
"uart0_aper", "uart1_aper", "gpio_aper", "lqspi_aper", "smc_aper",
"swdt", "dbg_trc", "dbg_apb";
compatible = "xlnx,ps7-clkc";
fclk-enable = <0xf>;
ps-clk-frequency = <33333333>;
} ;
} ;
} ;
ps7_ttc_0: ps7-ttc@f8001000 {
clocks = <&clkc 6>;
compatible = "xlnx,ps7-ttc-1.00.a", "cdns,ttc";
interrupt-names = "ttc0", "ttc1", "ttc2";
interrupt-parent = <&ps7_scugic_0>;
interrupts = <0 10 4>, <0 11 4>, <0 12 4>;
reg = <0xf8001000 0x1000>;
xlnx,ttc-clk0-clksrc = <0x0>;
xlnx,ttc-clk0-freq-hz = <0x69f6bcb>;
xlnx,ttc-clk1-clksrc = <0x0>;
xlnx,ttc-clk1-freq-hz = <0x69f6bcb>;
xlnx,ttc-clk2-clksrc = <0x0>;
xlnx,ttc-clk2-freq-hz = <0x69f6bcb>;
} ;
ps7_uart_1: serial@e0001000 {
clock-names = "ref_clk", "aper_clk";
clocks = <&clkc 24>, <&clkc 41>;
compatible = "xlnx,ps7-uart-1.00.a", "xlnx,xuartps";
current-speed = <115200>;
device_type = "serial";
interrupt-parent = <&ps7_scugic_0>;
interrupts = <0 50 4>;
port-number = <0>;
reg = <0xe0001000 0x1000>;
xlnx,has-modem = <0x0>;
} ;
ps7_usb_0: ps7-usb@e0002000 {
clocks = <&clkc 28>;
compatible = "xlnx,ps7-usb-1.00.a", "xlnx,zynq-usb-1.00.a";
dr_mode = "host";
interrupt-parent = <&ps7_scugic_0>;
interrupts = <0 21 4>;
phy_type = "ulpi";
reg = <0xe0002000 0x1000>;
} ;
ps7_xadc: ps7-xadc@f8007100 {
clocks = <&clkc 12>;
compatible = "xlnx,ps7-xadc-1.00.a";
interrupt-parent = <&ps7_scugic_0>;
interrupts = <0 7 4>;
reg = <0xf8007100 0x20>;
} ;
} ;
} ;

can u please tell me regarding this problem.

Regards
Aditya
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 zedhed over 9 years ago

Hi Aditya,

Unfortunately, it looks like the kernel crash arises due to some problem within drivers/clk/zynq/clkc.c which can be very difficult to track down.

One method to track this down is to undo all of your hardware platform and devicetree changes to get back to a known working point. Slowly adding pieces back in until it fails is usually one of the only ways to find out which setting can be causing issues resulting in the crash you reported.

Regards,

-Kevin
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel