Re: [USRP-users] Error when burn fpga image file into USRP X310

2017-11-09 Thread Jason Matusiak via USRP-users
Did this ever get resolved?  Because I am having the same issues now too. Hi Luis, I will follow up with you on this issue off the list, within the thread that has been sent to support at ettus.com.

Re: [USRP-users] feedback from a USRP message

2017-10-30 Thread Jason Matusiak via USRP-users
ging your GNU Radio logging settings. https://gnuradio.org/doc/doxygen/page_logger.html Regards, Derek On Mon, Oct 30, 2017 at 2:54 PM, Jason Matusiak via USRP-users mailto:usrp-users@lists.ettus.com>> wrote: Is there anyway to get feedback from a sent message command to a USRP s

[USRP-users] feedback from a USRP message

2017-10-30 Thread Jason Matusiak via USRP-users
Is there anyway to get feedback from a sent message command to a USRP source in GR?  I was sending some commands and was /pretty/ sure I was doing it right, but to know for sure I sent a bogus command, and it didn't complain (I expected to see something on the terminal).  Is there anyway to tur

[USRP-users] problem with aplay on E3xx

2017-10-26 Thread Jason Matusiak via USRP-users
Just want to use a flowgraph that was working fine on an older (load-wise) SG1 E310 system on an up-to-date SG3 E312 system and it throws up if I were to type: aplay -i to start up the app, I get: root@ettus-e3xx-sg3:~# aplay -i ALSA lib /home/balister/docker-work/jethro/jethro-test/build/

[USRP-users] RFNoC dataGenerator block not outputting to radio

2017-09-29 Thread Jason Matusiak via USRP-users
OK, I have a weird problem.  I have a block I wrote a couple of months ago that doesn't seem to be working anymore.  I don't think I've updated anything within uhd-fpga except for some patches that Jonathon sent me so that I could add the logic in that keeps blocks from blasting data before the

Re: [USRP-users] the rfnoc fifos

2017-09-29 Thread Jason Matusiak via USRP-users
via USRP-users wrote: On Wed, Sep 27, 2017 at 01:42:22PM -0400, Jason Matusiak via USRP-users wrote: OK, dumb question, but I just can't come up with a good answer.  I understand that the RFNoC FIFOs are a must if you only have one NoC block that you want to use and are using the GNURadio

[USRP-users] the rfnoc fifos

2017-09-27 Thread Jason Matusiak via USRP-users
OK, dumb question, but I just can't come up with a good answer.  I understand that the RFNoC FIFOs are a must if you only have one NoC block that you want to use and are using the GNURadio host [1].  So why do pretty much most of the examples ALWAYS have at least one, and why would I want to fi

Re: [USRP-users] Quad channel receiver operation of B210

2017-09-15 Thread Jason Matusiak via USRP-users
Sumit, There is a T/R switch between the TX/RX and RX2 ports, so you can only use one at a time for each channel. On 09/15/2017 01:17 PM, Sumit Kumar via USRP-users wrote: I asked because the TX/RX port can also be used as RX right. That's why I had the perception that all 4 ports can be used

Re: [USRP-users] problem with RFNoC block not outputting

2017-09-12 Thread Jason Matusiak via USRP-users
OK, I think that I have solved it. A vector size of 2048 seems to not work in RFNoC, no matter who wrote the block. When I dial back to 256 that seems to work. I changed my block to output a tlast every 256 samples, and data passes through fine now. Is there a way to make 2048 work in RFNoC?

Re: [USRP-users] problem with RFNoC block not outputting

2017-09-11 Thread Jason Matusiak via USRP-users
One other piece of information. It seems like I always get hung up on the same output sample, 6905860. I noticed that that is almost exactly 3372 packets of 2048 sample vectors. Is there a set number of samples that can be buffered before the system stops? I set the MTU to be 11 in the axi_

[USRP-users] problem with RFNoC block not outputting

