Okay, here’s the thing, “rohm,dh2228fv” for some reason is not being recognized as a spidev node, so kernel doesn’t create a spidev pseudofile (i.e. /dev/spi0.0, dev/spi1.2, etc.)
Another thing here is that one of the GPIO CS lines are overlaid ontop of default mmc1 pins.
So the kernel panics only whenever I enable eMMC and include this SPIDEV overlay.
But from the dmesg printout it didn’t want to list the P8_04 for some reason.
Namely, I assume that P8_15 & P8_16 are being used as the default mmc1_d6 & mmc1_d7, so it complained that it cannot get these
is there a way to instruct uboot overlay for emmc (#disable_uboot_overlay_emmc=1 in uEnv.txt) which loads the /boot/dtbs/5.10.168-ti-r84/overlays/BB-BONE-eMMC1-01-00A0.dtbo
it to load before any of the uboot_overlay_addr.
Found 0 extension board(s).
uboot_overlays: \[fdt_buffer=0x200000\] ...
uboot_overlays: uboot loading of \[BB-ADC-00A0.dtbo\] disabled by /boot/uEnv.txt \[disable_uboot_overlay_adc=1\]...
uboot_overlays: loading /lib/firmware/BB-I2C1-00A0.dtbo ...
1102 bytes read in 7 ms (153.3 KiB/s)
uboot_overlays: loading /lib/firmware/VERBATIM-SPIDEV1-GEN2.dtbo ...
2234 bytes read in 33 ms (65.4 KiB/s)
uboot_overlays: loading /boot/dtbs/5.10.168-ti-r83/overlays/BB-BONE-eMMC1-01-00A0.dtbo ...
1605 bytes read in 7 ms (223.6 KiB/s)
uboot_overlays: uboot loading of \[BB-HDMI-TDA998x-00A0.dtbo\] disabled by /boot/uEnv.txt \[disable_uboot_overlay_video=1\]...
loading /boot/initrd.img-5.10.168-ti-r83 ...
to switch SPIDEV overlay in front of eMMC1:
Found 0 extension board(s).
uboot_overlays: \[fdt_buffer=0x200000\] ...
uboot_overlays: uboot loading of \[BB-ADC-00A0.dtbo\] disabled by /boot/uEnv.txt \[disable_uboot_overlay_adc=1\]...
uboot_overlays: loading /lib/firmware/BB-I2C1-00A0.dtbo ...
1102 bytes read in 7 ms (153.3 KiB/s)
uboot_overlays: loading /boot/dtbs/5.10.168-ti-r83/overlays/BB-BONE-eMMC1-01-00A0.dtbo ...
1605 bytes read in 7 ms (223.6 KiB/s)
uboot_overlays: loading /lib/firmware/VERBATIM-SPIDEV1-GEN2.dtbo ...
2234 bytes read in 33 ms (65.4 KiB/s)
uboot_overlays: uboot loading of \[BB-HDMI-TDA998x-00A0.dtbo\] disabled by /boot/uEnv.txt \[disable_uboot_overlay_video=1\]...
loading /boot/initrd.img-5.10.168-ti-r83 ...
Or just combine them into one overlay.. If your spidev is using pins used by eMMC, it’s best to disable eMMC.. On one of the early lcd design’s it shared pins with the eMMC, this condition led up to eMMC file system corruption…
Sure, I’d like to have the eMMC and the spidev chipselects though. No luck with reordering with uEnv.txt, so I’ll hedge my bets with simply combining them under one overlay (which was my initial idea)
BTW… once “FDT_ERR_NOTFOUND” occurs, the memory u-boot used to apply the overlay is now corrupt and anything after is completely invalid.. (aka don’t spend time debugging anything after)
Yes, I’ve used some other development image (that is less secured) on which I’ve built dtbos natively via BeaglBone-DeviceTrees. However it’s kernel was r83, while the device tree’s one was probably building for r84.
Anyway, defaulting back to my regular bulid system with everything aligned seems to work. So I’m going to batch automate a bunch of trial runs.
Still not sure if the FDT_ERR_BADMAGIC is cursing me here ...
