Search the Community

I've this old tv box from a brazilian brand, called Intelbras IZY Play, the OEM appears to be SDMC, with the codename DV8038, it uses the s805x SoC. From what I've looked, it should be compatible using the files meson-gxl-s805x-p241.dtb u-boot-s905x-s912 The device does not have an SD card slot, so i'm trying to do it with a flash drive, however, after flashing it with balenaEtcher and doing the necessary changes to the files in my Windows PC, I cannot get it to boot, it justs enters a loop of showing the splash screen, turning off, showing the splash screen, and so on. I'm trying to turn it on pressing the hidden button that it has between the usb ports with a paper clip while I connect the power cable, if I do that without the USB stick on, it boots into a sort of recovery/fastboot screen similar to what android phones have. I've tried all variants of Armbian Bookworm, and I'm flashing Jammy as I write this post to test it as well, if it does work I will update the post.

Armbian_community_24.5.0-trunk.306_Aml-s9xx-box_bookworm_current_6.6.23 Is that what you mean with "build"? I just downloaded it from https://www.armbian.com/amlogic-s9xx-tv-box/

@jock I knew something was off.....that's why I was seeing Random characters output when I echo ..thanks for telling me that and it also explains why I get permission denied sometimes. ...guess I still need to make it where it's a virgin uart with no influence on debug too! I thought it was just a console control. Yeah this took extra steps but it frees up a USB port on the box itself for keyboard and mouse with out using a hub and it sorta copies a pi now and I had all this laying around anyways so. Update:1 Ok successfully fixed the issue, disabled all access to that uart part temporarily. Was able to successfully communicate to the Arduino through nanpy. No more permission issues. This is super cool. Now the Arduino works like an extension to the TV box. The processing power of the TV box is way better than the Arduinos so this opens up a bit of a cool niche use case. I'll call it THE ARMBIAN PI.. Still dont have wifi though. I ran the config and such but wifi isn't being able to run. Not sure what's stopping that but I'm sure it's not too hard to fix. Update:2 Finally I do see one more serial port that I have yet to figure out what exactly it's for. But this gives me another idea to attach one more Arduino or to connect directly to a 3d printer. It shows up as a device in the serial list tree. Got any idea what it is? Would it might be the IR port?

Does This Brick My Tv Box?

it actually did not require recompiling the bootloader at all actually heres what i did and it works! I worked on connecting a TV box running Armbian with an Arduino using a UART connection, allowing them to communicate. The aim was to control the Arduino using commands sent from the TV box. Firstly, I programmed the Arduino to react to simple text commands that would turn an LED on or off. This step was crucial to test whether commands from the TV box were being correctly received by the Arduino. Next, I focused on setting up the TV box for UART communication. Through the terminal, I found the UART device (/dev/ttyS2) and temporarily disabled its console service using the command sudo systemctl start serial-getty@ttyS2.service or sudo systemctl stop serial-getty@ttyS2.service This was necessary to use the port for sending commands to the Arduino without interference from the TV box’s system. To ensure the setup worked, I connected the TV box to a Windows computer using a USB-to-Serial adapter ( using my Arduino uno for this shorting the reset and GND together to by pass the chips mcu ) and monitored the communication with PuTTY. By sending a test message from the TV box and seeing it in PuTTY, I confirmed the UART port was functioning correctly. This allowed for successful data transmission between the two devices. A key part of this was a external port i made. i went in and solder on pin cables and routed it as neat as i could permanently so i can access the UART easily . This setup made it easy to connect and disconnect the Arduino without opening the TV box each time. It effectively allowed the Arduino to act like a USB-to-Serial device and vice versa, simplifying the communication process. I adjusted permissions to access the UART port without needing administrative rights and ensured the baud rates on both devices matched. this has thus far enabled general commutations through the UART and when i want to log back in through uart if ever i can simply start the serial -getty and log in this then allows me to run NANpy, making the arduino act like a slave to the tv box much like how people take rasberry pis and do the same thing to expand the gpio ports through serial communication using nanpy on the pi! this basically turns our silly ole tv box with the rk3318 into a raspberry pi with out the features lacking! that was the one thing about the pi that made it better for most tasks. well this helps level that disadvantage! @jock

Thank you, looking more calmly, I found the headers marked as G, R, T. Would these be: ground, tx, rx? I think I'm confusing it with my second TVbox which has a slightly different PCB, if this is the UART interface, I'll solder headers and connect my USB adapter, at what baud rate should I listen? It worked, it was these pads, here is the output with booting from the SD card: DDR Version V1.10 20190926 In ID:0xFFF 660MHz DDR3 Bus Width=16 Col=11 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB mach:2 OUT U-Boot SPL 2021.04-armbian (May 06 2021 - 19:15:25 +0000) Trying to boot from MMC2 I/TC: I/TC: Non-secure external DT found I/TC: Switching console to device: /serial@11030000 I/TC: OP-TEE version: 3.10.0-40-ga1d5c81f (gcc version 9.2.1 20191025 (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10))) #6 Wed Sep 16 21:36:15 UTC 2020 arm I/TC: Primary CPU initializing M/TC: Not protecting region 1: 0x68400000-0x68600000 I/TC: Primary CPU switching to normal world boot U-Boot 2021.04-armbian (May 06 2021 - 19:15:25 +0000) Model: Generic Rockchip rk322x TV Box board DRAM: 992 MiB MMC: dwmmc@30000000: 1, dwmmc@30020000: 0 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial@11030000 Out: serial@11030000 Err: serial@11030000 Model: Generic Rockchip rk322x TV Box board Net: eth0: ethernet@30200000 starting USB... Bus usb@30040000: USB DWC2 Bus usb@30080000: USB EHCI 1.00 Bus usb@300c0000: USB EHCI 1.00 Bus usb@30100000: USB EHCI 1.00 scanning bus usb@30040000 for devices... 1 USB Device(s) found scanning bus usb@30080000 for devices... 1 USB Device(s) found scanning bus usb@300c0000 for devices... 1 USB Device(s) found scanning bus usb@30100000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2909 bytes read in 5 ms (567.4 KiB/s) ## Executing script at 60000000 Boot script loaded from mmc 1 238 bytes read in 5 ms (45.9 KiB/s) 6094752 bytes read in 282 ms (20.6 MiB/s) 8771448 bytes read in 475 ms (17.6 MiB/s) 50042 bytes read in 10 ms (4.8 MiB/s) 786 bytes read in 7 ms (109.4 KiB/s) Applying kernel provided DT overlay rk322x-emmc.dtbo 1286 bytes read in 7 ms (178.7 KiB/s) Applying kernel provided DT overlay rk322x-led-conf1.dtbo 232 bytes read in 7 ms (32.2 KiB/s) Applying kernel provided DT fixup script (rk322x-fixup.scr) ## Executing script at 600f0000 ## Loading init Ramdisk from Legacy Image at 64000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 6094688 Bytes = 5.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 61f00000 Booting using the fdt blob at 0x61f00000 EHCI failed to shut down host controller. EHCI failed to shut down host controller. Using Device Tree in place at 61f00000, end 61f74fff Starting kernel ... I/TC: Secondary CPU 1 initializing I/TC: Secondary CPU 1 switching to normal world boot I/TC: Secondary CPU 2 initializing I/TC: Secondary CPU 2 switching to normal world boot I/TC: Secondary CPU 3 initializing I/TC: Secondary CPU 3 switching to normal world boot Armbian 24.2.1 bookworm ttyS2 rk322x-box login: this is the emmc boot output running the same image from the sd card written on it: ⸮⸮DDR Version V1.10 20190926 In ID:0xFFF 660MHz DDR3 Bus Width=16 Col=11 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB mach:2 OUT U-Boot SPL 2021.04-armbian (May 06 2021 - 19:15:25 +0000) Trying to boot from MMC2 I/TC: I/TC: Non-secure external DT found I/TC: Switching console to device: /serial@11030000 I/TC: OP-TEE version: 3.10.0-40-ga1d5c81f (gcc version 9.2.1 20191025 (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10))) #6 Wed Sep 16 21:36:15 UTC 2020 arm I/TC: Primary CPU initializing M/TC: Not protecting region 1: 0x68400000-0x68600000 I/TC: Primary CPU switching to normal world boot U-Boot 2021.04-armbian (May 06 2021 - 19:15:25 +0000) Model: Generic Rockchip rk322x TV Box board DRAM: 992 MiB MMC: dwmmc@30000000: 1, dwmmc@30020000: 0 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial@11030000 Out: serial@11030000 Err: serial@11030000 Model: Generic Rockchip rk322x TV Box board Net: eth0: ethernet@30200000 starting USB... Bus usb@30040000: USB DWC2 Bus usb@30080000: USB EHCI 1.00 Bus usb@300c0000: USB EHCI 1.00 Bus usb@30100000: USB EHCI 1.00 scanning bus usb@30040000 for devices... 1 USB Device(s) found scanning bus usb@30080000 for devices... 1 USB Device(s) found scanning bus usb@300c0000 for devices... 1 USB Device(s) found scanning bus usb@30100000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 Card did not respond to voltage select! : -110 Device 0: unknown device switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... libfdt fdt_check_header(): FDT_ERR_BADMAGIC 7[r[999;999H[6n8Card did not respond to voltage select! : -110 Scanning disk dwmmc@30000000.blk... Disk dwmmc@30000000.blk not ready Scanning disk dwmmc@30020000.blk... Found 2 disks No EFI system partition BootOrder not defined EFI boot manager: Cannot load any image ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-8e-44-db-3b-e1-5d ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000000 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/000000 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/000 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/00 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/0 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-rk322x-rk322x-box ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-rk322x ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/default ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 Config file not found ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 =>

unfortunately I don't have access to the serial UART of the TV box, I didn't find any pad with the tx rx labels on the PCB, I'm going to try to replace the rootfs, in the functional Armbian image, with the exception of the boot directory, then write it using multitool , I'll post here if this works. Thank you very much for the tips and quick responses

@jock is there a way to revert said changes? can you at least pin point me in the general direction i might look and maybe fix it myself? it makes sense that its something to do with hdmi. iv been going through this entire thread as much as i can and i saw you made some kind of patch for the 6 series kernal and then i saw someone mention they found the source of hdmi issues with some kind of hex editor fix? im not sure what could be the case but i do have this running just fine on this older build and im scared to try to upgrade anything. i forze the kernal updates in the config does that mean i can apt upgrade all and kernal wont be touched? if so then im fine for now but im scared to touch apt upgrade in fear it might upgrade the kernal by force. is there a way to freeze it so it wont upgrade it no matter what? im using this as a pi hole and a klipper setup and it works but i wanna update my packages if i can. also yes a sbc would be easier but i wanna try to hack this together just for the fun of it. im wondering if i could wire up a powered hub inside a 3d printer encloser along with the board and make it have one internal port and then 4 external by wiring directly to the usb pads to make it intigrated then use a arduino as a slave board for GPIO to make this a hacked together rasberry pi they have githubs made to make the arduinos dedicated GPIO for linux based machines which allow the computer to controll the gpio instead of the MCU on the arduino which makes this idea seem feesable the goal is to make this basically as close to a rasberry pi as possible with a little extra steps but it will end up faster than the pi too which is even better. once i found out about tv boxes being reposed into linux machines i was hooked iv been addicted to this for awhile now just trying to iron out the issues i have atm,

Hi, @jock. I have a same tv box as this https://forum.armbian.com/topic/34923-csc-armbian-for-rk322x-tv-box-boards/?do=findComment&comment=113935 But I can not boot from multitool, what can I do ? I'm pretty sure that my tf card is ok. Because I've checked by H2testw and I flash multitool by balenaEtcher without error.

Hey, @jock! After selecting led-conf7 (R29 MXQ, R2B MXQ, H20) in rk322x-config, the screen was displayed immediately without the need to boot from the SD card. Thank you for helping me install Armbian on my tv box.

I've just found that my tv box has no screen but is shown on the network. Even it can be connected via ssh, and works fine. It's a purpose that doesn't require the screen, but I'm curious as to why the screen doesn't come up.

This is the MXQ PRO 4K 5G TV BOX with RK322A CPU, 1GB RAM, and 8GB eMMC. I booted MULTITOOL onto the SD card and burned the latest jammy image and Legacy 4.4 image for RK322X. After REBOOT on MULTITOOL, I got a nice ARMBIAN screen and everything was fine. But when I restart it after shutdown, the screen goes blank. It is still possible to boot with MULTITOOL on SD, and from here you can enter ARMBIAN through the REBOOT menu, but booting with only eMMC fails as the monitor screen goes into sleep mode. What's the problem?

I need to mention as an update. If I stay in the minimal old 5.15 kernal I get HDMI out but if I run apt upgrade or upgradable if I then reboot once I'm done. HDMI out no longer works. However if I don't update anything. I can reboot all day. This is flashed directly on the internal storage because sd card booting does not work for me. I can only boot this stuff after flashing it directly from multi tool. This makes it harder to quickly test different kernals such. if i even attempt to use the desktop ready imgs on the same kernal hdmi out also does not seem to work. i have no way of knowing if its actually booting at all or not either. is there a way to log into the system even if its the first time boot and there is no account setup? maybe then i can go in the shell somehow and enable things? it would be great to have a working desktop. i opened up the tv box and the motherboard is blue. idk if that matters. this was made in 2019 apparently . ok update i was able to log in with ssh both blue and red led is flashing after using the latest mainline installs. but ssh works not sure what i can do to proceed i setup the configs too, got the proper led working wifi not working but im using ethernet my ultimate goal is to wire up a gpio board to the system with its usb ports being spared and making this a sudo sbc computer but a little extra steps i already have a Arduino so making it a slave would be cool this is offtopic but if i can get the hdmi out working ill be closer to my goal, ( i was thinking of directly wiring the usb port to the usb port that way it works as device but spare the other usb port too maybe a wired hub inside the case so i wont be missing ports but still have the board hardwired in? it seems possible.... ok ok final edit i installed a very older build with a desktop env it works! but the kernel is in the 5 series.....i really wish i could have a more up to date kernel. for now i enabled blocking of kernel updates.

Hi im using a x88 pro at least thats what the model states under the tv box. for some reason i cant get any hdmi out signal from the box after flashing the desktop environment versions of this linux install i used the archives and the one that work the best was Debian Bullseye minimal - mainline kernel 5.15.16 this one does not give me a desktop however so thats sorta not what i wanted. not sure why but i cant seem to get the nightly releases working i made sure it was the rk3318 versions too. the goal is to get a working desktop environment working with XFCE as thats one the most lightest weight desktop env i know of. am i missing something? the multi tool is flashed the image is in the images folder i burn said image and when i reboot with out the sd card inserted no signal at all i see a single red led inside the box through its vent that just stays lit. i can work with the debian bullseye but i see its using a older kernal and id like the latest working one if possible at the very least..... any advice?

I had X96 Mate from long time, which is 4GB/32GB with H616 CPU, (It is almost same as Tanix TS6s) Tried many images from orange pi for same chip, none worked perfectly. Found out Sunix Linux community got support for H616, but they don't build full OS images, After hell of searching found a repo from https://github.com/warpme/miniarch He hosts MiniArch SD card image which works on many devices, from same link got SD card image for Tanix tx6s which also worked on x96_Mate (both got H616) Here is the file I used - https://github.com/warpme/miniarch/releases/download/20230106-6.1.5-g78293cd3/MiniArch-20230106-6.1.5-board-h616.tanix_tx6s-SD-Image.img.xz 1- Wrote img to SD card using Etcher 2- Inserted SD card in Device 3- Powered ON the device and it Booted from SD card 4- followed update instructions on GitHub Repo. 5- Rebooted after all updates, 6- Basic Arch was ready to be used Here USB keyboard , LAN, HDMI worked normally. After reboot, logged in as root, and ran "start" command, Now here selected option 5, which is install EndeavourOS Process just ask you Yes/No questions, then you can select your DE, location etc. Automated script downloaded bunch of files and started its installation. Got the message that installation is done successfully and came back to terminal. Rebooted from terminal After this point got only blank screen , dont know it is still booting without HDMI or not So need to revert back to step -1 writing basic image to SD card. And this time sticking to terminal only. all this process is done on SD card only, and android on eMMC is safe .

Maybe we can bundle our effords regarding a working S805 image? I also have hundreds of new TV sticks (not boxes) with an Amlogic S805 (Meson 8B). The original Android ROM has the codename stvm8b. Currently I only have a working Android 4.2.2 image with a patched kernel for real 1080p output which can be flashed using TWRP onto the internal eMMC. I really would love to get some kind of more recent and non-Android image up and running. It's a real struggle to get any custom images as most links are dead already which makes it more complicated. Currently I have full UART access to the device and I'm able to interact with the uBoot shell. I also see the full kernel output of the working Android image and have a root shell there. But as others already pointed out kernel 3.10 is way to old to be used in production. So "porting" a more recent kernel would be great. My main goal is to get a Linux image up and running on the box which makes it still useful as device for digital signage or as a small webserver. Some more details on the hardware: ro.product.name=stvm8b ro.product.device=stvm8b ro.product.board=stvm8b ro.product.cpu.abi=armeabi-v7a ro.board.platform=meson8 uBoot output dropping to shell: QA5:A;SVN:B72;POC:1FF;STS:0;BOOT:0;INIT:0;READ:0;CHECK:0;PASS:0; no sdio debug board detected TE : 76654 BT : 15:34:06 May 13 2015 ##### VDDEE voltage = 0x044c CPU clock is 792MHz DDR mode: 32 bit mode DDR size: 1GB (auto) DDR check: Pass! DDR clock: 636MHz with 2T mode DDR pll bypass: Disabled DDR init use : 14831 us HHH Boot From SDIO C SD_boot_type: 00000002 card_type: 00000003 0x0000009f ucl decompress...pass 0x12345678 Boot from internal device 1st eMMC on SDIO C TE : 301370 System Started U-Boot Version: 2011.03-ad3b84b(20150513.153356) clr h-ram DRAM: 1 GiB relocation Offset is: 2feb4000 show partition table: part: 0, name : logo, size : 2000000 part: 1, name : recovery, size : 2000000 part: 2, name : misc, size : 2000000 part: 3, name : boot, size : 2000000 part: 4, name : system, size : 40000000 part: 5, name : cache, size : 20000000 part: 6, name : backup, size : 20000000 part: 7, name : data, size : end aml_card_type=0x0 MMC: [mmc_register] add mmc dev_num=0, port=1, if_type=6 [mmc_register] add mmc dev_num=1, port=2, if_type=6 SDIO Port B: 0, SDIO Port C: 1 power init out reg=c110804c,value=dfffffff IR init done! register usb cfg[0][1] = 3ff6c19c register usb cfg[0][2] = 3ff6c184 NAND: EMMC BOOT: not init nand do not init nand : cause boot_device_flag without nand get_boot_device_flag: init_ret -1 get_boot_device_flag EMMC BOOT: Emmckey: Access range is illegal! [mmc_init] SDIO Port C:1, if_type=7, initialized OK! [mmc_get_partition_table] skip cache partition. Partition table get from SPL is : name offset size flag =================================================================================== 0: bootloader 0 400000 0 1: reserved 2400000 4000000 0 2: cache 6c00000 20000000 2 3: env 27400000 800000 0 4: logo 28400000 2000000 1 5: recovery 2ac00000 2000000 1 6: misc 2d400000 2000000 1 7: boot 2fc00000 2000000 1 8: system 32400000 40000000 1 9: backup 72c00000 20000000 1 10: data 93400000 13ec00000 4 mmc read lba=0x12000, blocks=0x1 mmc read lba=0x12001, blocks=0x1 mmc_read_partition_tbl: mmc read partition OK! eMMC/TSD partition table have been checked OK! i=0,register --- emmc_key MMC BOOT, emmc_env_relocate_spec : env_relocate_spec 59 set_storage_device_flag: store 2 bad chip version!!! efuse mac is : ac:db:da:3d:c4:e5 set ethaddr is : ac:db:da:3d:c4:e5 usid is MH0507015420365 mmc flash is used high freq info->dtbversion = 1025 boardname=stvm8b boardtype=m8b_dongle wifi=rtl8189es dtbtype=stvm8b_dongle_1g Multi dtb tool version: v2 . Multi dtb detected, support 5 dtbs. aml_dt soc: stvm8b platform: dongle variant: 1g dtb 0 soc: stvm8b plat: dongle vari: 1g dtb 1 soc: stvm8b plat: dongle vari: 512m dtb 2 soc: stvm8b plat: normal vari: 1g dtb 3 soc: stvm8b plat: normal vari: 1gcm dtb 4 soc: stvm8b plat: normal vari: 512mcm Find match dtb: 0 vpu clk_level in dts: 3 set vpu clk: 182150000Hz, readback: 182150000Hz(0x701) Net: Meson_Ethernet init suspend firmware done. (ret:0) cvbs trimming.1.v5: 0xa0, 0x0 preboot new... check board version... bad chip version!!! efuse mac is : ac:db:da:3d:c4:e5 set ethaddr is : ac:db:da:3d:c4:e5 usid is MH0507015420365 mmc flash is used high freq info->dtbversion = 1025 boardname=stvm8b boardtype=m8b_dongle wifi=rtl8189es dtbtype=stvm8b_dongle_1g Hardware version information has been written and the check is successful hdmi tx power init mode = 8 vic = 16 set HDMI vic: 16 mode is: 8 viu chan = 1 config HPLL config HPLL done reconfig packet setting done Hit Enter key to stop autoboot -- : 1 tstc enter exit abortboot: 1 The original name was "MyGica ATV185" and each device has a Quad-Core processor (Cortex A5, 1 GHz), 1 GB RAM, 8 GB internal eMMC storage, a WIFI module, 1x USB2.0, 1x microSD slot, 1x HDMI plug and 1x microUSB as power supply. The device should be the same like the ODroid C1 Would love to participate in the process of creating a useful image for the S805 platform and especially for this piece of hardware.

TV Box Status Information Template Version 1.0 ======================================= TV Box Name: Leelbox S1 (PCB marking: "A95X_DDR4" "V1_1 2160906") CPU: AMLogic S905X RAM: 1 GB DDR4 (reported: 860 MiB) - 2 x SpecTek (Micron) "PPE05-075" "F1646" Armbian build file name: Armbian_community 24.5.0-trunk.226 DTB file used: meson-gxl-s905x-p212.dtb Kernel Version: Linux 6.6.22-current-meson64 Distribution Installed: Bookworm Working Ethernet (Yes/No): Yes Max Ethernet Speed that works (100/1000): to be verified Does wifi work (Yes/No): Yes (RTL8189ETV) Does bluetooth work (Yes/No): No Does HDMI audio work (Yes/No): Not tested Comments: - also sold as ABOX-A1 according to online sources; - installation to MMC worked without issue using the dedicated script.

Hi, I am having problems connecting my orange pi zero 3 to my TV via hdmi: No matter what I try the TV reports "no signal". Before I came to armbian I have tried the vendor-supplied debian and arch images and could not get hdmi output on any of them, so it might be that my micro-hdmi adapter is faulty or that the hdmi-port on the device itself is faulty, but over the weekend I cannot replace any hardware so I thought I try here to see if anyone has an idea on what to try. The image I am currently running is Armbian_community_24.5.0-trunk.58_Orangepizero3_jammy_current_6.6.17_gnome_desktop.img. When I log into the device I can see that an Xorg process is running. xrandr produces this output: Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 HDMI-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00* 800x600 60.32 56.25 848x480 60.00 640x480 59.94 When I disconnect the hdmi-cable xrandr reports "HDMI-1 disconnected", so at least a little bit of hdmi-functionality is there... The device is connected via an micro-hdmi adapter and a hdmi-cable, I have checked the hdmi-cable but I do not have another adapter nor do I have another micro-hdmi device, so unfortunately I cannot test the adapter. What I have noticed is that (at least sometimes) the device seems to lose network-connectivity (ethernet) when the hdmi-cable is connected - and regains connectivity as soon as the hdmi-cable is disconnected, so there seems to be some conflict between hdmi and ethernet. I do not know where the display modes come from that xrandr displays as the TV is a 4k model that supports a lot more modes. So my question is: Is there anything I could try to get hdmi working or at least to narrow down the problem?

If you have the ability plug a computer monitor into it, if it works it's settings on your TV. On my Roku if I remember correctly I had to set it to computer for that input.

@well83 thanks for the uboot, now my system is booting just fine before it would just bootloop like this I'm using the image Armbian_community_24.5.0-trunk.123_Aml-s9xx-box_bookworm_current_6.6.20_minimal.img with the meson-sm1-a95xf3-air.dtb in my tv box a95x f3 air

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

Hi, I have an A95X F3 Air tv box that has an s905x3 chipset. I followed the instructions here. I believe i used the correct dtb file and tested out multiple others. I've tried reformatting my drive with SD card formatter. I've tried flashing my stock firmware. However I cannot seem to get armbian to boot. I'm getting no video output. I'm not sure what I'm doing wrong here. I've searched high and low on the internet and I could not find a solution. I have seen aml_autoscript.zip being mentioned here and there however the image I've downloaded doesn't seem to have it. Any help would be appreciated.

How many times do I have to say, it isn't possible to do with Armbian builds. Armbian does not have a uboot for your TV Box. So there is no way for you to boot from something other than your emmc unless you have a uboot built for your box. And since Armbian doesn't produce such code, we can't help you here.

Hello, I have a rk322x TV box. I installed multitool on it. I put the armbain img file in the images file. A black screen appears when the TV box boots

Here is my A95X F3 Air, I have installed the slimbox tv firmware that works fine, and now I'm trying to install armbian, with an sdcard and utilizing the meson-sm1-a95xf3-air.dtb file and the uboot u-boot-s905x3 I'm able to get an image, but it keeps in this infinite bootloop, nothing seems wrong, but why isn't booting?