All Activity

moved

Hi! I'm building a custom board for the AM69 processor, which is similar to AM68. My question is if there is any Arabian support for AM69 with web browsing e.g Chromium with streaming ability such as Youtube/Netflix etc? Any pre-compiled builds?

When things are not actively monitored, features stopped working without knowing. This has to be find out. At least all Armbian distributions have the same kernel, regardless of its upstream origin - Debian X,Y,Z and Ubuntu A,B,C ... have same kernel. But of course kernels versions go up all the time. I am not managing this that deep / specific. Where to search? On this forum. I am sure that this was already brought up.

@LanMarc77, I think you meant to tag @laibsch there What you're saying sounds like it could be a good option.

Actually, the connections on the cable harness appear to be good as well as all the capacitors. They are not expanded and they are not leaking--and no, I am not certain. I did not consider that it might be a board issue because I sniffed the board, there were no unusual odors when the system is powered up. Visually nothing appeared burnt. The failure occurred randomly after functioning for 4+ years. It has always been connected to an Online UPS that supports AVR, and Pure Sinewave on my server rack. I am not proficient at soldering, nor do I have a microscope, soldering iron or any of the required accessories to attempt a repair. For testing purposes, yesterday, I supplied power using an external power source from a USB enclosure and it worked. SATA Ports 1 and 2 are both functional, it is definitely related to power. I am meeting with my CEO tomorrow to discuss purchasing a new NAS type system. Leaning towards an HPE MicroServer Gen11. Going from a fantasic little affordable unit to an actual server that is going to cost around CAD$4,000 (price includes HDDs). YIkes. Thank you to everyone that took the time to read and reply though. I appreciate you, your time, and your suggestions. I was hoping I could just buy a cable and move on lol.

Alright, let's give a real quick overview where the code for A20 comes from. Let's focus on current. First stop. Board config: https://github.com/armbian/build/blob/main/config/boards/bananapipro.csc -> BOARDFAMILY="sun7i" Next stop. Family config: https://github.com/armbian/build/blob/main/config/sources/families/sun7i.conf -> No sources defined. However there are includes. Next stop. Includes: https://github.com/armbian/build/blob/main/config/sources/families/include/sunxi_common.inc -> No kernel source URL defined. Therefore kernel comes from mainline (kernel.org to say). However a version is tagged: v6.12.43 So we know: Linux source comes from unmodified mainline and the version is 6.12.43 Next stop. Patches: https://github.com/armbian/build/tree/main/patch/kernel/archive/sunxi-6.12 -> vendor family = sunxi, kernel major.minor is 6.12 All these patches are applied on top of the kernel source from kernel.org. And yes, that's a lot. I think sunxi is the worst family regarding number of additional patches to make stuff work. Next component is u-boot. https://github.com/armbian/build/blob/main/config/sources/families/include/sunxi_common.inc -> BOOTBRANCH:-"tag:v2024.01" so uboot is tagged to this version. So we know: U-Boot source comes from unmodified mainline and the version is v2024.01. And BOOTPATCHDIR="${BOOTPATCHDIR:-"u-boot-sunxi"}" which means here we find the patchset put on top of that version. Let's check. https://github.com/armbian/build/tree/main/patch/u-boot/u-boot-sunxi -> folders starting with board_ are applied only if the target board is being built. All remaining paches are always applied. There are more definitions of stuff appling for multiple families, whole architectures or even all boards regardless of architecture but in this case they are not important. Just including for the sake of completion/information: https://github.com/armbian/build/blob/main/config/sources/armhf.conf https://github.com/armbian/build/blob/main/config/sources/common.conf Good luck.

@grendel Sure you're certain you need a new cable harness? A few years ago, I replaced the HDD power switches myself, they’re just small smd transistors. 1 and 2 (Channel A) power on simultaneously, followed by 3, 4, and 5 (Channel B). There’s a built-in delay between the two channels to help manage voltage spikes that occur during HDD initialization — Channel A starts first, then Channel B.

