Nick A

I just updated my repository. I changed one line to include boot.cmd https://github.com/NickAlilovic/build/commit/d578b352143d15abee25c805880f6ba6016a9490

Thanks Juan, I was able to boot the kernel with some changes. I used this extlinux.conf file. Changed the kernel to /Image and fdt to /dtb. I manually created a directory called extlinux in the boot directory. I then moved the extlinux.conf there. /extlinux/extlinux.conf label ARMBIAN kernel /Image fdt /dtb/allwinner/sun55i-a527-radxa-a5e.dtb append earlycon=uart8250,mmio32,0x02500000 clk_ignore_unused console=ttyS0,115200 loglevel=8 root=/dev/mmcblk0p2 rw rootwait radxa-cubie-a5e.csc I changed one line BOOTSCRIPT="extlinux.conf" # Allwinner Cortex-A55 octa core 2/4GB RAM SoC USB3 USB-C 2x GbE BOARD_NAME="radxa cubie a5e" BOARDFAMILY="sun55iw3" BOARD_MAINTAINER="Nick A" BOOTCONFIG="radxa-a5e_defconfig" OVERLAY_PREFIX="sun55i-a527" BOOT_LOGO="desktop" KERNEL_TARGET="edge" FORCE_BOOTSCRIPT_UPDATE="yes" BOOT_FDT_FILE="dtb/allwinner/sun55i-a527-radxa-a5e.dtb" BOOTFS_TYPE="fat" BOOTSCRIPT="extlinux.conf" IMAGE_PARTITION_TABLE="msdos" BOOTSTART="1" BOOTSIZE="512" ROOTSTART="513" UBOOT_EXTLINUX=yes" UBOOT_EXTLINUX_ROOT=root=UUID=%%ROOT_PARTUUID%%" UBOOT_EXTLINUX_FDT="sun55i-a527-radxa-a5e.dtb" Most Armbian boards use the boot.cmd for their bootscript. I found the line I missed in build/config/sources/families/sun55iw3.conf. I cloned a clean build and changed one line in sun55iw3.conf. declare -g BOOTSCRIPT='boot-sun50i-next.cmd:boot.cmd' declare -g ATF_TARGET_MAP="PLAT=sun55i_a523 DEBUG=1 bl31;;build/sun55i_a523/debug/bl31.bin" declare -g ATFBRANCH="branch:a523" declare -g BOOTSCRIPT='boot-sun50i-next.cmd:boot.cmd' declare -g BOOTDELAY=1 declare -g BOOTSOURCE='https://github.com/apritzel/u-boot' _ _ _ __ __ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ ___ _ _ _ _ ___ / _|/ _(_)__(_)__ _| | / _ \| '_| ' \| '_ \ / _` | ' \___| || | ' \/ _ \ _| _| / _| / _` | | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| \_,_|_||_\___/_| |_| |_\__|_\__,_|_| v25.02 rolling for radxa cubie a5e running Armbian Linux 6.12.12-edge-sun55iw3 Packages: Debian stable (bookworm) Updates: Kernel upgrade enabled and 6 packages available for upgrade Support: DIY (custom image) IP addresses: (LAN) IPv4: IPv6: Performance: Load: 5% Up time: 4 min Memory usage: 4% of 3.83G Usage of /: 3% of 58G Commands: Configuration : armbian-config Upgrade : armbian-upgrade Monitoring : htop nick@radxa-cubie-a5e:~$

Hi Juan, I'm having the same issue. I believe it's due to this scp.bin file that's needed by a523 u-boot. Trying to figure out how to modify the build scripts to add scp.bin before u-boot compiles. I tried to add a patch to include this binary but I would get an error about patching binary files not supported. https://github.com/warpme/minimyth2/tree/master/script/bootloaders/board-a527.cubie_a5e/files I also need to add extlinux.conf or boot.cmd/boot.scr.

