Search the Community

Does This Brick My Tv Box?

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

Well it took me longer than i hoped but i have managed to forward port icenowys code for TVE on the H2+/H3 to mainline armbian. It seems to work totally fine, with a few caveats. First: Sample images of it in action -> https://imgur.com/a/vXQEM Second: the patch itself -> https://github.com/stevenj/h3-tve/tree/v0.0.11 Third a prebuilt image for Orange Pi Zero: -> https://github.com/stevenj/h3-tve/releases/tag/v0.0.11 Howto: just put the patch into userpatches for the sunxi-next kernel, and build. it should apply cleanly. Its for H2+/H3. I have only tried it on a orange pi zero, but it should work on all H2+/H3 boards. You then need to edit /boot/armbianEnv.txt add tve to overlays to enable it. the driver will only run and enable tv out when the tv out devices are specifically enabled, so i created an overlay which does this. If you want to turn TV out off, just remove tve from the overlays line. My armbianEnv.txt overlays looks like this: overlays=usbhost2 usbhost3 tve If you want copious amounts of DRM debug info in your logs, add this as well: extraargs=drm.debug=0xF Its not needed, unless you really want the debug info. Notes: 1. The default mode is PAL, with 720x576 resolution. Thats outside of normal PAL displayable area, and so the screen overscans. I dont know how to correct this, although its mostly just annoying with terminals. I also don't know how to change the video mode to NTSC. 2. The standard font is a bit thin for composite video, and causes slight strobing and color impurity. Its because PAL needs pixels to be a certain MINIMUM width or color information can not be properly encoded. A way to resolve this is use : # apt-get install fbterm ... $ fbterm -s 20 This will run a terminal which is easy to change the font, and pick a bigger one. its much easier to read. Look at the help for fbterm to work out everything it can do. 3. I used the program "fim" to display the test images. there are others for doing stuff on the terminal. 4. I haven't tried X. I am not interested in running an X terminal on a TV, but it should probably work fine. Other than that it all seems good. I originally tested my hardware with the legacy kernel, and the image quality from this patch seems superior to what the legacy kernel produces. (legacy was noisy) The only other thing you need to know is Orange Pi Zero is missing filter circuity from its Composite Output, the most important thing you need to do is put a 50 ohm resistor between the signal and GND. i soldered one inside my RCA connector, it fits fine and isn't too difficult. IF you don't do this the image will bloom and look like total crap, so you have been warned. As this patch allows TVE to be enabled/disabled through use of the Device Tree overlays, i think it should be fine if the Armbian devs want to include it. I am happy to clean out some of the debug messages i added if they are interested in making a standard part of the build. If not, its easy enough to build your own image, just follow the guides on how to rebuild armbian. EDIT: I need to mention, all props go to Icenowy Zheng who wrote the original driver. I just tweaked the device tree stuff and got it in a state where it can apply cleanly to the armbian mainline kernel and build system. Original code is here: https://github.com/Icenowy/linux/tree/tve-v2

I have a RK3328 android tv box. After flashing new firmware to it, using Rockchip Batch Tool, the box, connected to the tv, shows briefly RK3328 logo on tv screen, and then black screen. After that, I connect the box to the computer using usb cable, without pressing reset button on the box. Rockchip Batch Tool software, under the Connected Device, shows a green symbol. It shouldn't, because I didn't press the reset button on android tv box. It's like android tv box is in reset mode, and I didn't put it in reset mode. It's like there is a short somewhere that puts it in reset mode. And, maybe that is the reason the box doesn't boot up normally, but has a black screen. I flashed the box many times, the same outcome, black screen tv, and reset mode on. Can anyone, please, help me solve this problem? Thank you!

Hi Guys, I am looking for latest Armbian image which works for Beelink GT1 Ultimate 3/32GB (S/N = G912) Amlogic S912 TV box. My requirement is only wired network to be working and that Armbian image must have kernel headers. The only old image that work is Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_mate_20171226.img but missing kernel headers & not able to find kernel headers that matches kernel in the image. I tried Armbian_20.10_Arm-64_focal_current_5.9.0_desktop.img with 3 different dtb files as follows: dtb file: /dtb/amlogic/meson-gxm-q200.dtb dtb file: /dtb/amlogic/meson-gxm-gt1-ultimate.dtb dtb file: /dtb/amlogic/beelink_gt1_g2.dtb also configured extlinux.conf but it stuck on Beelink boot logo. Could some one please guide which latest image works this Beelink GT1 Ultimate TV box? Thanks in advance.

