Booting Issue beaglebone black

My BBB doesn’t boot, I tried flashing it with factory Angstrom image available at beagleboard.org website. The 4 LEDs light up and the process is completed. But doesn’t boot even after that. To see what is happening I connected my Serial to USB converter to the BBB and using Putty I saw the U-Boot message which appears like the following:

U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53)

timed out in wait_for_pin: I2C_STAT=0

Could not probe the EEPROM; something fundamentally wrong on the I2C bus.

Could not get board ID.

Unknown board, assuming Beaglebone LT/Black.musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)

musb-hdrc: MHDRC RTL version 2.0

musb-hdrc: setup fifo_mode 4

musb-hdrc: 28/31 max ep, 16384/16384 memory

USB Peripheral mode controller at 47401000 using PIO, IRQ 0

musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)

musb-hdrc: MHDRC RTL version 2.0

musb-hdrc: setup fifo_mode 4

musb-hdrc: 28/31 max ep, 16384/16384 memory

USB Host mode controller at 47401800 using PIO, IRQ 0

OMAP SD/MMC: 0

mmc_send_cmd : timeout: No status update

reading u-boot.img

reading u-boot.img

U-Boot 2013.04-dirty (Jul 10 2013 - 14:02:53)

I2C: ready

DRAM: 512 MiB

WARNING: Caches not enabled

timed out in wait_for_pin: I2C_STAT=0

Could not probe the EEPROM; something fundamentally wrong on the I2C bus.

Could not get board ID.

NAND: No NAND device found!!!

0 MiB

MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1

*** Warning - readenv() failed, using default environment

musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)

musb-hdrc: MHDRC RTL version 2.0

musb-hdrc: setup fifo_mode 4

musb-hdrc: 28/31 max ep, 16384/16384 memory

USB Peripheral mode controller at 47401000 using PIO, IRQ 0

musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)

musb-hdrc: MHDRC RTL version 2.0

musb-hdrc: setup fifo_mode 4

musb-hdrc: 28/31 max ep, 16384/16384 memory

USB Host mode controller at 47401800 using PIO, IRQ 0

Net: not set. Validating first E-fuse MAC

cpsw, usb_ether

Hit any key to stop autoboot: 0

gpio: pin 53 (gpio 53) value is 1

Card did not respond to voltage select!

mmc0(part 0) is current device

Card did not respond to voltage select!

No micro SD card found, setting mmcdev to 1

mmc_send_cmd : timeout: No status update

mmc1(part 0) is current device

gpio: pin 54 (gpio 54) value is 1

SD/MMC found on device 1

reading uEnv.txt

26 bytes read in 3 ms (7.8 KiB/s)

Loaded environment from uEnv.txt

Importing environment from mmc …

gpio: pin 55 (gpio 55) value is 1

4385024 bytes read in 768 ms (5.4 MiB/s)

gpio: pin 56 (gpio 56) value is 1

24808 bytes read in 54 ms (448.2 KiB/s)

Booting from mmc …

Booting kernel from Legacy Image at 80007fc0 …

Image Name: Angstrom/3.8.13/beaglebone

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 4384960 Bytes = 4.2 MiB

Load Address: 80008000

Entry Point: 80008000

Verifying Checksum … OK

Flattened Device Tree blob at 80f80000

Booting using the fdt blob at 0x80f80000

XIP Kernel Image … OK

OK

Using Device Tree in place at 80f80000, end 80f890e7

Starting kernel …

Uncompressing Linux… done, booting the kernel.

[ 1.148261] omap_i2c 44e0b000.i2c: controller timed out

[ 1.148304] tps65217 0-0024: Failed to read INT reg

[ 1.148322] tps65217 0-0024: Failed to probe pwr_but

[ 2.148252] omap_i2c 44e0b000.i2c: controller timed out

[ 3.152151] omap_i2c 44e0b000.i2c: controller timed out

[ 3.182788] omap2_mbox_probe: platform not supported

[ 4.246560] omap_i2c 44e0b000.i2c: controller timed out

