The FMC carriercard V2 supposed should have .BIn files for each picoZed models, but the SD card after loading it on a computer displays empty. There is nothing in the SD card that was supposed to be pre-programmed.
Is there a link or resources where I can manually download BOOTPZ7030.BIN file?
To zedmann2000:
I may be missing something but the page that you linked to only list ZIP files with PDF documents inside them. In "Wind River
Pulsar
Linux OS" i found a link to the actual page that has the ready-made images: https://distro.windriver.com/public_feeds/WindRiver-Pulsar-Linux-Avnet-PicoZed-image/Releases/Latest/
"The SDCARD does not come preprogrammed as we do not know which PicoZed you are choosing to use with it"
(1) That does not rhyme with the the product page that clearly lists the following as included: "microSD card preloaded with Wind River Pulsar Linux (with SD adapter card)"
(2) Your claim does not make complete sense anyways, there are 4 variants of PicoZed and each boot image is about 1 GB (see link above) which more than comfortably fits in the 8 GB card (I even got a 16 GB one, though empty). Even if the card needs to be wiped and made bootable there is still no reason not to include the images to start with.
There must have been a production mistake which has not been communicated properly to the forum moderators.
Hi there,
Sorry for any confusion. The documentation you reference needs to be updated, but we do not support WindRiver as an out of box experience any longer. Customers that wish to have this will need to follow the documentation as I linked.
On the page I linked, there is a document under "Wind River Pulsar Linux OS" which will allow you to go through the process of obtaining WindRiver. Within that document, you will see a link to the WindRiver repository of images.
The PicoZed images are located here: https://distro.windriver.com/public_feeds/WindRiver-Pulsar-Linux-Avnet-PicoZed-image/Releases/Latest/
Following the document, you will see that you need to sector-by-sector write the image. It is not the same procedure as when using a PetaLinux image.ub/boot.bin combination.This means that you cannot have multiple images on the card, unless you create something custom, even though there is room for more than 1 at about 1 GB each. There was not a production mistake, as I said, we do not support this as an out of box experience any longer and the documentation has not been updated. I have put in a request to get this moved up in queue to be taken care of.
Thank you for pointing it out to us!
–Dan
