Re: [USRP-users] RFNoC not re-tuning consistently

2019-10-01 Thread Jason Matusiak via USRP-users
OK, I think I found the issue. I am not sure what was causing things to sometimes work vs other times, but it seems to be the difference. I pulled up an example RFNoC flowgraph and it didn't have any issues. So then I started stripping things out and trying to compare things. The only real

Re: [USRP-users] RFNoC not re-tuning consistently

2019-10-01 Thread Jason Matusiak via USRP-users
Marcus, I am not 100% sure I understand what you mean, but I am not sure why anything would need to be done differently (and in the past I feel like I had no issues). They certainly don't talk about anything needed to be modified here:

Re: [USRP-users] RFNoC not re-tuning consistently

2019-10-01 Thread Marcus D Leech via USRP-users
I wonder if this is just because in RFNoC the DDC is explicitly visible, so you have to program it to account for synthesizer step size? Sent from my iPhone > On Oct 1, 2019, at 12:52 PM, Jason Matusiak via USRP-users > wrote: > > I have an issue that is very odd to me. I have tried two

[USRP-users] RFNoC not re-tuning consistently

2019-10-01 Thread Jason Matusiak via USRP-users
I have an issue that is very odd to me. I have tried two different X310s with different daughter cards and they are all exhibiting this behavior. It feels like I am doing something stupid, but I can't quite figure out what. (a picture is attached) If I have a usrp source connected to a freq

Re: [USRP-users] One sample - 5 ns delay between the two RF signals/ X310

2019-10-01 Thread Daniel Jepson via USRP-users
Fabian, I had a hunch it was just the 3.3V part--thanks for clarifying! Cherif, the DAC interface timing (and for that matter, the ADC timing) should be fairly tight. What you're seeing is expected and matches the numbers we designed it to. The FPGA constraints are intentionally tight to provide

[USRP-users] [UHD] 3.14.1.1 Release Announcement

2019-10-01 Thread Michael West via USRP-users
UHD 3.14.1.1 is now available! This is a patch release. It is API compatible with 3.14.0.0 and ABI compatible with 3.14.1.0. This release includes several bug fixes. Installers for Windows and Fedora are available here: http://files.ettus.com/binaries/uhd/uhd_003.014.001.001-release/ The PPA

[USRP-users] uhd_usrp_loader script defaults firmware to pre-built bin file

2019-10-01 Thread Francesco Restuccia via USRP-users
Hi Marcus, This is the output of the command: frank@frank-iMac:~$ which uhd_image_loader /opt/uhd_gnuradio_installs/bin/uhd_image_loader And yes, the file should be ok: frank@frank-iMac:/opt/uhd$ ls -la /opt/uhd/firmware/usrp2/build/usrp2p/usrp2p_txrx_uhd.bin -rwxr-xr-x 1 frank frank 16383

Re: [USRP-users] USRP X310 problem

2019-10-01 Thread Paolo Palana via USRP-users
Try the command. dd if=.bit of=.bit count= count=1 and then try to configure the fpga .bit On 27/09/19 16:12, Aaron Montilla via USRP-users wrote: > Hi, > I am trying to set the connection between my PC and my USRP X310. > I ran the command uhd_find_devices, and successfully it found the >

Re: [USRP-users] X310 image 8 bytes too large with default image

2019-10-01 Thread Paolo Palana via USRP-users
I had the same problem indeed, I think this is because vivado 2017.4 output image size is a bit different from the output imase size of vivado 2015.4. I say so because the error did not appear with uhd-3.10.3. I think the problem is that no one updated the tools provided with libuhd used to