I solved the issue, so I'm gonna say really quickly what went wrong: I was defining a greater number of Computation Engines than the number of blocks I was actually instantiating, so the Crossbar was expecting two more blocks to be connected (and hence the timeouts, I guess from trying to ping the NoC Shells that were not present).
Thansk anyway! On Tue, Sep 11, 2018 at 1:12 PM Leandro Echevarría <leoechevar...@gmail.com> wrote: > Hey folks, > > I'm working on a modified rfnoc-devel FPGA image for the x310, which > involves doing custom RFNoC blocks and modifying some of the existing too. > > In the last test I made, I synthesized instantiating two of my custom > blocks (one of them twice), plus some other modification to the AXI DMA > FIFO block to use the SDRAM in a different way (no longer a FIFO). > > The thing is, when running usrp_uhd_probe I'm getting some errors arising > apparently from a lack of response packets from my blocks. I'm attaching > the log of the command output, and hoping you could answer some questions > about it: > * What can I be missing? I made sure rb_stb stays asserted, and I'm using > the AXI Wrapper in Simple Mode and 64 bits width. The output (upstream) rdy > to the AXI Wrapper only asserts under certain conditions, but I wouldn't > expect any problem from that behavior. > * You can see that the same "no response" error is repeated for several > different CE_xx_Port_yy. Does it mean something's failing for more than one > Computation Engine? And the names of the ports range all the way to the > hundreds, what does that number mean? > > I hope I made myself clear, and you could give me a hand. > > Thanks, as always! > > Leo >
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
