PicoZed Hardware Design - Recent Threads

Picozed 7020 sd card boot not working

vishnukannan01 — Thu, 18 Sep 2025 13:30:14 GMT

Hi Iam developed a carrier card for picozed 7020 som. Carrier card have ethernet and sd card boot interface. When i boot through qspi mode board was booting since no uart interface provide i cant see the booting but fpga done indication through led in my carrier card glows. But when i made a boot image for booting from sd card it is not booting and fpga done led also not glowing. Pls help me.

RE: Picozed 7020 sd card boot not working

vishnukannan01 — Tue, 30 Sep 2025 05:45:51 GMT

tcl file showing some error. do you have BOOT.BIN file so that i can use in my carrier card.

RE: Picozed 7020 sd card boot not working

iksevas — Mon, 29 Sep 2025 16:12:45 GMT

github.com/.../PZ7020_FMC2

RE: Picozed 7020 sd card boot not working

vishnukannan01 — Mon, 29 Sep 2025 15:09:13 GMT

Can you share picozed 7020 tcl file for vivado?

RE: Picozed 7020 sd card boot not working

iksevas — Sat, 27 Sep 2025 07:43:10 GMT

See here:

adaptivesupport.amd.com/.../61064

RE: Picozed 7020 sd card boot not working

vishnukannan01 — Sat, 27 Sep 2025 04:25:55 GMT

I already implemented cd but not wp. Whether it required?

RE: Picozed 7020 sd card boot not working

iksevas — Thu, 25 Sep 2025 18:48:36 GMT

Your Vivado design could be suffering from not implementing CD (Card Detect) and / or write protect (WP)?

RE: Picozed 7020 sd card boot not working

iksevas — Thu, 25 Sep 2025 18:47:01 GMT

Here is schematic from PicoZed Carrier for SD card. Did you reference/copy this?

RE: Picozed 7020 sd card boot not working

iksevas — Thu, 25 Sep 2025 18:45:13 GMT

Carrier Card Generic Guidelines are here:

https://www.avnet.com/wps/wcm/connect/onesite/6dbe6459-a114-436b-b0e1-413e6907a70b/5283-CDG-PicoZed-V2.5.pdf?MOD=AJPERES&CACHEID=ROOTWORKSPACE.Z18_NA5A1I41L0ICD0ABNDMDDG0000-6dbe6459-a114-436b-b0e1-413e6907a70b-nDjtICF

As far as layout is concerned, the SOM routing of the BANK 501 MIO signals to the JX connector are all length matched. So, guidance for the layout of the carrier card can follow the guidance provided in the Zynq-7000 PCB Design Guidelines. Zynq-7000 SoC PCB Design Guide (UG933) • Viewer • AMD Technical Information Portal

RE: Picozed 7020 sd card boot not working

vishnukannan01 — Thu, 25 Sep 2025 18:31:43 GMT

Iam using sdhc card 16gb. What are the things to check in layout. Also when iam booting in qspi mode fpga done led in my carrier card is glowing and it is not when iam booting from sd card. Do you have any boot image for the part xc7z020clg400 because iam doughting the board selection in vivado. I already probed clock and data line and cmd line in pcb. Iam getting clock for a ms at the time of booting then it is saturating. Command also like that. Any thing else to check

RE: Picozed 7020 sd card boot not working

iksevas — Thu, 25 Sep 2025 16:10:38 GMT

Concern is layout on custom carrier card.

Have you tried slowing down SD card interface to see if you begin to function?

What about SD card? Have you changed cards? You should be using SDHC type card and not SDXC.

RE: Picozed 7020 sd card boot not working

vishnukannan01 — Thu, 25 Sep 2025 14:26:40 GMT

RE: Picozed 7020 sd card boot not working

vishnukannan01 — Thu, 25 Sep 2025 13:35:45 GMT

I tried with both bare metal(BOOT.BIN) and peta linux both of them are not working. Switch position I conformed. I have picozed evaluation board through that sd card boot file was working. In vivado i choosen evaluation board support file when I am making vivado code for my carrier card I am choosing xc7z020clg400-1. Still my sd card is not detecting. Ethernet port in my sd card is working that I conformed. I could change the ip and ping also working that i checkd throuh uart.

RE: Picozed 7020 sd card boot not working

iksevas — Thu, 18 Sep 2025 16:19:20 GMT

Did you properly set boot mode switch? Did you make sure to include the PL code when making your boot files? On your SD card, is your design Linux or bare metal? By this, I mean did you included the correct files on the SD card (BOOT.BIN, BOOT.SCR, IMAGE.UB for Peta Linux or BOOT.BIN for bare metal? Do you have a PicoZed Carrier Card from Avnet (a known functional system) that you can try and test your process on to make sure your development process is sound?

matlab simulink support?

nonameavailable — Mon, 07 Oct 2024 17:44:11 GMT

I'm aiming to use thie board to implement some simple algorithms to control other chips. but i have some questions:

Does this SOM and the carrier board compatible to matlab simulink or do i need other external tools?

Does any one have similar experience or resources to share?

Thanks !!

RE: matlab simulink support?

bidrohini — Thu, 10 Oct 2024 07:41:19 GMT

I only found these links:

https://www.mathworks.com/hardware-support/arduino.html

https://www.mathworks.com/matlabcentral/fileexchange/40312-simulink-support-package-for-arduino-hardware

RE: Ordering Picozed from AVNET

nonameavailable — Thu, 03 Oct 2024 16:51:55 GMT

Thanks, and i will also need to buy the main board to plug in this SOM right? also wondering does this set work well with matlab simulink?

Ordering Picozed from AVNET

nonameavailable — Wed, 02 Oct 2024 23:01:09 GMT

I’m interested in your Picozed product and support Zynq-7000 SoC family and I have the following questions

When ordering your product (ex.AES-Z7PZ-7Z010-SOM-G/REVE), does that include both the SoC and the board? And if yes, are they soldered together already?
Is AES-Z7PZ-7Z010-SOM-G/REVE and AES-Z7PZ-7Z015-SOM-I-G/REV-E different board or they just come with different SoC but the same board?
If they are different board, where do I choose which SoC to put on when I order?

Thanks,

Andrew

RE: Ordering Picozed from AVNET

c_chil — Thu, 03 Oct 2024 05:11:05 GMT

Please refer to the Avnet Boards Product page for PicoZed for more information. https://www.avnet.com/wps/portal/us/products/avnet-boards/avnet-board-families/picozed/picozed-board-family

Answers:

1) Yes and Yes

