All Activity

@dale it seems like vfd-convert has not worked well. Perhaps because of some mix between script version and the template files version. Whatsoever, I've looked closer at the patch link you previously posted, this is the older pre-review dt-bindings syntax. You should be go to start with something like: /dts-v1/; /plugin/; #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/leds/common.h> &{/} { display_client: spi { #address-cells = <1>; #size-cells = <0>; compatible = "spi-gpio"; sck-gpios = <&gpio 7 GPIO_ACTIVE_HIGH>; mosi-gpios = <&gpio 2 GPIO_ACTIVE_HIGH>; cs-gpios = <&gpio 12 GPIO_ACTIVE_LOW>; num-chipselects = <1>; display@0 { compatible = "fdhisi,fd628"; reg = <0x0>; spi-3wire; spi-lsb-first; spi-rx-delay-us = <1>; spi-max-frequency = <500000>; titanmec,digits = [00 01 02 03]; titanmec,segment-mapping = [03 01 02 06 04 05 00]; #address-cells = <2>; #size-cells = <0>; led@4,0 { reg = <4 0>; function = LED_FUNCTION_ALARM; }; led@4,1 { reg = <4 1>; function = LED_FUNCTION_USB; }; led@4,2 { reg = <4 2>; function = "play"; }; led@4,3 { reg = <4 3>; function = "pause"; }; led@4,4 { reg = <4 4>; function = "colon"; }; led@4,5 { reg = <4 5>; function = LED_FUNCTION_LAN; }; led@4,6 { reg = <4 6>; function = LED_FUNCTION_WLAN; }; }; }; }; Note that I haven't tested it, just made it from some copy-paste. If it doesn't work, even partially, you would most likely need to replace &gpio with the right reference to the gpio controller wired to the display.

Do you mean gpu model? Like mail-g31?

Disabling automount (drive letter assignment) in windows before flashing might help - probably it is mount time when windows is checking and changing partition table.

First off, I would recommend using the "psuedo official" instructions from this site: https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus And there you will find the following warning: Note: If you have previously run other distributions on the box such as coreelec the below installation will not work. You will need to restore the original android firmware before attempting the install. coreelec changes the boot environment in ways that are incompatible with these Armbian builds.

Hey Guys, I know this post is old but I have some questions. I was following @Jaybyrd's instructions and I have a question pertaining to the Plugin USB-C to the power on the device "I am assuming that is on The OPi5 device." Am I supposed to plug in something else? Because it says to open a terminal "what terminal? On what device?" Thank you for your time, Michael

I wouldn't be so categorical - I have rock pi 4b, which never saw android or any os other than armbian, which has same thing- two boot devices on emmc. Since it doesn't bother me, I didn't investigate further.

@Ducdanh Nguyen Can you find the gpu version?

No that is not true. These are not from Armbian. As I said earlier if your eMMC previously had Android (which defines and uses these special partitions) even after a normal Linux repartitioning these will still appear.

It seems that eMMC has built-in boot partitions. eMMC devices are not just "raw storage" (like SD-Cards) they have special reserved hardware partitions defined by the JEDEC eMMC standard. These include: boot0 – a small partition (usually a few MB) reserved for bootloader code. boot1 – a second small boot partition, often used as a backup. RPMB (Replay Protected Memory Block) – a secure partition for keys and counters. The SoC’s boot ROM (first-stage loader) can be configured to read directly from boot0 or boot1 when powering on. Also, these partitions are read-only to decrease the risk of having corrupted boot code. Beware that they’re not used by the Linux filesystem unless explicitly written to (usually via dd when flashing U-Boot).

Hi, I am using Nanopi Neo board and I need RS485 driver to control DE pin automatically. I have prepared DTS Overlay file: /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&uart1>; __overlay__ { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&uart1_pins &uart1_de_pin>; rs485-rts-gpios = <&gpio6 8 0>; /* PG8 active-low */ linux,rs485-enabled-at-boot-time; rs485-rts-delay = <0 300>; }; }; fragment@1 { target = <&uart2>; __overlay__ { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&uart2_pins &uart2_de_pin>; rs485-rts-gpios = <&gpio0 2 0>; /* PA2 active-low */ linux,rs485-enabled-at-boot-time; rs485-rts-delay = <0 300>; }; }; }; I produced dtbo file from dts one with the command: dtc -@ -I dts -O dtb -o rs485.dtbo rs485.dts I copied this rs485.dtbo file to /boot/dtb/overlay. Also I added rs485 string to ArmbianEnv.txt and rebooted. But only TX works, RX doesn't. What should I do else to make it work?

