Overlays do not apply even when selected in armbian-config and then rebooting

[Jorropo]

armbianmonitor -u

https://paste.next.armbian.com/hoyonuruye

 

I installed the newest fresh debian minimal image for the RockPi-S and no matter what I do overlays do not apply.

I've followed

and compiled spi1 and spi2 rk3308. I've also tested the external antenna device tree as I have installed an external antenna:

 

However neither the external antenna is being used nor spidev are present.
I have diffed

dtc -I fs -O dts /proc/device-tree

and they are identical before and after enabling the overlays in armbian-config and rebooting.

 

I was able to confirm the "overlays" work by manually copypasting their changes in linux's source dts and generating a patch file, placing it in armbian's linux patch folder and recompiling from scratch, so if I do change the options spidev works, just I somehow can only do this by editing the source.

 

Here is the `/boot/armbianEnv.txt` file generated:

verbosity=1
bootlogo=false
console=serial
overlay_prefix=rk3308
fdtfile=rockchip/rk3308-rock-pi-s.dtb
extraargs=cma=16M
rootdev=UUID=036c1484-611d-470e-b2ef-775fe550149b
rootfstype=ext4
fdt_overlays=rk3308-s0-ext-antenna rk3308-spi1-spidev rk3308-spi2-spidev
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

Also after editing the overlays in armbian-config this error pops up:

/boot/armbianEnv.txt: line 9: rk3308-spi1-spidev: command not found

 

[Werner]

9 hours ago, Jorropo said:

verbosity=1
bootlogo=false
console=serial
overlay_prefix=rk3308
fdtfile=rockchip/rk3308-rock-pi-s.dtb
extraargs=cma=16M
rootdev=UUID=036c1484-611d-470e-b2ef-775fe550149b
rootfstype=ext4
fdt_overlays=rk3308-s0-ext-antenna rk3308-spi1-spidev rk3308-spi2-spidev
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

 

Try this:

 

verbosity=1
bootlogo=false
console=serial
overlay_prefix=rk3308
fdtfile=rockchip/rk3308-rock-pi-s.dtb
extraargs=cma=16M
rootdev=UUID=036c1484-611d-470e-b2ef-775fe550149b
rootfstype=ext4
overlays=s0-ext-antenna spi1-spidev spi2-spidev
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

 

For once the prefix is already set and for the other IIRC it is just overlays instead of fdt_overlays. But not sure.

Overall there might be a bug in config-ng with overlays. Just need to verify that manual applying works.

[brentr]

Applying the overlays manually works.

I use the s0-ext-antenna and b@1.3ghz overlays frequently.

I've never done it any other way.

 

[Jorropo]

44 minutes ago, Werner said:

verbosity=1
bootlogo=false
console=serial
overlay_prefix=rk3308
fdtfile=rockchip/rk3308-rock-pi-s.dtb
extraargs=cma=16M
rootdev=UUID=036c1484-611d-470e-b2ef-775fe550149b
rootfstype=ext4
overlays=s0-ext-antenna spi1-spidev spi2-spidev
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

This does not work either.

[Jorropo]

25 minutes ago, brentr said:

Applying the overlays manually works.

I use the s0-ext-antenna and b@1.3ghz overlays frequently.

I've never done it any other way.

Have you tried it with debian minimal image or the noble CLI ?

[Meestor_X]

I too am not seeing any overlays added via armbianEnv.txt whether I add them on the overlays= line or user_overlays= line.
ls /proc/device-tree is the same whether items are added or not.

Running 24.8.3 (bookworm). Can anyone confirm that overlays aren't working in case it's something I'm doing wrong?

Edited December 11, 2024 by Meestor_X

[eselarm]

For my ROCK3A (rockchip RK3568) using Armbian 24.11.x I enable SATA (beta 6.1.84 kernel). I need the file: /boot/dtb/rockchip/overlay/rock-3a-sata.dtbo, that exists.

 

I see in armbianEnv overlay_prefix=rk35xx, but from boot.cmd there is now an extra option without applying overlay_prefix, which is needed in my case I see. I compared with and older NanoPi-NEO (allwinner sun8i/H3), how i did it there.

 

