You can measure power all you want but if there is no way to reset the processor what good is the device in a remote location. I have had things on a remote mountain top at a transmitter site in winter that if things were unresponsive would ruin 2 or 3 days trying to get there to reset the device on a snowmobile.
Fail-safe computers are desirable. Hangs with no way to reboot a system are not. On 12/2/2015 7:58 PM, John Syne wrote: > We can speculate all day long, but measuring the 5V current > consumption will tell us a lot more about the power mode state than > anything else. > > Regards, > John > > > > >> On Dec 2, 2015, at 3:19 PM, William Hermans <yyrk...@gmail.com >> <mailto:yyrk...@gmail.com>> wrote: >> >> If the software is locked up, the USR LEDs would not cycle as if the >> system is attempting to restart. >> >> On Wed, Dec 2, 2015 at 4:08 PM, John Syne <john3...@gmail.com >> <mailto:john3...@gmail.com>> wrote: >> >> From what Gerald said previously in this thread: >> >> "The reset is an input pin read by the processor, not actually a >> HW power reset. If the SW is locked up, this could happen.” >> >> Regards, >> John >> >> >> >> >>> On Dec 2, 2015, at 2:55 PM, William Hermans <yyrk...@gmail.com >>> <mailto:yyrk...@gmail.com>> wrote: >>> >>> If the board was in sleep, then why wont the reset button reset >>> ? Passed that, why would the USR cycle( flash on then off ) then >>> nothing ? >>> >>> On Wed, Dec 2, 2015 at 3:47 PM, John Syne <john3...@gmail.com >>> <mailto:john3...@gmail.com>> wrote: >>> >>> Sounds to me that like BBB has gone into sleep mode and >>> there is no trigger to wake it up. Is there a way to measure >>> the current consumption? >>> >>> Regards, >>> John >>> >>> >>> >>> >>>> On Dec 2, 2015, at 2:40 PM, William Hermans >>>> <yyrk...@gmail.com <mailto:yyrk...@gmail.com>> wrote: >>>> >>>> One more thing of note. I do not run systemd - Ever. I run >>>> SYSV as an init daemon. I only mention this as I think >>>> Robert said something about systemd lessening this issue. >>>> >>>> On Wed, Dec 2, 2015 at 3:36 PM, Gerald Coley >>>> <ger...@beagleboard.org <mailto:ger...@beagleboard.org>> wrote: >>>> >>>> Hmm, not sure what is going on. Sounds like the >>>> processor has stopped running the code and halted but >>>> it forgot to turn off the lights. >>>> >>>> Gerald >>>> >>>> On Wed, Dec 2, 2015 at 4:26 PM, William Hermans >>>> <yyrk...@gmail.com <mailto:yyrk...@gmail.com>> wrote: >>>> >>>> Gerald, it's like the board hangs at power down, >>>> but I can not be 100% sure. The reason why I >>>> "assume" it's at power down, is that the heartbeat >>>> blink stops, but the rest of the LEDs stay on, and >>>> the ethernet port light still blinks. >>>> >>>> The board I experienced this on last night is an >>>> Element14 RevC, but I do also have a circuitco A5A >>>> that exhibits the same thing. >>>> >>>> On Wed, Dec 2, 2015 at 3:22 PM, Gerald Coley >>>> <ger...@beagleboard.org >>>> <mailto:ger...@beagleboard.org>> wrote: >>>> >>>> Is this on power up or is this state happening >>>> some time later? If it is on power up, then the >>>> power supply most likely is the issue based on >>>> the ramp requirements of the PMIC. >>>> >>>> If the power LED is on, then the PMIC is on and >>>> ramped up. That is why I asked for the voltages. >>>> >>>> It also could be a boot pin read issue where it >>>> misreads the boot pins. If that is the case you >>>> should see that from the serial port. >>>> >>>> Gerald >>>> >>>> >>>> On Wed, Dec 2, 2015 at 4:15 PM, William Hermans >>>> <yyrk...@gmail.com <mailto:yyrk...@gmail.com>> >>>> wrote: >>>> >>>> For what it's worth Gerald, this happens >>>> with nothing connected to the board as >>>> well. This just happened to me last night >>>> after issuing a reboot command from the >>>> command line. >>>> >>>> I remember at some point you all were >>>> talking about something about the "ramp >>>> time" of the PMIC or something. >>>> >>>> On Wed, Dec 2, 2015 at 3:11 PM, Gerald >>>> Coley <ger...@beagleboard.org >>>> <mailto:ger...@beagleboard.org>> wrote: >>>> >>>> I would start with your cape design and >>>> try and rule that out first. >>>> >>>> The reset is an input pin read by the >>>> processor, not actually a HW power >>>> reset. If the SW is locked up, this >>>> could happen. >>>> >>>> If you hold the power button for a 8 >>>> seconds or more the board should power >>>> cycle. >>>> >>>> When it is in this state, what do the >>>> voltages read? >>>> >>>> Gerald >>>> >>>> >>>> On Wed, Dec 2, 2015 at 3:54 PM, >>>> Jonathan Ross <jonr...@nephology.org >>>> <mailto:jonr...@nephology.org>> wrote: >>>> >>>> Once in a blue moon one of my >>>> beaglebones will get into a state >>>> where it has power (the power LED >>>> is lit), but it is not booted. >>>> Normally this would be fine, just >>>> hit the power button to reset. But >>>> in this weird state the power >>>> button does nothing. The reset >>>> button does nothing. >>>> I checked the power and reset >>>> button pins on the header, the >>>> power was low, the reset was high. >>>> The only way to get the board out >>>> of this state was to pull the 5V power. >>>> I'm using a KL16 on a cape to do a >>>> watchdog on the BB, and reboot it >>>> via power and/or reset buttons on >>>> the header if the BB stops sending >>>> checkins over uart. This has been >>>> working great, except for the rare >>>> case where the board ends up in >>>> this state where the power and >>>> reset buttons are not functioning. >>>> Any ideas how the BB could get into >>>> this state, and if there's any >>>> other way to force a reboot other >>>> than physically pulling the 5v power? >>>> Thanks, >>>> JR >>>> >>>> -- >>>> -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
