The boards will reboot if :
a) OTG is disabled in the kernel build, and
b) g_multi.ko is loaded, and
c) the usb cable is disconnected.
If you remove b) then they stay up.
This is with kernel 3.12.9
--
For more options, visit http://beagleboard.org/discuss
---
You received this message becau
The port is not an OTG port and does not support OTG functionality. It is
only a client port. The PMIC was not designed for an OTG port. It expects
to see a host port from the PC. That is why OTG probing is not in the
kernel we created for the BeagleBone Black.
Gerald
On Fri, Dec 6, 2013 at 7:5
H.
Gerald
On Fri, Nov 29, 2013 at 2:46 PM, Maxim Podbereznyy wrote:
> Hey guys!
>
> If anyone still experiences the unexpected reboot issue I've found another
> solution to avoid it: raise the pin 2 (unconnect it from a pcb pad) of
> TL5209 (soic-8 chip) and solder a wire between this pin
Hey guys!
If anyone still experiences the unexpected reboot issue I've found another
solution to avoid it: raise the pin 2 (unconnect it from a pcb pad) of
TL5209 (soic-8 chip) and solder a wire between this pin and 5V supplied
from a wall adapter. TL5209 feeds mostly the Ethernet PHY and sometime
That is not what it was for. It was to prevent a premature loss of reset
during power up.
Gerald
On Fri, Nov 22, 2013 at 12:18 AM, rod calabio wrote:
> There was a note on Beaglebone Black that the newest version BBB version
> 6 has or'd the reset button and the power button to prevent a r
There was a note on Beaglebone Black that the newest version BBB version
6 has or'd the reset button and the power button to prevent a reset, now
whether or not it is the same problem
as posted originally, ho knows. But I had the same issue where I was ssh'd
into the BBB for several hours an
Hey guys!
I'm pretty sure that this mail-list is also read by people who are invloved
into kernel development and they may be aware of why 3.8 does not reboot
and 3.2 (TI) reboots the BBB. Are they here and can surmise where the issue
is?
2013/11/20 Maxim Podbereznyy
> Ldo3 and ldo4 are not us
Ldo3 and ldo4 are not used to power any of really current- hungry unit like
the ddr3 or the cpu core.
20 нояб. 2013 г. 13:23 пользователь "Jakub Żymełka"
написал:
> On the TI product page http://www.ti.com/product/tps65217B#feature is the
> information about current limit:
>
> "Two Independent Lo
On the TI product page http://www.ti.com/product/tps65217B#feature is the
information about current limit:
"Two Independent Load Switches That Can Be Configured as LDOs
Configured as LDOs:
- LDO Output Voltage Range: 1.5 V – 3.3 V
- VIN Range: 2.7 V – 5.8 V
*- 200-mA Current Limit (TPS65217A, B)*
Can you prove it? You mean it can supply more current? :)
> But tps65217C (in BBB) has a more power availability vs. tps65217B (in
BBW).
2013/11/20 Jakub Żymełka
> Ok, I see.
> But tps65217C (in BBB) has a more power availability vs. tps65217B (in
> BBW).
> Reducing the CPU speed is not the so
Ok, I see.
But tps65217C (in BBB) has a more power availability vs. tps65217B (in BBW).
Reducing the CPU speed is not the solution. For example I would like to
work with a clock speed of 1GHz.
So, are You suggesting that the PMIC is incorrect?
Can anyone else give an opinion? Maybe the designers
Jakub, answering to your question:
tps65217b is not tps65217b (bbb)
Bbw 600mhz vs bbb 1000mhz
Ddr2 pwr consumption != ddr3
That is why when people reduce the cpu freq systems become stable, but I
don't think it can help because I run my board in cpu ondemand governor and
it still reboots. However
Lei Wang,
yes, You can just use a wire to connect SYS_5V and VDD_5V after boot up.
We've done this before we choose the option with the transistor.
We are working on the 04.2013 U-boot, so we will try the newest version
10.2013 and I will let you know about my results.
lisarden,
According to yo
this issue can probably be because tps65217 simply can't handle too much
current through a single pin. If an internal switch AC|USB=SYS get
overheated then it can just shutdown to avoid a system damage
2013/11/19 Lei Wang
> The time jumping issue seems to relate to u-boot per Robert Nelson's
>
The time jumping issue seems to relate to u-boot per Robert Nelson's
suggestion (
https://groups.google.com/forum/#!category-topic/beagleboard/beaglebone-black/xPxzYyNsA78).
I dropped in a newer u-boot images. It seems to fix the problem.
For the random reboots, I limited the CPU clock frequenc
My BBB is A5C version. We've tested more than 10 pcs BBB and all of it has
the same problem...
One, but not very elegant solution is to after start the board, make a
jumper between pins SYS_5V and VDD_5V, in example with any mosfet
transistor.
With this jumper, on kernel 3.2 there was no reset f
I have the same problem with BBB running Android. I tested TI prebuilt
Android JB4.2 image. We have two versions of BBBs (A5A and A5C). Both of
them have the issue.
I posted my question on Ti e2e website:
http://e2e.ti.com/support/embedded/android/f/509/p/297726/1049885.aspx#1049885
However i
There are no hints or any solutions...??
Please help!
W dniu środa, 23 października 2013 13:09:00 UTC+2 użytkownik Jakub Żymełka
napisał:
>
> Hello!
> I have a problem. It is based on an involuntary resetting of the BBBlack.
> This happens occasionally. About once a day. Totally when you least ex
18 matches
Mail list logo
