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 ?



On Fri, Apr 18, 2014 at 12:33 PM, João Paulo Bodanese <
[email protected]> wrote:

> Robert,
>
> I think didn't work out. Take a look in the log:
>
> 1) With boot button pressed: http://pastebin.com/CJGwkG5v
> 2) Next bootup: http://pastebin.com/zcAxdhw0
>
> The Linux boot, but the errors persist.
>
> Regards,
> João Paulo
>
> 2014-04-18 14:21 GMT-03:00 Robert Nelson <[email protected]>:
> > On Fri, Apr 18, 2014 at 12:16 PM, João Paulo Bodanese
> > <[email protected]> wrote:
> >> Hi,
> >>
> >> Yes, I have a real BBB (am3359) bought from Farnell Newark
> >> (www.farnellnewark.com.br) 3 weeks ago. I am from Brazil.
> >>
> >> The full log: http://pastebin.com/Si2584Et
> >>
> >> I requested a RMA. But I am not sure if Farnell in Brazil is an
> >> BeagleBoard authorized.
> >
> > Humm, a lot of boards recently are coming up with that i2c eeprom
> failing...
> >
> > Give this a shot:
> >
> >
> http://rcn-ee.net/deb/testing/2014-04-14/BBB-blank-eMMC-flasher-debian-7.4-2014-04-14-2gb.img.xz
> >
> > If it actually boots, next ground out the board eeprom's write-protect
> > pin and it'll write the correct firmware on the next bootup..
> >
> > 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 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].
> > 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.
>

-- 
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.

Reply via email to