Ok thanks Gerald

On Mon, Nov 23, 2015 at 7:28 PM, Gerald Coley <[email protected]>
wrote:

> You might hook up a JTAG emulator and break in and see where it is stuck.
> Gerald
> On Mon, Nov 23, 2015 at 1:27 PM, Lee Armstrong <[email protected]> wrote:
>> OK that is a start and I will look into those other points.
>>
>> Is there any way to debug a hang like this where it simply locks up?
>>
>>
>>
>>
>> On Mon, Nov 23, 2015 at 7:26 PM, Gerald Coley <[email protected]>
>> wrote:
>>
>>> From my viewpoint, sounds like something in you application.
>>>
>>> Gerald
>>>
>>>
>>> On Mon, Nov 23, 2015 at 12:32 PM, evilwulfie <[email protected]>
>>> wrote:
>>>
>>>> Oh one more question
>>>>
>>>> Does the board lockup while not running your application.
>>>>
>>>>
>>>> On 11/23/2015 10:59 AM, Lee Armstrong wrote:
>>>>
>>>> Gerald,
>>>>
>>>> We are not seeing any booting issues though, the boards all boot fine
>>>> and have never had an issue there.  The boards are powered on and then
>>>> simply look like they power off and trying to troubleshoot the issue, is
>>>> there any info we can get by attaching to the PMIC at all?
>>>>
>>>> I have a serial debug cable attached  to the BBB and that simply logs
>>>> nothing in the console and then becomes unresponsive.  The OS is off,
>>>> confirmed as it loses network and all TTY access.  Pretty sure it is not
>>>> software induced as nothing in logs etc when it does come back.
>>>>
>>>> The only thing that gets it back and working is to remove and re-apply
>>>> power.
>>>>
>>>> What would cause this to happen is what we are trying to get to the
>>>> bottom of.
>>>>
>>>> Lee
>>>>
>>>>
>>>> On Mon, Nov 23, 2015 at 5:55 PM, Gerald Coley <[email protected]>
>>>> wrote:
>>>>
>>>>
>>>> --
>>>> 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 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.

Reply via email to