Hi, I have a X96 mini box. I can install old version of armbian like Armbian_20.10_Arm-64_bullseye_current_5.9.0.img.xz but the newest versions are Uefi example Armbian_23.02.2_Uefi-arm64_bullseye_current_5.15.94.img.xz Can I install it ? Or there are no uefi versions ? Best regards

Description OrangePi kernel patched to enable TV Output on OrangePi Zero (LTE). Changes made according: https://github.com/robertojguerra/orangepi-zero-full-setup/blob/main/README2.md 7.3 Add the TV encoder driver to the Linux kernel source sunxi-6.1/0036-wip-h3-h5-cvbs-armbian.patch : makes additions to the "dts", which tells the kernel where are the new devices. Adds kernel code to interact with the tv encoder. With my modifications, now it is applicable to Armbian (this patch came from the LibreElec github). sunxi-6.1/zzzz2-tv.patch : by Armbian user "gleam2003", adds directives to make sure that the dtbo (device tree binary overlay) is compiled sunxi-6.1/zzzz3-tv.patch : more additions to the "dts" and "dtsi" (like C include files), which I noticed were included in "yam" patch, but missing from the LibreElec patch All merged into one patch file arm-dts-sun8i-h3-orangepizero-add_tve.patch AR-1660 OrangePi Zero (LTS) TV output not working [PATCHing needed] How Has This Been Tested? Image compiled using: ./compile.sh BOARD=orangepizero BRANCH=current RELEASE=bullseye BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,img Image flashed to SD card OrangePi Zero LTE booted with image TV Output checked on monitor with RCA video input Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

“Adafruit Feather RP2040 with DVI Output Port” is another Raspberry Pi RP2040 board with an HDMI port that can output DVI video signal (no audio) to most TVs or monitors with an HDMI input port thanks to the PicoDVI project. The board builds upon the company’s Adafruit Feather RP2040 with the HDMI port adding just a few dollars. Adafruit Feather RP2040 with DVI Output Port specifications: MCU – Raspberry Pi RP2040 dual-core Arm Cortex M0+ microcontroller ~125 MHz (but it should be overclocked for DVI output) with 264 KB RAM Storage – 8MB SPI flash Video Output – 1x HDMI port for DVI output up to 320×240 or 400×240 resolution with 16-bit pixels, I2C signals to read EDID data, plus CEC and Utility pads broken out USB – 1x USB Type-C port I/Os Adafruit Feather compatible headers Up to 21x GPIOs 2x I2C, 2x SPI, 2x UART 4x 12-bit ADC [...] The post $15 Adafruit Feather RP2040 with DVI Output Port connects to your HDMI TV or monitor appeared first on CNX Software - Embedded Systems News. View the full article

Rockchip demonstrated the Rockchip RK3528 TV box SoC at Mobile World Congress 2023, and the first Android 13 TV boxes based on the processors are now showing up for sale starting with the LEMFO X88Pro 13 TV box. The device comes with up to 4GB RAM and 64GB storage, supports up to 8Kp25 video decoding, features Fast Ethernet and WiFi 6 networking, as well as a few USB ports, and possibly optical S/PDIF audio output. LEMFO X88Pro 13 (preliminary) specifications: SoC – Rockchip RK3528 CPU – Quad-core Arm Cortex-A53 processor GPU – Arm Mali-450 GPU VPU H.265/HEVC up to 8Kp25 H.264/AVC, VP9 up to 4Kp60 VP8, MPEG-1 MPEG-2, MPEG-4, VC1 up to 1080p60 System Memory / Storage configurations: 2 GB RAM and 16 GB flash 4 GB RAM and 32 GB flash 4 GB RAM and 64 GB flash A microSD card is most likely present too Video Output – [...] The post X88Pro 13 8K TV box runs Android 13 on Rockchip RK3528 SoC appeared first on CNX Software - Embedded Systems News. View the full article

Hi all, My s905x TV box worked well with Armbian_23.02.0 (03.17.0615/Armbian_23.02.0_amlogic_s905x_bullseye_5.15.100_server_2023.03.17.img.gz). Today I tried Armbian_23.05.0 (03.19.0453/Armbian_23.05.0_amlogic_s905x_bullseye_5.15.100_server_2023.03.19.img.gz) Debian is stucked at first boot with network configuration. Same issue ethernet plugged or unplugged I cannot find anymore Armbian_23.02.0 prebuilt image Edit: Armbian_23.02.0 found in 03.19.0427 Many thanks!

