Re: [USRP-users] timout issue on RFNoC output

2017-07-26 Thread Jason Matusiak via USRP-users
Jonathon, I have been working on this the last two days and can't seem to get it working. My destructor looks like this: dataGenerator_impl::~dataGenerator_impl() { std::cout << "In here3.\n"; uhd::rfnoc::dataGenerator_block_ctrl temp; temp.issue_stream_cmd(::uhd::stream_cmd_t::S

Re: [USRP-users] timout issue on RFNoC output

2017-07-24 Thread Jason Matusiak via USRP-users
What I did was instead of creating an enable flag, I used the PKT_SIZE value I write when I execute a flowgraph to be my enable: assign enabled = (PKT_SIZE > 0) ? 1'b1 : 1'b0; assign o_tvalid = enabled; That should work, right? If not, how do I know that initialization is done? I didn't write

Re: [USRP-users] timout issue on RFNoC output

2017-07-24 Thread Jonathon Pendlum via USRP-users
In the first screenshot you captured your block sending out a command response packet. That is normal. In the second screenshot, I couldn't see the full value of the header / first word, so I cannot say if it had any issues. Did you add an explicit enable for your block that turns it on after ini

Re: [USRP-users] timout issue on RFNoC output

2017-07-24 Thread Jason Matusiak via USRP-users
One last piece of oddball info I've discovered. RFNoC:dataGenerator -> RFNoC:FIFO -> throttle -> QT GUI Time Sink 1 - If I program the X310 and run it, I get timeouts streaming immediately and nothing shows up on the timesink. If I then stop it and run it again, I get some data through, and t

Re: [USRP-users] timout issue on RFNoC output

2017-07-21 Thread Jonathon Pendlum via USRP-users
Yep On Fri, Jul 21, 2017 at 11:54 AM, Jason Matusiak < ja...@gardettoengineering.com> wrote: > I need to re-setup my debug messages to check. To be clear, you are > talking about the o_tdata (etc) up in my upper level > noc_block_dataGenerator, right? > > > > On 07/21/2017 02:52 PM, Jonathon Pen

Re: [USRP-users] timout issue on RFNoC output

2017-07-21 Thread Jason Matusiak via USRP-users
I need to re-setup my debug messages to check. To be clear, you are talking about the o_tdata (etc) up in my upper level noc_block_dataGenerator, right? On 07/21/2017 02:52 PM, Jonathon Pendlum wrote: Here is what should happen on the axi stream bus to the crossbar. You should first see the

Re: [USRP-users] timout issue on RFNoC output

2017-07-21 Thread Jonathon Pendlum via USRP-users
Hey Jason, Here is what should happen on the axi stream bus to the crossbar. You should first see the header on o_tdata with o_tvalid asserted. After a few clock cycles, depending on how long arbitration takes, you should see o_tready assert. Are you seeing that sequence? Jonathon On Fri, Jul 21

[USRP-users] timout issue on RFNoC output

2017-07-21 Thread Jason Matusiak via USRP-users
I am still struggling with my "output only" RFNoC block and can't seem to figure out what silly thing I am doing wrong. I am generating data by reading from a ROM and can see it happening by monitoring the o_tdata (etc) lines coming from my lower module. If I look in my noc_block_dataGenerator