jock

in armbian/rkbin repository

Yes, it could be the 660 Mhz ddr that is causing a bit too many troubles around. If have practice with hexadecimal editors, you can open the image find the red bytes in the top half of this screenshot and exchange with the red bytes in the lower half; save and try again.

Honestly, I don't know. I did not even know that rk322x could boot from a SPI device. About the USB thing, despite the "adapter" you may need to do what you ask, the boot options depend upon the original firmware you have on the SPI right now and, AFAIK, USB boot is not available in any original firmware. Surely the SOC itself is not capable to boot from USB, there should be a piece of software installed on the SPI (read: uboot) that will do that. If you put an sdcard in a USB dongle and then the USB dongle in the USB port clearly you're trying to boot from USB, so it won't work

Yes and no. They are known to report quite high temperatures but the heatsink is just barely warm. Surely a reported temperature of 80°C at idle is a bit too high. Mines are idling around 65°C

Nope, usually the ethernet is working very well by default and does not require any specific configuration: both phy and mac are in the 322x SoC, so once configured properly in the dtb, there are practically no chances of misconfiguration at kernel level. There may be some corner cases, but as long as this thread exists, I never encountered a board which required a specific configuration for ethernet.

You should use the images from this thread instead of the firefly

I'm afraid you have to find and use the emmc clock pin to enter in maskrom mode and clean the emmc with rkdeveloptool using a male-to-male cable

This is essential, since nand is supported only with legacy 4.4 kernel. That's clearly and boldly stated in the first page. That board is perfectly supported, but probably it is more convenient for you to run a fresh mainline kernel from sd card than an ancient legacy kernel from nand.

Sorry, just to be clear (I'm curious...): you tried the latest Ubuntu Lunar with edge 6.3 kernel you can download from https://github.com/armbian/community ?

@mydeardiary hello, as @RaptorSDS said, rtl8723as and rtl8723bs are two different chips and require different drivers and firmwares. rtl8723as driver is not in the linux kernel and looks like quite difficult to find a suitable driver. Libreelec folks did some adaptation for the rtl8723au: https://github.com/dtechsrv/LibreELEC-AML/pull/24

I would suggest you to keep the multitool around. Make a backup first of the entire system, but beware the 4G file size limit. You have to double check the validity of the compressed file after you make the backup, because the multitool won't give you errors 😕 You can use it in case something happens and you need to do maintenance. About the upgrade process per-se, I did a couple of times an upgrade from buster to bullseye and a "downgrade" from sid to bookworm. Despite the "usual" issues when doing upgrades, kernel and bootloaders have been kept at their places. Anyway check that the kernel, uInitrd and dtb files are still there in /boot after the upgrade (they should) and follow the standard debian/armbian upgrade instructions and cross the fingers!

@EmilB I'm getting quite confused among the "unmodified" and "original" attributes. Still I don't understand if you have had success in installa jumpstart on nand or not. One thing is sure: the bootloader of multitool and armbian is well able to boot from USB, so if you keep the sdcard in the slot, it will also try to boot from USB. As you see, there are several stages in the boot process that can lead to a multitude of situations, it's not easy to explain and understand the "tree" of options that will come out. One thing that is often sure is that if you completely erase the internal NAND/eMMC, the board will indeed boot from sdcard, but with NANDs if could be not so easy to completely erase the flash due to differences among the already installed bootloaders (ie: it may work from multitool, or may require rkdeveloptool, ...)

@EmilB sure you can mix things. On the first kernel upgrade the whole thing will break and the system won't boot anymore. I won't suggest to others doing the same.

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.