Guys, I need to build a cheap NAND reader/writer to clone few NAND chips, and I have some old android TV Boxes that I'm thinking to re-purpose for this job. It's a one time job so I don't want to buy a professional NAND programmer as they tend to be quite expensive. Do you guys think this would be possible? So, I'm thinking to boot from an sd-card or usb stick with Armbian and get access to the NAND chips that all my tv boxes have (I have some old MX-III and M8 boxes, model K200 I think, with S802 cpus and 8GB NAND). If I manage to get NAND access I can de-solder and solder other chips that I need to write from/to. Does anyone have any experience with this and can give me any advise? I would really appreciate it. Thank you!

Hi, can anybody tell me if the Armbian release by developer Awawa for the Tanix TX6 tv-box Allwinner H6 will work on mt T95 mini tv box? I'm asking because it works on the T95 max also. I am currently running the Inovato Quadra image on my T95 mini but it has a terribly annoying flaw, in that it changes the MAC address after every reboot, which as you can imagine is infuriating when you're trying to set up SSH/SFTP/VNC. I have a workaround by manually setting the IP address on the box to a static IP then setting up port forwarding in my router to that address but i seem to lose access via the local network yet via my external IP address it works fine. I also read on the Inovato forums that Awawa's image runs on the T95 max and has fixed the random MAC address change so i would love to run it on my T95 mini if at all possible. Both the max and the mini have the same processor and as far as i can tell, the only real difference is that the max model has 4GB or ram as opposed to 2GB on the mini. Any advice here would be greatly appreciated. It doesn't specifically have to be this particular image that i want to run on my T95 mini, i just want any stable image that will run and not change the damn MAC address. TIA

