None of those should cause any booting issues

Gerald
.

On Mon, Nov 23, 2015 at 11:49 AM, Lee Armstrong <[email protected]> wrote:

> Hi Gerald,
>
> Not that I am aware of, We use UART2 & UART4 (TX & RX) and also GPIO3_19.
>
> We also have the PWR_But & Sys_Reset pins wired in.
>
> These units are booting fine and at some point in the future, can be
> anywhere from 15 mins of running to several hours they just exhibit the
> beahviour I describe.  We are not sure where to look on the BBB side of
> things to see why it is in the state it is.
>
>
> On Mon, Nov 23, 2015 at 5:44 PM, Gerald Coley <[email protected]>
> wrote:
>
>> What do you have on the board that is plugged in? Does it use any of the
>> LCD pins?
>>
>> Gerald
>>
>>
>> On Mon, Nov 23, 2015 at 11:42 AM, Lee Armstrong <[email protected]>
>> wrote:
>>
>>> Thank you Gerald,
>>>
>>> Sorry I meant that we are using the VDD_5V pins to power the unit and
>>> not the SYS_5V.  Fat fingers there!
>>>
>>> With that in mind any sort of debugging we can do to tell if it is
>>> software our hardware?
>>>
>>> Lee
>>>
>>>
>>> On Monday, November 23, 2015 at 5:39:29 PM UTC, Gerald wrote:
>>>>
>>>> I would not power the board using the SYS_5V pins. That is the output
>>>> of the PMIC. Not sure what issues that would cause. It also sounds like
>>>> that the boot pins maybe are being affected in some way that prevents the
>>>> boot cycle after a power failure or removal.
>>>>
>>>>
>>>> Gerald
>>>>
>>>> On Mon, Nov 23, 2015 at 11:35 AM, Lee Armstrong <[email protected]>
>>>> wrote:
>>>>
>>>>> Anyone got any ideas, this is happening on a few units and nothing is
>>>>> logged at all.
>>>>>
>>>>> Need to narrow down if it is software or hardware issue, from the
>>>>> Debian side of things it just looks like the power was removed from the
>>>>> unit however the NIC lights are still on and also the PWR light on the
>>>>> BBB.  The BBB is powered via the SYS_5V pins.
>>>>>
>>>>>
>>>>>
>>>>> On Friday, November 20, 2015 at 11:48:12 AM UTC, Lee Armstrong wrote:
>>>>>>
>>>>>> Also further to that the USR LEDs are all extinguished but the LED's
>>>>>> on the NIC are ok and the power LED is still lit.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Friday, November 20, 2015 at 11:36:03 AM UTC, Lee Armstrong wrote:
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> I have a very strange issue that I cannot seem to work out and get
>>>>>>> more info for!
>>>>>>>
>>>>>>> We have a BBB Rev C that is powered via the 5V header pins.  It also
>>>>>>> uses UART2 heavily (3MBps) and this is configured using the built in
>>>>>>> BB-UART2 device tree overlay.
>>>>>>>
>>>>>>> The board is running...
>>>>>>>
>>>>>>> BeagleBoard.org Debian Image 2015-10-04
>>>>>>>
>>>>>>> 4.1.13-ti-r31
>>>>>>>
>>>>>>>
>>>>>>> What seems to happen is that the board drops off the network and
>>>>>>> also the serial debug cable I have attached becomes unresponsive.  
>>>>>>> Nothing
>>>>>>> had been logged in the console at all on the serial cable and when it 
>>>>>>> boots
>>>>>>> back up there is nothing in any of the previous syslogs at all to give 
>>>>>>> even
>>>>>>> the hint of anything happening.
>>>>>>>
>>>>>>>
>>>>>>> What is even more puzzling is that the network LED's continue to
>>>>>>> flash!
>>>>>>>
>>>>>>>
>>>>>>> To get this back I have to pull power and it then unsurprisingly
>>>>>>> works ok after that.
>>>>>>>
>>>>>>>
>>>>>>> I'm trying to get to the bottom of this but if nothing is logged I
>>>>>>> don't know where to go next!
>>>>>>>
>>>>>>>
>>>>>>> Any ideas at all anyone?
>>>>>>>
>>>>>> --
>>>>> 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].
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Gerald
>>>>
>>>> [email protected]
>>>> http://beagleboard.org/
>>>>
>>> --
>>> 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].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Gerald
>>
>> [email protected]
>> http://beagleboard.org/
>>
>> --
>> 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/SXP2YuC0dTA/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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].
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

[email protected]
http://beagleboard.org/

-- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to