jock

Most probably for some reason jumpstart is not getting written on the nand. Clean the NAND and then armbian should boot from sdcard. As said, I updated the instructions to be used with rkflashtool, you can perhaps try with that.

@EmilB No, the upgrade of the loader does not magically gives you the USB boot. I didn't even understand why you had to this loader upgrade, on NAND boards it is not suggested to do. The only thing you should have done (and you have to do right now) is installing the jumpstart thing via multitool, then it should boot armbian/libreelec from both sdcard or USB stick/drive

@dicky soeliantoro follow the instructions, you don't need to change dtb files manually. The approach is radically different: there is a basic device tree installed by default which is very compatible among the various boards then, with the help of rk3318-config script, you can choose your board and apply a device tree overlay which further enables features and compatibility settings with specific boards. Exchanging device trees without consciousness is the proper way to cause unwanted troubles.

Actually H3 are way less troublesome because they boot first from sdcard (rockchip first boot from emmc). People have had quite success in using the Sunvell R69 image for them: https://github.com/armbian/community

@dicky soeliantoro On first page you can find the "Prebuilt images" links. The "archived" ones are quite recent with kernel 6.1.x are good to go with stable kernel. There are also the "nightly stables", which have 6.3.x kernel, which is newer and with more features, but also could be less stable. The choice is yours, it depends on what you want to do with the box.

The reference thread for 322x device is this: anyway, for your specific case, the board is a very old one, in fact it has a much better design and components than newer boards, which have been under a cost cutting over time. You have what it looks like a very accessible serial port (the four holes near the sdcard), so the first step to do debug is getting a TTL-to-USB adapter and logging what happens on the board. Of course armbian does not boot from sdcard: it is done on purpose that way; the installation procedure is described in the post above and the multitool is designed to that exactly that. Also note that the led should be blinking when the multitool boots; also if you don't see anything on screen, you can still access it via network using SSH. Everything is described in the first post of that thread

None, since you say your box has a rk3288 which is not rk3318 nor rk3328

@EmilB from the logs you posted above, I see "Opening loader failed"; did you download the bootloader file in the same directory of the tools? Looking into the rkdeveloptool source code, the error comes out because the file is not found. 🤨 Also to upgrade the loader upgrade_tool is the only one which was reported to be working: rkdeveloptool will tell that everything went fine, but actually won't upgrade anything. The procedure is described in this post, but I guess you already read it. edit: about the hack you had to do to boot the multitool correctly, I don't know where the problem lies. We know that in some cases the multitool does not boot but instead libreelec do. We did some speculation with @ilmich and thought it was some sdcard "power" missing in the multitool device tree, but after doing the changes, it still does not work. edit2: I update the nand bootloader installation process in this post to use rkflashtool in place of rkdeveloptool/upgrade_tool. It is suggested to use that tool and the shipped bootloader binaries which have tested. Also I checked the multitool jumpstart feature with an USB stick right now and it works pretty well.

It is widely known that often they reuse those chips which are not up to the specs. They pick parts from the trash and assemble the tvboxes. Sure you are not the only one, but helping solve the problem without the board in my lab for tests is difficult anyway.

5v, no less no more. Anything else will probably destroy the board. Unfortunately I don't think you can do anything with maskrom mode; I don't have such a board so I absolutely don't know what is going on with that particular board. All we can do is guessing 🤷‍♂️ rkdeveloptool via maskrom mode if you have a full-image backup, or AndroidTool and the upgrade images for your board you can find on the internet. You have to find the right one though, which can be a time consuming task. Well, tvboxes are not really serious things. If you really need the board to do something minimally serious, it is better to go with a proper SBC and even better a proper SBC officially supported by armbian. if you want to toy around, tvboxes can be funny but beware they are often assembled with scrap parts stick together with hacks, especially the cheapest ones, and supporting them is quite painful.

@Scmel actually it is neither armbian nor homeassistant problem. I mean, armbian community does not have to tell you how to install homeassistant, and homeassistant does not have to tell you how to install it on every platform available on the planet. You have to find the way through, as I said I installed the core version successfully following the instructions on the homeassistant site and it was sufficient to me.

