RevD booting

A simple hello world project which boots from SD on the RevC board, will not boot on the RevD board. The DDR3 is different on the RevD. Therefore, I revised the board definition file to account for the DDR3 and created a custom hardware platform in EDK for the RevD, export it to the SDK hello world project, compiled, created new boot.bin and try it on the RevD, but it still does not work. The linux image on the SD that came with board works and boots fine, but I can't get a bare metal application to work. Can anyone explain why this is happening? Is there something else that is missing in the RevD board definition file that must be revised?

I was able to run the hello world application through PROG usb (J17).

Parents

0 bhfletcher over 12 years ago
The DDR3 on the Rev D is backwards compatible with the DDR3 on Rev C, so those changes weren't necessary. The biggest change going to Rev D was the switch to production silicon.

Zynq C and CES are essentially compatible in every way except

    JTAG ID http://www.xilinx.com/support/answers/37579.htm

    Timing (production timing first appeared in 14.4 w/ Device Pack http://www.xilinx.com/support/answers/54044.htm)

    Correction of errata http://www.xilinx.com/support/answers/47916.htm

Designs that were working for CES will likely work with C devices with no change as long as the application isn’t explicitly checking for the CES JTAG ID

If migrating older designs to the newer tools to achieve production timing, beware of tool migration issues:

    http://www.xilinx.com/support/answers/51807.htm

New designs created in 14.5 for C-grade ZedBoard are fully backward compatible with the CES boards (as long as you aren’t exercising the JTAG ID or something in the errata)
Bryan
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Former Member over 12 years ago in reply to bhfletcher

Thanks!
I managed to boot an RSA authenticated image from SD, but now I can not get the same image to boot from QSPI. When I use the XMD to read out the reboot_status[15:0], I get a BootROM error code of 0xE00C. I cannot decipher this code because its not listed under the BootROM error code table 6-12 in the TRM. Any clues what this error code is?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Former Member over 12 years ago in reply to bhfletcher

Thanks!
I managed to boot an RSA authenticated image from SD, but now I can not get the same image to boot from QSPI. When I use the XMD to read out the reboot_status[15:0], I get a BootROM error code of 0xE00C. I cannot decipher this code because its not listed under the BootROM error code table 6-12 in the TRM. Any clues what this error code is?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data