I am using an adapter which gives me an output of 5V, 1A. Below are some pictures of my BBB.
<https://lh4.googleusercontent.com/-4DQ3mCzQca4/Ut_uhT2LdKI/AAAAAAAABmY/pdm5ZWLGh7A/s1600/top.jpg> <https://lh3.googleusercontent.com/-0290kW0czLY/Ut_vJCSfAqI/AAAAAAAABmg/v-EYOUYqbPc/s1600/serialno.jpg> <https://lh5.googleusercontent.com/-MHr_BcSpXsA/Ut_vrSHU5zI/AAAAAAAABmo/Vg7VQ_oai9Q/s1600/bottom.jpg> It has a beaglebone logo, so I think it is a original board and the vendor mentions it that it is original. The vendor is ready to check it and replace it if it has some hardware issues. Thanks for your support guys. Like I said, I had issue on the first day itself, but I re-flashed it, it worked for a week, after using ubuntu and expanding the file system in that, the issue began. On Wednesday, 22 January 2014 20:23:47 UTC+5:30, Jason Kridner wrote: > > On Tue, Jan 21, 2014 at 10:18 PM, <[email protected] <javascript:>>wrote: > >> Can you tell me how to find out weather it is a clone or original. I >> don't think it is a clone. >> > > If it has the BeagleBoard.org logo, it better not be a clone! I think > Robert's question was more along the lines of if you were making your own > hardware. With the issue description, it really looks like a hardware issue. > > >> Because I flashed it once with the eMMC flasher image available at >> beagleboard website. It was working at that time. I followed the >> instructions to boot it from sd card with ubuntu and I tried to expand the >> file system, everything worked. And after that I removed sd card and tried >> to boot from eMMC I am stuck. I already posted my question in forum but >> didn't get any answer so I posted it in the way that you will look into it >> Robert to give a solution, the link of my previous post: >> http://beagleboard.org/Community/Forums?place=topic%2Fbeagleboard%2FQFp3aMdKIwQ%2Fdiscussion. >> > > I feel something else must have been done to the board. > > >> >> Finally yesterday I sent a mail to Jason and he has replied. I will like >> this post to my previous post so that Jason will also look into this in >> detail. And you two tech guys can help me on fixing this. >> > > Escalating to me when you don't get an answer with a link to the public > post is good. I can't tell you how many times I tell people to post here > FIRST! Anyway, given that you cannot read the EEPROM even from u-boot SPL, > I think something must be up with the bus. I think it would give a > different error if you had simply over written the EEPROM. > > What are you using as a power supply? What do you have connected to the > board? > > >> >> On Wednesday, 22 January 2014 01:20:06 UTC+5:30, RobertCNelson wrote: >> >>> On Tue, Jan 21, 2014 at 1:07 PM, <[email protected]> wrote: >>> > >>> > I am trying to flash my Beaglebone Black with Debain flasher image >>> available >>> > at >>> > https://rcn-ee.net/deb/flasher/wheezy/BBB-eMMC- >>> flasher-debian-7.3-2013-12-17-2gb.img.xz >>> > >>> > But I am not able to do it. >>> > >>> > I am holding the boot button and then turning on the power supply for >>> the >>> > board. The LEDs doesn't turn on even after a long time as I am holding >>> the >>> > boot button. I tried to look into what is happening with the help of >>> Serial >>> > to USB converter and go the message displayed bellow: >>> > >>> > >>> > U-Boot SPL 2013.10-00015-gab7a95a (Nov 08 2013 - 16:01:27) >>> > i2c_probe: pads on bus 0 probably not configured (status=0x10) >>> > Could not probe the EEPROM; something fundamentally wrong on the I2C >>> bus. >>> > Could not get board ID. >>> > i2c_probe: pads on bus 0 probably not configured (status=0x10) >>> > Could not probe the EEPROM; something fundamentally wrong on the I2C >>> bus. >>> > Could not get board ID. >>> >>> Oh, that's fun.. Your board's eeprom no longer has its id.. >>> >>> is this a "real" bbb or a clone? >>> >>> The reason the ancient rootfs works, it assumes a bbb, boots, then >>> programs the eeprom and initial eMMC file system. Then ships to >>> customers.. >>> >>> 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/groups/opt_out. >> > > -- 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/groups/opt_out.
