Dear all, I combined noc_block_siggen and noc_block_fir_filter to transmit pulses with its samples can be updated using a E312. I borrowed some code from the axi_fir_filter.v for sample update. The updated samples are stored in block memory. The transmitter works well for both channels. However, after I added receiver blocks it gave me a strange error:
"Uterminate called after throwing an instance of 'uhd::io_error' what(): EnvironmentError: IOError: Block ctrl (CE_00_Port_10) packet parse error - EnvironmentError: IOError: Expected packet index: 983 Received index: 982 s: line 14: 1820 Aborted" Here are some questions: 1. I guess "CE_00_Port_10" is one of the noc_block_siggen port, but not sure... 2. This error happens when I start transmitting and update tx channel 2. My tx channel 1 works fine with the receiver with no error. I have tried to find any the difference between the codes in verilog and c++ for the two tx channels. I used the same rfnoc module(same verilog .v files) in e310_core. Just not sure where the difference could be... 3. I also find that rx_stream->recv() stops the transmission and triggers the error. For example, after start transmitting and update tx channel 2 samples, tx channel 2 can transmit updated waveform. As long as rx_stream->recv() started after the sample update, the transmission is killed. Then after several samples received, the whole program exited with the error. My first thought was to manage my transmit and receive threads in order to let receive thread wait for the tx sample update. However, no mater how long receiver wait for the update, the next rx_stream->recv() will stop the program. 4. I don't know how the receiver stream could related to the transmitter. I used set_taps() for tx sample update. Since set_taps() related to writing register (sr_write(SR_RELOAD, uint32_t(taps[i]));), I have checked clear_tx_stream in axi_wrapper but it is not related to this issue in my case. I also checked EOB for the transmitter, it seems not related to this issue too. http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2018-May/056462.html http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2017-June/053210.html Any ideas and comments about this question are welcome. Thank you in advance!!! <http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2018-May/056462.html>
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