@Scmel Honestly, you should ask on homeassistant forums perhaps, or read the documentation. I have an instance of homeassistant core installed on a rk322x box and works fine, but you have to install it manually by yourself. The other versions may require virtualization or other unsupported/unavailable features.

Hello @guitoscan , two possible issues come up to my mind right now: 1. the system is unstable because some of some wrong cpu/memory setting (voltage too low, frequency too high, things like that) 2. the trust os is doing something bad, and since it is closed source, we could never know what it is doing. To handle the former issue, you can try adding cpu-stability overlay in /boot/armbianEnv.txt adding a line like this: overlays=cpu-stability beware that running rk322x-config will overwrite the overlays line, so you will have to append cpu-stability to the other overlays if you run rk322x-config The latter issue can't be solved easily right now 😕

Yes, then the red and blue leds are alternative and cannot be controlled independently. It is very common. For making them blink on "disk" operations, for which I intend sdcard/emmc IO, you have to echo the right mmc device (mmc0, mmc1 or mmc2 - depending on what you want) to trigger.

@pakos96 https://linuxreviews.org/HOWTO_Control_LED_Lights, in particular the paragraph "Inspecting Your LED Lights" Note that, depending on the board, red and blue leds can be controlled independently or are mutually exclusive (ie: "on" state turns red led on, "off" state turns blue led on)

