So, I'm pretty sure there is a way to bypass the EEPROM check, and force the correct device tree board file. But I am not sure how to go about doing that. Plus, I'm not sure what else is involved. Maybe Robert can chime in and tell us whether what I'm thinking is a good idea or not ? As uboot has to know some things too . . .
On Tue, Dec 1, 2015 at 2:29 PM, Bryan Hood <[email protected]> wrote: > Serial number is blank. I just see a large white rectangle to the right of > "S/N" on the bottom silkscreen. > > re: circuitco - I purchased it through Adafruit 2 years ago, so I don't > believe so. > > On Tue, Dec 1, 2015 at 1:12 PM, William Hermans <[email protected]> wrote: > >> Is this a circuitco board ? >> >> On Tue, Dec 1, 2015 at 2:10 PM, Bryan Hood <[email protected]> wrote: >> >>> Oh wow! I have an answer. I went to go probe U7, the EEPROM, and >>> discovered that it has fallen off the PCB. All that was left was a single >>> pin dangling on a pad. I can see where the other chip legs used to be >>> soldered on.There must have been a defect during the SMT process. >>> >>> So my next question is, is there a way to get a programmed EEPROM to fix >>> my BBB? Can I get an RMA? Or should I just buy a new one? >>> >>> On Tue, Dec 1, 2015 at 1:01 PM, Bryan Hood <[email protected]> >>> wrote: >>> >>>> Here is my UART output: >>>> >>>> U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) >>>> Could not probe the EEPROM; something fundamentally wrong on the I2C >>>> bus. >>>> Could not get board ID. >>>> Could not probe the EEPROM; something fundamentally wrong on the I2C >>>> bus. >>>> Could not get board ID. >>>> Unknown board, cannot configure pinmux.### ERROR ### Please RESET the >>>> board ### >>>> >>>> >>>> On reset, the same message repeats. I'll probe the I2C bus and see what >>>> I can find. >>>> >>>> Bryan >>>> >>>> >>>> On Sun, Nov 29, 2015 at 10:40 PM, William Hermans <[email protected]> >>>> wrote: >>>> >>>>> Make sure your serial adapter is 3v3 ttl. >>>>> >>>>> On Sun, Nov 29, 2015 at 11:16 PM, Bryan Hood <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi William, >>>>>> >>>>>> I tried flashing the eMMC as you suggested, but no luck. The LEDs >>>>>> never turned on, so I just waited a very long time. I'll work on getting >>>>>> the serial output next. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Bryan >>>>>> >>>>>> On Sun, Nov 29, 2015 at 7:44 PM, William Hermans <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Using a serial debug cable will give you a better idea of what's >>>>>>> going on. It will not always let you know exactly what the problem is, >>>>>>> but >>>>>>> based on what you get as output, someone here could give you a better >>>>>>> idea >>>>>>> what's happening. >>>>>>> >>>>>>> Passed that . . . try flashing this to sdcard, and booting from it. >>>>>>> >>>>>>> >>>>>>> http://debian.beagleboard.org/images/bone-debian-7.5-2014-05-14-2gb.img.xz >>>>>>> >>>>>>> This is an older image, and I have a good reason as to why you >>>>>>> should attempt booting from this. Older eMMC images can interfere with >>>>>>> newer sdcard images at boot. This should give you( us ) a better idea >>>>>>> what >>>>>>> is going on. Typically though, with an older 1st, and 2nd stage boot >>>>>>> loader, if you press and hold the boot button at boot. the board should >>>>>>> be >>>>>>> forced to boot from, and use the 1st, and 2nd stage bootloader from the >>>>>>> sd >>>>>>> card, instead of attempting to use the boot loaders from the eMC . . . >>>>>>> >>>>>>> On Sun, Nov 29, 2015 at 7:45 PM, Bryan Hood <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> I've got a beagle bone black that used to have debian on it, but >>>>>>>> it's been sitting on my desk unpowered for over a year. I recently >>>>>>>> tried >>>>>>>> booting it, but the user LEDs won't turn on; only the power LED will >>>>>>>> light >>>>>>>> up. I tried programming the on board flash, and booting from a microSD >>>>>>>> card, but no luck. Any suggestions? I've got tools at work to probe the >>>>>>>> debug header, but I'm hoping it doesn't come to that. Thanks! >>>>>>>> >>>>>>>> -- >>>>>>>> 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 a topic in >>>>>>> the Google Groups "BeagleBoard" group. >>>>>>> To unsubscribe from this topic, visit >>>>>>> https://groups.google.com/d/topic/beagleboard/jUhsE9jPSUo/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 a topic in the >>>>> Google Groups "BeagleBoard" group. >>>>> To unsubscribe from this topic, visit >>>>> https://groups.google.com/d/topic/beagleboard/jUhsE9jPSUo/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 a topic in the >> Google Groups "BeagleBoard" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/beagleboard/jUhsE9jPSUo/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.
