That's interesting ... so what firmware and kernel are you using?redhawk wrote:Despite the reported problems with Bluetooth audio I'm not experiencing any lockups or loss of Ethernet connectivity.
I also think there is a flaw in Raspbian it's not taking the device offline but rather not bothering to initialise the dongle's parameters during the booting process.
I wrote a simple script to fix this i.e. dongle name, class, pmode, imode and now my Bluetooth headset can auto-connect without any fiddling.
The person who has been employed full time since the start of 2013 to fix the USB problem(s) will be ever so pleased to know that he has been wasting his time.rajeshm wrote:After extensive debugging I have come to the conclusion that all keyboard and other USB peripheral related problems have to do with the power supply.
rajeshm wrote:After extensive debugging I have come to the conclusion that all keyboard and other USB peripheral related problems have to do with the power supply. My guess is that the supply to the USB related circuitry is borderline and any drop at all anywhere along the path is enough to cause the board to stop responding to the USB peripherals. This problem is bad enough that with a good adapter (Apple iPad charger), a nice thick USB wire connecting the charger to the Pi but with the charger plugged into an overloaded socket at the end of a long extension cord (don't try this at home, folks) caused the Pi to stop responding to the keyboard. But when I plugged the charger directly into the wall socket, the keyboard was just fine. Note that even when the keyboard does not respond, the network connection works just fine and you can ssh to the Pi and see that everything else works as intended.
So the solution is to make sure that the supply is as good as you can make it. Exchanging the Pi for another one is probably not going to help much. They should fix this problem on the next rev of the Board.
Correct. But if you want to get simple peripherals like keyboards and mice to work, and your only other option is to return the Pi, improve the power supply and there's a very good chance you can get things to work.1) Power supply problems only add to USB issues, eliminating problems with power quality does not eliminate the remaining problems with USB device interaction (of which there are still many).
This was not a test method. LOL. My keyboard had worked a couple of times and then suddenly stopped working even if I tried all the other things that were mentioned elsewhere. I was going to return it but wanted to make a last-ditch effort to get it to work and started thinking back about the times it had worked. And I was exaggerating about how overloaded the socket is. It's probably drawing 12A from a typical wall socket. But the extension cable is pretty crappy so I think there's a drop of a few volts at the end. But I also have a cable modem, a DSL modem. a router and a VoIP phone adapter also running off the same supply at the same point as the Pi and everything else works. So the problem is with the Pi is that it's tolerance to supply variations is much worse than than normal caused by a less-than-robust board design and/or manufacturing problems.2) Your method of test is flawed - the Apple charger described is rated at 100-240Vac input. In any country, if you overloaded an extension lead to the point where the point-of-use voltage was less than 100V, you'd better have a fire extinguisher handy.
I dont' think the problem is with the USB "blob". There surely are software problems but I'm quite convinced that there are supply related hardware problems on the board. Otherwise, it's impossible for something to work with a higher supply when it's non-functional with a lower one. It should be fairly easy for them to get failing test vectors, generate shmoo plots and probe the board and isolate the cause of the failure.3) The core processor on the Pi is the BCM2835. The USB blob within this processor is unlikely to be changed with a new revision of the Pi, as it would require changing the CPU, which would require re-porting linux to the system. As of the rev 2 model B, there are very few hardware issues remaining that would warrant a board artwork/schematic change.
Hopefully. gsh is working on it. There is a possibility that some issues may be unfixable, but we think that's unlikely.MastaG wrote:So will there be fixes for high speed isochronous usb devices like webcams/dvb-tuners etc?
Or will it never be possible to use isoc usb transfers without forcing usb 1.1?
Isoc transfers behave quite wierdly on the Pi. I have found that it is wholly dependent on the transfer size and numbers of packets per transfer - I have a webcam that works flawlessly at only one setting, which corresponds to a specific transfer size of 1x768 bytes. All other settings either produce garbled packets or empty packets. It appears that USB1.1 doesn't make much difference (in my case), but forcing USB1.1 in other cases will mandate changing the transfer size that the device uses - which may improve things.MastaG wrote:So will there be fixes for high speed isochronous usb devices like webcams/dvb-tuners etc?
Or will it never be possible to use isoc usb transfers without forcing usb 1.1?
Untrue. The only blob baked into the CPU is the SD boot-loader. Everything else is in the /boot partition of the SD card.M33P wrote:The USB blob within this processor is unlikely to be changed with a new revision of the Pi, as it would require changing the CPU, which would require re-porting linux to the system.
The "blob" I am referring to is the "IP core" integrated into the BCM2835. This was (licensed/purchased) from Synopsys, which usually takes the form of a pile of hardware description language which eventually integrates into the silicon. While Broadcom most likely modified parts of it to glue it into the particular processor, you can be sure that the major internals are untouched. Thus, it's a vendor blob.rurwin wrote:Untrue. The only blob baked into the CPU is the SD boot-loader. Everything else is in the /boot partition of the SD card.M33P wrote:The USB blob within this processor is unlikely to be changed with a new revision of the Pi, as it would require changing the CPU, which would require re-porting linux to the system.
Pluggy is referring to the Roku not XBMC just so you know And to be fair, it's the only other thing that we're aware of which does necessarily mean it's the only thing that there is. B-com tends to be tight lipped about this sort of stuffpluggy wrote: The only other thing it is used in is a telly media player and that is with proprietary software.
As far as I can remember I imported the (then) current kernel options, so if it's missing some functionality it means it wasn't there in my system in the first place.Doobster wrote:I installed your Kernel, but I wonder if you compiled your kernel without RAID support.
Just a FYI, I believe the Roku2 using the 2835 uses Linux, on which they run a custom application.pluggy wrote:The power and software issues on the Pi's USB are real and are separate issues but noobs often can't tell the difference. The USB power problems are often overstated on here because few people have actually measured how much current their peripherals actually consume. Its nice and convenient to blame the excessive power draw of peripherals. I've measured most of my USB stuff (Self employed computer bod - I tend to collect junk so have quite a few keyboards, mice, cameras etc ) and very little of it would worry a 100mA supply. For example only one of my keyboards pulls more than single figure milliamps - A Microsoft Sidewinder X4 which draws 55mA with the backlighting full up. Most of my mice (all wired optical) use between 10 and 20mA, an old ball mouse I have uses less. My two wifi adaptors consume about 30mA at the low traffic and strong signals I use them at. They will probably use more with very weak signals and/or high traffic. The odd peripherals I have which actually mention power consumption always overstate the case, often by an order of magnitude. I have the means to feed Pis with power via GPIO (takes the F3 polyfuse out of the equation) and have no difficulty getting a solid 5.1 volts into the Pi.
The USB software issues are real, are being worked on and hopefully will improve in the future. They have improved a lot since the Pi was first launched. Using a powered hub will often cause more problems than it solves. (another USB peripheral for the Pi's interface to trip up on). Part of the problem I believe is that the Broadcom BCM2835 wasn't envisaged to ever be a USB host. The only other thing it is used in is a telly media player and that is with proprietary software.
Users browsing this forum: uzierek and 50 guests