robertoenr

  • Content Count

    29
  • Joined

  • Last visited

About robertoenr

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi, I have a complete solution to the problem, at least in my case with TX3 Mini 2021 with s905w cpu, 1.6 board, and AP6330 wifi chip. Summary tips: Install an Android stock firmware with kernel 3.XX. It seems that usually on Android versions with this kernel the bootloader is older and looks "more compatible" with Armbian. Use Armbian 20.05.6 with kernel 5.7.2, and modify the install script, locate this part and update to this: parted -s "${DEV_EMMC}" mklabel msdos parted -s "${DEV_EMMC}" mkpart primary fat32 1000M 1512M parted -s "${DEV_EMMC}" mkpart primary ext4 1513M 100
  2. Hi @Joel Mercedes the last image you can install for Amlogic devices is the 20.10 with kernel 5.9.0 created by @balbes150 WIFI generally does not work on this cheap devices. You must use ethernet or a 1$ wifi-usb dongle. Anyway: What image did you install to get the kernel 5.9.7? Or did you update the kernel over 5.9.0? What DTB are you using?
  3. Partial solution to the problem! I've upgraded the stock firmware+bootloader to another more recent (Android 9 with kernel 3.14 oficial) with Amlogic USB Flash tool, checking the option "Erase bootloader". After this, I've booted completely Android. Next , I've booted Armbian, installed the WIFI, change the keyboard layout, timezone and hostname. And installed on eMMC. Now, with Armbian 20.10 Focal 5.9 installed on eMMC, I've restarted hundreds of times and the "black-screen-non-booting" problem has disappeared. So, if you don't have more official firmw
  4. On my TX3 Mini TV Box I always must boot armbian from USB. Activating multi-boot with toothpick doesn't make it boots from SD. Everytime I've installed Armbian, I've done from USB drive. Anyone has the same issue?
  5. The curious thing about the boot hang from eMMC is that, when it happens, you plug the USB with the bootable armbian and start with it once. After that, the issue is fixed. Next time you can boot without the USB and it starts OK from eMMC. It does until the issue happens again randomly other day. From the first time when the issue happen, the boot logo from manufacturer is replaced by a black screen, even when it's repaired with this method. The fact is that the chainloaded u-boot file in eMMC is the same on USB. And the bootloader+legacy u-boot remains the same at the begining on
  6. Yes, when running from SD/USB the issue is not present. It only fails when installing on eMMC
  7. Yes, initially usually works, but try to perform this actions: Make the internal WIFI works and connect to WIFI network. Mine is AP6330 wifi chip, so use these lines: sudo mv /lib/firmware/brcm/brcmfmac4330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt.old sudo ln -s /lib/firmware/brcm/brcmfmac-ap6330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt Try to reboot/shutdown several times (in my case sometimes the previous step is enough to reproduce the fail). If not perform more actions. Change the keyboard layout with armbian-config (mine to ES). Try to re
  8. Thank you do much for the advice! But since the "non-booting-black-screen" issue only happens once installed on eMMC, how can I test it by using SD/USB?
  9. Hi @hexdump @SteeMan I've tried the following u-boot files on my TX3 Mini (GXL S905W), downloaded from here, on the 20.10 Focal with 5.90 kernel last balbes image: gxl-u-boot.bin.gz. Uncompressed and renamed to "u-boot.ext". It starts OK from USB and looks the same version as packaged on the balbes image "2020.07-dirty (Jul 26 2020 - 13:24:26 +0200) hexdump-gxl". gxl-u-boot.bin-serial.gz. Uncompressed and renamed to "u-boot.ext". It starts OK from USB and this is the version showed "2020.07-dirty (Oct 24 2020 - 11:34:29 +0200) hexdump-gxl". I suppose that the gxl-u-boot.bin
  10. Sounds like a challenge! Any entry point or way to flash over the balbes image? I've seen that an some files"u-boot-s905", and "u-boot-s905x" and similar on the /boot partition. In my case renamed the second to "u-boot.ext". Should I must replace this over? Other doubt I have is if u-boot is located on the eMMC or on the SoC internal flash, because on the previous mentioned issue the boot logo sometimes dissappeared and the reboot/shutdown doesn't work, I think it could be related with u-boot.... Sorry about my ignorance, I'm trying Armbian and community to learn
  11. Hi @hexdump, your work is really interesting! Do you think the following issue could be solved with your new u-boot? Or it is a different problem? https://forum.armbian.com/topic/16837-problems-rebooting-amlogic-based-boxes-from-emmc Note: using Armbian 20.10 last from balbes for Amlogic with u-boot 2020.07 In case of "yes" any way to test it? I'm developer but not linux expert. Thanks in advance!
  12. More tests! Update 07/02/2021: TV Box is the same as described on https://forum.armbian.com/topic/16837-problems-rebooting-amlogic-based-boxes-from-emmc/?do=findComment&comment=117801 Some tests with recent and historical versions of Armbian from @balbes150 TEST 1. Try Armbian 20.02: Install Stock firmware on the TV Box with Amlogic USB Tool. After that, boot Android. Finally plug off the AC plug. Boot "Armbian_20.02.0-rc1.037_Aml-s9xxx_bionic_current_5.5.0-rc6_desktop_20200205.img" from USB drive using DTB "meson-gxl-s905w-tx3-mini.dtb".
  13. If your TX3 Mini with S905W is the 2021 version, as mine, you can try the following commands to make the wifi working: sudo mv /lib/firmware/brcm/brcmfmac4330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt.old sudo ln -s /lib/firmware/brcm/brcmfmac-ap6330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt After this, reboot your device. Hope it helps!
  14. Yes, there is no way to shudown the box with this command. Always is been rebooted. PD: My box is a TX3 Mini with S905W CPU
  15. Update 25/01/2021: The attempt described on previous post doesn't work. I have a new boot fail today. Method to reproduce the boot fail My method to reproduce the boot fail is to leave the TV Box on during almost 48h. Also I have a service that writes rows each second to a PostgreSQL database. After 48h of continuous work, I plug off the TV Box from wall. Then keep the TV Box off during almost 3h. When you plug on again... BOOM here is the fail. Fail cause suspect Taking from base that my TV Box is writing to eMMC during 48h of work and I plug off from th