Well I tried everything to make it work, including switching from PoE to a proven USB power supply, nothing worked. The only thing that worked is flashing back the latest Radxa bullseye image with 5.10.110 kernel, and upgrading to bookworm. I have a lot of errors at boot, so I might consider updating the kernel at some point, but I have absolutely no idea how to do that without flashing a new image. Considering 5.10.110 is the last kernel available from Radxa, I think I'm stuck... I suppressed the radxa apt in the sources.list as there is no bookworm apt, only bullseye. Could I still use the bullseye radxa apt with a bookworm debian? [ 59.024477] ramoops ramoops: failed to locate DT /reserved-memory resource [ 59.084556] fiq_debugger fiq_debugger.0: IRQ fiq not found [ 59.084581] fiq_debugger fiq_debugger.0: IRQ wakeup not found [ 59.084597] fiq_debugger_probe: could not install nmi irq handler [ 60.711536] rockchip-usb2phy ff770000.syscon:usb2-phy@e450: IRQ index 0 not found [ 60.714528] rockchip-usb2phy ff770000.syscon:usb2-phy@e460: IRQ index 0 not found [ 60.723981] rkvdec_init:1230: failed on clk_get clk_hevc_cabac [ 60.724074] mpp_rkvdec ff660000.rkvdec: shared_video_hevc_cabac is not found! [ 60.724090] rkvdec_init:1261: No hevc cabac reset resource define [ 60.746975] rockchip-vop ff8f0000.vop: missing rockchip,grf property [ 60.747264] rockchip-vop ff900000.vop: missing rockchip,grf property [ 60.750685] no ATF memory for init [ 60.763340] no ATF memory for init [ 60.767736] rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed [ 61.067311] vcc_cam: failed to get the current voltage: -EPROBE_DEFER [ 61.067671] vcc_mipi: failed to get the current voltage: -EPROBE_DEFER [ 61.090893] vcc_sdio: unsupportable voltage range: 3300000-3000000uV [ 61.094146] rockchip-dmc dmc: Failed to get ddr_leakage [ 61.094884] rockchip-dmc dmc: could not find power_model node [ 61.099683] rksfc_base v1.1 2016-01-08 [ 61.695258] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 61.695324] rockchip-pcie f8000000.pcie: deferred probe failed [ 69.217783] rk-multicodecs es8316-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 69.309154] rk-multicodecs es8316-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 69.456788] debugfs: File 'Left Hp mixer' in directory 'dapm' already present! [ 69.456983] debugfs: File 'Right Hp mixer' in directory 'dapm' already present! [ 69.457046] debugfs: File 'HPCP L' in directory 'dapm' already present! [ 69.457078] debugfs: File 'HPCP R' in directory 'dapm' already present! [ 69.457127] debugfs: File 'HPVOL L' in directory 'dapm' already present! [ 69.457157] debugfs: File 'HPVOL R' in directory 'dapm' already present! [ 70.938277] udc fe800000.usb: failed to start radxa-otgutils: -19 [ 81.008640] ieee80211 phy0: brcmf_escan_timeout: timer expired [ 89.540144] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 89.540187] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 89.540706] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 89.540728] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 89.541174] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 89.541195] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 6419.589939] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 6419.589981] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 6419.590499] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 6419.590521] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 6419.590978] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 6419.591003] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22

@dale looking at the openvfd_x98h.dtso file you shared, openvfd uses these pins: openvfd_gpio_clk = <&pio 2 7 0>; openvfd_gpio_dat = <&pio 2 2 0>; openvfd_gpio_stb = <&pio 2 12 0>; So you should try with their equivalent: mosi-gpios = <&pio 2 2 GPIO_ACTIVE_HIGH>; /* mosi is the same as openvfd_gpio_dat */ sck-gpios = <&pio 2 7 GPIO_ACTIVE_HIGH>; /* sck is the same as openvfd_gpio_clk */ cs-gpios = <&pio 2 12 GPIO_ACTIVE_LOW>; /* cs is the same as openvfd_gpio_stb */

