UPDATEAppears the DC port on the board failed.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
You will not burn the board but Nothing will change because when powering the board by a usb port the software limits the current to some level and when this limit is exceeded then the board reboots. Therefore even if you give 100A to the usb port the pmic will limit it
image |
Angstrom (3.8 kernel) |
Android(3.8 kernel) |
Android(3.2 kernel) |
clock (Hz) |
1G |
1G |
1G |
Display type |
HDMI |
HDMI |
HDMI |
current (mA) |
290 |
300 |
375 |
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
By the way when I connected 5vdc directly to the additional ldo ic I have grounded Vusb as well and the board worked without any reboot issue during 1 week. Probably I was in a wrong direction thinking that it was totally depending on the current overload at tps65217. One of the ideas was about the USB grounding and I combined all solutions at once
Will test only grounded Vusb to check your hypothesis
Follow your finding on the unexpected TPS65217C behavior, I patched the tps65217 driver with irq handling. The 3.2 kernel does not handle nNMI/PMIC_INT interrupt; the 3.8 kernel does. I placed printk in the interrupt handler and got the same result as yours. The PMIC_INT was issued every 2 seconds which is caused by the USBI flag in the TPS65217C interrupt register.
The abstract from the TPS65217 datasheet to describe what is going on here:
The linear charger periodically applies a 10-mA current source to the BAT pin to check for the presence of a
battery. This will cause the BAT terminal to float up to > 3 V which may interfere with AC removal detection and
the ability to switch from AC to USB input. For this reason, it is not recommended to use both AC and USB
inputs when the battery is absent.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
The abstract from the TPS65217 datasheet to describe what is going on here:
The linear charger periodically applies a 10-mA current source to the BAT pin to check for the presence of a
battery. This will cause the BAT terminal to float up to > 3 V which may interfere with AC removal detection and
the ability to switch from AC to USB input. For this reason, it is not recommended to use both AC and USB
inputs when the battery is absent.
--
Broadcast message from root@arm
(unknown) at 11:40 ...
The system is going down for reboot NOW!
[ 143.036193] Restarting system.
so somehow it might not be a complete physical problem, the system knows about it
(Linux version 3.7.10-x9 on Ubuntu 12.10 and beagleboard xm)
On Tue, Nov 12, 2013 at 8:37 AM, <lei...@gmail.com> wrote:
> I have similar issue. I have (2) versions of BBB (A5A and A5C). They both
> randomly reboot themselves while I am running TI prebuilt BBB android image
> (from a couple hours to ten to fifteen hours). When I plug in the USB (DC is
> still powered) for logging with logcat, the reboot issue seems to disappear.
>
> I don't have problem with BBB Angstrom image (based on 3.8 kernel). I don't
> have problem with Andrew Henderson's android image (based on 3.8 kernel)
> either.
>
> Another issue is that when I run TI BBB android image, the clock randomly
> jumps forward 2^17 seconds. This happens on both of my BBB boards. The
> problem goes away when I run Angstrom or Andrew's android.
This time 'issue' was fixed in u-boot sometime last year, so I'm
guessing the TI image has an un-patched u-boot..
>
> I suspect it has something to do with the processor, DDR3 (BBB: AM3359 1GHz
> + 512MB DDR3), the configuration, or apply workaround of errata. We have an
> AM335x EVM kit (AM3359 720MHz + 256MB DDR2). I also loaded TI prebuilt
> android image. I have run it for several months. It is rock solid. I never
> had problem with it.
>
> Here are the links to my other posts in regarding to this issue.
> https://groups.google.com/forum/#!category-topic/beagleboard/advanced/5qSJ4dQdar4
> http://e2e.ti.com/support/embedded/android/f/509/t/297726.aspx
>
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/xPxzYyNsA78/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.