[FS#1204] zedboard kernel not boot

[LEDE Bugs]

A new Flyspray task has been opened.  Details are below. 

User who did this - mybays (mybays) 

Attached to Project - LEDE Project
Summary - zedboard kernel not boot
Task Type - Bug Report
Category - Kernel
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - All
Due in Version - Undecided
Due Date - Undecided
Details - BoardType:ZedBoard rev.c
All lede release including snapshots boot failed

log:
U-Boot SPL 2016.03 (Nov 20 2017 - 12:10:57)
mmc boot
Trying to boot from MMC
reading system.dtb
reading uImage
spl_load_image_fat: error reading image uImage, err - -1
reading u-boot-dtb.img
reading u-boot-dtb.img


U-Boot 2016.03 (Nov 20 2017 - 12:10:57 +0000)

Model: Zynq Zed Development Board
Board: Xilinx Zynq
DRAM:  ECC disabled 512 MiB
MMC:   sdhci at e0100000: 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 at e0001000
Out:   serial at e0001000
Err:   serial at e0001000
Model: Zynq Zed Development Board
Board: Xilinx Zynq
Net:   ZYNQ GEM: e000b000, phyaddr 0, interface rgmii-id

Warning: ethernet at e000b000 (eth0) using random MAC address - 9a:6a:72:d7:cf:dc
eth0: ethernet at e000b000
Hit any key to stop autoboot:  0 
Zynq> printenv
baudrate=115200
bootcmd=run $modeboot
bootdelay=3
dfu_mmc=run dfu_mmc_info && dfu 0 mmc 0
dfu_mmc_info=set dfu_alt_info ${kernel_image} fat 0 1\\;${devicetree_image} fat 0 1\\;${ramdisk_image} fat 0 1
dfu_ram=run dfu_ram_info && dfu 0 ram 0
dfu_ram_info=set dfu_alt_info ${kernel_image} ram 0x3000000 0x500000\\;${devicetree_image} ram 0x2A00000 0x20000\\;${ramdisk_image} ram 0x2000000 0x600000
fdt_high=0x20000000
fdtcontroladdr=1eb24f90
fit_image=fit.itb
fit_size=0x800000
flash_off=0x100000
initrd_high=0x20000000
jtagboot=echo TFTPing FIT to RAM... && tftpboot ${load_addr} ${fit_image} && bootm ${load_addr}
load_addr=0x2000000
modeboot=sdboot
nor_flash_off=0xE2100000
norboot=echo Copying FIT from NOR flash to RAM... && cp.b ${nor_flash_off} ${load_addr} ${fit_size} && bootm ${load_addr}
sdboot=echo Copying FIT from SD to RAM... && load mmc 0 ${load_addr} ${fit_image} && bootm ${load_addr}
stderr=serial at e0001000
stdin=serial at e0001000
stdout=serial at e0001000
thor_mmc=run dfu_mmc_info && thordown 0 mmc 0
thor_ram=run dfu_ram_info && thordown 0 ram 0
usbboot=if usb start; then echo Copying FIT from USB to RAM... && load usb 0 ${load_addr} ${fit_image} && bootm ${load_addr}; fi

Environment size: 1241/131068 bytes
Zynq> setenv fit_image lede-zynq-zc702-fit.itb
Zynq> boot
Copying FIT from SD to RAM...
reading lede-zynq-zc702-fit.itb
5363072 bytes read in 915 ms (5.6 MiB/s)
## Loading kernel from FIT Image at 02000000 ...
   Using 'config at 1' configuration
   Verifying Hash Integrity ... OK
   Trying 'kernel at 1' kernel subimage
     Description:  ARM OpenWrt Linux-4.4.100
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x020000e4
     Data Size:    3841960 Bytes = 3.7 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x00008000
     Entry Point:  0x00008000
     Hash algo:    crc32
     Hash value:   dfa9a5b8
     Hash algo:    sha1
     Hash value:   7a8c18ddc3c684cae9e42b11032b9461f74abc08
   Verifying Hash Integrity ... crc32+ sha1+ OK
## Loading ramdisk from FIT Image at 02000000 ...
   Using 'config at 1' configuration
   Trying 'ramdisk at 1' ramdisk subimage
     Description:  ARM OpenWrt zc702 ramdisk
     Type:         RAMDisk Image
     Compression:  gzip compressed
     Data Start:   0x023aa1b8
     Data Size:    1507038 Bytes = 1.4 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: unavailable
     Entry Point:  unavailable
     Hash algo:    crc32
     Hash value:   ad7db36e
     Hash algo:    sha1
     Hash value:   0897d778cd4dfe15cb948d4ce86657d743ccc9b6
   Verifying Hash Integrity ... crc32+ sha1+ OK
## Loading fdt from FIT Image at 02000000 ...
   Using 'config at 1' configuration
   Trying 'fdt at 1' fdt subimage
     Description:  ARM OpenWrt zc702 device tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x0251a1a8
     Data Size:    12483 Bytes = 12.2 KiB
     Architecture: ARM
     Hash algo:    crc32
     Hash value:   3f1a2246
     Hash algo:    sha1
     Hash value:   1d92f37305263aaf7141e96692594b5a294b977a
   Verifying Hash Integrity ... crc32+ sha1+ OK
   Booting using the fdt blob at 0x251a1a8
   Loading Kernel Image ... OK
   Loading Ramdisk to 1e9b3000, end 1eb22ede ... OK
   Loading Device Tree to 1e9ac000, end 1e9b20c2 ... OK

Starting kernel ...

undefined instruction
pc : []          lr : []
reloc pc : []    lr : []
sp : 1eb24968  ip : 60406919     fp : 1ff488b0
r10: 00000000  r9 : 1eb27ef0     r8 : 020000e4
r7 : 60406919  r6 : 00008000     r5 : 1ffa5bb4  r4 : 00000000
r3 : 000030c3  r2 : 1e9ac000     r1 : 00000000  r0 : 1eb27fb0
Flags: nZCv  IRQs off  FIQs off  Mode SVC_32
Resetting CPU ...

resetting ...

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=1204