Hi, thanks for checking. I check dmesg -T | grep spi_gpio and see the error spi_gpio spi: probe with driver spi_gpio failed with error -22. Also the /sys/class/leds is empty. Do you think the gpio pins are not correct? Below are current gpio pins I try this time mosi-gpios = <&pio 2 11 GPIO_ACTIVE_HIGH>; /* PC11 = data */ sck-gpios = <&pio 2 12 GPIO_ACTIVE_HIGH>; /* PC12 = clock */ cs-gpios = <&pio 7 5 GPIO_ACTIVE_LOW>; /* PH5 = strobe/latch */

That will definitely make you not get hardware accelerated video Make sure to follow the 3 commands to install the custom repo, its certificate and higher priority: sudo wget http://apt.undo.it:7242/apt.undo.it.asc -O /etc/apt/trusted.gpg.d/apt.undo.it.asc . /etc/os-release && echo "deb http://apt.undo.it:7242 $VERSION_CODENAME main" | sudo tee /etc/apt/sources.list.d/apt.undo.it.list $ echo -e "Package: *\nPin: release o=apt.undo.it\nPin-Priority: 600" | sudo tee /etc/apt/preferences.d/apt-undo-it sudo apt update Then check that the new custom dpkgs are available for install/upgrade apt list ffmpeg-whatever Here's how I force install a specific version: sudo apt install packagename=nn.nn.n

Thanks, all's clear I might be such random person lol. However it would need either a lot of time or information delivered when it has been broken; open code is nice but there are too many kernel versions and distributions. That matter would need some deeper conversation. I think you was the person managing this area so maybe you know where to search the issue to correct it or you know the person who might know. I'm affraid I found the reason of long image generation time: my laptop fans are to silent today and it might be the reason...

Thinking about a better automated option to revert (e.g. just power off like @The Tall Man suggested) while still not touching uboot or even lower level layers the initrd might be an option based on the current setup. I assume we have very little probability for kernel+initrd load problems. Most issues will probably occur after the rootfs was mounted and handover. Integrating additional scripts inside the initrd could be used to auto revert the symlink in case of failure. Before we are going to reboot we place a status file inside the boot partitions boot directory that we just updated. For this first reboot we call this testboot1. When the new system boots up initrd script checks for this file and renames it to testboot2. If the system boots up correctly or can be accessed remotely /boot/testboot2 is deleted. But if the initrd script sees a testboot2 file during its boot process it knows something went wrong. It then changes the /boot symlink to the other boot folder deletes testboot2 and reboots instead of handing over to the rootfs. If the new system got stuck after it handed over to the rootfs the initrd script should have renamed the file to testboot2 already and a hard restart should revert. This hard reset could probably also be fully automated if the SBC has a hardware watchdog. If the watchdog module is integrated in the initrd it could set it to a reasonable value. The watchdog is then only disabled or changed to normal operation once the system is reliable working or if disabled via remote access. This concept would build on top of what exist. Any community member could choose to test the idea and implement management scripts. I guess everything can be done in bash/sh. It could also lead to a new armbian package: simpleAB which is not perfect but might be enough for many. It would not need many uboot or architectural changes. I guess it also works for all armbian supported devices? But as @Igor already said. One needs to invest.

@ebin-dev@mtlmarko189 Not sure if this issue can be resolved. I've been running tests with different chip versions and discovered that the first batch of Helios64 devices includes an unreliable chip. Take a look at this: root@helios64:~# lsusb -v -d 0bda:8156 | grep bcdDevice bcdDevice 30.00 bcdDevice 31.04 According to cnx-software 30.00 corresponds to RTL8156 31.00 corresponds to RTL8156B 31.04 correspond to the third version, RTL8156BG So far, the RTL8156BG has been working better with Linux kernel 6.12.42. P.S. The workaround suggested by @ebin-dev helps reduce the symptoms, but the NIC is still sending corrupted packets.

"apt policy ffmpeg" FTW ;-) apt also has a command-line option to force the installation of a particular package version. To automate this, you can put a file under /etc/apt/preferences.d/

