Search found 455 matches

by jynik
Thu Jun 16, 2016 11:37 am
Forum: Troubleshooting
Topic: bladeRF in GRC Windows?
Replies: 2
Views: 9421

Re: bladeRF in GRC Windows?

Whoops -- forgot an important link. You can find more information about the bladeRF-specific osmocom block device arguments here:

http://sdr.osmocom.org/trac/wiki/GrOsmo ... SourceSink
by jynik
Thu Jun 16, 2016 11:35 am
Forum: Troubleshooting
Topic: bladeRF in GRC Windows?
Replies: 2
Views: 9421

Re: bladeRF in GRC Windows?

Could you kindly share the output of the bladeRF-cli "info" and "version" commands? While not directly related, your two issues indicate a common element of using the Cypress driver backend. I have found that the bladeRF.dll that ships with GNU Radio does not include the Cypress backend support, whi...
by jynik
Thu Jun 16, 2016 11:29 am
Forum: Troubleshooting
Topic: Simulink hangs when transmitting
Replies: 1
Views: 7737

Re: Simulink hangs when transmitting

I've recently been hearing reports of TX hanging/crashing when using the Cypress driver backend lately and am trying to find some time to look into this. A workaround for the time being is to use the libusb backend in Windows. Are you using the Cypress backend? If so, could you try switching to the ...
by jynik
Thu Jun 16, 2016 11:17 am
Forum: Troubleshooting
Topic: NULL pointer passed to sync_rx issue
Replies: 3
Views: 11978

Re: NULL pointer passed to sync_rx issue

The code that prints that NULL pointer message may be found here . This implies to me that the code calling bladerf_sync_rx is passing a NULL buffer or has called bladerf_sync_config before attempting to start calling the RX function. Try setting a break point in the line of code I linked, and getti...
by jynik
Wed Jun 15, 2016 11:37 am
Forum: Tutorials and Examples
Topic: no need to panic while updated to firmware 2.0.0
Replies: 3
Views: 17594

Re: no need to panic while updated to firmware 2.0.0

Thanks for sharing peekli! The 2.0.0 series of firmware migrates to the new VID we will be using in the future on the bladeRF and any future devices. As noted on the firmware download page, this required libbladeRF v1.6.0 or later. If you ever run into trouble with firmware, you can always use the b...
by jynik
Tue Jun 14, 2016 3:27 pm
Forum: Troubleshooting
Topic: load fpga hostedx115.rbf succesful but " FPGA size UNKNOWN
Replies: 5
Views: 16474

Re: load fpga hostedx115.rbf succesful but " FPGA size UNKNO

Hi Kees,

Kudos to you for keeping good notes! :)

Yes, the factory calibration should still be quite good. Use 0x9a5d in that flash_init_cal command:

Code: Select all

flash_init_cal 115 0x9a5d
by jynik
Tue Jun 14, 2016 9:35 am
Forum: Digital Signal Processing
Topic: GPS simulating
Replies: 8
Views: 33599

Re: GPS simulating

Those calibration results are very good. The "error" quantifies how many DAC/ADC counts offset from 0 the result is. The possible range is [-2048, 2047]. Thus, less than 1 is good and no further correction is possible within the device itself. Just curious, is your mobile under test in "Airplane Mod...
by jynik
Tue Jun 14, 2016 9:32 am
Forum: Software development
Topic: Question about ADS-B setup mentioned in blog
Replies: 1
Views: 9394

Re: Question about ADS-B setup mentioned in blog

I believe that is the Altera Edition of ModelSim.

I'm assuming that this is showing data captured with the bladeRF-cli being run through a simulation of the ADSB core.
by jynik
Tue Jun 14, 2016 9:28 am
Forum: Troubleshooting
Topic: load fpga hostedx115.rbf succesful but " FPGA size UNKNOWN
Replies: 5
Views: 16474

Re: load fpga hostedx115.rbf succesful but " FPGA size UNKNO

Based upon your VCTCXO DAC calibration being the "default" and the unknown FPGA size, it seems like you've wiped out your flash at some point. You can run the following in the bladeRF-cli to reflash this information. You will need to power-cycle after completing this command and exiting the CLI. fla...
by jynik
Tue Jun 14, 2016 9:21 am
Forum: Troubleshooting
Topic: LIBUSB_ERROR_NO_DEVICE
Replies: 3
Views: 11502

Re: LIBUSB_ERROR_NO_DEVICE

You noted this happens after 1 hour -- does this duration correspond to any power save settings on the machine? I have seen similar issues like this when my machine went to sleep or into some lower power state. Turning off the low-power standby modes when I was performing long-running tests addresse...