The guidance I found is on Github, nexbox-a95x-arm https://github.com/berci9ke101/nexbox-a95x-armbianbian. I think its similar to some guidance I looked at when I first looked at Armbian and how I got Coreelec to run on my A95X box

Please elaborate what do you mean by "hardware defined". Both obviously were created by armbian-config script after full emmc format during system transfer to emmc. Questions remain the same: what for and where are they used?

Hi! With latest edge 6.15.4 the board boots fine, shutdown also clean and complete but on reboot it does not again start up. Need to powercycle😒 I gets stuck et end of shutdown. Same for latest bookworm image (I think it's 6.12x). Earlier ones did work. => Any other board also affected? => Is for reboot the watchdog involved? T.

Hi and thanks! Tested now but no luck. Compiled edge 6.15.4 Linux nanopiduo2 6.15.4-edge-sunxi #1 SMP Fri Jun 27 10:13:43 UTC 2025 armv7l GNU/Linux now i get Device creation failed: -14. [h264 @ 0x11f9b40] No device available for decoder: device type drm needed for codec h264. Stream mapping: Stream #0:0 -> #0:0 (h264 (native) -> wrapped_avframe (native)) Device setup failed for decoder on input stream #0:0 : Bad address [AVIOContext @ 0x11ac030] Statistics: 498846 bytes read, 0 seeks command as follows: ffmpeg -v trace -re -hwaccel drm -i Big_Buck_Bunny_720_10s_10MB.mp4 -f null - also tried fbdev output but same result. ffmpeg version is still ffmpeg -v ffmpeg version 5.1.7-0+deb12u1 Copyright (c) 2000-2025 the FFmpeg developers built with gcc 12 (Debian 12.2.0-14+deb12u1) configuration: --prefix=/usr --extra-version=0+deb12u1 --toolchain=hardened --libdir=/usr/lib/arm-linux-gnueabihf --incdir=/usr/include/arm-linux-gnueabihf --arch=arm --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librist --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --disable-sndio --enable-libjxl --enable-pocketsphinx --enable-librsvg --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-libplacebo --enable-librav1e --enable-shared libavutil 57. 28.100 / 57. 28.100 libavcodec 59. 37.100 / 59. 37.100 libavformat 59. 27.100 / 59. 27.100 libavdevice 59. 7.100 / 59. 7.100 libavfilter 8. 44.100 / 8. 44.100 libswscale 6. 7.100 / 6. 7.100 libswresample 4. 7.100 / 4. 7.100 libpostproc 56. 6.100 / 56. 6.100 Unfortunately there are countless forks of ffmpeg. I used the one from here https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/ As of now I haven't found anything about a current kernel and ffmpeg working on any H3, only stuff back in 2019 and/or kernel 4.x 🙂 I also tried several extraargs=cma=### up to 256M but all same error. I really woud love to get some more tech background on "how stuff works" which may help me troubleshoot. => Can we enable debug output from the cedrus driver? How? => Can we enable debug output from thev4l2 layer? How? => Which libraries are involved, eg. v4l2request, other v4l2* which may need additional install/update? => Do in need v4l2-util / v4l2-ctl to configure some stuff? If yes, what exactly? (Remember, Its currently for file playback. I know about for cam capture) => Could the v4l2loopback help? => Can anybody confirm it really works on H3 maybe on an OrangePi board? If yes I can pull the Opi device tree and compare for possible differences. T.

@Jean-Francois Lessard sorry for making you confused. Device tree source for tm16xx driver that I convert from a working openvfd.conf is below /dts-v1/; /plugin/; #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/leds/common.h> &{/} { display_client: spi { #address-cells = <1>; #size-cells = <0>; compatible = "spi-gpio"; sck-gpios = < 7 GPIO_ACTIVE_HIGH>; mosi-gpios = < 2 GPIO_ACTIVE_HIGH>; cs-gpios = < 12 GPIO_ACTIVE_LOW>; num-chipselects = <1>; display@0 { compatible = "fdhisi,fd628"; reg = <0>; spi-3wire; spi-lsb-first; spi-max-frequency = <500000>; digits { #address-cells = <1>; #size-cells = <0>; 01 02 03 04 }; leds { #address-cells = <2>; #size-cells = <0>; led@{GRID0},0 { reg = <{GRID0} 0>; function = "apps"; }; led@{GRID1},1 { reg = <{GRID1} 1>; function = "setup"; }; led@{GRID2},2 { reg = <{GRID2} 2>; function = LED_FUNCTION_USB; }; led@{GRID3},3 { reg = <{GRID3} 3>; function = LED_FUNCTION_SD; }; led@{GRID4},4 { reg = <{GRID4} 4>; function = "colon"; }; led@{GRID5},5 { reg = <{GRID5} 5>; function = "hdmi"; }; led@{GRID6},6 { reg = <{GRID6} 6>; function = "video"; }; }; }; }; }; The convert script I downloaded from this commit https://github.com/jefflessard/tm16xx-display/blob/a93b257ed4c73780fcdefbb1f1dd189599cf6ecc/vfdconf-convert Can you please help get it to work? Thanks!

@Nick A based on chatgpt with website research, it depends on with box meaning that mine still have a h313, its cortex a53. 64 bit, then what is it? (I can give you more proof that mine is allwinner h313)

Everything you wish for here is achievable with pure U-Boot technology. A long time ago, I tried to practice how to realize this here in the forum, but my lesson from it was: You can't teach old dogs new tricks, and Armbian users want to celebrate their cargo cult and hope that it will magically fulfill their wishes.

I think Thunderbird, Firefox and other programs should configure firewall as well, of course without any information about that.

@Ducdanh Nguyen without a axp chip I’m pretty sure you don’t have a h313. You’re going to have research your box on your own. Sorry but I’m too busy.

What guidance are you trying to follow?

To anyone interested, I am seeking help to test the latest tm16xx changes for the (hopefully) final upstreaming submittal. You will find in-tree patches here: https://github.com/torvalds/linux/compare/master...jefflessard:linux:tm16xx, just suffix with ".patch" to get all patches in a single download. You will find out-of-tree version, device-specific dtso and latest display-service in the https://github.com/jefflessard/tm16xx-display/tree/v4-feedback branch. Thanks to all of you for you help so far!

Flashing under Linux you will have many options to do it and check some problems on partitions etc. Normally, I use the Balena Etcher and dd by console.

I have a ssh connection with my TV BOX (it is a AMLOGIC with S912), in my etc/ssh/sshd_config I have "UsePAM yes" and without any delay for connection, and probably it was not the problem of your delay in the start connection. In addition, I installed a vnc service to work remotely using the graphical interface. Either ssh and vnc Viewer (xtightvncviewer in my Debian Desktop) run pretty well. Please, check your basic network services, as well, fix the IP in the TV BOX. In my case I did some adjusts such: cat /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.15.22 netmask 255.255.255.0 gateway 192.168.15.1 dns-nameservers 8.8.8.8 1.1.1.1 There are some network services that can be impling in your delay by ssh (it is robust, old and fast application of Linux) I hope to help you too.

I'd read rumors that uBoot has the ability for a multi-boot menu, but I was never able to get any video out of it to my DVI monitor to explore that too deeply. What I ended up doing was installing this UEFI port, and booting from it (instead of uBoot): https://github.com/edk2-porting/edk2-rk3588 The built image is about 6.6 MB, but the image actually uses 9 MB:. It consists a GPT table for a 16 MB device, plus a portion of an 8 MB partition (no flags) who's name must be uboot. The difference within the 8 MB partition is where it stores the user configuration settings. So I think the easiest and most secure way to flash the image is to first promote its size to 9 MB before flashing it to the microSD card or SPI-NOR (I've done each with good results): sudo dd if=/dev/zero of=final-for-flashing.img bs=1M count=9 sudo dd if=RK3588_NOR_FLASH.img of=final-for-flashing.img bs=512 conv=notrunc There are a few other versions of it for other hardware (other than rk3588). https://github.com/orgs/edk2-porting/repositories?type=all&q=edk2 That will boot UEFI and into grub very easily, and I do use grub to select which OS to boot into. I have one grub partition, and multiple installed OS partitions. The edk2 port is highly configurable, and recognizes hardware, including the network. Not sure if it's usable for remote access or not in its current build, but I think it can, at least, boot off the network. You can also configure a standard layout/path for your devicerees and overlays, where it will load them, but I haven't tested that out yet. If you don't override in the edk2 configuration or in grub, it will use the Vendor or Edge kernel's devicetrees (built in), or ACPI (also built in). Btw, I built it last night with a tiny change I made to the Orangepi5-plus edge devicetree to re-enable the ES8388 audio, and tested it out in Trisquel 12 with its kernel (with the devicetree from edk2) - it worked! The great thing is - their git clone and build process puts ALL the source files on your computer, so you don't need the internet to build, and you can know that any changes you make in the source code won't be "updated" overwritten by the build process. I've found with Grub, the update-grub utility will not find and add devicetrees, so you have to do that manually or hack in (which is what I've done). But again, apparently the edk2 port would make that unnecessary. So to add to the resources already mentioned, the edk2 port is open-source - they did it. Btw, I have also read that uBoot can boot grub directly, but I think you have to supply it with the address to load it into. Without knowing what I'm doing (when I first got my SBC), I didn't want to touch that.