On 7/2/2014 2:06 PM, jmelson wrote: > > On Wednesday, July 2, 2014 12:45:05 PM UTC-5, RobertCNelson wrote: >> >> Are you sure this wasn't labeled as a "flasher" image, 18 minutes is >> about how long it takes to flash the eMMC with 1.7Gb of data. >> >> HMMMM, VERY interesting comment! Yes, it may have been set > up that way, and may be flashing the eMMC every time is starts > up. That would explain the extensive flickering of the user LEDs > when I don't expect much to be happening. > > Is there an easy way to check if this is a flasher setup? > How about a way to turn off the flasher process? Is it just a service > that is run out of /etc/init.d ? > > What does the flasher do when it is done? Call for a shutdown?
With the stock flasher images from RCN, you get a customized background that indicates it's a flasher uSD. Since the Machinekit images use a custom background image with a different name, they don't get changed when building a flasher image, so it can be hard to tell. To fix this (and other problems) I fixed the flasher scripts to run from init (so you don't even get a desktop) and added a "cylon" pattern to the LEDs so you know for sure the flasher script is running. Of course, these changes are not in the April Machinekit flasher image (these problems are what prompted me tweak things), so the best way to tell is to run top and see if a bunch of rsync processes are chewing up CPU and disk bandwidth. The next set of Machinekit images will use the new flasher scripts, but I've been holding off to try and get images based on the newly available packages rather than the "build-from-source" that's been used up until now. -- Charles Steinkuehler char...@steinkuehler.net -- 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.
