cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Adventurer
Adventurer
3,582 Views
Registered: ‎12-07-2015

JTAG BOOT and SD CARD BOOT

Hello,

I want to test my application without sd card boot. I have the trd 2015.4 here and thought i could use it with jtag boot aswell. So thats my order of commands in xmd:

fpga -f C:/Users/FF/Desktop/Neuer_Ordner/zc702_base_trd_wrapper.bit
connect arm hw
dow C:/Users/FF/Desktop/Neuer_Ordner/zynq_fsbl.elf
con
stop
dow -data C:/Users/FF/Desktop/Neuer_Ordner/devicetree.dtb 0x2a00000
dow -data C:/Users/FF/Desktop/Neuer_Ordner/uramdisk.image.gz 0x2000000
dow -data C:/Users/FF/Desktop/Neuer_Ordner/uImage 0x3000000
dow C:/Users/FF/Desktop/Neuer_Ordner/u-boot.elf
con

then i type in terminal program:

bootm 0x3000000 0x2000000 0x2a00000

but then the uramdisk.image.gz fails:

 

 

 

U-Boot 2015.07 (Dec 18 2015 - 14:45:06 +0530)

Model: Zynq ZC702 Base TRD
I2C:   ready
DRAM:  ECC disabled 1 GiB
MMC:   zynq_sdhci: 0
SF: Detected N25Q128A with page size 256 Bytes, erase size 64 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Zynq ZC702 Base TRD
Net:   Gem.e000b000
Hit any key to stop autoboot:  0
TFTPing Linux to RAM...
Gem.e000b000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Gem.e000b000: No link.
zynq-uboot> bootm 0x3000000 0x2000000 0x2a00000
## Booting kernel from Legacy Image at 03000000 ...
   Image Name:   Linux-4.0.0-xilinx-g468329e
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3663976 Bytes = 3.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02000000 ...
   Image Name:
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    31452673 Bytes = 30 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid

. I think it's because it is written:

SF: Detected N25Q128A with page size 256 Bytes, erase size 64 KiB, total 16 MiB

or am i wrong? what causes the error?

kind regards,

lunarix

0 Kudos
1 Reply
Highlighted
Moderator
Moderator
3,525 Views
Registered: ‎10-06-2016

Hi @lunarix94-

 

According to your screenshot the size of your ramdisk is 0x1DFEE01, so the image will be located in the 0x2000000 - 3DFEE01. So when you download your kernel image you have an overlap. That's why the CRC of the ramdisk is producing an error message.

 

Regards,

Ibai


Ibai
Don’t forget to reply, kudo, and accept as solution.
0 Kudos