@spinning banner Yes, it should work that way (except your board has some more other flaws which I'm not aware about...)

@spinning banner Hello! Unfortunately R29 boards seem to have a widely well-known issue with HDMI output, which is not working for some unknown reason. Some research has already been done in the past on device trees, inspecting photos and logs, but still the problem is unknown, as long as I don't have such a board in my lab to really study where the problems are. The S9012P wifi chip also is a no-name chip, as long as I remember it is a chinese chip with no known drivers that "emulates" a realtek chip (not a broadcom one, like those which AP6xxx are based upon), but I can be wrong. @RaptorSDS did some research on that chip, but as far as I know, there is no solution because there is no driver for that (see https://forum.armbian.com/topic/12656-csc-armbian-for-rk322x-tv-boxes/page/57/#comment-156548) R29 is a quite weird board actually; despite being very similar to others, has some compatibility issues all-around and it does not surprise me the multitool has troubles with emmc, although it should have none. From the android dmesg I see on android the eMMC runs at 31.25 MHz; Multitool runs it at standard 50 MHz, and that may be the cause of the flash storage issues on multitool. The reason could be a very poor quality board or eMMC, because ALL the boards with eMMC I have ever seen runs the eMMC at 50Mhz perfectly fine and I never had to downclock the eMMC frequency to solve an issue like that.

@olivluca well, it is not totally a stupid idea, but consider that tv boxes are mostly just-for-fun kind of product; I would rather go with a properly supported SBC, or at least a community supported SBC. For example, today I test a Radxa Pi-e board (very small, one gigabit eth, one fast eth, 802.11ac/b/g/n wifi) that turned out being a very impressive throughput of > 100mbps on a 300mbps 802.11n 2.4ghz link, and the access point was one floor above! SImilar results came from an Orange Pi 4 LTS; the tv boxes I tried couldn't reach such bitrate and one of them which had the ssv6051 wifi on board was not even working right. I never tried RaspAp, but looks very good if it does what it promises. But if you want something reliable, go with an SBC + armbian, otherwise find an access point that supports openwrt.

There is no prebuilt image of that kind on purpose: whenever you do an update of the kernel/uboot, it will break the system and it won't boot anymore.

@Anthony Walter The Mali-400 GPU is supported out of the box with recent kernel and distributions. There is already a driver in the kernel, but (I guess) it has to be properly set up in the device tree and in userspace for your particular board. Since your board is not maintained by anyone, support is community based. If someone step out for help good, otherwise you have to do it yourself.

@http418 Still, the necessity of the boot logs are sine-qua-non condition to understand why the board does not boot, otherwise anyone can't be of any help here. To get the boot logs you need the serial adapter and to find the serial pads/pins on your board. Possibly they are below the heatsink, but I have no such board so I don't know. About your board, an R29, the HDMI port is reported to not work and I can't fix that, because - again - I have no such board. Did you try to access via SSH to the board after 5 minutes it booted to see if is working or not?

@sermayoral if you search through this thread, you will see that box vendors are often altering the specs on purpose to fraud people, other time they are just coarse.

@http418 If you don't provide any logs, photos, description of the issue (you were talking about the loader before, now you talk about armbian dtb...) you will be banging the head for yet long time...

Nope, the cpu is 32 bits.

­DISCLAIMER (PLEASE READ): everything you can find in this thread (binaries, texts, code snippets, etc...) are provided AS-IS and are not part of official Armbian project. For this reason not people from Armbian project nor myself are responsible for misuse or loss of functionality of hardware. Please don't ask about support or assistance in other non-community forums nor in the official Armbian github repository, instead post your questions in this thread, in the TV Boxes forum section (hardware related) or in the Peer-to-peer support section (general linux/software related). Thank you! This thread is to give stable and mature long-term range support to rk3318/rk3328 found in many tv boxes in Armbian project as Community Supported Configuration (CSC). The current work is mainlined into Armbian project, but your mileage may vary; most recent developments live on my personal fork on github -> here <- Important notes: is just a personal opinion, but apparently widely supported, that rk3318 chip is not an official rockchip part. They probably are scrap rk3328 parts which have not passed conformance tests but are sold anyway to tv boxes manufacturers. They don’t reach the same operating frequency of the rk3328, have much higher leakage currents (and thus higher temperatures) and often the boards they are installed on are low quality with low quality components, in fact a very very common issue is the eMMC failure due to bad parts and bad soldering. So said, I personally suggest not to buy any rk3318 tv box, but instead find a properly supported SBC (Single Board Computer) if you need a reliable product. In the unfortunate case you already have such product, this thread may help you have some fun with them. What works: • Works on RK3318 and RK3328 TV boxes with DDR3 memories • Mainline u-boot • Mainline ATF provided as Trusted Execution Environment • All 4 cores are working • Ethernet • Serial UART (configured at stock 1.5Mbps) • Thermals and frequency scaling • OTG USB 2.0 port (also as boot device!) • EHCI/OHCI USB 2.0 ports and XHCI USB 3.0 ports • MMC subsystem (including , SD and sdio devices) • Hardware video acceleration (fully supported via RKMPP on legacy kernel, support via hantro and rkvdec kernel driver on mainline) • Various WIFI over SDIO are supported • Full acceleration on legacy kernel and mainline kernel • U-boot boot order priority: first the sdcard, then the USB OTG port and eventually the internal ; you can install u-boot (and the whole system) in the internal and u-boot will always check for images on external sdcard/USB first. Unbrick: Technically, rockchip devices cannot be bricked. If the internal flash does not contain a bootable system, they will always boot from the sdcard. If, for a reason, the bootable system on the internal flash is corrupted or is unable to boot correctly, you can always force the maskrom mode shorting the clock pin on the PCB. The procedure is explained here for rk322x, but for rk3318/28 is the same. In most of the rk3318/28 boards, shorting the clock pin is difficult or impossible because eMMC are BGA chips with no exposed pins. Pay double attention when burning something on the internal flash memory and always test first the image booting from the sdcard to be sure it works before burning anything in internal flash. This is a list of posts where forum users have been able to spot the eMMC clock pin to trigger the maskrom mode: H96 Max+ (board signature: RK3318_V1.4) by @Gausus X88 PRO 10 (board signature: X88_PRO_B) by @mathgaming HK1 Max (board signature YX_RK3318) by @Constantin Gatej Ninkbox N1 Max RK3318 by @enigmasphinx Hongtop H50 (board signature t98-3318-221-v11) by @GmP Partecipation and debugging: If you want to partecipate or need help debugging issues, do not hesitate to share your experience with the installation procedure of the boxes. In case of issues and missed support, provide as many as possible of these things is very useful to try and bring support for an unsupported board: some photos of both sides of the board. Details of the eMMC, DDR and Wifi chips are very useful! upload the device tree binary (dtb) of your device. We can understand a lot of things of the hardware from that small piece of data; and alternative is a link to the original firmware (you can do a full backup with the Multitool); dmesg and other logs (use armbianmonitor -u that automatically collects and uploads the logs online) attach a serial converter to the device and provide the output of the serial port; Multimedia: Mainline kernel: 3D acceleration is provided by Lima driver and is already enabled. Hardware video decoding: https://forum.armbian.com/topic/19258-testing-hardware-video-decoding-rockchip-allwinner/ Legacy kernel: If you need multimedia features, like OpenGL/OpenGL ES acceleration, hardware accelerated Kodi, ffmpeg and mpv you can take a look to this post Installation (via SD card): Building: You can build your own image follow the common steps to build armbian for other tv boxes devices: when you are in the moment to choose the target board, switch to /TVB/ boards and select "rk3318-box" from the list. Prebuilt images: Nightly stables - built from trunk by Armbian servers and GPG-signed: https://github.com/armbian/community Multitool: Multitool - A small but powerful image for RK3318/RK3328 TV Box maintenance. Download it from here Quick installation instructions on eMMC: Build or download your preferred Armbian image and a copy of the Multitool; Burn the Multitool on an SD card; once done, place the Armbian image in images folder of the SD card NTFS partition; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; OPTIONAL: you can do a backup of the existing firmware with "Backup flash" menu option; Choose "Burn image to flash" from the menu, then select the destination device (usually mmcblk2) and the image to burn; Wait for the process to complete, then choose "Shutdown" from main menu; Unplug the power cord and the SD card, then replug the power cord; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt. On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run rk3318-config to configure the board specific options Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed! Despite the procedure above is simple and reliable, I always recommend to first test that your device boots Armbian images from SD Card. Due to the really large hardware variety, there is the rare chance that the images proposed here may not boot. If a bad image is burned in , the box may not boot anymore forcing you to follow the unbrick section at the top of this post. Quick installation instructions to boot from SD Card: If you are already running Armbian from eMMC, skip to the next step. Instead if you are running the original firmware you need to first erase the internal flash; to do so download the Multitool, burn it on an SD Card, plug the SD Card and power the TV Box. Use "Backup flash" if you want to do a backup of the existing firmware, then choose "Erase flash" menu option. Build or download your preferred Armbian image; Uncompress and burn the Armbian image on the SD Card; Plug the SD Card in the TV Box and power it on; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt; On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run rk3318-config to configure the board specific options Run armbian-config to configure timezone, locales and other personal options, or also to transfer the SD Card installation to internal ; Congratulations, Armbian is running from SD Card! Tutorial - How to install Armbian on your TV Box (by @awawa) : https://www.hyperhdr.eu/2022/01/tv-box-mania-i-part-x88-pro-10.html A note about boot device order: With Armbian also comes mainline U-boot. If you install Armbian, the bootloader will look for valid bootable images in this order: External SD Card External USB Stick in OTG Port Internal The Multitool does not boot / How to burn image directly on eMMC: Some boards have the sdcard attached to an auxiliary (called also sdmmc_ext or external) controller which is not the common one. Forum findings declare that those boards are not able to boot from sdcard with stock firmware and they neither do in maskrom mode: the stock firmware always boots even if you put the multitool on sdcard. In such case, burning images directly on eMMC is the only way to have a working Armbian installation. You can follow these instructions by @fabiobassa to burn images directly on eMMC: https://forum.armbian.com/topic/17597-csc-armbian-for-rk3318rk3328-tv-box-boards/?do=findComment&comment=130453 Notes and special hardware: Script to change DDR memory frequency here Wireless chip AP2734, SP2734, HY2734C and similars: they are clones of AmPAK AP6334 which is combo wifi + bluetooth of broadcom BCM4334/B0 chips. You may need a special nvram file, instructions by @paradigman are here Critics, suggestions and contributions are welcome! Credits: @fabiobassa for his ideas, inspiration, great generosity in giving the boards for development and testing. The project of bringing rk3318 into armbian would not have begun without his support! @hexdump for his precious support in early testing, ideas and suggestions @MX10.AC2Nfor his patience in testing mxq-rk3328-d4 board support All the rockhip64 maintainers at Armbian project who have done and do most of the work to support the platform