>>> Does anyone have any input as to why the PocketBeagle design fails and
>>> why the BBBW works ?

Robert Nelson is really the right person to answer that.

>From what I understand, during boot, uBoot examines the configuration
EEPROM and decides which files/modules to load. Even though the hardware
is identical, it could load different modules, if the configuration
EEPROM is different. So, one load has the bug, the other doesn't.

Or, you are actually running different revision levels of silicon, and
one has a bug.


>>> Also if Tying VIN_USB to VIN_AC works, would the problem go away if a
>>> battery was connected to VIN_BAT ?

I have never tried that, but definitely worth a try.  It is a third
separate isolated power input. I assume with different management software.


>>> Any thoughts would be appreciated.
Beagleboard.org needs to decide if this is a serious enough problem that it
is worthy of being fixed.  So far, they have decided that we don't know
what
we are doing, and are inducing a spurious problem; or that it is not serious
enough a problem to spend the time fixing. I personally think it prevents
the PocketBeagle from being used for any serious application.

On Fri, Aug 16, 2019 at 12:35 AM Dave <[email protected]> wrote:

> As I have noted in a previous post, I am seeing this problem on a board
> with a design derived from the pocketBeagle.
> Based on the information here we have managed a workaround -  tying
> VIN_USB to VIN_AC, and as a consequence have several boards that have been
> runing for over 48hours, when we could not reach 18hrs before and often had
> resets every 30min.
>
> I have run the same software with nearly the same devicetree and the same
> linux(5.1.18) on a BBBW without any failures.
>
> I have compared the schematic of the BBBW which also uses that OSD335X SOC
> with that of my board and the pocketBeagle and  can not see a meaningful
> difference in the input power design.
>
> Does anyone have any input as to why the PcketBeagle design fails and why
> the BBBW works ?
>
> Also if Tying VIN_USB to VIN_AC works, would the problem go away if a
> battery was connected to VIN_BAT ?
>
> Any thoughts would be appreciated.
>
> Though atleast we have a workarround now.
>
> Thank you.
>
>
>
>
>
>
>
>
>
>
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> 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/FwmkeG4itT0/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/dadd11c2-3887-4c87-8d02-0048fd10dd92%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/dadd11c2-3887-4c87-8d02-0048fd10dd92%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CANN_KV5ySrb2ZCHv74Se1GjYDisQG15B_y46UPASRDNaX1W_xg%40mail.gmail.com.

Reply via email to