Re: [USRP-users] RFNoC: complex_vector support from reprogrammable embedded settings registers

2017-08-08 Thread Andrew Lanez via USRP-users
Typo, the 3rd to last paragraph should read: Or I could hack *rfnoc_fir_cci()*. I started this by replacing int vectors with std::complex vectors everywhere FIR taps were referenced in the in-tree module's C++ library but I stopped when it traced up to block.h because that may affect other modules

[USRP-users] RFNoC: complex_vector support from reprogrammable embedded settings registers

2017-08-08 Thread Andrew Lanez via USRP-users
Hi, I am developing a FIR filter that will eventually accepts complex taps reprogrammable during runtime. As a first iteration, I want to verify it works like the in-tree module with int_vector real taps. So I configure the settings register in OOT module's .xml file to take int_vector taps but ru

Re: [USRP-users] RFNoC: complex_vector support from reprogrammable embedded settings registers

2017-08-13 Thread Andrew Lanez via USRP-users
;ve created a C++ driver that accepts floating point inputs and converts > to fixed point before programming to FPGA registers. Your preference. > > Hope this helps, > EJ > > > > On Tue, Aug 8, 2017 at 6:00 AM, Andrew Lanez via USRP-users < > usrp-users@lists.et

Re: [USRP-users] RFNoC: complex_vector support from reprogrammable embedded settings registers

2017-08-14 Thread Andrew Lanez via USRP-users
>> taps as your HDL code requires. >>> >>> You'll notice fir_block_ctrl_impl uses integer taps. This ends up being >>> a little clumsy when developing flowgraphs, since your flowgraph >>> application needs to handle the floating point / fixed point convers