[ 5.254176] omap_i2c 44e0b000.i2c: controller timed out

[ 6.767826] omap_i2c 44e0b000.i2c: controller timed out

[ 7.779563] omap_i2c 44e0b000.i2c: controller timed out

[ 9.293213] omap_i2c 44e0b000.i2c: controller timed out

[ 10.305060] omap_i2c 44e0b000.i2c: controller timed out

[ 11.818596] omap_i2c 44e0b000.i2c: controller timed out

[ 12.830340] omap_i2c 44e0b000.i2c: controller timed out

Similarly when I try to boot the board using Ubuntu on SD Card I see the following message:

▒m▒▒▒▒▒▒▒rpqsnqpmpprtym▒qu▒u▒▒▒h▒▒▒qw@rpqsmqvzsuzqqi

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

After the flashing did you remove the power from the board as instructed?

http://www.elinux.org/Beagleboard:Updating_The_Software

Gerald

Yes I did Gerald. I removed the power supply then only I removed the sd card and gave power to it again. I have already flashed my eMMC once as soon as a bought it last week as I ran into boot problem as I deleted some file during date time update. At that time it worked, so I know the flashing process. I was running ubuntu precise from my sd card, and I was trying to use the leftover space available in the sd card by following the guide in the following web link: http://elinux.org/Beagleboard:Expanding_File_System_Partition_On_A_microSD, only after doing this, I ran into the booting issue that I am not able to fix. Thanks in advance for your reply.

My BBB doesn't boot, I tried flashing it with factory Angstrom image
available at beagleboard.org website. The 4 LEDs light up and the process
is completed. But doesn't boot even after that. To see what is happening I
connected my Serial to USB converter to the BBB and using Putty I saw the
U-Boot message which appears like the following:

U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53)

timed out in wait_for_pin: I2C_STAT=0

Could not probe the EEPROM; something fundamentally wrong on the I2C bus.

Do you have any boards attached? This is an odd response.

Could not get board ID.

Unknown board, assuming Beaglebone LT/Black.musb-hdrc: ConfigData=0xde
(UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)

musb-hdrc: MHDRC RTL version 2.0

musb-hdrc: setup fifo_mode 4

musb-hdrc: 28/31 max ep, 16384/16384 memory

USB Peripheral mode controller at 47401000 using PIO, IRQ 0

musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
SoftConn)

musb-hdrc: MHDRC RTL version 2.0

musb-hdrc: setup fifo_mode 4

musb-hdrc: 28/31 max ep, 16384/16384 memory

USB Host mode controller at 47401800 using PIO, IRQ 0

OMAP SD/MMC: 0

mmc_send_cmd : timeout: No status update

reading u-boot.img

reading u-boot.img

U-Boot 2013.04-dirty (Jul 10 2013 - 14:02:53)

I2C: ready

DRAM: 512 MiB

WARNING: Caches not enabled

timed out in wait_for_pin: I2C_STAT=0

Could not probe the EEPROM; something fundamentally wrong on the I2C bus.

Could not get board ID.

NAND: No NAND device found!!!

0 MiB

MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1

*** Warning - readenv() failed, using default environment

musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
SoftConn)

musb-hdrc: MHDRC RTL version 2.0

musb-hdrc: setup fifo_mode 4

musb-hdrc: 28/31 max ep, 16384/16384 memory

USB Peripheral mode controller at 47401000 using PIO, IRQ 0

musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
SoftConn)

musb-hdrc: MHDRC RTL version 2.0

musb-hdrc: setup fifo_mode 4

musb-hdrc: 28/31 max ep, 16384/16384 memory

USB Host mode controller at 47401800 using PIO, IRQ 0

Net: <ethaddr> not set. Validating first E-fuse MAC

cpsw, usb_ether

Hit any key to stop autoboot: 0

gpio: pin 53 (gpio 53) value is 1

Card did not respond to voltage select!

mmc0(part 0) is current device

Card did not respond to voltage select!

No micro SD card found, setting mmcdev to 1

mmc_send_cmd : timeout: No status update

mmc1(part 0) is current device

