Hi João Paulo, I seem to be having the same problem. I checked the voltage on the SDA and SCL pins of U7 (the eprom) and they stay at 0V. This voltage on a health BBB is at 3.3. Did you request an RMA or did you find a work around. I'd like to know what causes the problem. This is the boot screen using internal emmc: http://pastebin.com/DkXzvhSK Using a bootable sd with ubuntu and holding down the boot button: http://pastebin.com/MEFtSQSe
Any help in understanding why this happens would be great. Thanks in advance. Bobby PS I am powering the BBB with a 2A power supply at 5V Il giorno martedì 22 aprile 2014 00:55:33 UTC+2, João Paulo ha scritto: > > Robert, > > Do you recommend I request a RMA or do you think should be a work > around to solve the issue? > > Regards, > João Paulo > > 2014-04-18 23:24 GMT-03:00 João Paulo Bodanese <[email protected] > <javascript:>>: > > Robert, > > > > Now the Linux boot, but the error messages persist: > > > > http://pastebin.com/x71Ufu1Z > > > > Regards, > > João Paulo > > > > 2014-04-18 17:09 GMT-03:00 William Hermans <[email protected] > <javascript:>>: > >> Yeah, I noticed your most recent post to the OP. Could not believe that > I > >> missed "undefined"( making me feel pretty silly ), although I suppose > the > >> file could be undefined in both cases ? *shrug* > >> > >> > >> On Fri, Apr 18, 2014 at 12:57 PM, Robert Nelson <[email protected] > <javascript:>> > >> wrote: > >>> > >>> On Fri, Apr 18, 2014 at 2:52 PM, William Hermans <[email protected] > <javascript:>> > >>> wrote: > >>> > This almost seems like the EEPROM error that happens once in a > while. > >>> > Why > >>> > and how I dont know but I remember . . . > >>> > > >>> > > >>> > Could not probe the EEPROM; something fundamentally wrong on the I2C > >>> > bus. > >>> > > >>> > So then this happens . .. > >>> > > >>> > reading /dtbs/undefined > >>> > ** Unable to read file /dtbs/undefined ** > >>> > Kernel image @ 0x82000000 [ 0x000000 - 0x38ba80 ] > >>> > ERROR: Did not find a cmdline Flattened Device Tree > >>> > Could not find a valid device tree > >>> > > >>> > In essence uboot does not know which device tree file to load for > the > >>> > board, > >>> > so not everything is configured properly. > >>> > > >>> > Robert, didnt you used to have an EEPROM flasher script to fix this > >>> > situation ? Or is this not appropriate any longer ? > >>> > >>> Oh I do... Just haven't actually blanked out an EEPROM to test it yet. > >>> ;) Looks like i missed one check.. > >>> > >>> Regards, > >>> > >>> -- > >>> Robert Nelson > >>> http://www.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] <javascript:>. > >>> > >>> 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 a topic in the > >> Google Groups "BeagleBoard" group. > >> To unsubscribe from this topic, visit > >> https://groups.google.com/d/topic/beagleboard/yLAbudOgAIU/unsubscribe. > >> To unsubscribe from this group and all its topics, send an email to > >> [email protected] <javascript:>. > >> 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.
