SteeMan

@Zsolt Tóth That is not an Armbian build. You should request help from where you got that code. From the devmfc readme: "What are these images NOT...They are NOT Armbian and are NOT Armbian based"

What Armbian image are you using?

These minimal/iot images are intended for expert usage and don't contain all packages you might need or want. It is assumed users of these images know what they are doing to review logs and install things that they might need.

That is new in terms of Amlogic support in mainline kernel 🙂

That is a relatively new soc. It may be a couple of years (if ever since mainline support for amlogic CPUs is poor and getting worse as most open source developers have gravitated to supporting rockchip socs) before you have something that will work for that soc.

You previously talked about this command. What is it? It appears you have run or installed something that is causing changes to your extlinux.conf file. You need to restore the contents of that file to the version that was originally installed. In your last log, in addition to your image and uinitrd being wrong, your append line is also wrong.

What do you mean by this? How are you updating the kernel? It looks like something is corrupting the contents of your extlinux.conf file.

It could be as simple as using the latest uboot source code. From you log, it looks like the shipped binaries are using uboot 2023.10.

The key thing to note is that this is a u-boot issue as it isn't even getting to the point of starting the linux kernel. The aml-s9xx-box /boot directory has instructions on how the various chainloaded uboots are built. So you can look at the uboot source code and test different things in the s905x3 uboot you are using.

Are you following the instructions on the download page? Tell us what steps you did for your install.

In your log you will see: Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 1: Armbian 25.5.0-trunk.61 bookworm 6.12.13-current-meson64 Retrieving file: /vmlinuz-6.12.13-current-meson64 Skipping l0 for failure retrieving kernel 2: Armbian 25.5.0-trunk.61 bookworm 6.12.13-current-meson64 (rescue target) Retrieving file: /vmlinuz-6.12.13-current-meson64 Skipping l0r for failure retrieving kernel EXTLINUX FAILED: continuing... 78003 bytes read in 43 ms (1.7 MiB/s) Card did not respond to voltage select! : -110 Card did not respond to voltage select! : -110 This means that uboot can't reliably read your media.

moved to TV Box forums

This design decision has been around from the early days of Armbian and SBC's. If you think about Armbian as a firmware for your board instead of a general operating system like on your PC, that makes some sense as to why originally that would have made the most sense (you install new firmwares, you don't upgrade them in place). Also, all those early boards were limited on the amount of internal emmc storage they may have had, if any, and SD cards were also much smaller in storage capacity at that time. So wasting space with an entire extra kernel wasn't really an option. Now move forward 10 years and most of those limitations are lessened. So it could be supported today for most build targets. But the current approach would likely still be needed for some boards. So while it would be feasible to support having multiple kernels installed it would take a lot of effort to implement (across all the different booting scenarios, u-boot scripts, extlinux, uefi, etc). Also in many of these scenarios it doesn't really help as you need an interactive boot (i.e. with hdmi and keyboard/mouse input) to present a menu to the user to select an alternate boot target, and that interactive boot environment isn't common on SBC's (unlike the PC world). If you have to solder and hookup a USB-UART connector to monitor the debug output to be able to switch your boot kernel, is that better/easier then just popping in a different SD card? So ultimately like a lot in the open source world, this change while possible, hasn't attracted the interest/need for any developer out there to want to undertake this effort. Which leads me to the inevitable next comment, PRs are always welcome for contributions to the project 🙂 (Personally this is something I would also like to see, but in looking into the effort it would take, I know I personally don't have the time to implement, and the workarounds are good enough for me)

I don't think you got the substance of Igor's comments. This board isn't supported by Armbian. It is community supported, which mostly means that is is unsupported unless someone cares enough to submit a PR to make any change/fix/improvements. You saying this or that needs to be done, makes no difference as no one is around to do that work. If you want something improved you either need to submit a PR yourself or pay to have someone do it. Or wait until someone else finds it important enough to do it for you, which may be never.

yes those pins should be the debug uart. I don't have a recommendation on one, but two things to think about, 1) boards will generally either be 3.3v or 5v (so both types exist, although many allow you to switch the voltage with a jumper), if you don't know your voltage start with 3.3v. Then some boards (Rockchip CPUs have a high baud rate that some adapters don't support), which wouldn't be an issue for this amlogic box, but if you might use it in the future for a rockchip based board you might want to make sure yours is capable of those higher speeds.

No. USB isn't available as the board is booting. You need the debug output which early in the boot process is only sent to the debug uart

You we will need to find the debug uart pins on your board, solder connectors to them and connect the usb-uart connector. Some boards come with pins already soldered in place but most don't. It can be difficult to sometimes find the right points as they may not be labeled well.

Booting armbian from SD on this box? Or something else. The way the armbian build works for these amlogic TV boxes is specifically designed to boot from the android uboot on emmc.

The boot process uses the native android uboot on emmc. I have no idea what uboot OSMC uses and if it is compatible with the mechanism that armbian uses to chain from the native uboot to the u-boot.ext. To understand what is happening during the boot you will need to hookup a usb-uart connector to the board and capture the uboot output.

Never heard of this command. What does it do? What do you mean by add it to the boot choice? Have you read and followed the instructions on this site to install to emmc?

What do you mean by that. Please be specific as I don't know what you are referring to.

If you have the android image and the proper amlogic tools, yes.

Never tried an emmc install with CE installed. I have no idea if that will work or not.

Try booting from an SD card, and then try to boot from emmc. I have one box that won't reboot without first doing a boot from SD. But after a boot from an SD card, then it will boot from EMMC correctly.

When you say "doesn't work as expected", what exactly isn't working?