I found some postings about the issue on the internet at different
other places, but I can't remember anymore, where it was. Many
repliers stated, that it's caused by hardware or cabling. In my case,
when the USB cable is too long, the issue occured. But it also occured
on some specific devices
update information
4.1.0-rc7-bone7, use usb webcam logitech c920 to take pictures.
Babble interrupt issues still exist..
The following is the part of dmesg while having the issue
[ 349.815873] musb-hdrc musb-hdrc.1.auto: Babble
[ 349.820659] musb-hdrc: setup fifo_mode 4
[ 349.820706]
Hi there.
My experience is different, namely that power on the hub is not essential
to alleviate babble interrupts. I've seen lots of babble using a specific
device (GNS-5890 ADS-B receiver from
http://www.gns-gmbh.com/index.php?id=238L=1) when hooked up directly to
the BBB USB host port,
Anyone know about the patch referenced here? Or any other workaround to make
USB usable on BBB?
http://comments.gmane.org/gmane.linux.usb.general/87138
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
I've seen the babble interrupt on all of the kernels I have tried. 3.8,
3.12, and 3.14. I have also seen a lot of vbus errors during the boot
process. Could the heart of the problem be the fact that the power filter
capacitor is of lower capacitance than is recommended by the USB 2.0 spec?
--
Do you by any chance know in what revision the babble interrupt problem was
fixed? Was it only fixed in 3.12 or also in other trees (e.g. 3.8)?
Op dinsdag 13 mei 2014 17:19:42 UTC+2 schreef cody:
What version of the 3.12 kernel do you have? The latest version of the
3.12 kernel should have
Hi!
I'm having this same issue with my BeagleBone Black. I have an USB
keyboard connected direct on the beagle's usb port and I'm using ubuntu
13.04 with kernel 3.12.
After some random amount of time, the keyboard stop working and the only
thing I see on dmesg is:
CAUTION: musb: Babble
My kernel is:
3.12.3-00082-g6cf1f10-dirty
I tried kernel 3.13 and 3.14 but they didn't worked for me because I need
capemanager.
Thanks
Em terça-feira, 13 de maio de 2014 12h19min42s UTC-3, cody escreveu:
What version of the 3.12 kernel do you have? The latest version of the
3.12 kernel
On Tue, May 13, 2014 at 11:38 AM, Renato Riolino
renato.neocor...@gmail.com wrote:
My kernel is:
3.12.3-00082-g6cf1f10-dirty
I tried kernel 3.13 and 3.14 but they didn't worked for me because I need
capemanager.
No one is really support the capemgr in v3.12.x, nor does it really work.
Very strange, because I have capemanager working here:
ubuntu@arm:~$ uname -a
Linux arm 3.12.3-00082-g6cf1f10-dirty #1 SMP Fri Dec 6 11:44:27 BRST 2013
armv7l armv7l armv7l GNU/Linux
ubuntu@arm:~$ cat /sys/devices/bone_capemgr.6/slots
0: 54:PF---
1: 55:PF---
2: 56:PF---
3: 57:PF---
5:
On Tue, May 13, 2014 at 12:06 PM, Renato Riolino
renato.neocor...@gmail.com wrote:
Very strange, because I have capemanager working here:
It works fine with the usarts, but lcd/spi/pwm it blows up pretty quickly..
If all you need is the usarts, we have a custom dtb for v3.14.x for you.
I use a LCD connected via gpio ( setting the gpio pins thru /sys/class/gpio
) and a DS1307 realtime clock via i2c.
Do they work too on kernel 3.14? Could you point me to the 3.14 kernel and
the custom dtb for usart? I need all usarts availables and UART1 needs to
be 485.
[]'s
Renato
Em
On Tue, May 13, 2014 at 12:20 PM, Renato Riolino
renato.neocor...@gmail.com wrote:
I use a LCD connected via gpio ( setting the gpio pins thru /sys/class/gpio
) and a DS1307 realtime clock via i2c.
Do they work too on kernel 3.14? Could you point me to the 3.14 kernel and
the custom dtb for
Ulf, does your kernel patch interrupt data streams? In other words, for
example, if I'm running a webcam and I hotplug another device, will data
transfers from the webcam be affected?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are
The following codes can workaround that...
#!/bin/sh
echo on /sys/bus/usb/devices/usb1/power/control
while [ 1 ]; do
cat /dev/bus/usb/001/001 /dev/null
sleep 5
cat /dev/bus/usb/001/002 /dev/null
sleep 5
done
On Saturday, August 31, 2013 11:42:09 PM UTC+8, jez...@gmail.com
I am getting this same issue on my new BBB running ubuntu saucy 13.10. My
FTDI peripheral loads up and works fine for ahile, but then the babble
interrupt inevitably comes, and nothing I do can allow the system to
recover. Is there anything I can change to be able to recover from this
Den tisdagen den 24:e december 2013 kl. 01:03:16 UTC+1 skrev Brent:
Ok, got it. I need to contribute to try it out. Here is my problem, and I
would like to hear if this solves it. I have a hub that uses the SMSC 2512
hub chip (USB2512QFN36). Mass storage devices work as long as it's
On Dec 24, 2013 2:04 AM, APRichelieu aprichel...@gmail.com wrote:
Den tisdagen den 24:e december 2013 kl. 01:03:16 UTC+1 skrev Brent:
Ok, got it. I need to contribute to try it out. Here is my problem,
and I would like to hear if this solves it. I have a hub that uses the
SMSC 2512 hub chip
Den tisdagen den 24:e december 2013 kl. 14:18:26 UTC+1 skrev RobertCNelson:
On Dec 24, 2013 2:04 AM, APRichelieu apric...@gmail.com wrote:
Den tisdagen den 24:e december 2013 kl. 01:03:16 UTC+1 skrev Brent:
Ok, got it. I need to contribute to try it out. Here is my problem, and
Den tisdagen den 24:e december 2013 kl. 17:42:02 UTC+1 skrev Brent:
I don't have any problem with your hourly rate, but I'm not confident your
patched kernel will fix my problem. Here's why... I bought the SMSC
evaluation kit for the 2512 chip that supports two downstream ports. I plug
it
Where do I go to get Ulf's kernel? I would like to test but I don't know
where to look. Is there a patch somewhere that I missed?
On Monday, December 9, 2013 5:57:56 PM UTC-5, bko...@scanimetrics.com wrote:
I've also put in $125 and must say that I haven't had any troubles since
using
Den måndagen den 23:e december 2013 kl. 20:26:20 UTC+1 skrev Brent:
Where do I go to get Ulf's kernel? I would like to test but I don't know
where to look. Is there a patch somewhere that I missed?
Check The http://igg.me link in your post.
On Monday, December 9, 2013 5:57:56 PM UTC-5,
Ok, got it. I need to contribute to try it out. Here is my problem, and I
would like to hear if this solves it. I have a hub that uses the SMSC 2512
hub chip (USB2512QFN36). Mass storage devices work as long as it's
inserted at power up. Any hot plugging after boot will not work. Does
your
I've also put in $125 and must say that I haven't had any troubles since
using Ulf's kernel.
Thanks Ulf
On Monday, December 2, 2013 1:53:39 PM UTC-7, Philippe Laurent wrote:
I've ponied up for the $125 donation. Gotta have this running right.
On Mon, Dec 2, 2013 at 7:23 AM, APRichelieu
Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev
jez...@gmail.com:
I'm using my Beaglebone Black with a USB temperature sensor. It works very
well, however I noticed monitoring stopped last night after roughly 35 days
uptime. This morning I looked more closely into the log file
I've ponied up for the $125 donation. Gotta have this running right.
On Mon, Dec 2, 2013 at 7:23 AM, APRichelieu aprichel...@gmail.com wrote:
Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev
jez...@gmail.com:
I'm using my Beaglebone Black with a USB temperature sensor. It works
I have two thumb drives same manufacture, different models. One drive I
can insert and it mounts just fine with a udev rule. I can take that drive
in and out as many times as I like and it always mounts and unmounts. The
other drive will lock up the Host, I can reset it by reading
Ulf, many thanks for the mention. If I hit the last brick wall, I'll hire
you to make the fix available.
Meanwhile, some interesting developments. Curious about the grounding
conversation, I removed the BBB from the metal case in which it was
enclosed, and placed it on a non-conductive mat.
Den lördagen den 31:e augusti 2013 kl. 17:42:09 UTC+2 skrev jez...@gmail.com:
I'm using my Beaglebone Black with a USB temperature sensor. It works very
well, however I noticed monitoring stopped last night after roughly 35 days
uptime. This morning I looked more closely into the log file and
Bummer, despite all of the research, the musb: Babble Interrrupt issue
continues to plague. In the hopes that there's a hardware dev out there
listening. The board I'm using is A5C.
On Saturday, August 31, 2013 11:42:09 AM UTC-4, jez...@gmail.com wrote:
I'm using my Beaglebone Black with a
In my case I have a cape that connects via USB (besides the usual headers).
And I have a TP on VBUS, sometimes just inserting a tester on the test
point generates a Babble Interrupt.
Mine isn't properly grounded.
You can always check the governor and cpu frequency with:
juanjo@balin:~$ cat
A few more updates. I've read in a number of other locations that this
might be due to a grounding issue or a power draw issue. Starting with
tackling the power draw issue, it appears that the system bus outputs
different power to the USB device depending on its CPU throttling status.
The
Crap. On third reboot (full power off/on), the device is experiencing the
same musb: Babble Interrupt error as before.
So... this is a hardware issue? The BBB is powered by a separate adapter
(not USB), so power shouldn't be the problem.
On Friday, November 1, 2013 1:13:09 PM UTC-4, Philippe
Same problem here. Im also willing to pay for a solution
Am Samstag, 31. August 2013 17:42:09 UTC+2 schrieb jez...@gmail.com:
I'm using my Beaglebone Black with a USB temperature sensor. It works very
well, however I noticed monitoring stopped last night after roughly 35 days
uptime. This
Ditto here, application/solutions developer skills, not driver/kernel stuff.
This 'CAUTION: musb: Babble Interrupt Occurred' error is an unfortunate
deal-breaker for me, and that's a real shame considering that we were going
to deploy ~28+ of these for our factory automation needs. The
I've got the same 'CAUTION: musb: Babble Interrupt Occurred' error in
dmesg. Running the latest Angstrom on the Black with a Symbol DS457
attached.
On Thursday, October 24, 2013 2:17:01 AM UTC-4, Rune wrote:
That's what I'm running, so then maybe that's not the answer :)
Any other ideas as
Not surprised. I've had all sorts of problems with USB when using a hub
chip. It all seems to point to a software/driver glitch. I really wish I
could help out to fix it, but I'm more of an application developer.
On Oct 28, 2013 8:33 PM, p...@ideos.com wrote:
I've got the same 'CAUTION: musb:
That's what I'm running, so then maybe that's not the answer :)
Any other ideas as to why the USB drops out?
Regards,
Rune
On Thursday, 24 October 2013 00:05:01 UTC+2, RobertCNelson wrote:
On Wed, Oct 23, 2013 at 5:01 PM, Rune B. Kalleberg
gre...@gmail.comjavascript:
wrote:
Have you
Have you confirmed that this patch works? I'm running Debian Wheezy and
getting the same issue myself. Wifi dongle drops out and will not come back
up unless i power cycle.
Would this kernel fix work with Debian? Or just Anstrom?
I often get another message as well:
[92458.978265] CAUTION:
On Wed, Oct 23, 2013 at 5:01 PM, Rune B. Kalleberg greb...@gmail.com wrote:
Have you confirmed that this patch works?
That patch was first enabled with the 3.8.13-bone28 release..
I'm running Debian Wheezy and
getting the same issue myself. Wifi dongle drops out and will not come back
up
40 matches
Mail list logo
