cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Newbie
Newbie
4,562 Views
Registered: ‎10-25-2012

U-Boot - Error lock down A304 - ZedBoard

Hello everyone:
We are working with ZedBoard and trying to make it boot.
we followed instructions from the wiki (http://wiki.xilinx.com/zc702-boot-from-flash).
But when we tur it on, this message appear:
"Error lock down A304"
Does anyone know what it means?

Thank you

Agu Martina

0 Kudos
4 Replies
Highlighted
Xilinx Employee
Xilinx Employee
4,552 Views
Registered: ‎09-10-2008

Re: U-Boot - Error lock down A304 - ZedBoard

Have u tried http://www.zedboard.org yet? Our team is not yet supporting that board, but plan to soon.

Sorry.
0 Kudos
Highlighted
Newbie
Newbie
4,491 Views
Registered: ‎11-11-2012

Re: U-Boot - Error lock down A304 - ZedBoard

I was the same error occurs.(Error lock down A304)

Did you solve?

0 Kudos
Highlighted
Adventurer
Adventurer
4,473 Views
Registered: ‎06-13-2011

Re: U-Boot - Error lock down A304 - ZedBoard

I experienced the same problem with the Xilinx ZC702 development board one time after I just flashed the QSPI with a new boot image.  I never tracked down the exact cause, but I created a new flash image and programmed the QSPI again and things worked.  At the time I figured I had a corrupted boot image file.

 

Steve

0 Kudos
Highlighted
Scholar
Scholar
4,444 Views
Registered: ‎05-28-2012

Re: U-Boot - Error lock down A304 - ZedBoard

Those messages are printed by the FSBL. They map to ARM exceptions:

A301 = undefined instruction executed
A302 = software interrupt occurred
A303 = current memory access could not be completed - prefetch abort
A304 = current memory access could not be completed - data abort
A305 = normal interrupt occurred
A306 = fast interrupt occurred

I think FSBL considers any exceptions as an error. An A304 would suggest that the processor ran an op-code that resulted in an memory access error. More likely that the op-code is bad. That op code could be in the FSBL or u-boot. Probably just enough FSBL got properly loaded to catch the exception and print the message. Some other part of the FSBL is corrupted in the source media (NAND, SD Card, QSPI, etc) and is corrupted in RAM where execution is occurring.

0 Kudos