On Fri, Oct 2, 2015 at 5:23 PM, Brian Adams <[email protected]> wrote: > We are building our images using the omap-image-builder scripts. Looks like > everything is current (u_boot_release="v2015.10-rc3") yet we are still > experiencing a 4.5% boot failure rate where we have a single power light and > no other leds lit. Do I understand correctly that the uboot software fix > that checks for any key press essentially reduces the failure rate because > the random noise on the uart would have to be in the range of a real > key-code to stop the boot sequence? And if that is right, that while > reduced, there is still a range of noise that can abort the boot sequence?
Random noise on tx/rx will stop the board... For a board that "stops" what happens when you plug in a usb-usart, are you really in u-boot? (u-boot prompt should echo back on the first enter) One reason i can't lock down u-boot by default, CircuitCo's tester expect to take over u-boot to program the eeprom as part of their tester machines.. Regards, -- Robert Nelson https://rcn-ee.com/ -- 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.
