Hi,
**If not, have you found the P1.1<=>P1.7 to be stable?
It has worked for me. No more random reboot after this.
I'm working in a clone board using the same IC as the PB, when they arrive
i will test stability powering from VIN and VUSB.
I have than this test on the BBBW and not detect any
We are seeing something similar on a board we designed using USB1 host. We
have PB powered through VIN, with P1.7 floating and are seeing spurious
reboots a few times per day. We are running on latest 9.5 image.
Our initial thought was that it was related to our 5V supply on Vin, and
were
Looks like I spoke too soon.
Both PB's reset themselves overnight, running Stretch 9.3 IoT.
With the Stretch 9.3 IoT release, it is more like once per day, than the
previous four times per day, but it is still happening.
Happens on both 4.4 and 4.9.
To answer Robert's question.
I generally
Thanks a lot for this analysis. I will update the image tomorrow as we try to
root source the problem on the old images.
> On Dec 17, 2017, at 4:10 PM, Graham wrote:
>
> Some further information.
>
> I have been unable to get your latest Stretch 9.3 IoT image to fail and
On Sun, Dec 17, 2017 at 3:10 PM, Graham wrote:
> Some further information.
>
> I have been unable to get your latest Stretch 9.3 IoT image to fail and
> autonomously reboot, when powered by Vin (P1-pin1)
> ie.:" bone-debian-9.3-iot-armhf-2017-12-10-4gb.img"
>
> I am
Some further information.
I have been unable to get your latest Stretch 9.3 IoT image to fail and
autonomously reboot, when powered by Vin (P1-pin1)
ie.:" bone-debian-9.3-iot-armhf-2017-12-10-4gb.img"
I am starting an extended test today, and letting two PBs run for the rest
of the week,
OK.
I'll be glad to gather any data for you that I can.
I can grab some scope traces of what the power looks like.
I don't have anything that will do 24 hour long captures.
The bench supply I have is well regulated, and quiet, 5 Amp.
I have run two PB (on Vin P1-pin1) from the same supply
Can you generate a plot of the power applied on P1_1? I suspect some
additional bulk capacitance might be required to keep it sufficiently
stable. Monitoring the RESET# line at the same time as P1_1 would be ideal.
I'll try to reproduce next week. I only ever tested with a bench supply and
not
P1-pin7 is the 5V power input normally associated with power coming in the
USB connectors.
In the case of the PocketBeagle, it is the input from the USB0 connector.
It can be used as either a 5V input or, if there is power coming in USB
port0, as a power output for USB port 1.
It is just a
On Sunday, December 3, 2017 at 4:21:33 PM UTC+1, Graham wrote:
>
> The PocketBeagle, when powered only by the Vin input (P1-pin1) is
> unstable.
> This is the power supply input, normally assigned to the barrel jack in
> the BBB, or the AC adapter input in the TI docs.
>
> Not to be confused
I'll try again.
The PocketBeagle, when powered only by the Vin input (P1-pin1) is unstable.
This is the power supply input, normally assigned to the barrel jack in the
BBB, or the AC adapter input in the TI docs.
Not to be confused with the Vi input (P1-pin7) which is connected to Vusb0
and
Same 'Stretch' bone-debian-9.2-iot-armhf-2017-11-19-4gb.img
running on uSD card on a Rev C BeagleBone Black running on
the same power supply is stable like a rock.
--- Graham
==
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are
LOLĀ With this email coming from Graham I seriously doubt it.
On 11/25/2017 10:13 AM, acheesehead wrote:
> A likely culprit is the power supply.
>
> On Friday, November 24, 2017 at 7:55:56 AM UTC-7, Graham wrote:
>
> I have two PocketBeagles.
>
> Both are exhibiting random reboots, two to
A likely culprit is the power supply.
On Friday, November 24, 2017 at 7:55:56 AM UTC-7, Graham wrote:
>
> I have two PocketBeagles.
>
> Both are exhibiting random reboots, two to four times per day. No
> indication in syslog as to any cause or problem. No pattern to
> the reboots. Can happen
14 matches
Mail list logo