Hey Steve, It's difficult to do a full diagnosis here without any additional info. In UHD 3, we used that bit to clear/flush blocks, so I'm guessing that's what you're doing too.
You might not need the pipeline FIFOs. That's because we separated the stream endpoints from the blocks and made the noc shell leaner and more bespoke. In general, the idea is that blocks focus on their key are of expertise (e.g., some DSP algorithm) and data movement can be handled by the infrastructure. --M On Sat, Oct 12, 2024 at 10:03 AM <steve.wake...@roke.co.uk> wrote: > Hi > > I am migrating a fairly complicated design over to RFNOC4.0 > > I am carefully comparing the design I have with a smple 4.0 deesign. > > Obviously there are big differences between around the AXI_WRAPPER and NOC > SHELL. We currently in 3.0 have pipeline FIFOs that go between the > NOC_SHELL and our logic. The clear for this uses *clear_tx_seqnum[0]* > > However clear_tx_seqnum does not exist in the template genereated for > RFNOC4 as the noc shell is very different. > > > How do I now handle clearing the pipeline FIFOs or indeed can I remove > them? > > > Thanks > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-le...@lists.ettus.com >
_______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
