I have two Beaglebone Blacks and one boots with the latest image and the other won’t (same SD card)
This is the image I’m using
However I have live image that boots on both
BeagleBoard.org Debian Buster IoT Image 2020-04-06
Linux beaglebone 4.19.94-ti-r42 #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC 2020 armv7l GNU/Linux
Here is the terminal output from the board that doesn’t boot with the latest image
U-Boot SPL 2022.04-ge0d31da5 (Aug 04 2023 - 18:48:26 +0000)
Trying to boot from MMC1
U-Boot 2022.04-ge0d31da5 (Aug 04 2023 - 18:48:26 +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
Loading Environment from EXT4... Board: BeagleBone Black
<ethaddr> not set. Validating first E-fuse MAC
BeagleBone Black:
Model: BeagleBone Black Industrial:
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: eth2: ethernet@4a100000, eth3: usb_ether
Press SPACE to abort autoboot in 0 seconds
board_name=[A335BNLT] ...
board_rev=[EIA0] ...
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
Scanning mmc 1:1...
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk mmc@48060000.blk...
Disk mmc@48060000.blk not ready
Scanning disk mmc@481d8000.blk...
Found 7 disks
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
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
Checking for: /uEnv.txt ...
15 bytes read in 2 ms (6.8 KiB/s)
gpio: pin 55 (gpio 55) value is 1
Loaded environment from /uEnv.txt
Importing environment from mmc ...
Checking if uenvcmd is set ...
Checking for: /boot/uEnv.txt ...
** Invalid partition 7 **
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.
ethernet@4a100000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
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
Any help would be much appreciated.
This shows us you have a ‘custom’ setting in /uEnv.txt , all factory images today use /boot/uEnv.txt and this would normally look like:
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
Checking for: /boot/uEnv.txt ...
gpio: pin 55 (gpio 55) value is 1
187 bytes read in 3 ms (60.5 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 ...
so please share your /uEnv.txt and we will try to help fix it…
Regards,
I’m trying to install the stock image from:
All I did was burn that to an SD card via etcher
here is the directory structure, there is no /uEnv.txt
root@ubuntu:/media/shane/rootfs# tree -L 1
.
├── bin
├── boot
├── dev
├── etc
├── home
├── ID.txt
├── lib
├── lost+found
├── media
├── mnt
├── opt
├── proc
├── root
├── run
├── sbin
├── srv
├── sys
├── tmp
├── usr
└── var
and under /boot there is a uEnv.txt contents below
root@ubuntu:/media/shane/rootfs/boot# cat uEnv.txt
#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
uname_r=5.10.168-ti-r71
#uuid=
#dtb=
###U-Boot Overlays###
###Documentation: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays
###Master Enable
enable_uboot_overlays=1
###
###Overide capes with eeprom
#uboot_overlay_addr0=<file0>.dtbo
#uboot_overlay_addr1=<file1>.dtbo
#uboot_overlay_addr2=<file2>.dtbo
#uboot_overlay_addr3=<file3>.dtbo
###
###Additional custom capes
#uboot_overlay_addr4=<file4>.dtbo
#uboot_overlay_addr5=<file5>.dtbo
#uboot_overlay_addr6=<file6>.dtbo
#uboot_overlay_addr7=<file7>.dtbo
###
###Custom Cape
#dtb_overlay=<file8>.dtbo
###
###Disable auto loading of virtual capes (emmc/video/wireless/adc)
#disable_uboot_overlay_emmc=1
#disable_uboot_overlay_video=1
#disable_uboot_overlay_audio=1
#disable_uboot_overlay_wireless=1
#disable_uboot_overlay_adc=1
###
###Cape Universal Enable
enable_uboot_cape_universal=1
###
###Debug: disable uboot autoload of Cape
#disable_uboot_overlay_addr0=1
#disable_uboot_overlay_addr1=1
#disable_uboot_overlay_addr2=1
#disable_uboot_overlay_addr3=1
###
###U-Boot fdt tweaks... (60000 = 384KB)
#uboot_fdt_buffer=0x60000
###U-Boot Overlays###
console=ttyS0,115200n8
cmdline=coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet
#In the event of edid real failures, uncomment this next line:
#cmdline=coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet video=HDMI-A-1:1024x768@60e
#Use an overlayfs on top of a read-only root filesystem:
#cmdline=coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet overlayroot=tmpfs
##enable Generic eMMC Flasher:
cmdline=init=/usr/sbin/init-beagle-flasher
Is it possible that it is still trying to load something from the internal flash and getting messed up. I’m holding the S2 boot button to force boot of the SD. Just really weird that it will work on a different board without issue.
S2 is read on power up, you need to make sure now power is applied… Push and hold S2, insert power, wait for led to turn on, then and only then you can lift up on S2… then i’ll read the microSD…
Regards,
Yes, I am holding the S2 button while powering on.
I would check with a DVM that the high side (pins 1 ) of switch S2 goes low when pressed. Might be a bad switch.
I did check the switch and it is working without issues, plus when I use a live image it boots fine off of that
does the non flasher version of the new image boot on both boards ?
It would appear that there is an issue writing to the emmc on one of the boards.
I would try booting a non flashing image from sd and then use dd to wipe the first few megs of the emmc.
Then repower the board with no sd card to make sure it is indeed wiped.
Then try flashing again.
Yes the non flasher version image works on both boards.
I have erased the emmc within uboot and that did not make a difference. I was able to get the emmc programmed by booting from the non flasher image and then using dd to restore an image.
To me it seems as if when booting the emmc flasher image it is selecting the wrong partition to boot from but I’m not sure why
Serial log is the best way to see what is happening…
Regards,
Yes, the output of the serial log is in the first post. I just don’t understand why two different beagle bones would behave differently
Started with a blank BBB…
voodoo@hestia:~$ tio /dev/ttyACM1
[10:18:35.936] tio v2.5
[10:18:35.936] Press ctrl-t q to quit
[10:18:35.937] Connected
CCCCCCCCCCCC
Using:
voodoo@hestia:~/Downloads$ sha256sum am335x-eMMC-flasher-debian-11.7-iot-armhf-2023-09-02-4gb.img.xz
21d2e5204f6ce78deed3f7beb82e8335009e568d77bbc09a83cdc225db8cd98f am335x-eMMC-flasher-debian-11.7-iot-armhf-2023-09-02-4gb.img.xz
Inserted microSD and applied power again…
voodoo@hestia:~$ tio /dev/ttyACM1
[10:18:35.936] tio v2.5
[10:18:35.936] Press ctrl-t q to quit
[10:18:35.937] Connected
CCCCCCCCCCCC
U-Boot SPL 2022.04-ge0d31da5 (Aug 04 2023 - 18:48:26 +0000)
Trying to boot from MMC1
U-Boot 2022.04-ge0d31da5 (Aug 04 2023 - 18:48:26 +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
Loading Environment from EXT4... ** File not found /boot/uboot.env **
** Unable to read "/boot/uboot.env" from mmc0:1 **
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: eth2: ethernet@4a100000, eth3: usb_ether
Press SPACE to abort autoboot in 0 seconds
board_name=[A335BNLT] ...
board_rev=[00C0] ...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
Couldn't find partition 0:2 0x82000000
Can't set block device
Couldn't find partition 0:2 0x82000000
Can't set block device
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk mmc@48060000.blk...
Scanning disk mmc@481d8000.blk...
Found 3 disks
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
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 ...
Checking for: /boot/uEnv.txt ...
gpio: pin 55 (gpio 55) value is 1
1712 bytes read in 4 ms (418 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-5.10.168-ti-r71 ...
11342336 bytes read in 716 ms (15.1 MiB/s)
debug: [enable_uboot_overlays=1] ...
debug: [enable_uboot_cape_universal=1] ...
debug: [uboot_base_dtb_univ=am335x-boneblack-uboot-univ.dtb] ...
uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot-univ.dtb] ...
uboot_overlays: Switching too: dtb=am335x-boneblack-uboot-univ.dtb ...
loading /boot/dtbs/5.10.168-ti-r71/am335x-boneblack-uboot-univ.dtb ...
210757 bytes read in 19 ms (10.6 MiB/s)
Found 0 extension board(s).
uboot_overlays: [fdt_buffer=0x60000] ...
uboot_overlays: loading /boot/dtbs/5.10.168-ti-r71/overlays/BB-ADC-00A0.dtbo ...
645 bytes read in 6 ms (104.5 KiB/s)
uboot_overlays: loading /boot/dtbs/5.10.168-ti-r71/overlays/BB-BONE-eMMC1-01-00A0.dtbo ...
1605 bytes read in 6 ms (260.7 KiB/s)
uboot_overlays: loading /boot/dtbs/5.10.168-ti-r71/overlays/BB-HDMI-TDA998x-00A0.dtbo ...
5321 bytes read in 6 ms (865.2 KiB/s)
loading /boot/initrd.img-5.10.168-ti-r71 ...
7719588 bytes read in 494 ms (14.9 MiB/s)
debug: [console=ttyS0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait init=/usr/sbin/init-beagle-flasher] ...
debug: [bootz 0x82000000 0x88080000:75caa4 88000000] ...
Kernel image @ 0x82000000 [ 0x000000 - 0xad1200 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8f8a3000, end 8ffffaa4 ... OK
Loading Device Tree to 8f80b000, end 8f8a2fff ... OK
Starting kernel ...
Please notice these major differences between your ‘posted’ log and mine…
Yours:
switch to partitions #0, OK
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
15 bytes read in 2 ms (6.8 KiB/s)
gpio: pin 55 (gpio 55) value is 1
Loaded environment from /uEnv.txt
Importing environment from mmc ...
Checking if uenvcmd is set ...
Checking for: /boot/uEnv.txt ...
** Invalid partition 7 **
Couldn't find partition mmc 1:7
Compared with mine:
switch to partitions #0, OK
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
Checking for: /boot/uEnv.txt ...
gpio: pin 55 (gpio 55) value is 1
1712 bytes read in 4 ms (418 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-5.10.168-ti-r71 ...
11342336 bytes read in 716 ms (15.1 MiB/s)
the only thing we are left with, you either modified am335x-eMMC-flasher-debian-11.7-iot-armhf-2023-09-02-4gb.img.xz or you are using something else…
Regards,
Just tried again, downloading and burning a new image, and erasing eMMC again.
PS C:\Users\srock> Get-FileHash C:\Users\srock\Downloads\am335x-eMMC-flasher-debian-11.7-iot-armhf-2023-09-02-4gb.img.xz -Algorithm SHA256
Algorithm Hash Path
--------- ---- ----
SHA256 21D2E5204F6CE78DEED3F7BEB82E8335009E568D77BBC09A83CDC225DB8CD98F C:\Users\srock\Downloads\am335x-eMMC-flasher-debian-11.7-iot-armhf-2023-09-02-4gb.img.xz
First line is booting without an SD card to ensure eMMC is empty and can’t boot, I then powered off and powered back on
CCCCCCCCCCCCC
U-Boot SPL 2022.04-ge0d31da5 (Aug 04 2023 - 18:48:26 +0000)
Trying to boot from MMC1
U-Boot 2022.04-ge0d31da5 (Aug 04 2023 - 18:48:26 +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
Loading Environment from EXT4... Board: BeagleBone Black
<ethaddr> not set. Validating first E-fuse MAC
BeagleBone Black:
Model: BeagleBone Black Industrial:
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: eth2: ethernet@4a100000, eth3: usb_ether
Press SPACE to abort autoboot in 0 seconds
board_name=[A335BNLT] ...
board_rev=[EIA0] ...
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.
ethernet@4a100000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
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
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-58-2b-0a-0a-fc-7d
ethernet@4a100000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
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
This is the boot up with the live image I have.
U-Boot SPL 2019.04-00002-gc9b3922522 (Aug 24 2020 - 16:42:18 -0500)
Trying to boot from MMC1
Loading Environment from EXT4... ** File not found /boot/uboot.env **
** Unable to read "/boot/uboot.env" from mmc0:1 **
U-Boot 2019.04-00002-gc9b3922522 (Aug 24 2020 - 16:42:18 -0500), Build: jenkins-github_Bootloader-Builder-144
CPU : AM335X-GP rev 2.1
I2C: ready
DRAM: 512 MiB
No match for driver 'omap_hsmmc'
No match for driver 'omap_hsmmc'
Some drivers were not found
Reset Source: Power-on reset has occurred.
RTC 32KCLK Source: External.
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from EXT4... ** File not found /boot/uboot.env **
** Unable to read "/boot/uboot.env" from mmc0:1 **
Board: BeagleBone Black
<ethaddr> not set. Validating first E-fuse MAC
BeagleBone Black:
Model: BeagleBone Black Industrial:
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: eth0: MII MODE
cpsw, usb_ether
Press SPACE to abort autoboot in 0 seconds
board_name=[A335BNLT] ...
board_rev=[EIA0] ...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
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 ...
Checking for: /boot.scr ...
Checking for: /boot/boot.scr ...
Checking for: /boot/uEnv.txt ...
gpio: pin 55 (gpio 55) value is 1
2062 bytes read in 34 ms (58.6 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-4.19.94-ti-r42 ...
10095592 bytes read in 663 ms (14.5 MiB/s)
debug: [enable_uboot_overlays=1] ...
debug: [enable_uboot_cape_universal=1] ...
debug: [uboot_base_dtb_univ=am335x-boneblack-uboot-univ.dtb] ...
uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot-univ.dtb] ...
uboot_overlays: Switching too: dtb=am335x-boneblack-uboot-univ.dtb ...
loading /boot/dtbs/4.19.94-ti-r42/am335x-boneblack-uboot-univ.dtb ...
162266 bytes read in 59 ms (2.6 MiB/s)
uboot_overlays: [fdt_buffer=0x60000] ...
uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...
867 bytes read in 177 ms (3.9 KiB/s)
uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...
1584 bytes read in 358 ms (3.9 KiB/s)
uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ...
4915 bytes read in 275 ms (16.6 KiB/s)
uboot_overlays: loading /lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo ...
3801 bytes read in 492 ms (6.8 KiB/s)
loading /boot/initrd.img-4.19.94-ti-r42 ...
6589689 bytes read in 445 ms (14.1 MiB/s)
debug: [console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet] ...
debug: [bootz 0x82000000 0x88080000:648cf9 88000000] ...
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8f9b7000, end 8ffffcf9 ... OK
Loading Device Tree to 8f92b000, end 8f9b6fff ... OK
Starting kernel ...
[ 0.002165] timer_probe: no matching timers found
[ 0.195619] l4_wkup_cm:clk:0010:0: failed to disable
[ 1.415072] omap_voltage_late_init: Voltage driver support not added
Debian GNU/Linux 10 beaglebone ttyS0
BeagleBoard.org Debian Buster IoT Image 2020-04-06
Support: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
default username:password is [debian:temppwd]
beaglebone login:
that board just doesn’t like something… it looks like windows in the background… what version of etcher.io etc are you using? or something else… i can try to replicate it…
Regards,
Yes using windows to burn the SD card
The version I’m using is 1.10.6
Thanks!
Just tried with the latest release of etcher (1.18.11) and same result.
@RobertCNelson any luck trying to replicate, is there anything else I can do to troubleshoot?
I am getting very similar results to those reported by @shanerock with at least one recent image downloaded from beagleboard.org different from the one he is using. It looks to me as if the uboot version(s) which are being put into these images are more recent than the build of uboot from 2019 which I get when I allow the device to boot from the eMMC, and these builds have the behaviour of outputting the “Trying to boot from MMC1” line directly after startup, and then chaining to partition 1 in the eMMC for the boot process instead of chaining to the filesystem on the SD card.
@shanerock’s log reports that the U-Boot build is
U-Boot 2022.04-ge0d31da5 (Aug 04 2023 - 18:48:26 +0000)
On the image I am running at the moment, the report has the same prefix “U-Boot 2022.04-ge0d31da5” but has a timestamp of “Dec 07 2023 - 16:17:19 +0000”.
I have multiple images available to run here downloaded from different parts of beableboard.org, the names and SHA256’s of the downloadable xz files are as follows:
tim@tim-OptiPlex-7450-AIO:~/Downloads/RPi+BBB$ sha256sum *.img.xz
58e76be5fd7415cca89f1187c6d96ed697b8d77fd2739ab4978f2d0ba9c87641 am335x-debian-11.7-iot-armhf-2023-09-02-4gb.img.xz
62ee9f6dab49d6df8b0822e5b5a491a34d92643d0b166392de0b5d0eb5bcf9f9 am335x-debian-11.8-iot-armhf-2023-10-07-4gb.img.xz
3fdac493ab7074ef8d5258abf07a1bdff1afdd2fda88f6b4625a015f003f4687 am335x-debian-11.8-minimal-armhf-2023-10-07-2gb.img.xz
8363a991d6115cf5906408f9875badc99fe38452436605af1906edbbc8dc0d36 am335x-debian-11.8-xfce-armhf-2023-10-07-4gb.img.xz
d66e120d2055cf4b9f30109488f293ff7b38a7b39c7374c1a163cce7a946c13d am335x-debian-12.4-minimal-armhf-2024-01-06-2gb.img.xz
a61b749119ce0a9827e2f5e0e36831a0b139482798fac668337b6da6fcea7038 am335x-eMMC-flasher-debian-11.7-xfce-armhf-2023-09-02-4gb.img.xz
f0ee00a83a72abb09a74663f8b860ab1c3fc0f5fd4ea29202057c7c93892f27e am335x-eMMC-flasher-debian-11.8-iot-armhf-2023-10-07-4gb.img.xz
I think the image in the device at the moment is am335x-debian-12.4-minimal-armhf-2024-01-06-2gb.img.xz (given the dates on the others it is unlikely they would contain a U-Boot binary built in December 2023). I’ll work through all of these again and report back if I find any which work, or which fail with different symptoms.
If there is a specific build anyon on the forum would suggest I try (particularly if there are any builds with U-boot built from different git commits, as I’m guessing @shanerock and I have builds based on the same commit).
If I am understanding this properly, you have a uboot conflict. What I do is us the IoT flasher image, that one has been working very well.
You will need to go in at the uboot prompt and break emmc boot, just write some 0’s to it. Then boot with the flasher image and it will lay down a fresh uboot image and install OS. It is much simpler doing it this way.
Some time ago I posted instructions for someone else that was having problems. I believe it was on this forum regarding doing that via debug port and IoT image.