Actions
Forum Thread Details
  • State Not Answered
  • Replies 3 replies
  • Subscribers 338 subscribers
  • Views 439 views
  • Users 0 members are here
Related

Custum picoZed carrier board doesn't work

tomtian

Hello,

We tested picoZed board (7010) on the FMC V2 carrier board and got the example codes working ("Hellow World", "Echo server", etc) without problems. 

 

We then designed our own carrier board with some custom functions.  We kept all the 20 PS MIO user pins the same as the FMC V2 carrier board: to SD card, USB UART, PS_LED1 etc. Also we kept the Gig Ethernet  pins (PETH_MD1_P, PETH_MD1_N, etc) the same locations as the FMC V2 carrier board. The power and reset pins are the same as the FMC V2 carrier board. 

 

In Vivado, we configure the PS with only one  axi gpio: pl_led_1bit. There is no other PL logic. In SDK, the "Hello World" and "Echo server" example works fine on FMC V2 carrier board. For the "HelloWorld" application, I measured the UART pins  (JX3.42, and JX3.44) and got the UART signals. For the "Echo sever" application, I can ping the picoZed board without issues. 

 

Then we moved the same pizoZed board to our custom carrier board. After power on, the D1 (power good) LED light up.  We used the same .bit file to program the FPGA on picoZed board and run applications.  We just can't get the applications works on our carrier board.  For the "HelloWorld" application, there is no signal from the UART pins (JX3.42, and JX3.44).  For the "Echo sever" application, I can't ping the picoZed board on our custom carrier board. 

 

I also measured the voltage and the reset pints (PG_Module, Carrier_SRST_N)  on our custom carrier board and didn't find problems.

 

I have been stuck with this problem for two weeks and don't understand why this simple PS peripheral IO (UART1, Ethnet 0) of Zynq processor don't work on our carrier board.  IAre there any other requirements to make the Zynq processor to run and spit out UART data on the UART pins ?  Someone must have done the similar approach to use picoZed board before.  I will highly appreciate if someone can shine some lights on this problem.

 

Thank you very much,

Tom

  • 0

    Hello Tom,

    When you say you use the same .bit file. Are you refering to the file you generated with the PicoZed FMC V2? If so that could cause an issue as your custom carrier board has different trace lengths and the board definition file would be different.

    Would you be willing to send me the schematic for your custom carrier card for a quick review?

    When you made your custom carrier card did you start with our FMC V2 design files?

    What is the end application for this product? do you plan to go into production with it?

    --Josh

  • 0 in reply to jafoste4

    Hello Josh,

    Thank you very much for the quick response.  I will be glad to send you the schematics of our carrier board to you. Can you let me know your email ?

    Yes, we want to use pizoZed as a real SoM (system on module).  We based our design on FMC V2 Altium Design files. We thought this is the easiest way to adapt the pizoZed into our carrier board. We kept the PS MIO user pins unchanged in schematics.  The PCB layout has been changed for our board.

    The end product is some scientific experimental units. Since we don't have man power to design a PCB with FPGA, memory, Ethernet, etc, the picoZed is a good choice and it saves us a lot of PCB design efforts.  I thought this is also the goal for picoZed as SoM. 

     

    We will use it as a off-shelf SoM module in our production units if we can overcome the issues to migrate from FMC V2 carrier board to our custom carrier board. Can you please help us on this migration ?  We appreciate your kind help.

    -Tom