bencrosby Posted January 25, 2016 Report Share Posted January 25, 2016 Hi, I have had a series of power problems that have resulted in my PBX mini (beagle bone) no longer joining the network. It boots fine, and is accessible via the serial port on board, but doesn't bring up a network interface. There are a few interesting error messages during boot, but I have no idea if they are normal. Could you provide a link via pm to re-download the image so I can re-flash the mmc ? Alternatively, if you can see the issue from the log below, please let me know how to resolve. Thanks Here is the boot log pasted below: U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53) 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 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 mmc_send_cmd : timeout: No status update 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 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 4 ms (5.9 KiB/s) Loaded environment from uEnv.txt Importing environment from mmc ... gpio: pin 55 (gpio 55) value is 1 4394080 bytes read in 763 ms (5.5 MiB/s) gpio: pin 56 (gpio 56) value is 1 24884 bytes read in 47 ms (516.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 80f89133 Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.195888] omap2_mbox_probe: platform not supported [ 0.206562] tps65217-bl tps65217-bl: no platform data provided [ 0.283025] bone-capemgr bone_capemgr.9: slot #0: No cape found [ 0.320132] bone-capemgr bone_capemgr.9: slot #1: No cape found [ 0.357240] bone-capemgr bone_capemgr.9: slot #2: No cape found [ 0.394350] bone-capemgr bone_capemgr.9: slot #3: No cape found [ 0.414181] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI) [ 0.423792] bone-capemgr bone_capemgr.9: slot #6: Failed verification [ 0.444301] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed [ 0.451601] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2) [ 0.519876] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8 [ 0.531613] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22 [ 0.538995] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single systemd-fsck[85]: Angstrom: clean, 41960/112672 files, 359580/449820 blocks [ 4.867688] libphy: PHY 4a101000.mdio:01 not found [ 4.872761] net eth0: phy 4a101000.mdio:01 not found on slave 1 .---O---. | | .-. o o | | |-----.-----.-----.| | .----..-----.-----. | | | __ | ---'| '--.| .-'| | | | | | | | |--- || --'| | | ' | | | | '---'---'--'--'--. |-----''----''--' '-----'-'-'-' -' | '---' The Angstrom Distribution pbx ttyO0 Angstrom v2012.12 - Kernel 3.8.13 pbx login: root Password: Last login: Sat Jan 1 11:00:30 EST 2000 on ttyO0 root@pbx:~# Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 25, 2016 Report Share Posted January 25, 2016 After all, it is just a Beagle Bone... The network has not much to do with the PBX service, which is probably running "fine" except that it cannot talk to anybody. So anything you can find about the beagle bone would apply here. My guess would be that somehow the Ethernet chip got damaged with a power spike. Do you see the connectivity LED come up on the Ethernet switch? Can you ping anything in the network? If you can get to the console, you might be able to tar the PBX working directory and e.g. write it to a SD card. Then you can resume backup on another physical hardware. Quote Link to comment Share on other sites More sharing options...
bencrosby Posted January 27, 2016 Author Report Share Posted January 27, 2016 Yup, I have backed up the working directory. I guess I can just reinstall angstrom and put back the pbx directory. Is there any documentation for startup / shutdown scripts etc anywhere ? Thanks ! Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 29, 2016 Report Share Posted January 29, 2016 We can send you the script that we are using in a private message. Quote Link to comment Share on other sites More sharing options...
bencrosby Posted February 7, 2016 Author Report Share Posted February 7, 2016 Thanks, That was perfect, all restored. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.