cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
ctbk1989
Visitor
Visitor
9,560 Views
Registered: ‎01-09-2014

Microzed Boot Error

Hi all,
I followed the xilinx tutorial. However when I boot the sdcard I get.

*******************************************
U-Boot 2013.01-dirty (Jun 14 2013 - 16:25:48)
DRAM: 512 MiB
WARNING: Caches not enabled
MMC: zynq_sdhci: 0
SF: Detected S25FL129P_64K with page size 64 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Net: Gem.e000b000
Hit any key to stop autoboot: 0
Copying Linux from SD to RAM...
Controller never released inhibit bit(s).
Device: zynq_sdhci
Manufacturer ID: 2
OEM: 544d
Name: SA04G
Tran Speed: 25000000
Rd Block Len: 512
SD version 2.0
High Capacity: Yes
Capacity: 3.7 GiB
Bus Width: 1-bit
Loading bitstream from SD/MMC/eMMC to RAM..
Controller never released inhibit bit(s).
Device: zynq_sdhci
Manufacturer ID: 2
OEM: 544d
Name: SA04G
Tran Speed: 25000000
Rd Block Len: 512
SD version 2.0
High Capacity: Yes
Capacity: 3.7 GiB
Bus Width: 1-bit
Controller never released inhibit bit(s).
** Bad device mmc 0 **
***************************************

I tried many way but it didn't work. What am I missing??

My's target is Microzed Rev.C, host operating system is winxp, xilinx tool version 14.5.
Boot.bin: command build <bootgen -image boot.bif -o i boot.bin>
Thanks in advance for any advice you can give me.

 

Be

0 Kudos
5 Replies
sampatd
Scholar
Scholar
9,538 Views
Registered: ‎09-05-2011

During boot-time, can you try stepping into u-boot console and try the following commands?

 

sd_boot.png
0 Kudos
sampatd
Scholar
Scholar
9,483 Views
Registered: ‎09-05-2011

Did you have chance to try this? I would like to know.

Thanks.
0 Kudos
ctbk1989
Visitor
Visitor
9,444 Views
Registered: ‎01-09-2014

I solved my  problem. I rebuild uboot, boot succesfful

 

Thanks you very much

0 Kudos
onurcansel
Visitor
Visitor
9,349 Views
Registered: ‎03-13-2011

I was getting the same error as the original poster while trying to run the "MicroZed_Open_Source_Linux_In_System_QSPI_Programming_14_5_02-Tutorial" on my MicroZed 7020.   

 

I tried the given u-boot commands to fix the problem. It worked like a charm and the script in the tutorial triggered writing the contents of the uSD to the QSPI. However once I tried to follow the tutorial and run the linux from FLASH i got the following error. 

 

 "

DRAM: 512 MiB
WARNING: Caches not enabled
MMC: zynq_sdhci: 0
SF: Detected S25FL129P_64K with page size 64 KiB, total 16 MiB
In: serial
Out: serial
Err: serial
Net: Gem.e000b000
Hit any key to stop autoboot: 0
Copying Linux from SD to RAM...
Device: zynq_sdhci
Manufacturer ID: 2
OEM: 544d
Name: SA08G
Tran Speed: 50000000
Rd Block Len: 512
SD version 2.0
High Capacity: Yes
Capacity: 7.3 GiB
Bus Width: 4-bit
Loading bitstream from SD/MMC/eMMC to RAM..
Device: zynq_sdhci
Manufacturer ID: 2
OEM: 544d
Name: SA08G
Tran Speed: 50000000
Rd Block Len: 512
SD version 2.0
High Capacity: Yes
Capacity: 7.3 GiB
Bus Width: 4-bit
reading system.bit.bin
2083740 bytes read in 293 ms (6.8 MiB/s)
Error: Timeout waiting for FPGA to config.
fpga - loadable FPGA image support

Usage:
fpga [operation type] [device number] [image address] [image size]
fpga operations:
dump [dev] Load device to memory buffer
info [dev] list known device information
load [dev] [address] [size] Load device from memory buffer
loadb [dev] [address] [size] Load device from bitstream buffer (Xilinx only)
loadmk [dev] [address] Load device generated with mkimage
For loadmk operating on FIT format uImage address must include
subimage unit name in the form of addr:<subimg_uname>

"

And trying the same u-boot commands quoted now gave the following error.

 

"## Booting kernel from Legacy Image at 03000000 ...
Image Name: Linux-3.8.0-xilinx
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2964792 Bytes = 2.8 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from FIT Image at 02a00000 ...
Bad FIT ramdisk image format!
Ramdisk image is corrupt or invalid"

 

I tried redoing all the steps and started from the image in the tutorial from the SD card and I get the same errors as above now, both from tutorial image and the flash boot.

 

How can I solve this problem or at the least revert back to the factory settings for the Flash?

 

Onur

0 Kudos
radheys
Xilinx Employee
Xilinx Employee
9,337 Views
Registered: ‎02-20-2014

Can you try resetting uboot environment variables.

 

env default [-f] var [...] - [forcibly] reset variable(s) to their default values

 

env default -a
saveenv

 

Also ensure that flash address where we are wriiting the ramdisk should be the same as where uboot is reading.

Do a printenv to see which offset uboot is reading the ramdisk image.

0 Kudos