2017-09-11 Thread Jason Matusiak via USRP-users
I have a block that I've been working on and it seems like I am missing something vital to get it to work properly. My block takes in a vector of 2048 samples and outputs 2048 samples as well. I simulated it and it passes simulation fine. But, if I look at the output as it goes to a file, no

Re: [USRP-users] Building FPGA image

2017-08-18 Thread Jason Matusiak via USRP-users
I'm glad you got it working. There are a lot of critical warnings and things of that ilk that scroll by, but as long as you don't get any errors and your project meets timing, I wouldn't worry too much about them. Happy FPGAing. On 08/18/2017 09:26 AM, Torres Figueroa, Luis Angel wrote: Hi

Re: [USRP-users] Building FPGA image

2017-08-16 Thread Jason Matusiak via USRP-users
I've done it many times. When you open it and you do a save-as of the project, make sure that you don't check the option box to copy the files over, you want to leave them in their current location. On 08/16/2017 10:15 AM, Torres Figueroa, Luis Angel via USRP-users wrote: Hi folks, Has som

Re: [USRP-users] reducing RFNoC sample rate simpler?

2017-08-10 Thread Jason Matusiak via USRP-users
rate. Everything works fine because UHD has no expectations on the line rate of the incoming data stream. On Tue, Aug 8, 2017 at 12:02 PM, Jason Matusiak via USRP-users mailto:usrp-users@lists.ettus.com>> wrote: I have an RFNoC block that is probably going to take in a vector of da

Re: [USRP-users] RFNoC:Delay block?

2017-08-08 Thread Jason Matusiak via USRP-users
Nick, I had worked on something similar (a keep m-in-n block actually), and may have oversimplified things. I kept track of how many samples I outputted and set the tlast accordingly, wouldn't that solve the "reconstituting packet boundaries" issue you mentioned? Also, I am not sure I investi

[USRP-users] reducing RFNoC sample rate simpler?

2017-08-08 Thread Jason Matusiak via USRP-users
I have an RFNoC block that is probably going to take in a vector of data (200msps off the RFNoC:Radio), sum it with some values and continue. Every X number of vectors (could be as high as 1024 times), it will output a vector of its own. This means that at 200msps, I could have a flow of data

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 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 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

