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?
On Tuesday, August 11, 2015 at 7:13:14 AM UTC-7, RobertCNelson wrote: > > On Mon, Aug 10, 2015 at 10:18 PM, <[email protected] <javascript:>> wrote: > > Hi, > > > > Robert, in place of 2015-07-17 image, I see 2015-07-28 image. In any > way, > > how it is fixed? > > Just weekly build snapshots, look at the log for major changes: > > https://github.com/RobertCNelson/omap-image-builder/commits/master > > >I just tried to flash it to my BBB and I still can go into > > u-boot pressing any single key. Shouldn't it be some key sequence like > > "uboot"? > > It's just a single key over the usart... > > If it's not working, you more then likely have a version in eMMC not from > me > > 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.
