Meestor_X

Further testing shows that Armbian 25.2.x through the current version all run the
arecord -c 2 -r 192000 -f S32_LE test.wav
without error, PROVIDED the 6.12.12 kernel is used.
 
But, any kernel version after 6.12.12 fails.
 
Now I've just got to find out what broke in 6.12.13 🙂
 

Be aware that the answer might depend on the filesystem you are using on your board Be aware that a resize operation can easily destroy your data or at least make it inaccessible have a look at shrink-backup for "reverse"

I think it is this script: https://github.com/armbian/build/blob/main/packages/bsp/common/usr/lib/armbian/armbian-resize-filesystem
 
There might be a switch or option to prevent resize, need to check documentation.
 
Or do manually after expansion:
https://unix.stackexchange.com/questions/656836/how-do-i-shrink-a-partition-right-after-shrinking-its-filesystem-with-resize2fs
 

You can use "evtest /dev/input/event0" to analyze its output.
 
Docs for gpio-leds:
https://www.kernel.org/doc/Documentation/devicetree/bindings/leds/common.yaml
https://www.kernel.org/doc/Documentation/devicetree/bindings/leds/leds-gpio.txt

I can not reiterate enough just how easy it is to "clone" your modified emmc, or microSD card OS, ... into an image file that you can easily restore with (balena)Ethcher afterwards, and all withiin Linux.
 
1:/ you'll need a USB-card-reader-adapter.
2:/ no matter how your USB-reader card reader sees your emmc, microSD card, ..., it'll most likely be mounted on a /dev/sda1 partition.
3:/ sudo dd bs=4M if=/dev/sda of=~/tmp/armbian_odroidc4_11_01_2025.img
(you don't dd the partition, you dd the drive).
4:/ (optionally) sudo xz -v armbian_odroidc4_11_01_2025.img  
(this will take some time).
 
...and that's it, ... and you know the rest.

The SoC has an ADC AFAIR, but it is used for 'Recovery Key' AFAIR. Look in Radxa PCB schematics to be sure.

No I don't think it has ADC. But you can use the numerous SPI or i2c ports to connect an external adc.

They are not on the board, you must connect to the header.
If you want to use the led on the board, you don't need the overlay

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.

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.

Copy that, @Igor. Just learning my way around here.
 
Hopefully my donation will help a little!
 
I appreciate you and your team. Armbian is a great gift to the SBC community.