Description Split adding a board with reworking patches for Opi3 and Opi3LTS that are preventing this hw from functional lan / audio. Jira reference number AR-1487 How Has This Been Tested? [x] Build test on 6.1.y, 6.2.y Checklist: [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 [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

So I got a new orange pi 3 lts and I have installed armbian bullseye on it, but I can't seem to make it work with my crt TV like my raspberry pi 3 b+, even though I am using the same cable and TV and it still works with my raspberry pi I have tried: -Changing the resolution -Changing the aspect ration But nothing works What am I supposed to do to make my armbian work on my CRT tv??

Rockchip showcased some new processors at Mobile World Congress 2023: the RK3528 for TV boxes, and the RK3562 for tablets both with a Cortex-A53 CPU subsystem, but the former comes with a Mali-450 GPU, and the latter with a faster Mali-G52 2EE GPU. Both are clearly for entry-level devices, but I’m a little surprised they didn’t go with Cortex-A55 cores instead. Rockchip demonstrated the new processors in a TV box running Android 13 and a tablet with a 144,506 score in the latest Antutu benchmark as shown below. Rockchip RK3528 preliminary specifications: CPU – Arm Cortex-A53 processor (core count unspecified) GPU – Arm Mali-450 GPU with AFBC compression support Memory – LP4, LP4X, LP3, DDR4, DDR3 Video decoding – Up to 8Kp25 Supported OS – Android 13 Rockchip RK3562 preliminary specifications: CPU – Quad-core Cortex-A53 processor @ 2 GHz GPU – Mali-G52 EE AI accelerator – 1 TOPS NPU VPU [...] The post Rockchip showcases RK3528 TV box SoC and RK3562 tablet SoC appeared first on CNX Software - Embedded Systems News. View the full article

I have Android TV box Tx3 mini with 4GB RAM and 32 GB ROM. I install Armbian followed a guide. When I logged in it showed Memory usage: 20% of 918 MB, Usage of /: 57% of 5.8G. How can I get it recognized full memory the box has? Thanks.

@balbes150 leaving is surely a big loss for all TV-boxers... Could you please elaborate - is requirement form "Getting started" regarding install " NAND: kernel 3.4.x and NAND storage " applied to his builds too? Years ago I successfully installed Armbian to NAND of MXQ 805 box (with nand-sata-install these days, I guess), and it worked like a charm, but now I can't find any s805 image with kernel 3.4, the earliest ones are 3.10 already. Thank you in advance if you could give a tip.

I found the TV box that played couple of years ago... and bricked 😞 The box looks like this one https://bestedshop.com/index.php?route=product/product&product_id=213 Seems like I flashed it with Khadas VIM bootloader and now it enters a boot loop because it's failing the vim_check preboot script. I tried all sorts of images via the SD card but it seems it ignores all of them. The serial console output: GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0; TE: 138075 BL2 Built : 11:58:42, May 27 2017. gxl gc3c9a84 - xiaobo.gu@droid05 set vcck to 1120 mv set vddee to 1000 mv Board ID = 1 CPU clk: 1200MHz DQS-corr enabled DDR scramble enabled DDR3 chl: Rank0+1 @ 768MHz - PASS Rank0: 1024MB(auto)-2T-11 Rank1: 1024MB(auto)-2T-11 DataBus test pass! AddrBus test pass! -s Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000 New fip structure! Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600 Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x00018400 Load bl33 from eMMC, src: 0x0003c200, des: 0x01000000, size: 0x00066800 NOTICE: BL3-1: v1.0(release):3348978 NOTICE: BL3-1: Built : 15:44:01, May 12 2017 [BL31]: GXL CPU setup! NOTICE: BL3-1: BL33 decompress pass mpu_config_enable:ok [Image: gxl_v1.1.3221-2cfba69 2017-05-27 16:03:58 qiufang.dai@droid07] OPS=0x82 48 e4 7a 44 9d 15 28 2d 57 4d 27 1 [0.347298 Inits done] secure task start! high task start! low task start! ERROR: Error initializing runtime service opteed_fast U-Boot 2015.01-gec7adb5 (Oct 28 2017 - 16:44:13) DRAM: 2 GiB Relocation Offset is: 76eaf000 register usb cfg[0][1] = 0000000077f56810 [CANVAS]canvas init vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters vpu: clk_level = 7 vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300) vpu: vpu_clk_gate_init_off vpp: vpp_init boot_device_flag : 1 Nand PHY Ver:1.01.001.0006 (c) 2013 Amlogic Inc. init bus_cycle=6, bus_timing=7, system=5.0ns reset failed get_chip_type and ret:fffffffe get_chip_type and ret:fffffffe chip detect failed and ret:fffffffe nandphy_init failed and ret=0xfffffff1 MMC: aml_priv->desc_buf = 0x0000000073eaf6b0 aml_priv->desc_buf = 0x0000000073eb19d0 SDIO Port B: 0, SDIO Port C: 1 emmc/sd response timeout, cmd8, status=0x1ff2800 emmc/sd response timeout, cmd55, status=0x1ff2800 init_part() 293: PART_TYPE_AML [mmc_init] mmc init success dtb magic edfe0dd0 start dts,buffer=0000000073eb4200,dt_addr=0000000073eb4200 parts: 10 00: logo 0000000002000000 1 01: recovery 0000000002000000 1 02: rsv 0000000000800000 1 03: tee 0000000000800000 1 04: crypt 0000000002000000 1 05: misc 0000000002000000 1 06: boot 0000000002000000 1 07: system 0000000080000000 1 08: cache 0000000020000000 2 09: data ffffffffffffffff 4 init_part() 293: PART_TYPE_AML eMMC/TSD partition table have been checked OK! check pattern success mmc env offset: 0x27400000 In: serial Out: serial Err: serial ## defenv_reserve Saving Environment to aml-storage... mmc env offset: 0x27400000 Writing to MMC(1)... done reboot_mode=normal hpd_state=1 [1080p60hz] is invalid for cvbs. set hdmitx VIC = 16 config HPLL = 2970000 HPLL: 0xc000027b config HPLL done j = 4 vid_clk_div = 1 hdmitx: set enc for VIC: 16 HDMITX-DWC addr=0x10004006 rd_data=0x40 Error: HDMITX-DWC exp_data=0xff mask=0x9f rx version is 1.4 or below div=10 hdmtix: set audio hdmitx phy setting done [store]To run cmd[emmc dtb_read 0x1000000 0x40000] _verify_dtb_checksum()-917: calc 4c291ff3, store 4c291ff3 _verify_dtb_checksum()-917: calc 4c291ff3, store 4c291ff3 dtb_read()-1039: total valid 2 dtb_read()-1106: do nothing Net: dwmac.c9410000amlkey_init() enter! [EFUSE_MSG]keynum is 4 [BL31]: tee size: 0 Start read misc partition datas! info->attemp_times = 0 info->active_slot = 0 info->slot_info[0].bootable = 1 info->slot_info[0].online = 1 info->slot_info[1].bootable = 0 info->slot_info[1].online = 0 info->attemp_times = 0 attemp_times = 0 active slot = 0 wipe_data=successful wipe_cache=successful upgrade_step=2 [OSD]load fb addr from dts [OSD]fb_addr for logo: 0x7f851000 [OSD]load fb addr from dts [OSD]fb_addr for logo: 0x7f851000 [CANVAS]addr=0x7f851000 width=3840, height=2160 amlkey_init() enter! amlkey_init() 71: already init! [EFUSE_MSG]keynum is 4 [BL31]: tee size: 0 [KM]Error:f[key_manage_query_size]L507:key[usid] not programed yet [KM]Error:f[key_manage_query_size]L507:key[deviceid] not programed yet saradc - saradc sub-system Usage: saradc saradc open <channel> - open a SARADC channel saradc close - close the SARADC saradc getval - get the value in current channel saradc get_in_range <min> <max> - return 0 if current value in the range of current channel gpio: pin GPIOAO_2 (gpio 102) value is 1 saradc - saradc sub-system Usage: saradc saradc open <channel> - open a SARADC channel saradc close - close the SARADC saradc getval - get the value in current channel saradc get_in_range <min> <max> - return 0 if current value in the range of current channel Product checking: fail! reboot use default mode: normal bl31 reboot reason: 0xd bl31 reboot reason: 0x1 system cmd 1. So my question is: Is there any hope? ...and if yes: How?

Hello, I am trying to add support for H96 Max X4 android box Here are the specs of my box: SOC: amlogic S905x4 RAM: 2GB Pictures I am trying to run this box as a raspberry pi alternative as I can't find a pi anywhere. I know that there is no official or unofficial support for this chip so I plan to add support for this box myself. After some research, I found that there are 4 variants according to coreelec community and they have already added support for generic S905x4 boxes. So my first intuition was to boot coreelec and try to move on from there. I tried their prebuild image and followed their guide but no success. The box didn't boot to coreelec. After that, I also downloaded the armbian community build for S9xx-box and then replaced the dtb file with the one that I pulled from coreelec image I also renamed the u-boot-s905x2-s922 to u-boot.ext but still it didn't boot. I did so cause I found that S905x4 is very similar to S905x3 so I thought that it might work and it was suggested in this forum post But no It didn't work. After all my initial failed attempts I then opened up the box and found the UART pins quite easily. I am currently quite new to hardware hacking and don't even have a USB to TTL converter in hand. I ordered one on amazon it will be delivered in a couple of days still I did some probing with a multimeter and found out which pin is TX and RX but I am not quite sure. PCB pic I am attaching the photos for someone else who stumbles upon this post and can use this info I know that U-BOOT used by these boxes is used by many routers but as I am so new I am not sure how I can use UART to build my very own dtb or U-BOOT.ext for this box When I tried opening the dtb file That I pulled from coreelec I could not read it at all it looks like it was encoded. Here is link to the file I pulled from coreelec https://www.dropbox.com/s/uqsohy4na0tnj6i/sc2_s905x4_2g.dtb?dl=0 If someone has resources that can help me build my own U-BOOT and dtb for this box it will be very helpful.

SDMC DV9286 is an 8K TV box for operators running Android 13 TV OS on an Amlogic S928X octa-core Cortex-A76/A55 processor with 4GB to 8GB RAM, WiFi 6E and Bluetooth 5.2 connectivity, an HDMI 2.1a port, and 8K AV1, H.265, VP9 video decoding support. We had started to see 8K TV boxes based on the Amlogic S928X processor at IBC 2022 last September, but with few details. SDMC DV9286 announcement brings a few more details such as the GPU used in S928X and which version of Android will be used. SDMC DV9286 (preliminary) specifications: SoC – Amlogic S928X octa-core Cortex-A76/A55 processor with Arm Mali-G57 MC2 GPU; 12nm process System Memory – 4GB LPDDR4 (up to 8GB option) Storage – 32GB eMMC flash Video Output – HDMI 2.1a up to 8Kp60 with HDCP2.2/2.3, HDR 10, HLG, HDR10+, Dolby Vision (optional), and HDMI 2.1-specific features such as eARC, VRR, QMS, QFT, ALLM, [...] The post SDMC DV9286 8K TV box runs Android 13 on Amlogic S928X processor for OTT/IPTV deployments appeared first on CNX Software - Embedded Systems News. View the full article