Unable to login on BeagleBone Black Rev C

[BBuser]

Hello there

I bought a new BeagleBone Black Rev C from Amazon last week and I am unable to login using the default username and password. Following is the output from Minicom to help you understand my issue:

I have not connected any Ethernet cable and I also tried connecting an Ethernet cable but unfortunately the same problem persists.

Can someone help me debug this issue. Thank you !

Welcome to minicom 2.7

OPTIONS: I18n 

Compiled on Feb  7 2016, 13:37:27.

Port /dev/ttyUSB0, 18:06:18

Press CTRL-A Z for help on special keys

U-Boot SPL 2015.10-00001-g143c9ee (Nov 06 2015 - 15:27:19)

bad magic

U-Boot 2015.10-00001-g143c9ee (Nov 06 2015 - 15:27:19 -0600), Build: jenkins-github_Bootloader-Builder-274

       Watchdog enabled

I2C:   ready

DRAM:  512 MiB

Reset Source: Global external warm reset has occurred.

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

Hit any key to stop autoboot:  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 ...

Checking for: /boot.scr ...

Checking for: /boot/boot.scr ...

Checking for: /boot/uEnv.txt ...

** Invalid partition 2 **

** Invalid partition 3 **

** Invalid partition 4 **

** Invalid partition 5 **

** Invalid partition 6 **

** Invalid partition 7 **

gpio: pin 56 (gpio 56) value is 0

gpio: pin 55 (gpio 55) value is 0

gpio: pin 54 (gpio 54) value is 0

switch to partitions #0, OK

mmc1(part 0) is current device

gpio: pin 54 (gpio 54) value is 1

Checking for: /uEnv.txt ...

Checking for: /boot.scr ...

Checking for: /boot/boot.scr ...

Checking for: /boot/uEnv.txt ...

gpio: pin 55 (gpio 55) value is 1

1800 bytes read in 15 ms (117.2 KiB/s)

Loaded environment from /boot/uEnv.txt

Checking if uname_r is set in /boot/uEnv.txt...

gpio: pin 56 (gpio 56) value is 1

Running uname_boot ...

loading /boot/vmlinuz-3.8.13-bone79 ...

5644336 bytes read in 326 ms (16.5 MiB/s)

loading /boot/dtbs/3.8.13-bone79/am335x-boneblack.dtb ...

26118 bytes read in 21 ms (1.2 MiB/s)

loading /boot/initrd.img-3.8.13-bone79 ...

2862929 bytes read in 174 ms (15.7 MiB/s)

debug: [console=ttyO0,115200n8 root=UUID=e9dd472d-cc3d-45bd-85a9-633f3fd8ff0f ro rootfstype=ext4 rootwait coherent_pool=1M quiet init=/lib/systemd/systemd cape_.

debug: [bootz 0x82000000 0x88080000:2baf51 0x88000000] ...

Kernel image @ 0x82000000 [ 0x000000 - 0x562030 ]

## Flattened Device Tree blob at 88000000

   Booting using the fdt blob at 0x88000000

   Loading Ramdisk to 8fd45000, end 8fffff51 ... OK

   Loading Device Tree to 8fd3b000, end 8fd44605 ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

[    0.372380] omap2_mbox_probe: platform not supported

[    0.528145] tps65217-bl tps65217-bl: no platform data provided

[    0.592204] bone-capemgr bone_capemgr.9: slot #0: No cape found

[    0.629312] bone-capemgr bone_capemgr.9: slot #1: No cape found

[    0.666420] bone-capemgr bone_capemgr.9: slot #2: No cape found

[    0.703529] bone-capemgr bone_capemgr.9: slot #3: No cape found

[    0.719264] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)

[    0.728821] bone-capemgr bone_capemgr.9: slot #6: Failed verification

[    0.735548] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)

[    0.752188] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed

[    0.815138] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8

[    0.826792] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22

[    0.834057] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single

Loading, please wait...

systemd-fsck[216]: rootfs: clean, 97227/227584 files, 514831/909056 blocks

Debian GNU/Linux 7 beaglebone ttyO0

BeagleBoard.org Debian Image 2015-11-12

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: [   26.200534] libphy: PHY 4a101000.mdio:01 not found

[   26.205594] net eth0: phy 4a101000.mdio:01 not found on slave 1

[Dennis Lee Bieber]

On Sat, 3 Dec 2016 19:12:30 -0800 (PST), BBuser
<get...@gmail.com> declaimed the following:

>Hello there
>
>I bought a new BeagleBone Black Rev C from Amazon last week and I am unable

You may have bought it through Amazon, but I doubt they were the actual
seller. If you include the one with a case, there are presently three
different dealers providing them (none of which are the dealer mine came
through last year). There are also a few companies manufacturing them...

>
>U-Boot SPL 2015.10-00001-g143c9ee (Nov 06 2015 - 15:27:19)
>bad magic
>
>
>U-Boot 2015.10-00001-g143c9ee (Nov 06 2015 - 15:27:19 -0600), Build:
>jenkins-github_Bootloader-Builder-274
>
> Watchdog enabled
>I2C: ready
>DRAM: 512 MiB
>Reset Source: Global external warm reset has occurred.
>Reset Source: Power-on reset has occurred.
>MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
>Using default environment

<SNIP>

How are you actually connecting to the device?

I've never seen boot output on mine* -- but that could be because I've
only Putty via either the USB connection, or over the Ethernet (preferred
as Ethernet means it can do NTP update for time/date), and by the time
those protocols are active, the system has booted. I thought the boot
output only came through if you connect an FTDI serial debug cable to the
debug pins.

Given the 2015 dates... You might want to download and write to a 4GB
(minimum) microSD card one of the current images

https://debian.beagleboard.org/images/bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb.img.xz

insert it, and boot from the card (only convert it to a flasher when you
know you've gotten it to work).

You should just need a USB cable -- sufficient for power and providing
a SSH on (Blast -- had a disk crash, and it looks like my rebuild did not
carry the Putty configurations across so I don't have easy access to the IP
number for the USB).
--
Wulfraed Dennis Lee Bieber AF6VN
wlf...@ix.netcom.com HTTP://wlfraed.home.netcom.com/

[Dennis Lee Bieber]

On Sun, 04 Dec 2016 13:56:45 -0500, Dennis Lee Bieber
<wlf...@ix.netcom.com> declaimed the following:

> I've never seen boot output on mine* -- but that could be because I've

forgot to add the footnote:


* Maybe on the one or two times I used a USB keyboard/mouse and had it on
HDMI to a TV... Then it may have shown the boot output.