jock

@remlei you can see from the u-boot log that the overlay is not applied because there is the rk322x prefix two times. The overlay must be set literally as usb-otg-peripheral as I wrote above, and not rk322x-usb-otg-peripheral: the rk322x prefix is added automatically. About the OTG functionality, as said your mileage may vary. Unforturnately the rk322x OTG port or driver does not seem to be very collaborative or totally standard compliant.

@remlei last time I checked, the usb gadget overlay was working fine and the UCD device was correctly spawning up. Some things work with rk322x (mass storage), some others don't (UAC1, UAC2), so your mileage may vary. Verify you have usb-otg-peripheral in /boot/armbianEnv.txt in the overlays= line

@Vinicius Guastala I agree with @fabiobassa, thanks for the very detailed post of your board and broad description of the behaviour. I would suggest you to erase the internal flash and try to boot from sdcard with this armbian image. It is an "experimental" image with opensource Trust OS; many recent boards are having issues with proprietary trust os, possibly yours has similar issues, so you could give a shot to this. By the way, the serial log output would be indeed very handy if you have the chance to find the serial port. Beware also that armbian (and multitool) use 115200bps baud rate for the serial, while proprietary software uses 1.5Mbps baud rate!

@gurzixo much better to steer to an officially supported SBC from armbian, if you need something reliable: https://www.armbian.com/download/?device_support=Platinum support&arch=aarch64

Yes, but use a flash device as swap is the worst idea you can have

The only way, which is really discouraged and discontinued, is to use a build with legacy kernel. On mainline kernel, the only driver supported is for ssv6051p, but it does not work for ssv6256p. There could be several reasons the eMMC is not detected. One of the reason is obviously it is the broken, even though the DDR part is still working. More often the board has some circuitry or the chip has some configuration that need to be tuned properly in software to work. Tv boxes have plenty and plenty of different configurations that is impossibile to cover all the compatibility issues that may arise. If the flash part of the eMCP is really broken, if you plug an sdcard with Armbian on it, the stock Android should not boot (obvious if the internal flash is broken) and Armbian should boot instead. About the MSN8800D, it seems to be a clone of AIC8800D chip, of which a driver is circulating and should already be integrated in armbian, but not yet enabled for rk322x.

@incbot just use a fresher image rather than a two years old one: https://github.com/armbian/community/releases/tag/25.5.0-trunk.444

I don't see any driver written with your name. Can you share that?

If you think it is so simple and you say you're so capable, do it yourself. Point me where your contributions to the project are and I will take this post seriously.

At the moment there is no driver for the mainline kernel to drive the analog output, so no composite output unfortunately. The driver in the vendor kernel does not seem very complex, but yet noone has ported it to mainline kernel.

Hello, you may want to edit the device tree and turn off the mmc@... node where the sdio wifi chip is connected. You may find it easily looking for supports-sdio property, then switch status property do disabled

Added support for Debian Trixie (only for arm64)

No factory images here; I just tried an Armbian image with Ubuntu Noble and it worked flawlessy with XFCE, just need to disable the XFCE compositor to have full framerate.

UPDATE! Hello everyone, I'm glad to give a fresh update. After a couple of weeks and more or hard work, I finished the complete overhaul of the repository. It is now handled in a much tidier way. The result of this is a much easier support for new distributions as soon as they are published! I have just updated the instructions, since the old repository is no longer active; I suggest you to remove the old repository from you apt sources and install the new repository as described in first page. Packages for Noble Numbat are already available! Enjoy!💪

with mainline kernel, yes

I don't know if this is trolling or not. Let's assume it is not and the question is genuine. There is no hate against cheap chinese tv boxes, but there are many objective problems: no support: hell yeah, you can't say anything against this, at most you get the original firmware from the vendor, expect nothing more varying hardware quality: plenty of stories of hardware failing after few weeks/months. Lucky you your hundreds worked so far (I wonder what do you do to sell hundreds of those...) varying hardware in general: pain and suffer to support; you should at least say thank you to people here around that spend their time (that will not come back) to let you have a cheap tv boxes working with free and open source software (not to mention those who sell them...) no documentation: it means, mostly, that it takes huge amount of time and advanced skills to reverse engineer the thingies. Time is the fundament of a salary, skills are the multiplication factor of a salary. People here - all the people, starting from the heads of Armbian project down to the forum user answering to posts - give both for free, but no salary for us, despite the passionate efforts.

@CtrlValCanc the fix has just been mainlined: https://github.com/armbian/build/pull/7959, so future dtb packages will have the fix already included!

@CtrlValCanc glad to hear you got it working, prego! About the ethernet, if the hardware is really failing, you may want to try and set the port to 10Mbps instead of 100Mbps with ethtool; it won't give you a fast connection, but at least the device could be reached on the net for maintenance.

@CtrlValCanc try to substitute /boot/dtb/rockchip/rk3318-box.dtb file with the one I provide attached to this post, reboot and see what happens rk3318-box.dtb

Hello; multitool has the port 22 open and listening for ssh connections. If it does not show the open port, then it is either freezed or did not start at all. Regarding your A6 Mini board, which seems the only one with rk322x, it is not a board that we have encountered here on the forums, which is quite curious since the board marks a production date of 2018. Consider it to be a fake board. I have not exactly understood what is what, since you declare you have a 2/16 S905W board with fake specs and a 1/8 RK322x board with (supposedly) real specs, but they could easily be both fake. Looking on google for A6_Mini boards, I only see S905L devices. You also say LibreELEC boots, but you did not say on which of those two boards boots.

My fault, didn't notice the log in the previous post. I will look into them.

It is common for tv boxes that some devices don't work out of the box. Tv boxes are not officially supported and will never be officially supported in armbian mainly for the reason they carry wildly different hardware and it is not feasible to give any kind of official support, hence it is totally a community effort. The reason rk3318-config does not show any wifi chip is that the wifi chip is either connected to a different mmc bus, or the "power on" gpio pin is the wrong one. Inspection of the device tree from the original firmware will surely clarify what is going on. Your particular board (X88 PRO is known to have the wifi chip on the "alternative" sdmmc_ext bus. In your case you have to run rk3318-config for a first time, configure the board with led-conf2, reboot, run again rk3318-config (this time it should show the wifi vendor and device IDs), let it configure the proper device tree overlay, reboot again and you should finally be able to see the wifi adapter. About the ethernet problem, I see NO-CARRIER: either the cable is not connected properly or the ethernet port is faulty. dmesg log is always very appreciated for debugging.

@CtrlValCanc SP6330 is a clone of AP6330, which is a combo device based upon Broadcom BCM4330, you should select the right board in rk3318-box (X88 Pro B should fit your case) then reboot and then it should be detected and perhaps even work without more intervention.

@CtrlValCanc hello! Yes there was an issue with latest u-boot and rk3318 devices: network interface could not be detected, hence its mac address could not be setup. The direct result is that, on every boot, the device receives a new MAC address and thus a new IP address each time. This is the pull request that fixes the problem and soon should go into repositories. In the meantime you could work around the issue setting a static IP address. Ps: congrats for the funny nickname

The environment has never been actually tested. Once it was saving and restoring it from a sector on eMMC, but then later changed to the "default" ext4 environment, but never tested even because older u-boot were used to corrupt ext4 partitions when trying to write to it.