Open lilyjayd opened 1 year ago
Hello again,
I think I have found a root cause of this problem. The thing is that in the instruction we copy combined uboot and dtb file to SD card:
sudo mkdir -p /media/rootfs/opt/backup/uboot/
sudo cp -v ./u-boot/MLO /media/rootfs/opt/backup/uboot/
sudo cp -v ./u-boot/u-boot-dtb.img /media/rootfs/opt/backup/uboot/
but the script is looking for u-boot.img, not u-boot-dtb.img which we copied to SD card:
if [ ! -f /opt/backup/uboot/u-boot.img ] ; then
mkdir -p /opt/backup/uboot/
wget --directory-prefix=/opt/backup/uboot/ http://rcn-ee.com/repos/bootloader/am335x_evm/${http_uboot}
mv /opt/backup/uboot/${http_uboot} /opt/backup/uboot/u-boot.img
fi
and since it did not find u-boot.img, it will download and install image from rcn-ee.com, as we an see in my session log:
113246208 bytes (113 MB, 108 MiB) copied, 2.85152 s, 39.7 MB/s
Erasing: /dev/mmcblk1 complete
-----------------------------
--2022-09-17 19:26:00-- http://rcn-ee.com/repos/bootloader/am335x_evm/u-boot-am335x_evm-v2019.04-r13.img
Resolving rcn-ee.com (rcn-ee.com)... 45.33.2.10, 2600:3c00::f03c:91ff:fe37:6ad5
Connecting to rcn-ee.com (rcn-ee.com)|45.33.2.10|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://rcn-ee.com/repos/bootloader/am335x_evm/u-boot-am335x_evm-v2019.04-r13.img [following]
--2022-09-17 19:26:01-- https://rcn-ee.com/repos/bootloader/am335x_evm/u-boot-am335x_evm-v2019.04-r13.img
Connecting to rcn-ee.com (rcn-ee.com)|45.33.2.10|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 474352 (463K)
Saving to: ‘/opt/backup/uboot/u-boot-am335x_evm-v2019.04-r13.img’
u-boot-am335x_evm-v 100%[===================>] 463.23K 512KB/s in 0.9s
2022-09-17 19:26:02 (512 KB/s) - ‘/opt/backup/uboot/u-boot-am335x_evm-v2019.04-r13.img’ saved [474352/474352]
Writing bootloader to [/dev/mmcblk1]
dd if=/opt/backup/uboot/MLO of=/dev/mmcblk1 count=1 seek=1 bs=128k
which will ultimately end up in having my own MLO flashed with some u-boot-am335x_evm-v2019.04-r13.img instead of my u-boot-dtb.img. When I flashed manually my original MLO and u-boot-dtb.img, my target boots correctly from eMMC.
I can fix that problem in the script if that's ok for you. This can be also fixed by changing the instruction to:
sudo cp -v ./u-boot/u-boot-dtb.img /media/rootfs/opt/backup/uboot/u-boot.img
Please let me know which option you prefer :)
Unfortunately, when I changed filename:
/opt/backup/uboot/u-boot-dtb.img -> /opt/backup/uboot/u-boot.img
and run bbb-eMMC-flasher-eewiki-ext4.sh again, target still can't be booted properly, with a different message this time:
U-Boot SPL 2022.04-00037-ge0d31da5 (Sep 16 2022 - 11:02:51 +0200)
Trying to boot from MMC2
Logs from the flashing with script below:
debian@arm:~$ sudo /bin/bash ./bbb-eMMC-flasher-eewiki-ext4.sh
-----------------------------
Version: [1.20200709: Fix v5.4.x eeprom read...]
-----------------------------
copying: [/dev/mmcblk0] -> [/dev/mmcblk1]
lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 14.5G 0 disk
└─mmcblk0p1 179:1 0 14.5G 0 part /
mmcblk1 179:256 0 3.6G 0 disk
└─mmcblk1p1 179:257 0 3.6G 0 part
mmcblk1boot0 179:512 0 2M 1 disk
mmcblk1boot1 179:768 0 2M 1 disk
-----------------------------
df -h | grep rootfs:
-----------------------------
update-initramfs: Generating /boot/initrd.img-5.15.65-bone28
Erasing: /dev/mmcblk1
108+0 records in
108+0 records out
113246208 bytes (113 MB, 108 MiB) copied, 10.4449 s, 10.8 MB/s
108+0 records in
108+0 records out
113246208 bytes (113 MB, 108 MiB) copied, 2.81274 s, 40.3 MB/s
Erasing: /dev/mmcblk1 complete
-----------------------------
Writing bootloader to [/dev/mmcblk1]
dd if=/opt/backup/uboot/MLO of=/dev/mmcblk1 count=1 seek=1 bs=128k
-----------------------------
0+1 records in
0+1 records out
106400 bytes (106 kB, 104 KiB) copied, 0.0132925 s, 8.0 MB/s
-----------------------------
dd if=/opt/backup/uboot/u-boot.img of=/dev/mmcblk1 count=2 seek=1 bs=384k
-----------------------------
2+0 records in
2+0 records out
786432 bytes (786 kB, 768 KiB) copied, 0.0787425 s, 10.0 MB/s
-----------------------------
Formatting: /dev/mmcblk1
sfdisk: [2.26.x or greater]
sfdisk: [sfdisk from util-linux 2.36.1]
sfdisk: [sfdisk --force /dev/mmcblk1]
sfdisk: [4M,,L,*]
Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk1: 3.6 GiB, 3867148288 bytes, 7553024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Created a new DOS disklabel with disk identifier 0xbbfd1b2a.
/dev/mmcblk1p1: Created a new partition 1 of type 'Linux' and of size 3.6 GiB.
/dev/mmcblk1p2: Done.
New situation:
Disklabel type: dos
Disk identifier: 0xbbfd1b2a
Device Boot Start End Sectors Size Id Type
/dev/mmcblk1p1 * 8192 7553023 7544832 3.6G 83 Linux
The partition table has been altered.
Calling ioctl() to re-read partition table.[ 892.838821] mmcblk1: p1
Syncing disks.
mkfs.ext4 /dev/mmcblk1p1 -L BEAGLEBONE
-----------------------------
mke2fs 1.46.2 (28-Feb-2021)
Discarding device blocks: done
Creating filesystem with 943104 4k blocks and 236176 inodes
Filesystem UUID: 08731777-64bc-4355-9979-096138b1d314
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736
Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
-----------------------------
Formatting: /dev/mmcblk1 complete
-----------------------------
Copying: /dev/mmcblk0p1 -> /dev/mmcblk1p1
[ 904.861620] EXT4-fs (mmcblk1p1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
rsync: / -> /tmp/rootfs/
[ 911.673850] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (88, <AValid), retry #3, port1 0008010c
Copying: Kernel modules
rsync: /lib/modules/5.15.65-bone28/ -> /tmp/rootfs/lib/modules/5.15.65-bone28/
Copying: /dev/mmcblk0p1 -> /dev/mmcblk1p1 complete
-----------------------------
Final System Tweaks:
UUID=08731777-64bc-4355-9979-096138b1d314
Generating: /etc/fstab
# /etc/fstab: static file system information.
#
UUID=08731777-64bc-4355-9979-096138b1d314 / ext4 noatime,errors=remount-ro 0 1
debugfs /sys/kernel/debug debugfs defaults 0 0
-----------------------------
Syncing: /dev/mmcblk1
100000+0 records in
100000+0 records out
51200000 bytes (51 MB, 49 MiB) copied, 1.50836 s, 33.9 MB/s
Syncing: /dev/mmcblk1 complete
-----------------------------
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=221716k,nr_inodes=55429,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=50044k,mode=755)
/dev/mmcblk0p1 on / type ext4 (rw,relatime,errors=remount-ro)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=15390)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=50040k,nr_inodes=12510,mode=700,uid=1000,gid=1000)
eMMC has been flashed:
-----------------------------
debian@arm:~$ sync
debian@arm:~$ shutdown
Failed to set wall message, ignoring: Interactive authentication required.
Failed to call ScheduleShutdown in logind, no action will be taken: Interactive authentication required.
debian@arm:~$ sudo shutdown
Shutdown scheduled for Sat 2022-09-17 23:36:27 UTC, use 'shutdown -c' to cancel.
debian@arm:~$ date
Sat Sep 17 23:36:25 UTC 2022
debian@arm:~$ Stopping Session 1 of user debian.
[ OK ] Removed slice system-modprobe.slice.
[ OK ] Stopped target Graphical Interface.
[ OK ] Stopped target Multi-User System.
[ OK ] Stopped target Login Prompts.
[ OK ] Stopped target Sound Card.
[ OK ] Stopped target Timers.
[ OK ] Stopped Periodic ext4 Onli…ata Check for All Filesystems.
[ OK ] Stopped Discard unused blocks once a week.
[ OK ] Stopped Daily rotation of log files.
[ OK ] Stopped Daily Cleanup of Temporary Directories.
[ OK ] Stopped target System Time Synchronized.
[ OK ] Stopped target System Time Set.
[ OK ] Stopped target Hardware activated USB gadget.
[ OK ] Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Stopping Modem Manager...
Stopping Avahi mDNS/DNS-SD Stack...
Stopping Regular background program processing daemon...
Stopping Getty on tty1...
Stopping A high performanc… and a reverse proxy server...
Stopping System Logging Service...
Stopping Serial Getty on ttyS0...
Stopping OpenBSD Secure Shell server...
Stopping Load/Save Random Seed...
[ OK ] Stopped Avahi mDNS/DNS-SD Stack.
[ OK ] Stopped Regular background program processing daemon.
[ OK ] Stopped System Logging Service.
[ OK ] Stopped Modem Manager.
[ OK ] Stopped Getty on tty1.
[ OK ] Stopped Serial Getty on ttyS0.
[ OK ] Stopped OpenBSD Secure Shell server.
[ OK ] Stopped Load/Save Random Seed.
[ OK ] Stopped A high performance…er and a reverse proxy server.
[ OK ] Stopped Session 1 of user debian.
[ OK ] Removed slice system-getty.slice.
[ OK ] Removed slice system-serial\x2dgetty.slice.
Stopping Authorization Manager...
Stopping User Login Management...
Stopping User Manager for UID 1000...
[ OK ] Stopped Authorization Manager.
[ OK ] Stopped User Manager for UID 1000.
Stopping User Runtime Directory /run/user/1000...
[ OK ] Stopped User Login Management.
[ OK ] Unmounted /run/user/1000.
[ OK ] Reached target Unmount All Filesystems.
[ OK ] Stopped User Runtime Directory /run/user/1000.
[ OK ] Removed slice User Slice of UID 1000.
Stopping Permit User Sessions...
[ OK ] Stopped Permit User Sessions.
[ OK ] Stopped target Network.
[ OK ] Stopped target Remote File Systems.
Stopping Network Manager...
Stopping Raise network interfaces...
Stopping WPA supplicant...
[ OK ] Stopped WPA supplicant.
[ OK ] Stopped Network Manager.
Stopping D-Bus System Message Bus...
[ OK ] Stopped D-Bus System Message Bus.
[ OK ] Stopped target Basic System.
[ OK ] Stopped target Paths.
[ OK ] Stopped target Slices.
[ OK ] Removed slice User and Session Slice.
[ OK ] Stopped target Sockets.
[ OK ] Closed Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK ] Closed D-Bus System Message Bus Socket.
[ OK ] Stopped target System Initialization.
[ OK ] Stopped target Local Encrypted Volumes.
[ OK ] Stopped Dispatch Password …ts to Console Directory Watch.
[ OK ] Stopped Forward Password R…uests to Wall Directory Watch.
[ OK ] Stopped target Swap.
[ OK ] Closed Syslog Socket.
Stopping Restore / save the current clock...
Stopping Network Time Synchronization...
Stopping Update UTMP about System Boot/Shutdown...
[ OK ] Stopped Network Time Synchronization.
[ OK ] Stopped Restore / save the current clock.
[ OK ] Stopped Update UTMP about System Boot/Shutdown.
[ OK ] Stopped Create Volatile Files and Directories.
[ OK ] Stopped Raise network interfaces.
[ OK ] Stopped target Local File Systems.
[ OK ] Stopped target Local File Systems (Pre).
[ OK ] Stopped Apply Kernel Variables.
[ OK ] Stopped Load Kernel Modules.
[ OK ] Stopped Create Static Device Nodes in /dev.
[ OK ] Stopped Create System Users.
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
[ OK ] Finished Power-Off.
[ OK ] Reached target Power-Off.
[ 1194.684832] systemd-shutdown[1]: Syncing filesystems and block devices.
[ 1201.797902] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[ 1201.820415] systemd-journald[221]: Received SIGTERM from PID 1 (systemd-shutdow).
[ 1203.729289] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[ 1203.780209] systemd-shutdown[1]: Unmounting file systems.
[ 1203.799811] [2316]: Remounting '/' read-only in with options 'errors=remount-ro'.
[ 1204.816047] EXT4-fs (mmcblk0p1): re-mounted. Opts: errors=remount-ro. Quota mode: none.
[ 1204.855634] systemd-shutdown[1]: All filesystems unmounted.
[ 1204.861456] systemd-shutdown[1]: Deactivating swaps.
[ 1204.866863] systemd-shutdown[1]: All swaps deactivated.
[ 1204.872239] systemd-shutdown[1]: Detaching loop devices.
[ 1204.878442] systemd-shutdown[1]: All loop devices detached.
[ 1204.884195] systemd-shutdown[1]: Stopping MD devices.
[ 1204.889885] systemd-shutdown[1]: All MD devices stopped.
[ 1204.895343] systemd-shutdown[1]: Detaching DM devices.
[ 1204.901055] systemd-shutdown[1]: All DM devices detached.
[ 1204.906577] systemd-shutdown[1]: All filesystems, swaps, loop devices, MD devices and DM devices detached.
[ 1204.925003] systemd-shutdown[1]: Syncing filesystems and block devices.
[ 1204.934414] systemd-shutdown[1]: Powering off.
[ 1204.968878] reboot: Power down
U-Boot SPL 2022.04-00037-ge0d31da5 (Sep 16 2022 - 11:02:51 +0200)
Trying to boot from MMC2
U-Boot SPL 2022.04-00037-ge0d31da5 (Sep 16 2022 - 11:02:51 +0200)
Trying to boot from MMC2
U-Boot SPL 2022.04-00037-ge0d31da5 (Sep 16 2022 - 11:02:51 +0200)
Trying to boot from MMC2
U-Boot SPL 2022.04-00037-ge0d31da5 (Sep 16 2022 - 11:02:51 +0200)
Trying to boot from MMC2
U-Boot SPL 2022.04-00037-ge0d31da5 (Sep 16 2022 - 11:02:51 +0200)
Trying to boot from MMC2
I pressed reset button couple of times. So to sum up, I have MLO and u-boot.img (which is renamed u-boot-dtb.img) in /opt/backup/uboot/ directory on a software booted from SD card. When I manually install this new u-boot via:
sudo dd if=MLO of=${DISK} count=2 seek=1 bs=128k
sudo dd if=u-boot.img of=${DISK} count=4 seek=1 bs=384k
(I do not install rootfs) then it is working fine - BBB is booted and looking for sources to boot:
U-Boot SPL 2022.04-00037-ge0d31da5 (Sep 16 2022 - 11:02:51 +0200)
Trying to boot from MMC2
U-Boot 2022.04-00037-ge0d31da5 (Sep 16 2022 - 11:02:51 +0200)
CPU : AM335X-GP rev 2.1
Model: TI AM335x BeagleBone Black
DRAM: 512 MiB
Reset Source: Power-on reset has occurred.
RTC 32KCLK Source: External.
Core: 150 devices, 14 uclasses, devicetree: separate
WDT: Started wdt@44e35000 with servicing (60s timeout)
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from EXT4... Board: BeagleBone Black
<ethaddr> not set. Validating first E-fuse MAC
BeagleBone Black:
BeagleBone Cape EEPROM: no EEPROM at address: 0x54
BeagleBone Cape EEPROM: no EEPROM at address: 0x55
BeagleBone Cape EEPROM: no EEPROM at address: 0x56
BeagleBone Cape EEPROM: no EEPROM at address: 0x57
Net: Could not get PHY for ethernet@4a100000: addr 0
eth2: ethernet@4a100000, eth3: usb_ether
Press SPACE to abort autoboot in 0 seconds
board_name=[A335BNLT] ...
board_rev=[000C] ...
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
mmc1(part 0) is current device
** No partition table - mmc 1 **
Couldn't find partition mmc 1: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
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
** No partition table - mmc 1 **
Couldn't find partition mmc 1:1
Checking for: /uEnv.txt ...
** No partition table - mmc 1 **
Couldn't find partition mmc 1:1
Checking for: /boot/uEnv.txt ...
** No partition table - mmc 1 **
Couldn't find partition mmc 1:1
** No partition table - mmc 1 **
Couldn't find partition mmc 1:2
** No partition table - mmc 1 **
Couldn't find partition mmc 1:3
** No partition table - mmc 1 **
Couldn't find partition mmc 1:4
** No partition table - mmc 1 **
Couldn't find partition mmc 1:5
** No partition table - mmc 1 **
Couldn't find partition mmc 1:6
** No partition table - mmc 1 **
Couldn't find partition mmc 1:7
starting USB...
Bus usb@47401800: Port not available.
USB is stopped. Please issue 'usb start' first.
starting USB...
Bus usb@47401800: Port not available.
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
musb-hdrc: peripheral reset irq lost!
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
USB RNDIS network up!
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
but when I run the script which I believe installs the same MLO and u-boot.img (plus rootfs), then this is not working and ends up with u-boot hangs at:
U-Boot SPL 2022.04-00037-ge0d31da5 (Sep 16 2022 - 11:02:51 +0200)
Trying to boot from MMC2
Hi @lilyjayd sorry about this, with bullseye, i've rewritten the eMMC flasher to be more modular, i really need to go back on buster and remove all the old scripts..
The debian package is "bb-beagle-flasher"
sudo apt update ; sudo apt install bb-beagle-flasher
pushed out to buster, bullseye, focal, and jammy..
The main script is:
https://github.com/rcn-ee/repos/blob/master/bb-beagle-flasher/suite/bullseye/debian/beagle-flasher
to configure for your board, you copy one of the config files to:
/etc/default/beagle-flasher
BBB: microSD -> eMMC
BBB: eMMC -> microSD
BBAI: microSD -> eMMC
BBAI: eMMC -> microSD
sudo cp -v /etc/beagle-flasher/beaglebone-black-microsd-to-emmc /etc/default/beagle-flasher
For the BBB it'll pull in the u-boot here:
bootloader=/opt/u-boot/bb-u-boot-am335x-evm/install-mmcblk1.sh
From debian userspace then just run:
sudo beagle-flasher
Regards,
Thanks @RobertCNelson. It went smooth with default MLO and u-boot-dtb.img from package you've mentioned:
INFO: [/bin/bash /opt/u-boot/bb-u-boot-am335x-evm/install-mmcblk1.sh]
dd if=/opt/u-boot/bb-u-boot-am335x-evm/MLO of=/dev/mmcblk1 count=2 seek=1 bs=128k
0+1 records in
0+1 records out
106028 bytes (106 kB, 104 KiB) copied, 0.0133077 s, 8.0 MB/s
dd if=/opt/u-boot/bb-u-boot-am335x-evm/u-boot-dtb.img of=/dev/mmcblk1 count=4 seek=1 bs=384k
2+1 records in
2+1 records out
987236 bytes (987 kB, 964 KiB) copied, 0.10033 s, 9.8 MB/s
U-Boot SPL 2022.04-gd0771d53 (Jul 21 2022 - 02:13:23 +0000)
Trying to boot from MMC2
U-Boot 2022.04-gd0771d53 (Jul 21 2022 - 02:13:23 +0000)
CPU : AM335X-GP rev 2.1
Model: TI AM335x BeagleBone Black
DRAM: 512 MiB
Reset Source: Power-on reset has occurred.
RTC 32KCLK Source: External.
Core: 150 devices, 14 uclasses, devicetree: separate
WDT: Started wdt@44e35000 with servicing (60s timeout)
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
[...]
Tomorrow I'll try with my own MLO and uboot image. And by the way, do you perhaps have some helper tools or instructions with modern approach for doing kernel + rootfs over tftp on BBB? Years ago I was doing that with dnsmasq and nfs version 2, but things changed a little bit since then, so maybe there's a better way now.
Hello,
first of all, I'd like to thank you @RobertCNelson - what you are doing is amazing!
So I followed your instructions for BBB (I skipped only HDMI and u-boot Overlays sections) from here:
https://forum.digikey.com/t/debian-getting-started-with-the-beaglebone-black/12967
It booted completely fine from SD card. And at that time my BBB was also properly booting old u-boot and kernel on eMMC. So I booted again from SD card to flash the fresh software to eMMC via:
After the script finished, I did sync + remove SD card and restart BBB. It did not end well:
Below, you can find logs from the whole session: boot from SD card with software installed by following instruction on digikey forum, download and execution of bbb-eMMC-flasher-eewiki-ext4.sh script and then restart without SD card inserted.
After that I booted again from SD card and used the bbb-eMMC-flasher-eewiki-ext4.sh once more - with the same result unfortunately. Below logs doesn't cover that second try.
What can be wrong here? Any way to debug and fix that?