LabVIEW FPGA Idea Exchange

About LabVIEW FPGA Idea Exchange

Have a LabVIEW FPGA Idea?

  1. Does your idea apply to LabVIEW in general? Get the best feedback by posting it on the original LabVIEW Idea Exchange.
  2. Browse by label or search in the LabVIEW FPGA Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  3. If your idea has not been submitted click New Idea to submit a product idea to the LabVIEW FPGA Idea Exchange. Be sure to submit a separate post for each idea.
  4. Watch as the community gives your idea kudos and adds their input.
  5. As NI R&D considers the idea, they will change the idea status.
  6. Give kudos to other ideas that you would like to see in a future version of LabVIEW FPGA!
Top Kudoed Authors
User Kudos Count
Showing results for 
Search instead for 
Did you mean: 

FPGA FIFO and Memory Editor

I have been working with FPGA for quite a while, and realized that manually opening and editing DMA, Target Scoped, P2P, VI scoped Memories, and project scoped memories can be very tedious and time consuming.  Wouldn't it be great if there was a way to edit FPGA FIFOs and Memories from a single place.  This notion gave birth to the FPGA FIFO Editor and FPGA Memory Editor.  These editors would give the ability to see, create, remove, and edit FIFOs or Memories for that specific project (list both project and VI scoped items).  Furthermore, their could be some additional logic built into the Editor that would alert the user when they have tried to configure something incorrectly (for instance an R Series target only has 3 DMA FIFOs, alert the user when they have configured more than that).


Listed below is  a mock-up of the FPGA FIFO Editor.


FIFO Editor.png

National Instruments
Active Participant

I'm curious, how many of those settings do you normally modify from the defaults? Would it be better if LabVIEW FPGA provided a way for you to create these resources from the diagram, wire up whatever configuration you care about, and then infer the rest from the code.


For instance, with a DMA channel the tool can in general infer the type of the channel from the data type you wire to the Write method. LabVIEW could similarly add a "type" terminal to the Read method so specify what you expect to read.


Personally, I end up making several changes during the design process or I forget to set something correctly.  This usually gets copied to several other locations on the BD.  Even if I don't end up editing the defaults, changing the FIFO names once they are created is time consuming process (especially for a typo).

National Instruments