Jump to content

SteeMan

Moderators
  • Posts

    1841
  • Joined

  • Last visited

Posts posted by SteeMan

  1. The only way to recover is to restore Android.  The armbian builds use the Android uboot environment on emmc to boot both from SD as well as emmc.  So once you copied to emmc which somehow corrupted your boot environment (which is why the instructions say to be cautious and copy to emmc at your own risk), you can't boot anything.  So the only recovery is to reflash Android and start over.

  2. Try all the USB ports on the box (if there are more than one, only one will work).  Also try with and without pressing the reset button while you are connecting.  I've sometimes had to try a few times to get the right timing/combination.  Bit I don't have your specific box so I can only provide general feedback.

     

  3. For amlogic based boxes, you will need a usba to usba cable and use the amlogic USB Burning tool to flash an original Android firmware image for your box.  You can also hookup a usb-uart connector to your box and get the uboot output which might shed some light on what is going wrong with your boot.

     

  4. On 2/6/2025 at 7:58 AM, SteeMan said:

    u-boot-refresh

    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.

  5. 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.

  6. 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)

  7. 16 minutes ago, Andrius Vainorius said:

    And also Debian Cinnamon 6.12 has no hw support so you can remove Mesa/vpu tag

    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.

     

  8. 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.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines