stuck in boot loop unable to flash new images and ssh displays network busy

hi members

my BBB is stuck in boot mode i am unable to login in ssh its displays as network busy

i tried flashing new images but it does not read the sd card … it was non responsive for 4 hrs :frowning:

any solution ?

Update 1

I have tried logging into debugging port and walla it works but i am not able to ssh to my computer and update the image through an uSD card

Any solution ? can i update the os through debugging ?

This is my output which i got

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

I2C: ready
DRAM: 512 MiB
WARNING: Caches not enabled
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
mmc_send_cmd : timeout: No status update
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
mmc_send_cmd : timeout: No status update
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
4394080 bytes read in 770 ms (5.4 MiB/s)
gpio: pin 56 (gpio 56) value is 1
24808 bytes read in 30 ms (806.6 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: 4394016 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.
[ 0.195496] omap2_mbox_probe: platform not supported
[ 0.206237] tps65217-bl tps65217-bl: no platform data provided
[ 0.282681] bone-capemgr bone_capemgr.8: slot #0: No cape found
[ 0.319787] bone-capemgr bone_capemgr.8: slot #1: No cape found
[ 0.356896] bone-capemgr bone_capemgr.8: slot #2: No cape found
[ 0.394005] bone-capemgr bone_capemgr.8: slot #3: No cape found
[ 0.413791] bone-capemgr bone_capemgr.8: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)
[ 0.423406] bone-capemgr bone_capemgr.8: slot #6: Failed verification
[ 0.443901] omap_hsmmc mmc.4: of_parse_phandle_with_args of β€˜reset’ failed
[ 0.451245] bone-capemgr bone_capemgr.8: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 0.519516] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.7
[ 0.531256] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.7) status -22
[ 0.538627] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
systemd-fsck[85]: Angstrom: clean, 49723/235248 files, 341964/939802 blocks
[ 6.044780] libphy: PHY 4a101000.mdio:01 not found
[ 6.049840] net eth0: phy 4a101000.mdio:01 not found on slave 1

.β€”O---.

.-. o o

-----.-----.-----.| | .----…-----.-----.
__ | —’| β€˜β€“.| .-’| | |

β€” || --’| | | ’ | | | |
β€˜β€”β€™---’–’--’–. |-----’’----’’–’ β€˜-----’-’-’-’
-’ |
β€˜β€”β€™

The Angstrom Distribution beaglebone ttyO0

Angstrom v2012.12 - Kernel 3.8.13

The above may be your problem. On BBB v. B running the same default
shipped Angstrom version as you I get exactly the same message. If I
unplug the Ethernet cable and then plug it back again it solves the
problem of network connectivity. I don't know what the root cause is.

I would suggest that you upgrade to Debian. It is much better than
Angstrom and I don't get that problem with it.

well.. mdio.01 would work, if you hacked up the board layout and added
a 2nd ethernet jack..

Regards

I had a new problem today on my BBB rev. B. I noticed it had stopped
working. It turned out that the MicroSD card had moved somewhere
between 0.5 and 1 mm out of its place and there was bad contact. The
lock in the card cage is not locking properly anymore. I talked with a
colleague that is a hardware developer and he said that replacing the
cage is possible but tricky.

I suggest that you make sure that the card is well inserted - and does not move.

Thanks for the explanation.

So that debug message is unrelated to the issue of this thread. Do you
have some idea why unplugging and plugging back the cable with fix
networking? I have not changed the configuration, so it is in DHCP
mode.

Well, it's an image from 2013, it's got lots of issues, time to just
let it die in peace..

Regards,