LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

FPGA program won't compile any more

    I have an FPGA program that I've compiled and run on several sbRIO's. Recently, I was going to load a new sbRIO. Opened up the project. It won't compile! It says the SCTL misses its 24.99ns window by 0.07ns. I haven't changed the code since the last time it compiled. And not only did it use to compile, but it always ran just fine. One thing that I have changed in the interim is that I've installed more recent versions of LV. (This VI is in 2018, I've installed 2020 and 2021, with FPGA.) So I think it's quite likely that the Xilinx tools have been upgraded since it last compiled correctly. Is it possible that a new version of Xilinx would refuse to let it compile even though it ran just fine when compiled by an older version?

TIA,

    DaveT

-------------------------------------------------------------
David Thomson Original Code Consulting
www.originalcode.com
National Instruments Alliance Program Member
Certified LabVIEW Architect
Certified Embedded Systems Developer
-------------------------------------------------------------
There are 10 kinds of people: those who understand binary, and those who don't.
0 Kudos
Message 1 of 4
(1,088 Views)

Things can change from version to version. It's possible that you were already pretty close to the 25ns requirement so some small change pushed you over.

 

If you're just looking to compile and won't be doing additional development you're probably close enough that you could try just running a few compilations to see if one works.

Matt J | National Instruments | CLA
0 Kudos
Message 2 of 4
(1,063 Views)

When I inherited a program that ran into this issue, the biggest thing that fixed my compile issues was to shrink a DMA FIFO (just went down to the next lower possible size).

 

The other trick that helped somewhat was to add Feedback Nodes in the middle of wire paths to add a form of pipeline.  This will add delays.  In a Single Cycle Timed Loop (SCTL), that delay is 1 clock cycle, which is usually bearable.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 3 of 4
(1,021 Views)

@crossrulz wrote:

When I inherited a program that ran into this issue, the biggest thing that fixed my compile issues was to shrink a DMA FIFO (just went down to the next lower possible size).


Do you find this to be helpful even if there are plenty of overall resources remaining?

Matt J | National Instruments | CLA
0 Kudos
Message 4 of 4
(999 Views)