So my statement added in armbianEnv.txt is:

 

overlays=rock-3a-sata

 

and that works.

 

 

Note that I added it with a text editor to armbianEnv.txt myself, as I needed to change paths related to booting unusual things that armbian-config doesn't know.

Edited December 11, 2024 by eselarm

[Igor]

3 hours ago, eselarm said:

I see in armbianEnv overlay_prefix=rk35xx,

This was a bug in armbian-config ... fixed with https://github.com/armbian/configng/pull/299

[Meestor_X]

@eselarm are you saying that overlays are working now in 24.11.1 ? (I'm unable to update due to an issue with Armbian-config and apt update not being able to find servers)

Edited December 11, 2024 by Meestor_X

[eselarm]

@Meestor_XMy 32-bit boards still use 24.8.3 according to /etc/armbian-release I see. There there the older armbian-config is installed and I see overlays are under System->Hardware.

 

My new RK35xx boards all run beta/rolling/testing/trunk, so armbian-configng and I see no list there you can tick at the moment (configng is work-in-progress). There is an option to edit armbianEnv.txt. So that is what you need to do, same as I did and others in this topic. Make sure you understand this linux kernel DTB and overlays well enough I would say, else take older image.

[Meestor_X]

@eselarmI've been working on this for several days, and as far as I can tell, on Armbian 24.8.3, if the "simple test" for whether an overlay has installed is to see if it shows up in `/proc/device-tree` then they are not loading, whether they are added via the overlays= or user_overlays= lines in /boot/armbianEnv.txt. This is for exisitng .dbto files (like s0-ext-antenna, bs, bs@1.3ghz, sdio@10mhz, etc), ones I've copied from websites or forums, or self-created ones.

The ONLY way I've been able to successfully install an overlay is by decompiling rk3308-rock-pi-s.dtb, editing it, and recompiling it. Annoyingly, `apt upgrade` will revert that file, so being able to add overlays or user_overlays would be very helpful.

References:

https://docs.armbian.com/User-Guide_Armbian_overlays/

https://forum.radxa.com/t/usb-sound-card-on-type-c-connector/17627

https://source.android.com/docs/core/architecture/dto/syntax#reference

 

 

Edited December 12, 2024 by Meestor_X

[Meestor_X]

Is anyone be able to say whether or not overlays are working in the latest Armbian (with or without armbian-config, I can edit /boot/armbianEnv.txt directly)?

[Meestor_X]

It's been a few weeks, I've been unable to figure out why overlays don't load in armbian. I've tried everything I can think of, scoured the internet with no answers... Anyone figured anything out yet? I can't be the only one having this problem??

[mm2189]

Hello,

I can confirm, that I have the same problem as you, I am using the latest Armbian 24.11.1 and the overlay files are not applied (checked with proc/device-tree)

 

Unfortunately I don't have any solution for that - if I've found one, I will write this into your Thread.

[Meestor_X]

My understanding is that it might take an RS232 logger to see what happens when the device is booting. I bought an RS232 to USB adapter and if I can figure out how to use it to watch the boot process maybe that will lead to an answer. 

I was hoping that one of the experts here had done this already, but I know how busy everyone is!

[eselarm]

Indeed you need to hook up a 'serial console cable' for cases like this. Some call it 'serial debug cable' or you say 'RS232 logger'.  It actually should not be RS232, that is serial but other higher voltage signal levels used for long wires, PCs in the past. It must be TTL level 0V en 3V3.

 

Which pin you need is undocumented for your RockPiS ('Comming soon', cheap board so no good documentation...)  https://radxa.com/products/rockpi/pis#techspec

I guess you need to take the same pin numbers from the colored header as for RaspberryPi boards and almost all others like for my Rock3A. See what is Rx, Tx, GND.

If you look in boot.cmd for your board you could derive what setting you need on the USB side of the cable(in your laptop or so). For Linux laptop controlling  my Rock3A I use for example: sudo screen /dev/ttyUSB0 1500000

Edited December 31, 2024 by eselarm

[MaxT]

It seems that new armbian config adds full overlay file name into armbianEnv.txt, in the same time there exists overlay_prefix variable, eg:

overlay_prefix=rockchip
overlays=rockchip-rk3399-spi-jedec-nor

AFAIU, to get a full file name of an overlay, boot script joins overlay_prefix and, in this case, a full overlay name (from overlays variable as added by armbian config), adding "-" in between and obviously cannot find the resulting file name since overlay_prefix + "-" are effectively doubled: rockchip-rockchip-rk3399-spi-jedec-nor

For me practical solution was to remove "rockchip-" from overlay name. Removal of overlay_prefix variable is not working, I guess this is because boot script anyway adds leading "-" making file name wrong.

Boot scripts are black boxes for me, but may be @Igor will be able to have a look whether scripts or armbian config need any changes in logic.

[Meestor_X]

@MaxT that sounds like it's working as intended. The `overlays=` line in /boot/armbianEnv.txt should NOT have the prefix on each overlay name, and the actual overlay files do have that prefix name.
e.g. here's my

/boot/armbianEnv.txt

 

 

cat /boot/armbianEnv.txt
verbosity=1
bootlogo=false
console=serial
overlay_prefix=rk3308
fdtfile=rockchip/rk3308-rock-pi-s.dtb
extraargs=cma=16M
rootdev=UUID=036c1484-611d-470e-b2ef-775fe550149b
rootfstype=ext4
overlays=s0-ext-antenna bs bs@1.3ghz sdio@10mhz
extraargs=net.ifnames=0
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

The files in /boot/dtb/rockchip/overlay are called:
 

ls -l /boot/dtb/rockchip/overlay/rk3308-*
-rw-r--r-- 1 root root  459 Nov 18 03:47 /boot/dtb/rockchip/overlay/rk3308-b@1.3ghz.dtbo
-rw-r--r-- 1 root root  459 Nov 18 03:47 /boot/dtb/rockchip/overlay/rk3308-bs@1.3ghz.dtbo
-rw-r--r-- 1 root root  688 Nov 18 03:47 /boot/dtb/rockchip/overlay/rk3308-bs.dtbo
-rw-r--r-- 1 root root  223 Nov 18 03:47 /boot/dtb/rockchip/overlay/rk3308-emmc.dtbo
-rw-r--r-- 1 root root 1204 Nov 18 03:47 /boot/dtb/rockchip/overlay/rk3308-s0-ext-antenna.dtbo
-rw-r--r-- 1 root root  226 Nov 18 03:47 /boot/dtb/rockchip/overlay/rk3308-sdio@10mhz.dtbo
-rw-r--r-- 1 root root  226 Nov 18 03:47 /boot/dtb/rockchip/overlay/rk3308-sdio@4mhz.dtbo

The overlay files have the prefix as part of their names (rk3308 in this case), so it should "just work", but sadly it does not.

Edited January 1 by Meestor_X

[Meestor_X]

Again, my only way of checking to see if the overlays loaded is to look at /proc/device-tree. I ASSUME any loaded overlay will show up there?

[MaxT]

Again, my only way of checking to see if the overlays loaded is to look at /proc/device-tree. I ASSUME any loaded overlay will show up there?

You mentioned that overlay name shouldn't contain prefix and that's right, but I see that armbian-config adds overlay name with prefix included and to make it work, one has to remove prefix, so not sure that it works as intended.

AFIAK since overlays modify DT nodes, you can only see modified data in relevant nodes, rather than an overlay itself.

Another consideration is that overlay itself might not work. Don't remember which exactly, but some overlay for eg rk3399 is not working.

[Meestor_X]

Well, it's all a bit of a mystery.
Learning as much I can, but I sure wish there were more experts here that could offer some help!

[eselarm]

2 hours ago, Meestor_X said:

Well, it's all a bit of a mystery.

You might have the situation that your Pi sees/has 2x U-Boot, 2x boot.scr

Or even more. boot.scr is generated from boot.cmd, look in there how scripting composes the name of your overlay files.

Multiple copies and/or versions will create mystery. Take your time and see what is what and where. And connect serial console. It allows you to load dtbo manually, needs a lot of U-boot commands study, I also had to learn myself.

[Meestor_X]

Ok, I've gotten the serial monitor working for a Rock S0 (same CPU and armbian build as the Rockpi-S AFAIK).

I created an overlay to enable PWM, and added it to armbianEnv.txt:

cat /boot/armbianEnv.txt
verbosity=1
bootlogo=false
console=serial
overlay_prefix=rk3308
fdtfile=rockchip/rk3308-rock-s0.dtb
extraargs=cma=16M
rootdev=UUID=edc1b473-11f6-4b32-bf33-0986876f47d1
rootfstype=ext4
user_overlays=pwm
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

 

Here's what I see on the serial log:

---- Opened the serial port /dev/tty.usbserial-12240 ----
DDR Version V2.06 20211109
CHIP ID = 0x00003308
REG2C: 0x00000034, 0x00000034
In
589MHz
DDR3
Col=10 Bank=3 Row=15 Size=512MB
OUT: sdram_init finish.
Boot1 Release Time: Mar 24 2022 08:28:57, version: 1.36
ROM VER:0x56323030, 19
chip_id:330800,0
ChipType = 0x13, 510
DPLL = 1300 MHz
...nandc_flash_init enter...
No.1 FLASH ID:ff ff ff ff ff ff
DPLL = 1300 MHz
sfc nor id: ff ff ff
DPLL = 1300 MHz
sfc_nand id: ff ff ff
NeedKHz=200KHz,clock=12000KHz
NeedKHz=200KHz,clock=12000KHz
NeedKHz=200KHz,clock=12000KHz
mmc2:cmd8,20
mmc2:cmd5,20
mmc2:cmd55,20
DPLL = 1300 MHz
NeedKHz=18000KHz,clock=650000KHz
DPLL = 1300 MHz
NeedKHz=48000KHz,clock=650000KHz
mmc2:cmd19,100
SdmmcInit=2 0
BootCapSize=2000
UserCapSize=7456MB
FwPartOffset=2000 , 2000
NeedKHz=200KHz,clock=12000KHz
NeedKHz=200KHz,clock=12000KHz
NeedKHz=200KHz,clock=12000KHz
mmc0:cmd5,20
DPLL = 1300 MHz
NeedKHz=24000KHz,clock=650000KHz
DPLL = 1300 MHz
NeedKHz=40000KHz,clock=650000KHz
SdmmcInit=0 0
BootCapSize=0
UserCapSize=60906MB
FwPartOffset=2000 , 0
StorageInit ok = 258238
SecureMode = 0
Secure read PBA: 0x4
Secure read PBA: 0x404
Secure read PBA: 0x804
Secure read PBA: 0xc04
Secure read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x3306530 signature is wrong
recovery gpt...
GPT 0x3306530 signature is wrong
recovery gpt fail!
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x600000, size=0x994a8
RunBL31 0x40000 @ 335685 us
INFO:    Preloader serial: 0
NOTICE:  BL31: v1.3(release):30f1405
NOTICE:  BL31: Built : 17:08:28, Sep 23 2019
INFO:    Lastlog: last=0x100000, realtime=0x102000, size=0x2000
INFO:    ARM GICv2 driver initialized
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 1
INFO:    plat_rockchip_pmu_init: pd status 0xe b
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x600000
INFO:    SPSR = 0x3c9


U-Boot 2022.04-armbian-2022.04-Se4b6-P2db4-He13b-Vc245-Bda0a-R448a (Nov 16 2024 - 02:36:02 +0000)

Model: Radxa ROCK S0
DRAM:  510 MiB
Core:  275 devices, 20 uclasses, devicetree: separate
MMC:   dwmmc@ff480000: 1, dwmmc@ff490000: 0
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Model: Radxa ROCK S0
rockchip_dnl_key_pressed read board id failed
Net:   eth0: ethernet@ff4e0000
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3633 bytes read in 4 ms (886.7 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1:1
251 bytes read in 3 ms (81.1 KiB/s)
14324658 bytes read in 610 ms (22.4 MiB/s)
30097920 bytes read in 1274 ms (22.5 MiB/s)
54895 bytes read in 9 ms (5.8 MiB/s)
538 bytes read in 5 ms (104.5 KiB/s)
Applying user provided DT overlay pwm.dtbo
Moving Image from 0x680000 to 0x800000, end=2560000
## Loading init Ramdisk from Legacy Image at 04000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    14324594 Bytes = 13.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 02800000
   Booting using the fdt blob at 0x2800000
   Loading Ramdisk to 1d17d000, end 1df26372 ... OK
ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0)
   Loading Device Tree to 000000001d107000, end 000000001d17cfff ... OK

Starting kernel ...

 

Not really seeing where the overlays are loading or not in this text - but I may have missed it?
 

Edited January 6 by Meestor_X

[MaxT]

Not really seeing where the overlays are loading
 

Search for the word overlay - it's in the u-boot part of the log, before starting kernel...

[Meestor_X]

NM, I see that it did load.

 

Applying user provided DT overlay pwm.dtbo

 

It didn't actually enable the PWM, but it does look like it loaded at least!

 

I'll have to try some system ones and see what happens.

Edited January 6 by Meestor_X

[Meestor_X]

Ok, tried some adding some other overlays via armbian-config and I see that they DIDN'T load..

.

root@rock-s0:~# cat /boot/armbianEnv.txt 
verbosity=1
bootlogo=false
console=serial
overlay_prefix=rk3308
fdtfile=rockchip/rk3308-rock-s0.dtb
extraargs=cma=16M
rootdev=UUID=edc1b473-11f6-4b32-bf33-0986876f47d1
rootfstype=ext4
user_overlays=pwm
fdt_overlays=rk3308-bs@1.3ghz rk3308-bs rk3308-s0-ext-antenna rk3308-sdio@10mhz
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

 

Found U-Boot script /boot/boot.scr
3633 bytes read in 4 ms (886.7 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1:1
331 bytes read in 4 ms (80.1 KiB/s)
14324658 bytes read in 610 ms (22.4 MiB/s)
30097920 bytes read in 1275 ms (22.5 MiB/s)
54895 bytes read in 8 ms (6.5 MiB/s)
538 bytes read in 6 ms (86.9 KiB/s)
Applying user provided DT overlay pwm.dtbo
Moving Image from 0x680000 to 0x800000, end=2560000
## Loading init Ramdisk from Legacy Image at 04000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    14324594 Bytes = 13.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 02800000
   Booting using the fdt blob at 0x2800000
   Loading Ramdisk to 1d17d000, end 1df26372 ... OK
ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0)
   Loading Device Tree to 000000001d107000, end 000000001d17cfff ... OK

 

Edited January 6 by Meestor_X

[Meestor_X]

Ok, so one issue is that armbian-config doesn't create the correct line for the overlays. The overlay_prefix is automatically added to the name, and the command is "overlays=", not "ftd_overlays="

 

root@rock-s0:~# cat /boot/armbianEnv.txt 
verbosity=1
bootlogo=false
console=serial
overlay_prefix=rk3308
fdtfile=rockchip/rk3308-rock-s0.dtb
extraargs=cma=16M
rootdev=UUID=edc1b473-11f6-4b32-bf33-0986876f47d1
rootfstype=ext4
user_overlays=pwm
overlays=b@1.3ghz s0-ext-antenna sdio@10mhz
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

 

Found U-Boot script /boot/boot.scr
3633 bytes read in 4 ms (886.7 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1:1
295 bytes read in 3 ms (95.7 KiB/s)
14324658 bytes read in 609 ms (22.4 MiB/s)
30097920 bytes read in 1274 ms (22.5 MiB/s)
54895 bytes read in 9 ms (5.8 MiB/s)
459 bytes read in 6 ms (74.2 KiB/s)
Applying kernel provided DT overlay rk3308-b@1.3ghz.dtbo
1204 bytes read in 7 ms (168 KiB/s)
Applying kernel provided DT overlay rk3308-s0-ext-antenna.dtbo
226 bytes read in 6 ms (36.1 KiB/s)
Applying kernel provided DT overlay rk3308-sdio@10mhz.dtbo
538 bytes read in 6 ms (86.9 KiB/s)
Applying user provided DT overlay pwm.dtbo
Moving Image from 0x680000 to 0x800000, end=2560000
## Loading init Ramdisk from Legacy Image at 04000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    14324594 Bytes = 13.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 02800000
   Booting using the fdt blob at 0x2800000
   Loading Ramdisk to 1d17d000, end 1df26372 ... OK
ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0)
   Loading Device Tree to 000000001d107000, end 000000001d17cfff ... OK

Starting kernel ...

 

Edited January 6 by Meestor_X

[Meestor_X]

Looks like the latest armbian-config is better, but it's still not respecting the overlay_prefix.

Used armbian-config to add the sdio@10mhz overlay, and it did this to armbianEnv.txt.

 

root@rock-s0:/boot# cat armbianEnv.txt
verbosity=1
bootlogo=false
console=serial
overlay_prefix=rk3308
fdtfile=rockchip/rk3308-rock-s0.dtb
extraargs=cma=16M
rootdev=UUID=edc1b473-11f6-4b32-bf33-0986876f47d1
rootfstype=ext4
overlays=rk3308-sdio@10mhz
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

 

Of course, it didn't load the overlay, due to the prefix being added.

 

Found U-Boot script /boot/boot.scr
3633 bytes read in 4 ms (886.7 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1:1
260 bytes read in 3 ms (84 KiB/s)
14325592 bytes read in 611 ms (22.4 MiB/s)
30097920 bytes read in 1275 ms (22.5 MiB/s)
54150 bytes read in 10 ms (5.2 MiB/s)
Failed to load '/boot/dtb/rockchip/overlay/rk3308-rk3308-sdio@10mhz.dtbo'
Moving Image from 0x680000 to 0x800000, end=2560000

 

My suggestion would be to have armbian change the armbianEnv.txt file to not include the overlay_prefix= line by default. Not sure if it serves any useful purpose?

 

[Meestor_X]

Ok, that doesn't work either! 😉 I understand what you mean, now, @MaxT

The added "-" messes everything up.

 

root@rock-s0:~# cat /boot/armbianEnv.txt 
verbosity=1
bootlogo=false
console=serial
fdtfile=rockchip/rk3308-rock-s0.dtb
extraargs=cma=16M
rootdev=UUID=edc1b473-11f6-4b32-bf33-0986876f47d1
rootfstype=ext4
overlays=rk3308-b@1.3ghz rk3308-s0-ext-antenna rk3308-sdio@10mhz
user_overlays=pwm
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

 

 

Found U-Boot script /boot/boot.scr
3633 bytes read in 4 ms (886.7 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1:1
294 bytes read in 4 ms (71.3 KiB/s)
14325592 bytes read in 610 ms (22.4 MiB/s)
30097920 bytes read in 1275 ms (22.5 MiB/s)
54150 bytes read in 11 ms (4.7 MiB/s)
Failed to load '/boot/dtb/rockchip/overlay/-rk3308-b@1.3ghz.dtbo'
Failed to load '/boot/dtb/rockchip/overlay/-rk3308-s0-ext-antenna.dtbo'
Failed to load '/boot/dtb/rockchip/overlay/-rk3308-sdio@10mhz.dtbo'
538 bytes read in 5 ms (104.5 KiB/s)
Applying user provided DT overlay pwm.dtbo
Moving Image from 0x680000 to 0x800000, end=2560000

 

 

[Jorropo]

@Meestor_X thx for all of this, could you please show

find /boot/overlay-user/ -type f

Or wherever you stores pwm.dtbo
I am not sure if this has the same prefix issues (I've tried both with and without rk3308- in armbianEnv.txt and neither works)

Edited January 6 by Jorropo