This is not recommended as its not controlled environment. It might work, but no warranties. HDMI output is broken in general (on this particular SoC) regardless of variant, desktop, cli, minimal. Its known bug, but we currently don't have anyone maintaining Allwinner A20 series so its up to random person to fix this. Code is open, so anyone can. Then it should be o.k. since HDMI output is not needed.

Thank you for your work, @dg4gg8cb9s

This is an H96Max Factory default work around, no TV box device really turn off, it's the way the factory deal with the "remote control" power on function, the device is always waiting for a IR remote control to trigger. You can find a way around it on the pmic section from DTS. Thats a problem caused by BOM of materials in the factory, they start to use a new wifi card because of chip shortages. You can work around it using this method

This is built on an old kernel 5.10 and would probably need a fair bit of work to get up to date. Last repo I came across with support for the old cedar driver was kernel 6.1 but I have not found anything more recent than this. Have you not created the configuration file as mentioned: It still looks to me like the packaged version of ffmpeg is being installed rather than from the custom repo. Notice that there is no option listed for v4l2-request. I had problems connecting and had to temporarily switch from my wifi to mobile in order to install the packages.

My setting was without docker and I was not using it. I was observing shell output, and because I selected version without desktop (on which HDMI could affect) while there were some desktop components additions during script processing. Small remark: I use sbc as server with good quality server 1TB 2,5"drive.

You will need to flash an android "Update image" first, into EMMC, to go back to factory defaults. https://wiki.youyeetoo.com/en/YY3568/unpack https://drive.google.com/drive/folders/11BrqafnkEyFaM-D0gaPFhrmnRM47JAEU MaskRom mode upgrade firmware First of all, make sure that you have entered the MaskRom upgrade mode, and then perform the following firmware upgrade operations. Upgrade firmware in loader mode Open the AndroidTool tool, the board enters the upgrade mode, and a LOADER device will be found on the AndroidTool. Then perform the following upgrade firmware operation.

Works well on my side - could not reproduce (with Docker based compilation), but however there is a (common to a20 boards) problem with HDMI output while boards otherwise works.

From @fevangelou 1. Install the "rkdeveloptool" tool first, as instructed in: https://docs.radxa.com/en/zero/zero3/low-level-dev/rkdeveloptool?host-os=debian sudo apt-get update sudo apt-get install -y libudev-dev libusb-1.0-0-dev dh-autoreconf pkg-config libusb-1.0 build-essential git wget git clone https://github.com/rockchip-linux/rkdeveloptool cd rkdeveloptool autoreconf -i ./configure make -j $(nproc) sudo cp rkdeveloptool /usr/local/sbin/ At the time of writing, this installed version 1.32. If you installed "rkdeveloptool" from Ubuntu's repos, it would install version 1.0 which may work, but let's be on the safe side here... 2. Connect and boot the device to loader/maskrom mode 2.1 While pressing the reset button (back/right) with a pin, connect the USB 2.0 port (back/left) and the power cable. Gotta be careful here not to miss the reset button pressing while connecting the cables. 2.2 Use the rkdeveloptool tool to identify the device and the mode it is on ("loader" or "maskrom"). $ rkdeveloptool ld ...should show the connected device if point 2.1 was successful - e.g. on my 8GB RAM device it printed this: DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=304 Loader Or after I had already flashed Armbian, it would show: DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=304 Maskrom (If you installed "rkdeveloptool" from Ubuntu's repo, the command is "rkdeveloptool list" if I recall correctly - every other "rkdeveloptool" command following though is the same) Now grab the latest release of Armbian for this device. At the time of writing it was: https://github.com/armbian/community/releases/download/25.11.0-trunk.106/Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img.xz (the name of the device is on the filename) Extract the included .img file with (sudo apt install xz-tools): $ unxz Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img.xz 2.2.1 If in "loader" mode (see the last part of the command's output above), simply flash Armbian directly. E.g. $ sudo rkdeveloptool wl 0x0 Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img (if you attempt to flash the attached bootloaders, you'll get a "device not supported" error - Armbian already contains a bootloader) 2.2.2 If in "maskrom" mode (e.g. if you are re-flashing Armbian), flash the bootloader first: # For the 8GB RAM device use the attached (in this post) H96-MAX-8gb-MiniLoaderAll.bin file $ sudo rkdeveloptool db H96-MAX-8gb-MiniLoaderAll.bin # For the 4GB RAM device use the attached (in this post) H96-MAX-4gb-MiniLoaderAll.bin file $ sudo rkdeveloptool db H96-MAX-4gb-MiniLoaderAll.bin ...and then re-flash Armbian as you did the first time: $ sudo rkdeveloptool wl 0x0 Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img 2.3 Reboot the device with: $ sudo rkdeveloptool rd Done! If all goes well, once you reboot the device you will be asked to set a root password and optionally a sudo user. Rebooting afterwards you should now be greeted with: _ _ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, | |___| |__/ v25.11 rolling for h96-tvbox-3566 running Armbian Linux 6.12.44-current-rockchip64 Packages: Debian stable (bookworm), possible distro upgrade (trixie) Updates: Kernel upgrade enabled and 2 packages available for upgrade Support: for advanced users (rolling release) IPv4: (LAN) 192.168.1.10 (WAN) 1.2.3.4 Performance: Load: 3% Uptime: 2 min Memory usage: 2% of 7.50G CPU temp: 40°C Usage of /: 3% of 57G Commands: Configuration : armbian-config Upgrade : armbian-upgrade Monitoring : htop Last login: Sat Aug 30 12:47:54 2025 Key points: - If you do this the first time, it's obviously a matter of just flashing the latest Armbian image directly. - You don't need to open the device or compile Armbian.