if anyone has a Radxa cubie A5E and wants to test the lastest bringup work here you go. I don't own the other h728/a523/t527 boards so I can't test them. I willl not provide images because this is experimental. git clone https://github.com/NickAlilovic/build.git --branch warpme-6.12 --single-branch

if anyone has a Radxa cubie A5E and wants to test the lastest bringup work here you go. I don't own the other h728/a523/t527 boards so I can't test them. I willl not provide images because this is experimental. https://github.com/NickAlilovic/build/tree/warpme-6.12I

I just started working on a new project using the latest Armbian build and warpme's 6.12 kernel patches. I'm going to add warpme's u-boot patches next. The Edge builds will use warpme's 6.12 patches for now. This should make it easier to add boards already supported by warpme.

Are you using Orangepie's DRAM settings? Or did you extract your boxes DRAM settings? For USB2 ports you probably need this in your dts &ehci2 { status = "okay"; }; &ohci2 { status = "okay"; };

Afiftyp, I tested your patches. First boot the kernel detected my bluetooth module. [ 15.837115] Bluetooth: hci0: BCM: features 0x2f [ 15.860556] Bluetooth: hci0: BCM4335B0 JA-3G SemcoB62 AFH_LimitPwr_EDR2 2STOPBIT-0343 [ 15.860579] Bluetooth: hci0: BCM4335A0 (002.001.006) build 0347 But after multiple reboots I would get hci1. [ 9.987983] Bluetooth: hci1: command 0x0c03 tx timeout [ 9.988039] Bluetooth: hci1: BCM: Reset failed (-110) Also some new panfrost errors. [ 58.359410] panfrost 1800000.gpu: js fault, js=0, status=DATA_INVALID_FAULT, head=0xa1cdec0, tail=0xa1cdec0

Yup, I saw that. It still compiles not sure why. At the time I didn't correct the mistake because it would break other board patches that were added after mine. I don't know if anyone is working on adding their own board now. I'll fix it. If people are getting u-boot compile errors with their fork then this is the reason. Thanks for the reminder.

Hi Javad, if you are playing youtube videos. 720p works fine for me. 1080 freeezes. robertoj was able to get hardware video decocding working with ffmpeg-v4l2request. I haven't tested this method yet.

Hi Javad, Did you apply the GPU enable patch in your u-boot? https://github.com/NickAlilovic/build/blob/v20241125/patch/u-boot/u-boot-sunxi/allwinner-h616-GPU-enable-hack.patch

You can find patches for A523/A527 here. Just need to port them over to Armbian. https://github.com/warpme/minimyth2/tree/master/script/bootloaders/board-t527.orangepi_4a/files https://github.com/warpme/minimyth2/tree/master/script/kernel/linux-6.12/files https://github.com/warpme/minimyth2/blob/master/script/kernel/linux-6.12/files/1172-arm64-dts-allwinner-t527-add-orangepi-4a-dts.patch

The solution I found to enable stereo after googling for a few days is: editing a pulseaudio conf file sudo nano /usr/share/pulseaudio/alsa-mixer/profile-sets/default.conf In this file look for a section starting with: [Mapping analog-mono] and ending with: priority=7 It will be about 6 or 8 lines long Comment these lines out by preceding them with a " ; " (without the " " of course) This will disable the analog-mono section Save the file, sudo reboot and voila: your device profiles will contain stereo output (as well as multichanel, wich I did not try out) And, even better, your sound IS in stereo Regards, aert077 https://forums.raspberrypi.com/viewtopic.php?t=293459 I found this.. I haven't tried it.

You need the header files from my build.. https://github.com/NickAlilovic/build/releases/tag/20241125

You need to build u-boot with your DRAM settings. You can find the settings in Android DT file or you can extract it from a factory update using sunxi-tools.

This is the box I'm using.. Everything works. Bluetooth still has some bugs. (Works only after I enable it in android). https://linux-sunxi.org/Transpeed_8K618-T

