I flashed the board and the problem persist. I dont have any board attached it.
The boot loader appear some problems related to the i2c: -Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14) 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 reading u-boot.img reading u-boot.img U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14) 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 Any ideia? Regards On Thursday, April 17, 2014 6:50:50 PM UTC-3, João Paulo wrote: > > Hi, > > Suddenly my bealgebone stop booting. > The log message is: > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > [ 1.156059] omap_i2c 44e0b000.i2c: controller timed out > [ 1.156104] tps65217 0-0024: Failed to read INT reg > [ 1.156123] tps65217 0-0024: Failed to probe pwr_but > [ 2.156056] omap_i2c 44e0b000.i2c: controller timed out > [ 3.159960] omap_i2c 44e0b000.i2c: controller timed out > [ 3.192906] omap2_mbox_probe: platform not supported > [ 4.262857] omap_i2c 44e0b000.i2c: controller timed out > [ 5.272375] omap_i2c 44e0b000.i2c: controller timed out > [ 6.786039] omap_i2c 44e0b000.i2c: controller timed out > [ 7.797989] omap_i2c 44e0b000.i2c: controller timed out > [ 9.311445] omap_i2c 44e0b000.i2c: controller timed out > [ 10.323312] omap_i2c 44e0b000.i2c: controller timed out > [ 11.836824] omap_i2c 44e0b000.i2c: controller timed out > [ 12.848568] omap_i2c 44e0b000.i2c: controller timed out > [ 14.362226] omap_i2c 44e0b000.i2c: controller timed out > [ 15.373935] omap_i2c 44e0b000.i2c: controller timed out > [ 16.887705] omap_i2c 44e0b000.i2c: controller timed out > [ 17.899350] omap_i2c 44e0b000.i2c: controller timed out > [ 19.413079] omap_i2c 44e0b000.i2c: controller timed out > [ 20.424713] omap_i2c 44e0b000.i2c: controller timed out > [ 21.938389] omap_i2c 44e0b000.i2c: controller timed out > [ 22.950188] omap_i2c 44e0b000.i2c: controller timed out > [ 24.463792] omap_i2c 44e0b000.i2c: controller timed out > [ 25.475572] omap_i2c 44e0b000.i2c: controller timed out > [ 26.989170] omap_i2c 44e0b000.i2c: controller timed out > [ 28.000916] omap_i2c 44e0b000.i2c: controller timed out > [ 28.514549] bone-capemgr bone_capemgr.8: Failed to scan baseboard eeprom > [ 28.539322] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' > failed > [ 28.575588] pinctrl-single 44e10800.pinmux: pin 44e10854 already > requested by 44e10800.pinmux; cannot claim for gpio-leds.7 > [ 28.587309] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.7) status > -22 > [ 28.594619] pinctrl-single 44e10800.pinmux: could not request pin 21 on > device pinctrl-single > [ 28.672322] cpufreq_cpu0: failed to scale voltage up: -22 > [ 28.678238] cpufreq_cpu0: failed to scale voltage up: -22 > [ 28.971626] hub 1-0:1.0: unable to enumerate USB device on port 1 > > > I dont have any device connected in the USB. > > any idea? > > 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
