Picozed 7030 image built with Petalinux won't boot

I am using the Picozed 7020 and 7030 interchangably with the FMC Carrier V2. When I used the default provided boot images, both are able to boot. I am also able to create custom images in Petalinux for the 7020. However, all of my custom builds for the 7030 do not boot. Even rebuilding the default files from the BSP results in a non-booting image.

Does anyone know why this might be? Are there extra steps involved in creating an image for the 7030 as opposed to the 7020?

0 zedhed over 7 years ago

Hi jthilliard,

Which device are you using to boot your 7030?

If you are planning to use QSPI, check out the document titled "Booting PicoZed Using QSPI and eMMC v3.0 (2015.2.1)" found here:

http://www.picozed.org/support/design/4701/76

Within that document is a section named "Changing MTD Partitions" which states the following:

"For larger devices, such as the PicoZed 7z030, the default MTD partition size for the boot image is too small. These steps show how to update the partitions so you can program larger images."

Please take a look at that and see if it is related to the issue that you are seeing.

Best Regards,

-Kevin
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 100jthilliard over 7 years ago

zedhed,
I have been using that document for a couple weeks now and I have followed all the listed steps, including changing the MTD partitions. Whether I change them or not, I still get nothing on the 7030 when I attempt to boot. I forgot to mention in the original post that I am using Petalinux 2017.4
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 zedhed over 7 years ago

Hi jthilliard,

We have not had a chance to get to 2017.4 BSPs to take a look and so we have not encountered this issue yet.

I am pretty sure that we have tested booting the 7030 with the 2017.2 BSP found here:

http://picozed.org/support/design/13076/106

Is there any way that you could use the 2017.2 tools for your design instead?

Best Regards,

-Kevin
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 100jthilliard over 7 years ago

Thanks, using 2017.2 tools fixed the booting problem when I use hardware description files from the provided BSP.
However, I'm still not able to boot images made from hardware description files that I created in Vivado with custom pins.
Is there something on the Vivado side that would cause this?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel