Search the Community

Description Move tv-box based rk3318-box and rk322x-box target to use u-boot v2024.07-rc5 from v2024.01, mostly for experimentation and also because v2024.07 contains some fixes for rockchip devices explained in this previous PR: https://github.com/armbian/build/pull/6731, in particular we can leverage uboot relocation for rockchip 64 bit devices and rk3328 hdmi/vop/phy drivers are now mainlined. This PR also rework hdmi/vop/phy patches for rk322x and fixes usb issues on rk3318-box The changes does not affect any other board, since none of them actually use v2024.07 of uboot (at the moment of writing the comment, it is still in RC5). The v2024.07 patch directory has been prepared though and it is ready for others to jump in. GitHub issue reference: Jira reference number AR-2400 How Has This Been Tested? [x] Various tests on rk322x-box system, including boot from sdcard, boot from emmc and checks about the expected boot order (sdcard -> usb -> emmc) [x] Same as above on rk3318-box system Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings View the full article

@Magd Almuntaser unfortunately this forum does not offer support for armbian forks for various technical issues. what I can tell you is that ipbs9505 dtb is correct if you boot the fork image from micro sd when you do the installation on emmc you will have to use that precise dtb as if you had the Wojia-TV-IPBS9505 (s905L2) tv box. I also bricked the board some time ago trying to install the official armbian on emmc. my problem was trying to overwrite an installation of a fork distro previously done on the emmc rather than starting from an emmc with the factory android image. I am currently using the fork image with this kernel Distribution: Armbian 24.2.1 jammy Kernel version: Linux 5.15.145-ophub aarch64 and I must say that it is stable for my experimental server needs. I have no interest in putting modern kernels because I noticed that using them on micro sd they were not very stable and I chose an older kernel.

These instructions are for Amlogic CPUs for TV Boxes. 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. Download links: Weekly Community Rolling Builds: https://www.armbian.com/amlogic-s9xx-tv-box/ or build your own image using the Armbian build framework Once you download your chosen build, you need to burn the image to an SD card. Generally balenaEtcher is recommended as it does a verification of the burn. Also be sure to use high quality SD cards. Once you have the SD card with your chosen build, then you need to edit the boot configuration file on the SD card. In the BOOT partition of the SD card there will be a file /boot/extlinux/extlinux.conf, that you need to edit. There will also be a extlinux.conf.template file to use as a reference. You will need to add a line into the extlinux.conf file for the Device Tree (dtb) file you will be using for your box. Place this line before the APPEND line as shown in the .template file. Basically you need to have the correct dtb for your box. You may need to attempt to use different dtb files until you find the one that works the best for your box's hardware (there are a bunch of dtb files in /boot/dtb/amlogic/... to try depending on your cpu architecture and hardware). It is unlikely that there will be a matching dtb file for your TV box. The idea is to find the one that works best for your box. This may mean that you try booting with different dtb files until you fine one that works good enough for your needs. By searching the forums you will find information about what dtbs other users have found work best for different boxes. Because you are booting from an SD card, you can easily try different dtb files. The dtd files are named by cpu family. So for example dtb files for the s905x2 cpu are named meson-g12a-*. Below there is a table that shows the identifiers for each familiy (g12a for s905x2 in this case). Next you need to copy the correct uboot for your box. This is needed for how these builds boot on amlogic boxes. There are four different u-boot files located in the /boot directory: u-boot-s905, u-boot-s905x-s912, u-boot-s905x2-s922, u-boot-s905x3 You need to copy (note copy not move) the u-boot file that matches your cpu to a new file named u-boot.ext in the /boot directory So for example with a TX3 mini box that has an s905w cpu you would copy u-boot-s905x-s912 to u-boot.ext: cp u-boot-s905x-s912 u-boot.ext (See table below for more details on which u-boot to use for which cpu) Once you have your SD card prepared you need to enable multiboot on the box. There are different ways documented to do this, but the most common is the "toothpick" method. The "toothpick" method means to hold the reset button while applying power to the box. The reset button is often hidden and located at the back of the audio/video jack connector. By pressing that button with a toothpick or other such pointed device you can enable multiboot. What you need to do is have the box unplugged, have your prepared sd card inserted, then press and hold the button while inserting the power connector. Then after a bit of time you can release the button. (I don't know exactly how long you need to hold the button after power is applied, but if it doesn't work the first time try again holding for longer or shorter times). You should now be booting into armbian/linux. Note that the first boot takes longer as it is enlarging the root filesystem to utilize the entire SD card. After you are satisfied that your box is working correctly for your needs you can optionally copy the installation from the SD card to internal emmc storage (assuming your box has emmc). (Note: Installing to emmc has some risks of bricking your box. Don't do this unless you feel you understand how to reinstall your box's android firmware) You install armbian to emmc by running the shell script in the /root directory: install-aml.sh. Note: It is not possible to install into emmc on boxes with the s905 cpu (s905x, s905w, s905x2, etc however should all be supported). It is recommended that you make a backup of emmc first. Also be prepared if anything goes horribly wrong with your emmc install to reinstall the android firmware using the Amlogic USB Burning Tool to unbrick your device. If you have or can find an original android firmware on the internet and you can generally (but not always) recover a bricked box using the Amlogic tool and the original firmware file. Mapping from CPU to uboot and dtb: u-boot-s905 s905 - gxbb u-boot-s905x2-s912 S905X - gxl S905W - gxl S905D - gxl S905L - gxl S805X - gxl S912 - gxm A311D - gxm u-boot-s905x2-s922 S905X2 - g12a S922 - g12b u-boot-s905x3 S905X3 - sm1 Not supported or not tested S805 - S905W2 - S905X4 - S805X2 - s4 A113D - axg A113X - axg Note: Followup posts in this thread should be limited to comments to improve or better understand these instructions. Other issues should be posted as new questions in the Amlogic CPU Boxes sub-forum.

Hi I’m thinking of buying a more powerful TV box, and I see that everyone recommends Rockchip. However, when I look at performance, I notice that the S905X3 has much more power than an RK3566 and is also cheaper. There are comments that development for Amlogic is stalled, but new versions continue to be released from what I can see. I only want it for setting up a Pi-hole and some Dockerized applications. Am I making a mistake if I go for an S905X3? Currently, I have an S905X, and although it was a bit challenging, it’s working quite well

Thank you all for all your responses. I finally bought a s905x3, h96 max x3, and all the hours and headaches spent with the s905x have greatly simplified the installation of the new tv box. for my needs, I don't need an sbc, at least for now.

Download Armbian with HA Then boot the image, wait few minutes and login via http://ip_address_of_armbian_running_ha:8123 (official onboarding manual) Home Assistant Supervised is, more or less, a full blown Home assistant. Main difference between HA OS and Armbian with HA is that underlying OS here is clean Armbian Debian Bookworm and there is custom dedicated buildroot OS that is provided for a few single board computers, primarily for Raspberry Pi. We provide HA on a small selection of single board computers, but in theory, its possible to run this on (almost) all that are possible to build. I am running HA on Odroid N2+ and it works without any problems. I have z-wave network with sensors and switches, air humidifier, Android TV, Android phones, dishwasher, ... Things works flawlessly, much better then few years back when I started with home automation for a first time, with OpenHab. This time it was setup from scratch and in a matter of days, most of devices are in function, playing with automation. Tested on: Odroid N2/N2+ Odroid M1 Nanopi R4S Rock 5B Uefi-x86 Khadas VIM1S Khadas VIM4 (Amlogic vendor kernel trouble, failing / need inspection) Bananapi M2 Pro Provided for but untested (images you find on board downloads locations, seek them here https://www.armbian.com/download/😞 DIY Contribute Support: single board computer hardware https://www.armbian.com/bugs home assistant functions https://community.home-assistant.io/

Hi Guys, I was trying to install Armbian in a couple of boxes buit I had no luck. One is a SEI500W from SEI Robotics with AML 905X2 and the other is a Sagecom DIW 585 with AML 905X I followed the process and after trying to boot to recovery they start Andoid tv as normal (just takes more time). In the other hand I was able to run EMUELEC (Gaming emulator) on both devices with an image on SD so I'm assuming the problem is not a block. What do you think? Is there any ideas to try? Thank you in advance!

https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first

Model: RK3228A. Hello, I'm having some problems while trying to burn an image onto my TV BOX. During the burning process (around 50% completion), the TV BOX shut down due to a power surge in my neighborhood. Now, when I try to use the Multitool, my keyboard doesn't work anymore. It lights up for a millisecond and then turns off. I have tried the following: Installed drivers during the Linux boot process by adding commands to the boot scripts, but I cannot change them due to permissions on the SD card. Reburned the SD card with the Multitool image, but it still doesn't work (I also tried different SD cards). Booted with an ISO to wipe data from memory and start again, but that didn't work either. Used another keyboard. Reset my TV BOX. Does anyone have any ideas to help me, please?

Sorry, don't have the Armbianmonitor info handy but wanted to get this started... I'm trying to bring up a Libre Renegade RK3328-CC for use as a media center. Armbian's performance is absolutely wonderful compared to the other builds I've tried on this box. Unfortunately, I want the HDMI output going to a Samsung Frame TV, and resolution negotiation fails badly -- I get obvious rasters with black between them, nowhere near the 4K that this TV model is capable of and not even a smooth conversion (Note that the eyes here suggests that the black line is occurring every third raster or something like that...) What information I have gathered so far: TV: Samsung 43" “The Frame”, model QN43LS03BAFXZA Firmware T-PTMAKVC-1622.4, BT-S 4K native resolution, but should be able to upconvert edid-decode (hex): 00 ff ff ff ff ff ff 00 4c 2d 7f 72 00 0e 00 01 01 20 01 03 80 5f 36 78 0a b3 61 ab 4f 46 a8 27 0b 50 54 bd ef 80 71 4f 81 c0 81 00 81 80 95 00 a9 c0 b3 00 d1 c0 04 74 00 30 f2 70 5a 80 b0 58 8a 00 50 1d 74 00 00 1e 56 5e 00 a0 a0 a0 29 50 30 20 35 00 50 1d 74 00 00 1a 00 00 00 fd 00 18 4b 0f 51 1e 00 0a 20 20 20 20 20 20 00 00 00 fc 00 53 41 4d 53 55 4e 47 0a 20 20 20 20 20 01 9f 02 03 51 f0 52 5f 10 1f 04 13 05 14 20 21 22 5d 5e 62 64 07 16 03 12 2f 0d 57 07 09 07 07 15 07 50 57 07 01 67 54 03 83 0f 00 00 e2 00 4f e3 05 c3 01 6e 03 0c 00 30 00 b8 44 20 00 80 01 02 03 04 e3 06 0d 01 e5 0e 60 61 65 66 e5 01 8b 84 90 01 02 3a 80 18 71 38 2d 40 58 2c 45 00 50 1d 74 00 00 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ea Block 0, Base EDID: EDID Structure Version & Revision: 1.3 Vendor & Product Identification: Manufacturer: SAM Model: 29311 Serial Number: 16780800 Made in: week 1 of 2022 Basic Display Parameters & Features: Digital display Maximum image size: 95 cm x 54 cm Gamma: 2.20 RGB color display First detailed timing is the preferred timing Color Characteristics: Red : 0.6699, 0.3115 Green: 0.2734, 0.6591 Blue : 0.1533, 0.0449 White: 0.3125, 0.3291 Established Timings I & II: IBM : 720x400 70.081663 Hz 9:5 31.467 kHz 28.320000 MHz DMT 0x04: 640x480 59.940476 Hz 4:3 31.469 kHz 25.175000 MHz Apple : 640x480 66.666667 Hz 4:3 35.000 kHz 30.240000 MHz DMT 0x05: 640x480 72.808802 Hz 4:3 37.861 kHz 31.500000 MHz DMT 0x06: 640x480 75.000000 Hz 4:3 37.500 kHz 31.500000 MHz DMT 0x09: 800x600 60.316541 Hz 4:3 37.879 kHz 40.000000 MHz DMT 0x0a: 800x600 72.187572 Hz 4:3 48.077 kHz 50.000000 MHz DMT 0x0b: 800x600 75.000000 Hz 4:3 46.875 kHz 49.500000 MHz Apple : 832x624 74.551266 Hz 4:3 49.726 kHz 57.284000 MHz DMT 0x10: 1024x768 60.003840 Hz 4:3 48.363 kHz 65.000000 MHz DMT 0x11: 1024x768 70.069359 Hz 4:3 56.476 kHz 75.000000 MHz DMT 0x12: 1024x768 75.028582 Hz 4:3 60.023 kHz 78.750000 MHz DMT 0x24: 1280x1024 75.024675 Hz 5:4 79.976 kHz 135.000000 MHz Apple : 1152x870 75.061550 Hz 192:145 68.681 kHz 100.000000 MHz Standard Timings: DMT 0x15: 1152x864 75.000000 Hz 4:3 67.500 kHz 108.000000 MHz DMT 0x55: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz DMT 0x1c: 1280x800 59.810326 Hz 16:10 49.702 kHz 83.500000 MHz DMT 0x23: 1280x1024 60.019740 Hz 5:4 63.981 kHz 108.000000 MHz DMT 0x2f: 1440x900 59.887445 Hz 16:10 55.935 kHz 106.500000 MHz DMT 0x53: 1600x900 60.000000 Hz 16:9 60.000 kHz 108.000000 MHz (RB) DMT 0x3a: 1680x1050 59.954250 Hz 16:10 65.290 kHz 146.250000 MHz DMT 0x52: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz Detailed Timing Descriptors: DTD 1: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz (1872 mm x 1053 mm) Hfront 176 Hsync 88 Hback 296 Hpol P Vfront 8 Vsync 10 Vback 72 Vpol P DTD 2: 2560x1440 59.950550 Hz 16:9 88.787 kHz 241.500000 MHz (1872 mm x 1053 mm) Hfront 48 Hsync 32 Hback 80 Hpol P Vfront 3 Vsync 5 Vback 33 Vpol N Display Range Limits: Monitor ranges (GTF): 24-75 Hz V, 15-81 kHz H, max dotclock 300 MHz Display Product Name: ‘SAMSUNG’ Extension blocks: 1 Checksum: 0x9f Block 1, CTA-861 Extension Block: Revision: 3 Underscans IT Video Formats by default Basic audio support Supports YCbCr 4:4:4 Supports YCbCr 4:2:2 Native detailed modes: 0 Video Data Block: VIC 95: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz VIC 16: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz VIC 31: 1920x1080 50.000000 Hz 16:9 56.250 kHz 148.500000 MHz VIC 4: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz VIC 19: 1280x720 50.000000 Hz 16:9 37.500 kHz 74.250000 MHz VIC 5: 1920x1080i 60.000000 Hz 16:9 33.750 kHz 74.250000 MHz VIC 20: 1920x1080i 50.000000 Hz 16:9 28.125 kHz 74.250000 MHz VIC 32: 1920x1080 24.000000 Hz 16:9 27.000 kHz 74.250000 MHz VIC 33: 1920x1080 25.000000 Hz 16:9 28.125 kHz 74.250000 MHz VIC 34: 1920x1080 30.000000 Hz 16:9 33.750 kHz 74.250000 MHz VIC 93: 3840x2160 24.000000 Hz 16:9 54.000 kHz 297.000000 MHz VIC 94: 3840x2160 25.000000 Hz 16:9 56.250 kHz 297.000000 MHz VIC 98: 4096x2160 24.000000 Hz 256:135 54.000 kHz 297.000000 MHz VIC 100: 4096x2160 30.000000 Hz 256:135 67.500 kHz 297.000000 MHz VIC 7: 1440x480i 59.940060 Hz 16:9 15.734 kHz 27.000000 MHz VIC 22: 1440x576i 50.000000 Hz 16:9 15.625 kHz 27.000000 MHz VIC 3: 720x480 59.940060 Hz 16:9 31.469 kHz 27.000000 MHz VIC 18: 720x576 50.000000 Hz 16:9 31.250 kHz 27.000000 MHz Audio Data Block: Linear PCM: Max channels: 6 Supported sample rates (kHz): 192 96 48 44.1 32 Supported sample sizes (bits): 24 20 16 Linear PCM: Max channels: 2 Supported sample rates (kHz): 48 44.1 32 Supported sample sizes (bits): 24 20 16 AC-3: Max channels: 6 Supported sample rates (kHz): 48 44.1 32 Maximum bit rate: 640 kb/s Enhanced AC-3 (DD+): Max channels: 8 Supported sample rates (kHz): 48 44.1 32 Supports Joint Object Coding MAT (MLP): Max channels: 8 Supported sample rates (kHz): 192 96 48 Supports Dolby TrueHD, object audio PCM and channel-based PCM Hash calculation not required for object audio PCM or channel-based PCM Speaker Allocation Data Block: FL/FR - Front Left/Right LFE1 - Low Frequency Effects 1 FC - Front Center BL/BR - Back Left/Right Video Capability Data Block: YCbCr quantization: No Data RGB quantization: Selectable (via AVI Q) PT scan behavior: No Data IT scan behavior: Supports both over- and underscan CE scan behavior: Supports both over- and underscan Colorimetry Data Block: xvYCC601 xvYCC709 BT2020YCC BT2020RGB Reserved MD0 Vendor-Specific Data Block (HDMI), OUI 00-0C-03: Source physical address: 3.0.0.0 Supports_AI DC_36bit DC_30bit DC_Y444 Maximum TMDS clock: 340 MHz Extended HDMI video details: HDMI VICs: HDMI VIC 1: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz HDMI VIC 2: 3840x2160 25.000000 Hz 16:9 56.250 kHz 297.000000 MHz HDMI VIC 3: 3840x2160 24.000000 Hz 16:9 54.000 kHz 297.000000 MHz HDMI VIC 4: 4096x2160 24.000000 Hz 256:135 54.000 kHz 297.000000 MHz HDR Static Metadata Data Block: Electro optical transfer functions: Traditional gamma - SDR luminance range SMPTE ST2084 Hybrid Log-Gamma Supported static metadata descriptors: Static metadata type 1 YCbCr 4:2:0 Video Data Block: VIC 96: 3840x2160 50.000000 Hz 16:9 112.500 kHz 594.000000 MHz VIC 97: 3840x2160 60.000000 Hz 16:9 135.000 kHz 594.000000 MHz VIC 101: 4096x2160 50.000000 Hz 256:135 112.500 kHz 594.000000 MHz VIC 102: 4096x2160 60.000000 Hz 256:135 135.000 kHz 594.000000 MHz Vendor-Specific Video Data Block (HDR10+), OUI 90-84-8B: Application Version: 1 Detailed Timing Descriptors: DTD 3: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz (1872 mm x 1053 mm) Hfront 88 Hsync 44 Hback 148 Hpol P Vfront 4 Vsync 5 Vback 36 Vpol P Checksum: 0xea I understand that Armbian is an experimental build and this combination may simply not work.... but if there's anything I can try to do to help the driver and monitor reconcile with each other, or to help you debug this, please let me know. (BTW, I don't mind the security timeout/rechecking on this webform, but having it drag focus back to that checkbox is somewhat disruptive.)

