Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BladeRF USB crashes on Beaglebone Black, Ubuntu 14.04 #320

Closed
vanushv opened this issue Aug 29, 2014 · 4 comments
Closed

BladeRF USB crashes on Beaglebone Black, Ubuntu 14.04 #320

vanushv opened this issue Aug 29, 2014 · 4 comments
Labels
Resolve: Invalid Reported issue is not valid

Comments

@vanushv
Copy link

vanushv commented Aug 29, 2014

OS: Ubuntu 14.04, on Beaglebone black. Using latest gr-osmosdr, FPGA and firmware.

With a simple gnuradio flowgraph (bladeRF source -> null sink, null sink -> bladeRF sink), the bladeRF crashes and is unable to be accessed except on reboot.

The flowgraph is started, then stopped after 5 seconds.

https://gist.github.com/vanushv/69a84637d4ea631d3dc5

@jynik
Copy link
Contributor

jynik commented Aug 29, 2014

I've found that some of the USB controllers on embedded platforms aren't able to supply ample current to the device, resulting in strange failures when enabling various modules on the device (e.g., PLLs).

Could you verify if this crash persists when you power the device vi the DC barrel jack with a +5 DC source, as opposed to powering through the USB connection? I'd recommend a power source rated to at least 1.5A, just to err on the side of caution.

Note that when doing this, you'll have move the two jumpers on J70. See the Jumpered power selection DC barrel vs USB3 bus section of the schematic, or ask here or on the forums if you're unclear on this.

@vanushv
Copy link
Author

vanushv commented Aug 30, 2014

I'll try this and get back to you.

@jynik
Copy link
Contributor

jynik commented Sep 29, 2014

@vanushv, any updates on this?

@jynik
Copy link
Contributor

jynik commented Oct 28, 2014

Since I haven't heard back on this, I'm going to close this issue. If the problem persists and you have more information, you may re-open it.

@jynik jynik closed this as completed Oct 28, 2014
@jynik jynik added the Resolve: Invalid Reported issue is not valid label Oct 31, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolve: Invalid Reported issue is not valid
Projects
None yet
Development

No branches or pull requests

2 participants