gpio: pin 54 (gpio 54) value is 1

SD/MMC found on device 1

reading uEnv.txt

26 bytes read in 3 ms (7.8 KiB/s)

Loaded environment from uEnv.txt

Importing environment from mmc ...

gpio: pin 55 (gpio 55) value is 1

4385024 bytes read in 768 ms (5.4 MiB/s)

gpio: pin 56 (gpio 56) value is 1

24808 bytes read in 54 ms (448.2 KiB/s)

Booting from mmc ...

## Booting kernel from Legacy Image at 80007fc0 ...

   Image Name: Angstrom/3.8.13/beaglebone

   Image Type: ARM Linux Kernel Image (uncompressed)

   Data Size: 4384960 Bytes = 4.2 MiB

   Load Address: 80008000

   Entry Point: 80008000

   Verifying Checksum ... OK

## Flattened Device Tree blob at 80f80000

   Booting using the fdt blob at 0x80f80000

   XIP Kernel Image ... OK

OK

   Using Device Tree in place at 80f80000, end 80f890e7

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

[ 1.148261] omap_i2c 44e0b000.i2c: controller timed out

[ 1.148304] tps65217 0-0024: Failed to read INT reg

[ 1.148322] tps65217 0-0024: Failed to probe pwr_but

[ 2.148252] omap_i2c 44e0b000.i2c: controller timed out

[ 3.152151] omap_i2c 44e0b000.i2c: controller timed out

[ 3.182788] omap2_mbox_probe: platform not supported

[ 4.246560] omap_i2c 44e0b000.i2c: controller timed out

[ 5.254176] omap_i2c 44e0b000.i2c: controller timed out

[ 6.767826] omap_i2c 44e0b000.i2c: controller timed out

[ 7.779563] omap_i2c 44e0b000.i2c: controller timed out

[ 9.293213] omap_i2c 44e0b000.i2c: controller timed out

[ 10.305060] omap_i2c 44e0b000.i2c: controller timed out

[ 11.818596] omap_i2c 44e0b000.i2c: controller timed out

[ 12.830340] omap_i2c 44e0b000.i2c: controller timed out

It again looks like something is hanging on your I2C bus besides the
EEPROM. It is conceivable the board has been damaged, but I'm more
suspicious of something hanging on the lines.

Similarly when I try to boot the board using Ubuntu on SD Card I see the
following message:

▒m▒▒▒▒`▒▒▒`rpqsnqpmpprtym▒qu▒u▒▒▒`h▒▒▒`qw@rpqs`m`qvzsuzqqi

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

Yup, all of this points to problems reading the on-board EEPROM more than
it just being corrupted. It is possible to reprogram it, but it just looks
like you can't even access it. What else has been done to this board?

__

Can any of you Guys figure out what is the problem? and how to fix it?
Thanks in Advance for your solution.

You'd need to probe the I2C pins to see if they are toggling or if
something has them strapped. There are many dependencies that would be a
pain to remove if you weren't able to fix the ability to read the EEPROM.

Thanks for the quick support Jason. Since, I didn’t get any reply from any of your support team for last few days, I posted a new post at http://beagleboard.org/Community/Forums?place=topic%2Fbeagleboard%2FyLAbudOgAIU%2Fdiscussion

And Robert has entered the discussion. Kindly take a look at it to know what I tried after this.

And which support team is that?

Gerald

I don’t know Gerald. There must be a team of members who will be working for support. Do you have any idea on what the issue with my board is, any idea on how to fix it.

All support is community based. There is a support email address and that comes to me. I see one email per month at that address.

Sounds like the board is damaged to me or the EEPROM has been overwritten… My suggestion is that you request an RMA so that we can take a look at the board to see what is wrong…

http://www.elinux.org/Beagleboard:BeagleBoneBlack#RMA_Support

Gerald

Ok, now I understand about the support. Is there no other way or option that I can try to fix it myself. I will take a look into RMA. Thanks for the reply.

Well, considering the fact I have no idea what the issue is, that would be rather hard to do.

Gerald

Ok Gerald. Thanks for the support.