SteeMan

moved.

So you say you have and Orange PI Zero Plus, but you have tagged this post as Orange PI Zero Plus2 H3. (Which are two completely different boards). So the first question is what actual board do you have (I know that Orange PIs board names are very confusing). And then what build are you testing?

I don't think anyone here has ever seen a device like the one you have posted. Why are you not asking for support from either the manufacturer of your device or who you purchased it from. These forums are for the Armbian build framwork and the images that mostly volunteers put together to get mainline linux working on various devices. It seems that you are requesting support for your device and this is not the place for you to find support.

My best guess is that you have an Android install on your eMMC (Android uses those two boot partitions as part of how it installs new versions, while still keeping the old). How Android formats a disk is generally somewhat custom and often the partitions aren't readable by mainline uboot / mainline linux. (It should be a GPT partition table, but for some reason I haven't dug into, isn't recognized by mainline). I deal with these things on Android TV Boxes all the time. You should be able to just format the entire emmc for your use as what is on their isn't useful to you. However, I'm not familiar with this specific board and what the specifics of its booting process is. So there is a chance that something on the eMMC is required for a successful boot.

Of course you are free to try Armbian images, but you should know that the Orange PI 3b is not an Armbian supported board. It is community support status and there is no maintainer who has volunteered to maintain it. I just want you to understand and set your expectations appropriately for what an Armbian build will provide you.

This isn't the right place to be posting your question. All the images you are testing are OrangePi images not Armbian images. For issues with Orange Pi images you should report in their forums.

What exactly are you looking for? This is an Armbian Linux forum. It seems you are looking for an Android firmware based on your post.

Have you tried the generic rk3328 builds found discussed in this thread: I would start there by reading that thread. Your box likely has a lot in common with what is discussed there.

@robertM You really should have an armbian-bsp-* package installed for your appropriate box as well. If I reread your previous posts that should be: armbian-bsp-cli-rock-5b So I would suggest running: sudo apt install armbian-bsp-cli-rock-5b That should clean up your login info to be up to date and you will then pick up future changes as well.

@adron That kernel isn't mainline 6.1 but based off the Rockchip BSP 6.1 kernel.

Stable images are produced every three months. Development builds are produced at least weekly depending on the support status.

You are most likely fine. But out of curiosity can you run the following: apt list --installed | grep armbian

It looks like you have your u-boot loaded to the spi based on what the log shows. So all you should now need to do is install an Armbian image to the SD card, boot into that image and then use armbian-config to copy the image to either eMMC or nvme (you can try both and experiment which you want to go with long term). You also have the option of having /boot on eMMC and the root filesystem on nvme (since the /boot is mostly read only that sometimes is a safer option than relying on being able to boot off of the nvme. There are lots of options available depending on your usage pattern and hardware.

@Error1429 If you were to submit a well thought out PR along with the necessary doc and website updates, I'm sure this would be accepted and incorporated. But I think the feedback thus far as that this isn't something of high enough priority to ever being incorporated with Armbian's very limited resources.

If it is NAND then you are out of luck as mainline Linux has no support for NAND. If it is eMMC then your dtb would likely need to be modified to support your hardware if it isn't showing up. My guess is that you have NAND.

You will have to uninstall the upstream wireguard as that will remove the dependancy on the non-armbian kernel.

That is the expected behavior. You always need to "install" u-boot after a new version from apt. The apt package just provides the binaries that you can install.

There are no instructions to do this because it isn't supported and it is really, really, really hard because there are many, many, many dependencies across many different repositories all changing over time. While you may be able to get something to work in some cases, you have to deal with tracking down build errors and figure out what changed and what to roll that source back to.

From the screenshot you included I can determine the following: 1) This is a repurposed TV Box type device since it is running the rk3318-box build. (Note Armbian does not support TV Boxes, these are all community supported) 2) You are running a build from May of 2022 (over three years old) 3) As it says: No end-user support: built from trunk (which means this isn't any sort of official armbian build) For support you really need to go to the company that you bought this from

You would also need to rollback all the patches that armbian applies to the point in time that Armbian built with that particular kernel version. And likely all the outside repositories that Armbian pulls in that have source code for the various drivers and other code that is also built into the kernel.

moved to the Pine A64 forum.

The rk322x is a 32bit CPU, so it can't run 64bit code

Generally debugging is done through the UART connector: https://debug.armbian.de/

I would first suggest that you read this post: That may give you lots of reasons why you shouldn't depending on what your goals are. Installing armbian on a TV Box depends on the TV Box. Each CPU has differing levels of support (from none to fairly well supported in mainline linux). And then given there are hundreds of different TV Boxes, each will have different sets of working/non-working features depending on a variety of factors. As far as supporting a USB audio device, it shouldn't be any different than support for the device on any other linux platform/distribution. On Armbian you may need to install the linux-firmware-full package to get the driver support as by default Armbian ships with a slimed down set of firmware support.

This would be very very hard. Would likely take years and would likely never achieve full functionality. If you have access to the source code for the firmware that comes on the device you would have a chance.