c0rnelius

If you are using the radxa-pkg github "which is the most up-to-date" know that its hardcoded to point to specific firmware. To get around this you need to create a file: This example is for an SDIO variant using the radxa dkms package cat > /etc/modprobe.d/aic8800-wireless.conf <<- EOT options aic8800_fdrv_sdio aicwf_dbg_level=0 custregd=0 ps_on=0 options aic8800_bsp_sdio aic_fw_path=/lib/firmware/aic8800_fw/SDIO/aic8800 EOT Also note that the AIC8800 firmware located in armbian-firmware is kind of old and probs not compat with the radxa builds.

Ur welcome.

Ok. Also I think these are wrong for the PI5: dtoverlay=disable-wifi dtoverlay=disable-bt I believe it's: dtoverlay=disable-wifi-pi5 dtoverlay=disable-bt-pi5 My notes on this: # Pi3 / ZERO2W dtoverlay=pi3-disable-wifi dtoverlay=pi3-disable-bt # PI5 dtoverlay=disable-wifi-pi5 dtoverlay=disable-bt-pi5 # Everything else dtoverlay=disable-wifi dtoverlay=disable-bt Back in the day, I read somewhere that Bluetooth can inhibit serial from functioning correctly on the Pi's. I've never seen it happen, but maybe using the wrong overlay is hindering it in some way? Worth looking into.

Does it work when you remove that HAT?

Same deal using Noble; https://paste.armbian.com/orexafoxen.less

I installed a fresh Trixie img to SD, made the adjustments I suggested, booted, upgraded and rebooted. root@rpi5b:~# ls /dev/ttyAMA* /dev/ttyAMA0 /dev/ttyAMA10 Still there.

Without it being enabled in the config.txt file `ttyAMA0` isn't visible under /dev, last I checked. pibox: ~ $ cat /boot/firmware/config.txt | grep "enable_uart*" enable_uart=1 pibox: ~ $ ls /dev/ttyAMA* /dev/ttyAMA0 /dev/ttyAMA10 I wouldn't use `raspi-config` on an img that isn't RASPIOS. I feel that is bound to produce failure.

Give serial priority console=tty1 console=serial0,115200

The /boot/firmware/cmdline.txt requires: console=serial0,115200 The /boot/firmware/config.txt requires: enable_uart=1 That's it.

Here is everything I have been able to piece together from the web. Maybe something in there would be helpful? https://github.com/pyavitz/binary/releases/download/060420/KICKPI.zip

Post a dmesg and sudo gpioinfo https://paste.armbian.com/

Looks like the same thing REV 1.1 uses. My guess would be the GPIO or PINCTRL may be different on the REV2. The problem is the schematic only shows 1.0 / 1.1 You could try shooting them an email in an attempt to obtain the v2 schematic? Without it, you would just be guessing.

Nice.

I was just about to post a binary with something similar. So does the above work for you? I was gonna try this: CONFIG_DRAM_SUNXI_DX_ODT=0x03030303 CONFIG_DRAM_SUNXI_DX_DRI=0x0e0e0e0e CONFIG_DRAM_SUNXI_CA_DRI=0x1f12 CONFIG_DRAM_SUNXI_TPR0=0xc0001002 CONFIG_DRAM_SUNXI_TPR10=0x2f1107 CONFIG_DRAM_SUNXI_TPR11=0xddddcccc CONFIG_DRAM_SUNXI_TPR12=0xeddc7665 CONFIG_MACH_SUN50I_H616=y CONFIG_SUNXI_DRAM_H616_DDR3_1333=y CONFIG_DRAM_CLK=648

Change the loglevel to 7 in the armbianEnv file and if anything comes up after Starting kernel ... post it.