Debian 13 trixie SPIDEV and UART dtbo

General Discussion
1

Hello,

I need help getting SPIDEV and UART dtbo overlays to function. I found under /opt directory sources to compile and install overlays. I compiled and installed them, got the SPIDEV0 and SPIDEV1. Then I enabled the overlays within uEnv.txt, but nothing happen.

I ran the beagle-version program, listed below. There are few things interesting in it, like: WARNING:pkg:[bb-cape-overlays]:[NOT_INSTALLED] but where is it? it is a pkg but apt cannot find it or install it. I see also this: uboot_overlay_options:[uboot_overlay=/boot/dtbs/6.15.10-bone26/BB-SPIDEV0-00A0.dtbo].

I’m so frustrated that I’m on the verge of giving up. Your assistance would be greatly appreciated.

eeprom:[A335BNLT000C1739BBBG1679]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Trixie Base Image 2025-08-26]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 2022.04-ge543709d (Jun 27 2025 - 18:09:26 +0000)]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-boneblack-uboot.dts]
UBOOT: Loaded Overlay:[BB-ADC-00A0.kernel]
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0.kernel]
kernel:[6.15.10-bone26]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay=/boot/dtbs/6.15.10-bone26/BB-SPIDEV0-00A0.dtbo]
uboot_overlay_options:[uboot_overlay=/boot/dtbs/6.15.10-bone26/BB-UART1-00A0.dtbo]
uboot_overlay_options:[disable_uboot_overlay_video=1]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade ]
WARNING:pkg:[bb-cape-overlays]:[NOT_INSTALLED]
pkg:[bb-customizations]:[1.20250808.0-0~trixie+20250808]
pkg:[bb-usb-gadgets]:[1.20250523.1-0~trixie+20250527]
pkg:[bb-wl18xx-firmware]:[1.20230703.0-0~trixie+20240703]
pkg:[kmod]:[34.2-2bbbio1~trixie+20250522]
WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED]
pkg:[firmware-ti-connectivity]:[20250410-2]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal input render netdev i2c bluetooth gpio admin tisdk weston-launch]
cmdline:[console=ttyS0,115200n8 root=/dev/mmcblk1p3 ro rootfstype=ext4 rootwait fsck.repair=yes earlycon coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100]
dmesg | grep remote
[ 14.645354] systemd[1]: Reached target remote-fs.target - Remote File Systems.
[ 33.487525] remoteproc remoteproc0: wkup_m3 is available
[ 35.980950] remoteproc remoteproc0: powering up wkup_m3
[ 36.037075] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217148
[ 36.080689] remoteproc remoteproc0: remote processor wkup_m3 is now up
[ 49.681080] remoteproc remoteproc1: 4a334000.pru is available
[ 49.702859] remoteproc remoteproc2: 4a338000.pru is available
dmesg | grep pru
[ 49.681080] remoteproc remoteproc1: 4a334000.pru is available
[ 49.702859] remoteproc remoteproc2: 4a338000.pru is available
dmesg | grep pinctrl-single
[ 4.372398] pinctrl-single 44e10800.pinmux: 142 pins, size 568
dmesg | grep gpio-of-helper
dmesg | grep wlcore
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lspci
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
END

2

can you proved the serial boot log?
remove quite from uEnv.txt file

3

Thanks, amf99 for your respose.
It is not clear to me what are you asking for. Do you mean you want to see the last boot log as if I run **journalctl --boot=XXXXXXX?
What do you mean when you say *“remove quite from uEnv.txt file”?

Thanks

4

connect a USB serial adapter, capture the serial log while booting the board.
as for “quite”, it seems that /boot/uEnv.txt does not have it on this image , but check anyway
if “quite” is at the end of
cmdline=fsck.repair=yes earlycon coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100
then remove it.

checked on
6.15.10-bone26 image

5

did the same, spidev are there
debian@BeagleBone:~$ ls /dev | grep spi
spidev0.0
spidev0.1

changes i did to uEnv.txt
enable_uboot_overlays=1

###Overide capes with eeprom
#uboot_overlay_addr0=.dtbo
#uboot_overlay_addr1=.dtbo
#uboot_overlay_addr2=.dtbo
#uboot_overlay_addr3=.dtbo

###Additional custom capes
uboot_overlay_addr4=BB-SPIDEV0-00A0.dtbo
uboot_overlay_addr5=BB-UART1-00A0.dtbo

6

I appreciate your help, it is working now.

I am guessing that what I was doing wrong was that I provided the full path to the overlay? Any way, thanks amf99.

R

1 Like