Member for
2 years
Points
22
SoC Labs Roles
Registered User

Projects

Articles

Interests

Design Flow

Technology

Authored Comments

Subject Comment Link to Comment
FPGA Build Scripts

Hi David,

Thank you for sharing this project! I've learned a lot from your code. A few comments on the FPGA Build Scripts:

  • For building the pynq_zcu104 project as well as the FPGA IP, a top level module was required to be set in the .tcl scripts; otherwise, all of the files get imported as "Unreferenced" and the project failed to build. I simply added: 

         set_property top cmsdk_mcu_chip [current_fileset]

    after reading in the verilog files in build_fpga_ip.tcl, and 

        set_property top design_1_wrapper [current_fileset]

    after creating the design wrapper in build_mcu_fpga_pynq_zcu104.tcl to fix this issue. 
     
  • Additionally, when creating the IP core, the ipx commands added Xilinx IP to a singular directory for some reason. This created the mcu custom IP to become locked, and I couldn't figure out how to "unlock" the IP. (I am using Vivado 2021.1 as well) In this case, I had to start from the beginning of build_mcu_fpga_pynq_zcu104.tcl. I ran all of the script until the ipx commands. I then used the GUI to manually package the IP with the appropriate settings. I then finished running the .tcl scripts to successfully get the bitstream for the chip.

Thank you for sharing your project!

-Meredith

view
IPX Error

Hey David,

I apologize for my late response. I have been working on other projects at the moment. I have tried to recreate the error with no success. The only thing I can think of- I have been running the .tcl script directly instead of the .scr. Maybe that has something to do with it. I plan on picking this project back up in a few weeks. If I run into this error, I'll be sure to document and share.

Meredith

view

User statistics

My contributions
:
0
My comments
:
2

Comments

Meredith,

It would be great to understand any specific areas of interest within Signal Processing you are investigating. Are you looking to develop some new algorithm or new compute architecture to execute existing known functions.

From a SoC perspective, last year the focus of nanoSoC was supporting development of custom accelerators that hopefully allow a more efficient execution environment than an alternate software-based implementation of the same algorithm running on the arm cpu using a standard SoC and memory architecture. Most projects were working on Machine Learning/Artificial Intelligence. This year we are looking at mixed signal but many of the design constraints are similar. Data movement through the SoC and where you can take advantage of parallelism. 

Hopefully some of the projects/teams in this years contest might be of interest to you?

We look forward to hearing from you.
 

Add new comment

To post a comment on this article, please log in to your account. New users can create an account.