[ 7.279210] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430a0-sdio for chip BCM43430/0 [ 7.284105] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430a0-sdio.sinovoip,bpi-m2-plus.bin failed with error -2 [ 7.284142] brcmfmac mmc1:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac43430a0-sdio.sinovoip,bpi-m2-plus.bin You need to rename "brcmfmac43430a0-sdio.bin" to "brcmfmac43430a0-sdio.sinovoip,bpi-m2-plus.bin"

I don't think it needs the blob.. at least my wifi works fine without it.

I haven't seen any mainline linux drivers for SV6256P chip.

Wifi: I don't see anything in your dmesg that helps. You need to open your box and take a picture of the wifi chip. HDMI audio: I think you need to switch the pulseaudio output device. It's probably set to your AV port right now. IR remote: sudo apt update ; sudo apt upgrade -y Yes it will break the custom kernel. You need to block kernel updates with the armbian config tool. You should read this thread. You'll find a lot of infomation here. https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/page/18/

To get wifi working we need to figure out which wifi chip your box has. The kernel might have already detected your wifi chip but you need to install the proper firmware. Can you post a copy of your dmesg.

Hi Mark, Try this image. First extract the image. Then use balenaEtcher software to write the image onto your SD card. A toothpick can be used to trigger FEL mode on an TX95 Max by pressing the FEL button on the PCB with the non-conductive tool. The FEL button is located inside the 3.5 mm headphone socket. To trigger FEL mode, press the button while the device is booting. https://etcher.balena.io/#download-etcher https://github.com/NickAlilovic/build/releases/download/20241125/Armbian-20241125-unofficial_24.11.0-trunk_Transpeed-8k618-t_bookworm_edge_6.10.10_xfce_desktop.tar.gz

The official armbian build hasn't patched HDMI in kernel's 6.10 and above. It's a 1000 lines of source that needs to be edited to apply cleanly. Not sure if there are other patches needed. kernel 6.7 was the last kernel version to use the patch. https://github.com/armbian/build/blob/main/patch/kernel/archive/sunxi-6.7/patches.armbian/drivers-hack-for-h616-hdmi-video-output.patch Most of the patches I use are from warpme's miniarch kernel build. I had to remove a few megous patches so warpme's patches would apply cleanly.

The usb ttl device will show you where your box stops booting using debug messages. Access to the serial console on ARM devices is even more important than on the PC. Even if you do not intend to do much U-Boot or kernel work, access to the serial console will be a life-saver when anything goes wrong. The UART pins are clearly marked with RX, TX, GND on three easy to solder pins on the PCB. This is where you connect your usb ttl device. You are adding a serial port. Remember, your RX and TX pins are crossed over. RX on your device is connected to TX on your PCB. Also, TX on your device is connected to RX on your PCB. GND on your device is connected to GND on your PCB. Every Allwinner SoC has a (BROM). You can't delete this. When your box boots up it executes the BROM which then checks the buttons for FEL mode. The BROM first checks SD-card boot availability, then NAND. The BROM will try to load the SPL (secondary program loader) from U-Boot in each of these devices, which in turn loads the kernel. There is a FEL button on the PCB (behind the AV socket), it can be reached by a non-conductive tool like a toothpick through the AV socket. Alternatively, enter FEL mode with the fel-sdboot.sunxi image written to an SD card. A non-standard USB A-to-A cable can be used to connect using FEL. https://linux-sunxi.org/FEL https://linux-sunxi.org/FEL/USBBoot https://linux-sunxi.org/UART https://github.com/linux-sunxi/sunxi-tools Your board might have secure boot enabled. Could be the reason why your board doesn't boot. Should be an easy fix. Just need to generate any RSA key and change the u-boot image type to TOC0. Most Allwinner sunxi SoCs have separate boot ROMs in non-secure and secure mode. The "non-secure" or "normal" boot ROM (NBROM) uses the existing sunxi_egon image type. The secure boot ROM (SBROM) uses a completely different image type, known as TOC0. Most secure-boot enabled devices do not burn the VENDOR_ID eFUSE, you can use any RSA key. https://linux-sunxi.org/TOC0

You should install Serial console then post your logs here