I purchased this fake clone TV box of the classic Tanix TX3 Mini 2GB Ram 16GB Rom for around 20 dollars (including shipping). I discovered that the soc is S905L2-B and before bricking the card with attempts to install it on eMMC I wanted to know if anyone of you found a firmware for this TV box compatible with the Amlogic USB Burning tool. On the internet I only found two tx boxes that mount the S905L2 soc and they are the X7 5G and ipbs9505 and I couldn't find firmware to try to load them on my tv box, it's difficult on the Chinese forums for me to be able to find the downloads. Any advice is welcome because with boot from the SD and the armbian-ddbr command I get an image but which I can only restore with the same command after booting from the SD so if the TV box is bricked and I can't boot this path won't work. I can use it to restore the Android factory image

I have Rock-5C 32GB Ram and these will not work i.e. I get the same Kernel Panic: Armbian_24.5.1_Rock-5c_noble_vendor_6.1.43_xfce_desktop Armbian_24.5.1_Rock-5c_noble_vendor_6.1.43 Armbian_24.5.1_Rock-5c_bookworm_vendor_6.1.43_minimal I`m testing other images. 6.8.10 and offial radxa images (rock-5c_debian_bullseye_kde_b2 with kernel 5.10.110) will get tv. But Fan is not working and sometimes crashes when transfering data between M.2 and usb HDD

This is a post to search for the firmware of the Tanix TX3 Mini TX box with S905L2-B soc (yet another fake TV box). I advise you to write a new post, after searching the forum for the information you are asking for. This low-end TV box will not allow you to use it as a replacement for a desktop PC. Internet browsing for example will be very slow.... These TV Boxes can be used as small Linux servers like for example an old Raspberry, with the difficulty that you don't have the same support as the Raspberry community and this means that you won't have updated images that work immediately. You will have to waste time to understand why it doesn't start immediately or how to copy to the Linux emmc and fear bricking the board with the hope of recovering it if its firmware from the specific manufacturer exists. Bye and good luck.

Changes to be committed: modified: config/boards/aml-s9xx-box.tvb modified: packages/bsp/aml-s9xx-box/boot/extlinux/extlinux.conf.template The aml-s9xx-box builds use the native TV Box u-boot. I've had as a todo item to figure out how to not build and include an unused u-boot. In a recent PR for a different board the opposite was being done (adding a u-boot where a board didn't previously ship one), thus I then had the info to remove it here. This also changes the generated extlinux.conf to include a fdt line by adding the boot_fdt_file to the board config file. This reduces the effort needed to manually modify the extlinux.conf. How Has This Been Tested? [x] Build aml-s9xx-box image and debs [x] Verify built contents Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas View the full article

@threpwood Since I'm the current maintainer of the Armbian amlogic TV Box builds I may be biased in my response. I will first state the official Armbian position which is that TV Boxes are crap and not supported. (This is often the case and you may find that you purchase something really cheap and it doesn't work with Armbian at all - this can be for any number of reasons, from TV boxes generally have the cheapest components, often two 'identical' boxes will have completely different components, etc). But, to address your original question, between the aml s905x3 and rk3566 I would recommend that you go with s905x3. That CPU is now many years old, which means its support within mainline linux is pretty mature. Whereas the rk3566 is relatively new and the mainline linux support is still being worked on. Also, while armbian has community builds for the older amlogic cpus and the older rockchip cpus (aml-s9xx-box, rk32xx-box, rk3318-box) there is only one community build for the h96-tvbox-3566 which is currently being worked on - other rk3566 boxes will be very hit or miss (but there is active work on getting more supported (search the forums for information). Now having said that, you need to be willing to deal with the limitations of the amlogic tv box builds (https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first), which I suspect you are based on the fact that you already appear to be using the armbian amlogic builds for an older box, but I mention here for completeness for others who may stumble across this post. Finally in my basic performance tests the s905x3 show that it is almost twice as fast as the older s905x. But neither is what I would call fast, but for general server type services, they do a fine job. I have an s905x2 box that hosts a few production websites and it is fine for that purpose.

If you don't need GPIOs and you're not a developer: don't buy SBCs as long as their prices are higher than the TV box. For the same price, you can buy a mini PC and it will be better than SBC. I advise you to buy a TV box on SOC s905x3. 1) You will be able to install Linux for your purposes. 2) As well as being able to use an android set-top box, amlogic is better in this regard. P.S. I believe that 90% of users do not need SBC, since they do not use GPIO, camera, ports for connecting the screen and the like. Many users need a cheap headless server. There are high-quality and inexpensive TV boxes for these purposes. In addition, for the price of banana pi m5, you can buy a mini PC that will work faster. SBC is a device for developers. For those who then make TV boxes and tablets. For ordinary users, SBC is unnecessary. The SBC manufacturer needs to pay attention to the user's need, which is: 1. SD card, emmc or M2. 2.LAN 1000/100 3. Wi-fi/BT 4. USB 3.0 5. 2/4/8 GB RAM The rest 90% of users do not need and therefore they will buy either a TV box or a mini PC as it is more profitable for the price

I installed armbian on a micro sd to be able to install it on my Dq08 RK3528. The boot succeeded on the sd card perfectly. I wanted to install armbian on the memory of the box with "armbian-install" I followed the instructions I did the 2. and Then I did the 5. it ask me to poweroff and since it does not want to turn on or be recognized by my peripherals connected. I've tried rebooting from an sd but it doesn't work. But I tried on another box with the same sd and it worked. So I think the box is brick. I've decided to do the tutorial from the sellers on aliexpress with the usb to usb cable. With the av button, the software doesn't even recognise it. I don't know what to do now.

@zetalex Were you able to use 4k120? If so, how did you enable 4k120 in Linux? I am not able to set the display (my TV) to 4k120, only 4k60... My TV's HDMI port is definitely a 4k120 port (verified with my PC and Nvidia GPU). Have you seen this tutorial? I lists all required steps if you want to use hardware acceleration on RK3588 with 6.1 kernel. https://jellyfin.org/docs/general/administration/hardware-acceleration/rockchip

When i boot on TV box armbian jammy (mis match version on th board). I try to reboot multitool from sd card but not work and i cann't install another version. Time in the screen freeze in yester day. Please told me the command to boot from sd card.

Hi, I'm doing some tests on my BTVe10 Box TV. I tried the image "Armbian_23.02.2_Aml-s9xx-box_jammy_current_6.1.11.img" with the dtb "meson-g12a-sei510.dtb" and it booted but the wifi didn't work. I used the command iwconfig and got the error "no wireless extensions". How can I make the wifi work?

- Please help me. I'm stuck 100% here after booting on mxq pro4k. (Rk3228a) Unable new reboot from sd card on tv box. - I think armbiam jammy not support in board. - How to boot sd card or command to boot. https://silpakorn-my.sharepoint.com/:f:/g/personal/koosiriwanich_s_su_ac_th/EukZkSlhAyZKiP3mCGqwFR8BHyHl3i4euWPhGaXiqRvUEw?e=3GUsYW

Can't really help with meson, but if this will make you feel not alone - rockchip also has issues with HDMI IMHO worth trying search in aml section of this forum. If patches are required, you might want to look into libreelec and minimyth2 GitHub repos. Since both are TV oriented, they might have necessary patches.

Can someone help? I have a H96 Max, but it cannot boot from multitools. It always boots from original Android TV, I tried replacing different sd card but no luck, meanwhile other ones work perfectly How can I do now?

Hi, I've been looking around for an Arm development platform. Banana Pi seems to be about the best value for money. I've been looking around at some TV boxes. However, I see mixed opinions about these being a option. SBCs seem to be almost twice the price of similar spec Arm TV box. Processing power and memory are mostly my priorities. Anything over 4GB seems insanely expensive. I can do SMD soldering work. So modding at TV box is an option. Are there any options for an 8gb Octa core system that isn't going to cost more than a decent PC?

Hello, I am new to this world and I want to use the TV box as an emergency PC. Can you tell me the steps on how to do it? I come from the previous publication but I understood what the steps are and it seems that we have the same pirate TV box Thanks in advance