SteeMan

Upgrade to what newer version? A userspace version (i.e. ubuntu focal to ubuntu jammy) or a kernel upgrade (i.e. 23.02 based armbian kernel to 23.05 armbian kernel)? For userspace it is recommeded to do an install, as upgrades are not tested (but I just did a focal to jammy upgrade last night and they generally do work). For the kernel, you can just do apt update/upgrades to continue following the builds over time (assuming you don't have your kernel frozen in armbian-config).

@helios thanks for posting that. One thing that has changed between the two versions is the name of the kernel image. It used to be uImage and is now Image. Can you look at the extlinux.conf files on the two versions to make sure they are changed appropriately for the kernel name change?

The u-boot-s905x2-s922 file hasn't changed. So it shouldn't be necessary to copy that. Can you look at the file size of the two and also run diff on the two files. Again they should be the same as that file hasn't changed. If they are different, then something in the build process is causing a problem.

Did you patch the Makefile so they build? For example a patch that adds dtbs: patch/kernel/archive/meson64-6.2/boards-g12-add-spi-nor-flash-enabled-dtbs.patch

Can you add the version information for the builds you are trying that are not working. I'm otherwise just guessing.

*minimal* is the key there, it really is minimal, you need to install armbianconfig if you want to use it: sudo apt install armbian-config (Note: since you have installed 23.05, the apt repositories don't yet have the 23.05 packages available (some issues still being addressed) so the apt install may not currently work until that is resolved)

userspace app issue, moved post to correct forum

@Alcide You are not using Armbian. The location you are downloading from is a fork of armbian. They use the Armbian name without permission. We can't help you in these forums because we don't know what code you are using, you need to direct your questions to the location you downloaded your code from. Those developers do not participate in these forums, nor support armbian development.

@guleli huseynzade @YanCorote You should be reading the following thread, and post your questions there. But simply saying it doesn't work, isn't going to get you much help. If you read that thread, you will see all the issues others have run into and the level of information necessary for getting help.

What exact image are you working with (download link please)? Please also read the following FAQ post:

@JaimeDB How did you install to emmc?

Have you tried using the amlogic usb_burning_tool (that is the common way to install/restore amlogic firmware)? Note you will need a usb-a to usb-a cable to do this.

This question is irrelevant. No one really knows the answer. What Igor is really saying, is if you want anyone to spend their time helping with this, you need to reproduce on current code. If this was a common problem, it would already be fixed as many others would report something like this. So it is either something due to your older code, or something specific to your environment. Those are difficult to diagnose, and when you are asking people to volunteer their time to help you, they are only going to do that, if it is a reasonable to do and you have done everything to narrow the scope of the problem to something reproduceable by someone else. My first thought is based on the lack of information provided, but is a common cause of mysterious errors, and that is power issues. How is all of this hardware powered? SBCs are notorious for having poor power supplies and under load have voltage drops that cause mysterious problems (especially with usb devices drawing some of that power).

Are you looking at current code in github source? I think this has already been fixed.

Have you tried with armbian-firmware-full?

@andersonpersan Could you do some tests for me? Since I can't reproduce the problem (the newest images work on my s905x boxes, including multiple TX3 mini's and X96 mini's), i'm not able to solve the problem. Since you have found that an older build is working for you, I would request that you try a couple of things to see we can figure out what isn't working in your case for the latest builds. Since you have already installed to emmc, the first test I would ask is to now try to boot a new build from an sd card with the old build in emmc. (The boot logic should boot from SD card first, before emmc)

@Koub Note that TV boxes are not supported by armbian. https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first

moved thread to correct forum

Moved post to correct location.

Second comment is that since there is no one that actively monitors the forums for allwinner tv box questions, your best bet is to search the archives for as much information as possible for your box/similar boxes.

First start by reading this: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first Note that of the non-supported tv boxes, allwinner is the least supported. Second note is that the H6 and H616/H313 are different allwinner cpus. You can't use a build for one with the others as the dtbs are very different.

A note that cheap android tv boxes are known to report fake data to the os. The best think to do is to open the box and directly inspect the board/chips. But even then, some manufacturers will alter the markings on their chips to falsify the board makeup. The goal for TV box manufacturers it so produce the lowest price box, so corners are cut everywhere. That is why it is impossible to support these boxes well, as any two boxes can have different internal components.

@Jaume Palomer García Please detail what box do you have, what build you are using, what instructions you are following, what dtb you are using and what uboot. You haven't provided any information that would allow anyone to help you.