[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

Re: [USRP-users] problem with RFNoC probing

2017-07-19 Thread Jason Matusiak via USRP-users
d off your block until after initialization. On Wed, Jul 19, 2017 at 9:44 AM, Jason Matusiak via USRP-users wrote: Could this have something to do with tlast?  I don't feel like it is the XML files, so I am limited to looking at the verilog, but it is pretty similar to my other blocks, so I a

Re: [USRP-users] problem with RFNoC probing

2017-07-19 Thread Jason Matusiak via USRP-users
Could this have something to do with tlast? I don't feel like it is the XML files, so I am limited to looking at the verilog, but it is pretty similar to my other blocks, so I am not sure what the problem could be. It is odd to me that the probing is enough to cause issues, I am not sure what

[USRP-users] problem with RFNoC probing

2017-07-17 Thread Jason Matusiak via USRP-users
I am not sure what is going on, but while working on my new RFNoC block, I can't probe my X310 anymore. When I do, I get this error: [INFO] [CORES] Performing timer loopback test... [ERROR] [UHD] Exception caught in safe-call. in virtual ctrl_iface_impl::~ctrl_iface_impl() at /home/jmat/rfn

Re: [USRP-users] does an RFNoC block HAVE to have an input and an output?

2017-07-14 Thread Jason Matusiak via USRP-users
15 PM, Jason Matusiak via USRP-users mailto:usrp-users@lists.ettus.com>> wrote: I have a block that I want to essentially be a source block in RFNoC (outputting data from a ROM), but when I go to probe, I get this error: RuntimeError: LookupError: Path not found in tree:

Re: [USRP-users] does an RFNoC block HAVE to have an input and an output?

2017-07-13 Thread Jason Matusiak via USRP-users
And if the below approach is allowed (a probe seems to run fine now), would that be causing the following errors when I try to run my flowgraph (RFNoC:dataGenerator -> RFNoC:FIFO -> RFNoC:Radio): [INFO] [UHD] linux; GNU C++ version 4.8.4; Boost_105400; UHD_4.0.0.rfnoc-devel-348-g

[USRP-users] does an RFNoC block HAVE to have an input and an output?

2017-07-13 Thread Jason Matusiak via USRP-users
I have a block that I want to essentially be a source block in RFNoC (outputting data from a ROM), but when I go to probe, I get this error: RuntimeError: LookupError: Path not found in tree: /mboards/0/xbar/dataGenerator_0/ports/in Is this because I set it up without sink input? Is there any

Re: [USRP-users] RFNoC timing clarification

2017-07-12 Thread Jason Matusiak via USRP-users
correction, etc. Jonathon On Wed, Jul 12, 2017 at 9:20 AM, Jason Matusiak via USRP-users mailto:usrp-users@lists.ettus.com>> wrote: I have a timing question that has me going in circles, I don't understand how the USRP timestamps work when using RFNoC. In a normal system, pa

[USRP-users] RFNoC timing clarification

2017-07-12 Thread Jason Matusiak via USRP-users
I have a timing question that has me going in circles, I don't understand how the USRP timestamps work when using RFNoC. In a normal system, packets have timestamps with them (or at least the first one does) and you can compute the time of any samples based on the timestamp, sample rate, and n

Re: [USRP-users] ERROR_CODE_BAD_PACKET

2017-07-10 Thread Jason Matusiak via USRP-users
7 PM GMT+02:00, Jason Matusiak via USRP-users wrote: I am splitting one of my RFNoC blocks into two different ones, and one of them is giving me issues. The block is essentially a keep m in n block, so I only spit out data once in a while. This worked fine when combined with

[USRP-users] ERROR_CODE_BAD_PACKET

2017-07-10 Thread Jason Matusiak via USRP-users
I am splitting one of my RFNoC blocks into two different ones, and one of them is giving me issues. The block is essentially a keep m in n block, so I only spit out data once in a while. This worked fine when combined with my other block, but now when I run it independently, it is throwing th

Re: [USRP-users] rfnoc-modtool cores

2017-07-07 Thread Jason Matusiak via USRP-users
yet, unfortunately-- Was waiting for confirmation if this approach will be supported in-tree in the future. I could put something together soon though if this would help. I'd also be interested in other good solutions, if anyone has a

Re: [USRP-users] RFNOC OOT module no longer building

2017-07-07 Thread Jason Matusiak via USRP-users
I think I solved this by blowing away everything within the testbench directory. I am not sure what happened, but this seems like the best fix for now. On 07/07/2017 12:04 PM, Jason Matusiak wrote: I added a new block to my OOT module and now when I run make from the build directory things do

[USRP-users] RFNOC OOT module no longer building

2017-07-07 Thread Jason Matusiak via USRP-users
I added a new block to my OOT module and now when I run make from the build directory things don't build properly. I source my setup_env.sh and then run make from build and see the following: -- PyBOMBS installed GNU Radio. Setting CMAKE_INSTALL_PREFIX to /home/jmat/rfnoc -- Build type not spe

[USRP-users] using VHDL modules in an RFNoC block

2017-07-06 Thread Jason Matusiak via USRP-users
I have some code from a previous coworker that I would like to take advantage of. Currently it is VHDL and their top block (which I am calling), has things like: USE WORK.TYPES.ALL; USE WORK.HARDWARE.ALL; USE WORK.MATH.ALL; USE WORK.UTIL.ALL; USE WORK.FILTERS.ALL; USE WORK.RESAMPLERS.ALL; I un

<    1   2   3