SteeMan

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.

armbian-config doesn't work for these amlogic tv box builds. Please follow the instructions here: https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus

What hardware? What dtb are you using? What exact build (filename)? What instructions to install did you use?

Did you install the armbian-firmware-full package?

Are you using Armbian? What version?

That is not the full log. Look at the last line of the output: Please post this.

Mpved to the correct forum.

@ison You are using the wrong image. No TV boxes I'm aware of support uefi. Please read the following two FAQ items: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus

What build are you using?

There is a bug in armbian-install in this version that will likely cause your scenario to fail. You can manually fix/verify the issue by looking at the armbianEnv.txt file installed on the nvme drive and look for the uuid of the drive. It should be prefixed with UUID= (compare to the armbianEnv.txt on your sd card). Or you can use a nightly image which will already contain the fix to armbian-install and retry.

@Thang The weekly images should work. Are you installing a weekly image, or upgrading to it? If you are upgrading, then you will need to edit the extlinux.conf file and change uImage to Image.

@tepo The Banana PI M2 Zero is not supported by Armbian maintainers. It is "Community Support" status, which means that it is available for the public at large to support. There is currently no one in the community that has stepped up to say they will be a maintainer for that board. So the board is languishing for lack of support by anyone interested enough to contribute. Armbian is first and foremost a platform for building images for the many different Arm based boards that are out there. But with limited resources (both people and money) only a handful of boards get officially supported by the project. The majority end up supported (or not supported) by the community of volunteers interested in the particular boards.

Maybe if you provided more than a one sentence description on what your problem is and what you have tried, you would get a better answer. u-boot logs are really useful in debugging booting issues for example.

Here is the line from the script install-aml.sh: mv -f $DIR_INSTALL/u-boot.ext $DIR_INSTALL/u-boot.emmc No u-boot.mmc

If you are using the community armbian build, then it will first try to boot from the sd card if present and then boot from emmc if no sd card. I don't know, I've never tried it. If you install to emmc, you should have a backup of your android firmware and know how to reinstall it if something goes wrong. Otherwise your box could end up bricked.