Boot failure after running bbb-eMMC-flasher-eewiki-ext4.sh

Embedded Linux Discussions
1

I built a successful SD card to boot from as per: https://www.digikey.com/eewiki/display/linuxonarm/BeagleBone+Black, but after running the eMMC script, the resultant boot fails from the eMMC (with the SD plugged in or not):

    U-Boot 2020.04-rc3-00132-gdb3b1818b7-dirty (Jun 25 2020 - 13:20:47 -0700)

    CPU  : AM335X-GP rev 2.1
    Model: TI AM335x BeagleBone Black
    DRAM:  512 MiB
    WDT:   Started with servicing (60s timeout)
    NAND:  0 MiB
    MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
    Loading Environment from FAT... Unable to use mmc 0:1... <ethaddr> not set. Validating first E-fuse MAC
    Net:   eth0: ethernet@4a100000
    Warning: usb_ether MAC addresses don't match:
    Address in ROM is          de:ad:be:ef:00:01
    Address in environment is  00:35:ff:8f:b6:c9
    , eth1: usb_ether
    Hit any key to stop autoboot:  0
    => mmc dev 0
    switch to partitions #0, OK
    mmc0 is current device
    => boot
    switch to partitions #0, OK
    mmc0 is current device
    SD/MMC found on device 0
    ** Unrecognized filesystem type **
    switch to partitions #0, OK
    mmc0 is current device
    Scanning mmc 0:1...
    switch to partitions #0, OK
    mmc0 is current device
    SD/MMC found on device 0
    ** Invalid partition 2 **
    switch to partitions #0, OK
    mmc1(part 0) is current device
    Scanning mmc 1:1...
    switch to partitions #0, OK
    mmc1(part 0) is current device
    SD/MMC found on device 1
    ** Invalid partition 2 **
    ## Error: "bootcmd_nand0" not defined
    starting USB...
    Bus usb@47401800: Port not available.
    link up on port 0, speed 100, full duplex
    BOOTP broadcast 1
    DHCP client bound to address 192.168.1.24 (109 ms)
    *** ERROR: `serverip' not set
    Cannot autoload with TFTPGET
    missing environment variable: pxeuuid
    Retrieving file: pxelinux.cfg/01-00-35-ff-8f-b6-c7
    link up on port 0, speed 100, full duplex
    *** ERROR: `serverip' not set
    Retrieving file: pxelinux.cfg/C0A80118
    link up on port 0, speed 100, full duplex
    *** ERROR: `serverip' not set
    Retrieving file: pxelinux.cfg/C0A8011
    link up on port 0, speed 100, full duplex
    *** ERROR: `serverip' not set
    Retrieving file: pxelinux.cfg/C0A801
    link up on port 0, speed 100, full duplex
    *** ERROR: `serverip' not set
    Retrieving file: pxelinux.cfg/C0A80
    link up on port 0, speed 100, full duplex
    *** ERROR: `serverip' not set
    Retrieving file: pxelinux.cfg/C0A8
    link up on port 0, speed 100, full duplex
    *** ERROR: `serverip' not set
    Retrieving file: pxelinux.cfg/C0A
    link up on port 0, speed 100, full duplex
    *** ERROR: `serverip' not set
    Retrieving file: pxelinux.cfg/C0
    link up on port 0, speed 100, full duplex
    *** ERROR: `serverip' not set
    Retrieving file: pxelinux.cfg/C
    link up on port 0, speed 100, full duplex
    *** ERROR: `serverip' not set
    Retrieving file: pxelinux.cfg/default-arm-am33xx-am335x
    link up on port 0, speed 100, full duplex
    *** ERROR: `serverip' not set
    Retrieving file: pxelinux.cfg/default-arm-am33xx
    link up on port 0, speed 100, full duplex
    *** ERROR: `serverip' not set
    Retrieving file: pxelinux.cfg/default-arm
    link up on port 0, speed 100, full duplex
    *** ERROR: `serverip' not set
    Retrieving file: pxelinux.cfg/default
    link up on port 0, speed 100, full duplex
    *** ERROR: `serverip' not set
    Config file not found
    starting USB...
    Bus usb@47401800: Port not available.
    link up on port 0, speed 100, full duplex
    BOOTP broadcast 1
    DHCP client bound to address 192.168.1.24 (263 ms)
    *** ERROR: `serverip' not set
    Cannot autoload with TFTPGET
    link up on port 0, speed 100, full duplex
    BOOTP broadcast 1
    BOOTP broadcast 2
    DHCP client bound to address 192.168.1.24 (653 ms)
    *** ERROR: `serverip' not set
    Cannot autoload with TFTPGET
    =>

I’m now in limbo because I can no longer boot from either the SD card or the eMMC. Is there a way to overcome this issue?

Ted

2

We still only ship v2019.04 for beagleboard.org , for u-boot after that point you lose ethernet with the classic “board” method. I’d like to move to a later version, but still need to do a ton of testing on every BeagleBoard variant to fully support the latest u-boot release (which utilize a built-in device-tree).

Hold the “boot” button with your finger nail, insert power, once 1 LED turns on, you can release your finger nail… In that mode, it’ll boot off microSD… If your finger can’t handle it, that same i/o is on the header, just run a quick wire and gnd the pin. (it’s in the BeagleBoard SRM)

Regards,

3

I was able to use u-boot’s ‘mmc erase’ command (e.g., dev mmc 1, mmc erase 0 0x400) to clear the eMMC and boot back to my working SD card.

(Now back to figuring out why the eMMC script not worky)