Hi,
I have following issue:
We changed our PC platform to Intel NUC, running with Ubuntu 14.04.
BladeRF is USB3.0 powered. (But same behaviour when taking 5V power from SATA connector).
Depending on last BIOS powerstate, FPGA is loaded or (mostly) not.
FX3 driver is loaded correctly all the time (tested with 1.6.1 and 1.7.0).
In case of "not loaded" bladeRF-cli can not load the FPGA manually -> timeout.
When I disconnect and reconnect the USB cable everything is okay.
Is there any other possibility to force a "FPGA-Reload"?
Before changing the PC we had this trouble only after resuming from hibernate, but not at 1st power-up.
Regards,
Andreas
PowerUp problem
-
- Posts: 9
- Joined: Fri Apr 04, 2014 4:19 am
Re: PowerUp problem
Hi.
I have done some investigations.
It does not help to reset the bladerf-usb-port (unbind/bind).
I have more success with this, when FPGA is not loaded after powerup:
bladeRF-cli
jump_to_boot
recover <bus><addr><fx3-firmware>
open
But I don't believe that this is a good solution to reconfigure FPGA.
I have done some investigations.
It does not help to reset the bladerf-usb-port (unbind/bind).
I have more success with this, when FPGA is not loaded after powerup:
bladeRF-cli
jump_to_boot
recover <bus><addr><fx3-firmware>
open
But I don't believe that this is a good solution to reconfigure FPGA.
-
- Posts: 9
- Joined: Fri Apr 04, 2014 4:19 am
Re: PowerUp problem
I think FX3-command
CyU3PDeviceReset(CyFalse);
is responsible for reloading the FPGA:
Would be nice, if someone could implement a fpga-reload-target to bladeRF-cli
CyU3PDeviceReset(CyFalse);
is responsible for reloading the FPGA:
Would be nice, if someone could implement a fpga-reload-target to bladeRF-cli
-
- Posts: 30
- Joined: Fri Mar 01, 2013 6:49 am
Re: PowerUp problem
When you say FX3 driver is loaded, do you mean the this one if so you should unload it, it's not being actively maintained and will not work as well as the standard libusb backend.
-
- Posts: 9
- Joined: Fri Apr 04, 2014 4:19 am
Re: PowerUp problem
I followed this guide: https://github.com/Nuand/bladeRF/wiki/G ... rom_source.
Imho only libusb should be involved.
What I have recognized:
GRUB is installed to manage different linux distributions.
In case of FPGA is not loaded, this status is already present when seeing the selection-screen, waiting for my choice.
When I do an usb-reconnect-cycle while grub is waiting, fpga is loaded correctly.
As I wrote before, our bladeRF is USB-powered.
Could it be, that the Bios limits the current during booting?
lsusb -v shows me a MaxPower of 200mA. Is this sufficient?
Imho only libusb should be involved.
Code: Select all
bladerf@bladerf-nuc:~$ bladeRF-cli -i
bladeRF> info
Serial #: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
VCTCXO DAC calibration: 0x9b23
FPGA size: 115 KLE
FPGA loaded: no
USB bus: 3
USB address: 2
USB speed: SuperSpeed
Backend: libusb
Instance: 0
bladeRF> version
bladeRF-cli version: 0.11.0-git-3a30c49
libbladeRF version: 0.16.0-git-3a30c49
Firmware version: 1.7.0-git-ee89b79
FPGA version: Unknown (FPGA not loaded)
GRUB is installed to manage different linux distributions.
In case of FPGA is not loaded, this status is already present when seeing the selection-screen, waiting for my choice.
When I do an usb-reconnect-cycle while grub is waiting, fpga is loaded correctly.
As I wrote before, our bladeRF is USB-powered.
Could it be, that the Bios limits the current during booting?
lsusb -v shows me a MaxPower of 200mA. Is this sufficient?
Code: Select all
....
iManufacturer 1 Nuand
iProduct 2 bladeRF
iSerial 3 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 123
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 200mA
.....