Unable to boot from SD Card for flashing eMMC with Debian/Ubuntu/Angstrom

[jayakar...@gmail.com]

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.

Unknown board, cannot configure pinmux.### ERROR ### Please RESET the board ###

Does anyone know how to solve this issue. This is not the case only with Debian image. I am not able to boot from any image. I can only run the image Angstrom Distribution (BeagleBone, BeagleBone Black - 4GB SD) 2013-06-20 available at http://beagleboard.org/latest-images.

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.

[Robert Nelson]

On Tue, Jan 21, 2014 at 1:07 PM, <jayakar...@gmail.com> 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/

[jayakar...@gmail.com]

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.

[Jason Kridner]

On Tue, Jan 21, 2014 at 10:18 PM, <jayakar...@gmail.com> 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?

 

--
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 beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[jayakar...@gmail.com]

I am using a 5V, 1A power supply and I have connected the Ethernet and Serial to USB converter to connectors Tx, Rx, and Gnd.

[jayakar...@gmail.com]

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. 

[Gerald Coley]

You must to go through the RMA processes before you can get it replaced.

Gerald

[jayakar...@gmail.com]

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.

[Gerald Coley]

Well, they are not an authorized distributor unfortunately.

Gerald

[jayakar...@gmail.com]

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.

[João Paulo]

Hi Jayakarthigeyan,

Any news about this issue? I am facing the same problem.

Regards,

João Paulo

[Robert Nelson]

On Fri, Apr 18, 2014 at 9:47 AM, João Paulo <joao.b...@gmail.com> wrote:
> Hi Jayakarthigeyan,
>
> Any news about this issue? I am facing the same problem.

"exact" same problem? Please pastebin.com your full serial boot log
from power on.

Beyond that, just one question, before i pass you a link. Do you have
a real BeagleBoard Black, with the 1Ghz am3358/am3359?

[João Paulo Bodanese]

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.

Regards,
João Paulo

> --
> 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 beagleboard...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Robert Nelson]

On Fri, Apr 18, 2014 at 12:16 PM, João Paulo Bodanese
<joao.b...@gmail.com> 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..

[João Paulo Bodanese]

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

[William Hermans]

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 ?

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 beagleboard...@googlegroups.com.

[Robert Nelson]

On Fri, Apr 18, 2014 at 2:33 PM, João Paulo Bodanese
<joao.b...@gmail.com> wrote:
> Robert,
>
> I think didn't work out. Take a look in the log:
>
> 1) With boot button pressed: http://pastebin.com/CJGwkG5v

My bad:

<quote>

"reading /dtbs/undefined
** Unable to read file /dtbs/undefined **"

</quote>

https://github.com/RobertCNelson/Bootloader-Builder/commit/80eef26383f60476ececfdd99d3a7b29cfc6d3e9

Can you open up the "uEnv.txt" file and hardcode this one variable:

fdtfile=am335x-boneblack.dtb

It should boot to a login prompt now. (with the boot button pressed)

[Robert Nelson]

On Fri, Apr 18, 2014 at 2:52 PM, William Hermans <yyr...@gmail.com> 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..

[William Hermans]

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*

[João Paulo Bodanese]

Robert,

Now the Linux boot, but the error messages persist:

http://pastebin.com/x71Ufu1Z

Regards,
João Paulo

> 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

[João Paulo Bodanese]

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

[bob...@gmail.com]

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

[João Paulo Bodanese]

Hi Bobby,

I requested a RMA and they replaced the BBB. 

I still do not know what happened.

Best regards,

João Paulo