>
> Hi,
>
> I've been playing around with Sakoman's precompiled kernel and rootfs
> and it all works fine.
What about the angstrom rootfs and kernels? I have no problems with
big USB transfers there. The 2.6.29 OE builds is working quite well,
but it heavily patches usb.
regards,
Koen
> The 2.6.29 OE builds is working quite well, but it heavily
> patches usb.
From the thread title it appears he is using ehci, so I don't think
that the musb patches matter in this case :-)
I too see no issues with large file transfers, so something else is
going on here.
Steve
I have such a mini A/A cable and a rev C. I can test if you tell me
how you can successfully cause the stress which results in a
disconnect.
Guylhem
Voltage drops of 0.02V wouldn't concern me. The voltage of 4.82V is a bit
low, but as well not scaring. I guess, that the reason why the voltage
increase after the error is, that the hub stops drawing current => Voltage
increases to unloaded level ~4.9V (ideal 5V)...
In case DMM is a Digital Multi Meter I'm afraid, you can't catch/see what
I'm searching for, since they normally contains some kind of low-pass filter
and thereby won't show spikes where the voltage might i.e. drop or rise
drastically (several volts) due to some kind of yet unknown reason... Can
you gain access to an oscilloscope?
As stated previously I have no arguments, that this should actually be the
case, but would just like to rule out this possibility completely since it
seems to be some kind of HW related issue since not everybody is
experiencing this problem... :-)
I myself unfortunately don't have a Rev C board for testing/measuring
myself...
Looking at the Rev C schematics, I see that the V_BUS cap is 100uf,
which should be just fine.
It will still be interesting to see what you find using a scope.
Perhaps the issue is the power source for your Beagle.
Steve
Agree there shouldn't be any glitches when the system is up running. We
however didn't knew this was the case for sure for the failing boards- There
might had been some kind of strange HW problem. But thanks to Eelcor
measurements today we can now totally rule out this possibility... :-)
> Since multiple Beaglers have seen the same problem, I would suspect a
> subtle race condition in the Host USB driver. Any time you have
> interrupt-driven software you have to be very careful with all shared
> variables. This is particularly nasty with a RISC processor where
> incrementing a variable that's in memory is usually not an atomic
> operation: it's a LOAD + register ADD + STORE. If an interrupt occurs
> between the LOAD and STORE and the interrupt service routine modifies
> the same variable, you end up with an inconsistent result. This is
> incredibly hard to reproduce since the chance of observing it in
> normal operation is tiny. However, if you exercise the driver with a
> long transfer, your chance of observing the hazard becomes
> significant.
Hi John,
I agree that ISR's and shared variables can cause trouble :-). I although
don't expect this to be the main reason in this case. Main reason for this
is, that Eelcor can provoke the error every time within few minutes (1 or 2
minutes - Right?), while Steve have tried for several hours with no luck at
all. I my world this points in the direction of a somehow HW related
problem...
In order to be 100% sure if it's a pure SW problem or not, I would suggest
Eelcor to write a 100% step by step description of what to do in order to
provoke the error. Including full path to images, MMC card type/size, USB
hub name, U-boot and x-loader version, etc... We need to 100% dummy step by
step guide to be 100% sure, that everybody is testing the *exact* same use
case...
Then other people can redo the exact same steps and see if they can provoke
the problem. In this case, I agree it's most likely a pure SW error. In case
they still can't provoke it, I suspect some kind of HW dependency to be
involved as well...
Best regards
Søren
Just realized, that the V_BUS is basically directly connected (through a
switch) to the DC_5V net. =>
The difference from 4.9 to 5.04V can most likely be tracked all the way back
to the power supply supplying the board...
> Eelcor wrote:
> Other suggestions for measurement points?
One far guess for another measuring point is: RBIAS on R52.
As far as I can read it's supposed to be 0.8V during normal operation.
A other idea could be to try to check the VBAT and VIO_1V8 near to the balls
C1 and B3 of the USB transceiver (USB3322). Alternatively - Try to increase
C104 and C106 to 10uF each...
Try to disconnect kbd and mouse and see if that helps. (if you have
serial, you can use serial to connect, if not start an ssh session to
your beagle).
For me mouse is working but kbd is not (although once I managed to get
it working, but could not reproduce that).
I think this is a driver issue somewhere.
usb on beagle still has some issues (see an earlier post from me).
FM
This could indicate that the quality of the power supply of the hub is
an important factor.
A thing to try is to cascade two powered hubs and use the 2nd one.
Assumption for this test is that the first hub will dampen power
transients that one way or another occur on the input of the 2nd hub.
FM.