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.
Unknown board, cannot configure pinmux.### ERROR ### Please RESET the board ###
This image also doesn’t boot up, if I press the boot button. It boots up automatically if I insert the sd card with the image in the beaglebone black and give power supply, without me pressing the boot button.
And my Beaglebone black doesn’t boot from eMMC also.
Can you tell me how to find out weather it is a clone or original. I don’t think it is a clone. 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 .
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.
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?
I am using an adapter which gives me an output of 5V, 1A.
Below are some pictures of my BBB.
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.
The vendor of the product http://www.crazypi.com/ in India will take care of that for me. They also have a good support team like yours. Thanks for the support.
That’s the reason why I didn’t apply for the RMA process myself Gerald, as per your advice, I contacted the vendor. They must be buying it from some distributor and they will contact them. I wish they must be buying it from an authorized distributor.
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 ?
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
Looks like i missed one check..