Hi guys, I appreciate your support. Sorry for the delay as I had to format my PC and get my FTDI cable to debug BBB. Once again, I installed Debian (bone-debian-7.5-2014-05-14-2gb'- BBB eMMC flasher) on BBB. I followed the flashing procedures properly (since it worked for the 1st time), but now all the user LED go black after around 20 minutes of flashing process and it does not become ON again. Also, I used the serial debug cable during flashing process. Below is the serial console output and I am not sure what the problem is.
U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) reading args spl_load_image_fat_os: error reading image args, err - -1 reading u-boot.img reading u-boot.img U-Boot 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - readenv() failed, using default environment 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 mmc0 is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 0 reading uEnv.txt 1672 bytes read in 7 ms (232.4 KiB/s) gpio: pin 55 (gpio 55) value is 1 Loaded environment from uEnv.txt Importing environment from mmc ... Checking if uenvcmd is set ... gpio: pin 56 (gpio 56) value is 1 Running uenvcmd ... reading zImage 4103240 bytes read in 641 ms (6.1 MiB/s) reading initrd.img 2952634 bytes read in 270 ms (10.4 MiB/s) reading /dtbs/am335x-boneblack.dtb 25926 bytes read in 14 ms (1.8 MiB/s) Kernel image @ 0x82000000 [ 0x000000 - 0x3e9c48 ] ## Flattened Device Tree blob at 88000000 Booting using the fdt blob at 0x88000000 Using Device Tree in place at 88000000, end 88009545 Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.378647] omap2_mbox_probe: platform not supported [ 0.533261] tps65217-bl tps65217-bl: no platform data provided [ 0.596968] bone-capemgr bone_capemgr.9: slot #0: No cape found [ 0.634078] bone-capemgr bone_capemgr.9: slot #1: No cape found [ 0.671185] bone-capemgr bone_capemgr.9: slot #2: No cape found [ 0.708293] bone-capemgr bone_capemgr.9: slot #3: No cape found [ 0.722947] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI) [ 0.732573] bone-capemgr bone_capemgr.9: slot #6: Failed verification [ 0.739329] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2) [ 0.756886] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed [ 0.819905] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8 [ 0.831594] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22 [ 0.838874] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single Loading, please wait... Scanning for Btrfs filesystems systemd-fsck[211]: eMMC-Flasher: clean, 78783/102752 files, 390214/410368 blocks Debian GNU/Linux 7 beaglebone ttyO0 default username:password is [debian:temppwd] Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian The IP Address for usb0 is: 192.168.7.2 beaglebone login: [ 29.136538] libphy: PHY 4a101000.mdio:01 not found [ 29.141713] net eth0: phy 4a101000.mdio:01 not found on slave 1 Sending SIGTERM to remaining processes... Sending SIGKILL to remaining processes. Unmounting file systems. Unmounted /sys/fs/fuse/connections. Unmounted /sys/kernel/debug. Unmounted /dev/mqueue. Unmounted /sys/kernel/security. Disabling swaps. Detaching loop devices. Detaching DM devices. [ 930.522071] (NULL device *): gadget not registered. [ 930.536657] Power down. [ 930.541957] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000 [ 930.541957] [ 930.551748] [<c00111f1>] (unwind_backtrace+0x1/0x9c) from [<c04c8955>] (panic +0x59/0x158) [ 930.560473] [<c04c8955>] (panic+0x59/0x158) from [<c00336ff>] (do_exit+0x5ff/0x68c) [ 930.568648] [<c00336ff>] (do_exit+0x5ff/0x68c) from [<c003dc5d>] (sys_reboot+0x105/0x15c) [ 930.577372] [<c003dc5d>] (sys_reboot+0x105/0x15c) from [<c000c841>] (ret_fast_syscall+0x1/0x46) [ 930.586637] drm_kms_helper: panic occurred, switching back to text console Even though all the LED's did not light up after flashing, I removed the power and microSD card to check whether eMMC has flashed properly. It seemed to work but I am not able to ping google or access internet in BBB. SSH - output root@beaglebone:/home/debian# route add default gw 192.168.7.1 root@beaglebone:/home/debian# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.7.1 0.0.0.0 UG 0 0 0 usb0 192.168.7.0 0.0.0.0 255.255.255.252 U 0 0 0 usb0 root@beaglebone:/home/debian# cat /etc/resolv.conf domain localdomain search localdomain nameserver 192.168.1.1 root@beaglebone:/home/debian# vim /etc/resolv.conf root@beaglebone:/home/debian# cat /etc/resolv.conf domain localdomain search localdomain nameserver 8.8.8.8 root@beaglebone:/home/debian# ping http://www.google.com ping: unknown host http://www.google.com root@beaglebone:/home/debian# Tests done as in this post *("Cannot ping google in BBB even after sharing internet")* Q2)Can you ping the ip address assigned to the usb0 interface (192.168.7.2)? If not then there is something not configured properly on your usb0 interface. Check the /etc/network/interfaces file to make sure the entry for usb0 is correct. Yes, it pings with 192.168.7.2 ( pings in SSH of putty) Q3) Can you ping the ip address of the PC's link interface (192.168.7.1)? If you can not ping the PC link interface address then there is something incorrectly configured on that interface - double check the interface settings to make sure the assigned IP address & netmask address is set correctly. >From BBB, I cannot ping 192.168.7.1 but I can ping the same from PC command line. Q4) From the PC can you ping the link interface (192.168.7.1)? If not there is something wrong with the link interface configuration. Yes, I can. ( in Cmd line of windows 7) Q5) From the PC can you ping the BeagleBone usb0 interface (192.168.7.2)? If not double-check the usb0 interface config Yes, I can. ( in Cmd line of windows 7) Q6) Can you ping the PC's network bridged IP address (the interface you have bridged over to the usb link interface on the PC)? If not make sure you have the bridging setup properly on the PC interfaces. Do I need to bridge the connections of my Wifi LAN adapter and BBB USB ethernet ? (as I only shared it as the previous youtube video). If I bridge it, I am not able to set any IP address for BBB in PC network settings. Q7) Can you ping the PC's default gateway IP address? I am able to ping the ipv4 address 192.168.1.36 (which is my PC's Wifi LAN adapter) from BBB. I am also able to ping 192.168.1.254 ( which is PC Wifi LAN's default gateway) fromm BBB My Wireless LAN adapter Wireless Network Connection details in command line: Connection-specific DNS Suffix . : IPv6 Address. . . . . . . . . . . : 2a01:e35:2eb7:8e10:24be:1ca6:da86:591b Temporary IPv6 Address. . . . . . : 2a01:e35:2eb7:8e10:5950:bc3c:4a70:4ffd Link-local IPv6 Address . . . . . : fe80::24be:1ca6:da86:591b%13 IPv4 Address. . . . . . . . . . . : 192.168.1.36 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : fe80::224:d4ff:fea6:5c0d%13 192.168.1.254 In above, subnet Mask is 255.255.255.0. But in BBB, its 255.255.255.252 as below. Will this be a problem for BBB not able to access internet? Do I need to set 255.255.255.0 as GenMask in BBB for gateway 192.168.7.1 ? Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.7.1 0.0.0.0 UG 0 0 0 usb0 192.168.7.0 0.0.0.0 255.255.255.252 U 0 0 0 usb0 Whatever I do, BBB LAN shows 'No internet access'in Network connections settings of Windows 7. Please help me as I have stuck in this for a very long time. Thanks in advance!! -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
