[bone-debian-8.4-iot-armhf-2016-05-13] Unable to connect via SSH with fresh image

I downloaded a new image (bone-debian-8.4-iot-armhf-2016-05-13-4gb) and wrote it to an SD card using Win32DiskImager. I know this is a very old image, I have some software written for that version which is incompatible due to changes to the cape manager related stuff. I don’t have the time to update it yet.

I then inserted it into a Beaglebone Black and powered on holding the S2 button. As expected the board booted onto the SD card. The lights are behaving normally, I can access the “Getting Started” drive. However, I am unable to SSH to or even ping ‘192.168.7.2’. I have been able to communicate via the JTAG serial header.

I have flashed (bone-eMMC-flasher-debian-10.3-iot-armhf-2020-04-06-4gb) onto the same board and had no issues. There is nothing wrong with the Beaglebone, the cables, or any other hardware.

The following is the JTAG output on boot to Debian 8.

    U-Boot SPL 2016.03-00001-gd12d09f (Mar 17 2016 - 16:16:15)
Trying to boot from MMC
bad magic


U-Boot 2016.03-00001-gd12d09f (Mar 17 2016 - 16:16:15 -0500), Build: jenkins-github_Bootloader-Builder-351

       Watchdog enabled
I2C:   ready
DRAM:  512 MiB
Reset Source: Power-on reset has occurred.
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
1179 bytes read in 7 ms (164.1 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 ...
1197 bytes read in 41 ms (28.3 KiB/s)
debug: [/boot/vmlinuz-4.4.9-ti-r25] ...
7833256 bytes read in 469 ms (15.9 MiB/s)
debug: [/boot/initrd.img-4.4.9-ti-r25] ...
4550796 bytes read in 284 ms (15.3 MiB/s)
debug: [/boot/dtbs/4.4.9-ti-r25/am335x-boneblack.dtb] ...
60958 bytes read in 61 ms (975.6 KiB/s)
debug: [console=tty0 console=ttyO0,115200n8 root=/dev/mmcblk0p1 rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable] ...
debug: [bootz 0x82000000 0x88080000:45708c 0x88000000] ...
Kernel image @ 0x82000000 [ 0x000000 - 0x7786a8 ]
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Using Device Tree in place at 88000000, end 88011e1d

Starting kernel ...

[    1.990552] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[    2.161414] omap_voltage_late_init: Voltage driver support not added
[    2.168852] PM: Cannot get wkup_m3_ipc handle
[    2.281318] bone_capemgr bone_capemgr: slot #0: No cape found
[    2.325284] bone_capemgr bone_capemgr: slot #1: No cape found
[    2.369303] bone_capemgr bone_capemgr: slot #2: No cape found
[    2.413279] bone_capemgr bone_capemgr: slot #3: No cape found
Loading, please wait...
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mmcblk0p1
fsck exited with status code 8
[   10.080244] systemd-fsck[156]: rootfs: clean, 106009/217728 files, 458745/870144 blocks
[   16.737033]  remoteproc1: failed to load am335x-pru0-fw
[   16.774666]  remoteproc1: request_firmware failed: -2
[   16.779973] pru-rproc 4a334000.pru0: rproc_boot failed
[   17.279045]  remoteproc1: failed to load am335x-pru1-fw
[   17.306166]  remoteproc1: request_firmware failed: -2
[   17.311465] pru-rproc 4a338000.pru1: rproc_boot failed
[   19.643988] platform 48300180.eqep: Cannot lookup hwmod 'eqep0'
[   19.690678] platform 48302180.eqep: Cannot lookup hwmod 'eqep1'
[   19.727236] platform 48304180.eqep: Cannot lookup hwmod 'eqep2'
[   20.349709] eqep 48300180.eqep: failed to get clock
[   20.476400] eqep 48302180.eqep: failed to get clock
[   20.573840] eqep 48304180.eqep: failed to get clock

Debian GNU/Linux 8 beaglebone ttyS0

BeagleBoard.org Debian Image 2016-05-13

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

The IP Address for usb0 is: 192.168.7.2
beaglebone login:

On that old image try dumping:

journalctl | grep am335x_evm

Regards,

output of journalctl | grep am335x_evm

May 13 18:44:41 beaglebone sh[298]: generic-board-startup: [startup script=/opt/scripts/boot/am335x_evm.sh]

I have been able to reach the Beaglebone! However, have had no luck over usb0.

I logged into debian:temppwd over the JTAG serial connector as previously described. Then I just ran ifconfig and established an ssh connection to the address printed there.

Still unable to diagnose why I am unable to do so via USB at 192.168.7.2.

Just took some time to experiment; 8.7 (2016-12-09) and above work, 8.6 (2017-03-19) does not.

so, /opt/scripts/ is a git repo, you ‘can’ try git pull’ing in it, but honestly it’ll probably break 2016.05.13 more then in fixes it so prepare to reflash…

Regards,