2) Same mating connector, different SoC

3) See Link. The SoC is in the part number ie, 7Z010, 7Z015, or 7Z020

Please note there are Industrial and Commercial Grade SOMs.

How to interface HDMI display i2c touch Picozed (xc7z030)?

fpga_test — Fri, 28 Jun 2024 13:48:24 GMT

Hii,

I want to interface hdmi with PICOZED(XC7Z030) but there should be i2c touch.

I am using vivado 2022.2 and vitis 2022.2

I refer your design but not get clear id, how you hdmi display i2c touch.

/products/devtools/avnetboardscommunity/m/files/48648#

can you please explain it 1. why you use second axi_gpio_1 (pl_pbs_5bits). and how your device know its i2c touch.

2. .xdc also missing when i added https://github.com/Avnet/hdl/blob/master/Boards/PZ7030_FMC2/PZ7030_7015_RevC_FMCV2_RevA_v1.xdc

do not understand which pin are given to axi_gpio_1.

3. sdk there is no platform and application. please share proper vitis application.

4. without using rgb to vga is only using axi iic ip we got the hdmi display i2c touch? if yes ? how?

NVMe SSD connected to fpga drive is not detecting

nithinsteffy — Thu, 06 Jun 2024 04:33:05 GMT

Hi Team,

I've my new Picozed FMC Carrier Card Gen 2 equiped with Picozed 7015/7030 SOC on it.

I've successfully done booting through SD card with a prebuilt petalinux image. 2021.1

when i write command lsblk or lspci, it's not listing my WD Blue SN580 NVMe ssd connected to it.

Any solution for this?

Warm regards

NITHIN

RE: NVMe SSD connected to fpga drive is not detecting

nithinsteffy — Fri, 14 Jun 2024 04:41:02 GMT

Hi Shabaz,

The solution is pretty simple, I've done this using Windows, not in Linux.

first of all we need to install Vivado 2022.1 and Vitis 2022.1

Then clone this repository to your desired directory.

Then follow the steps in this link.

It will automatically create a vivado project and a vitis workspace .

then open vivado and open this project in vivado, then generate a bitstream for the block deign already prepared

then export the project including bitstream

After that open the vitis workspace and run the project as GDB as mentioned in the link.

you can see the output in putty connected to fmc carrier card

I've done this in picozed fmc carrier card equipped with picozed 7015 SOC.

Please remember to put the switches in JTAG boot mode.

That's all

Regards

NITHIN

RE: NVMe SSD connected to fpga drive is not detecting

shabaz — Fri, 14 Jun 2024 03:02:16 GMT

Hi,

What was the solution? (so that anyone else that hits this, can see the answer : )

RE: NVMe SSD connected to fpga drive is not detecting

nithinsteffy — Wed, 12 Jun 2024 10:14:46 GMT

Hi Team,

Problem solved

Zynq 7020 SD FAT corruption

EniX2000 — Wed, 29 May 2024 15:45:18 GMT

Hi there!

I'm encountering a very nasty FAT corruption problem. The problem appears systematically after a first write in a file stored in an uSD card.

There is a workaround: to place the file at the very beginning of the uSD card or in the first 2Gb of uSD space. In this case the problem is avoided whaterver the number of writes (hundreds) !

The problem does not appear during file reads. For instance I can place the BOOT.BIN at the very end of the uSD card (after 23Gb of data) and the system boots OK every time! I manage to read without probles configuration files placed also at the high end of the uSD capacity.

The FAT corruption is quite strange since I use standard ff.c functions (version R0.10b, 19 May 2014, included in Vivado 2015.2 ) in order to open the pre-existing file and to write data into.

The file is contiguous and its size remains constant so there should be no cluster allocation/change. Despite this after the first write in the file I see the first sector number truncated. Runing chkdsk detects an file entry crossing which is quite abnormal since once again I use standard access functions.

My application:

-Bare Metal on PicoZed (Zynq 7020)

-Vivado 2015.2 (project legacy reasons)

-xilffs 3.0

-uSD SanDisk MaxEndurance, 32Gb HC I U3 C10

-Standard factory FAT32 formatting (512bytes sector size, 32768bytes cluster size).

I force a uSD check-up and the card is free from errors prior to an atomic writing. After a first write, if the file is in a "high" position the portion of FAT concerning the respective file appears to be corrupted.

One hypothesis is that the initial formatting of the uSD is not compatible with the xilff library. What formatting works for you and with what capacity ?

Any help will be greatly appreciated.!!!

Regards,