@djurny Sorry for the super late response. Here the answers on your questions: ls -Failh /dev/rtc* 457 lrwxrwxrwx 1 root root 4 Mar 7 01:56 /dev/rtc -> rtc0 107 crw------- 1 root root 253, 0 Mar 7 01:56 /dev/rtc0 542 crw------- 1 root root 253, 1 Mar 7 01:56 /dev/rtc1 ls -Failh /sys/class/rtc/ total 0 3926 drwxr-xr-x 2 root root 0 Jan 1 1970 ./ 10 drwxr-xr-x 63 root root 0 Jan 1 1970 ../ 8295 lrwxrwxrwx 1 root root 0 Jan 1 1970 rtc0 -> ../../devices/platform/soc/1f00000.rtc/rtc/rtc0/ 21463 lrwxrwxrwx 1 root root 0 Sep 3 23:18 rtc1 -> ../../devices/platform/soc/1c2ac00.i2c/i2c-0/0-0068/rtc/rtc1/ egrep -- . /sys/class/rtc/*/name /sys/class/rtc/rtc0/name:sun6i-rtc 1f00000.rtc /sys/class/rtc/rtc1/name:rtc-ds1307 0-0068 dmesg | egrep -i -- 'rtc' [ 1.042165] sun6i-rtc 1f00000.rtc: registered as rtc0 [ 1.042235] sun6i-rtc 1f00000.rtc: setting system clock to 1970-01-01T00:00:04 UTC (4) [ 1.774229] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes [ 1.776966] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes [ 19.347508] rtc-ds1307 0-0068: registered as rtc1 sudo hwclock --rtc=/dev/rtc0 # per default this is the H2+ built-in RTC 2025-09-03 23:32:07.935209+10:00 ==> date set to Australia (Tasmania) sudo hwclock --rtc=/dev/rtc1 # per default this is going to be the I2C RTC 2000-01-02 15:51:14.147878+11:00 ==> ?????????? So, I clearly don't understand the system. What do I want? Just the right time when connected to a wireless network. (If not available, my system switches to being an Access Point) If my system is acting as an Access Point, the date and time needs to be correct to, that's why I thought I need an RTC module. If not needed, how do I get the right time when my system operates as an Access Point. Thanks for helping