balbes150

If you have u-boot to eMMC, you don't need to write u-boot to SD. To run ArmbianTV from an SD card or USB drive, you just need to edit (boot.ini) on eMMC. Add these lines after the first line. for SD DROIDC2-UBOOT-CONFIG setenv dtbaddr 0x1000000 setenv loadaddr 0x20000000 fatload mmc 1 loadaddr boot.scr source loadaddr # Resolution Configuration # 'hdmimode' must be one of below to configure display resolution within for USB DROIDC2-UBOOT-CONFIG setenv dtbaddr 0x1000000 setenv loadaddr 0x20000000 usb start fatload usb 0 loadaddr boot.scr source loadaddr # Resolution Configuration # 'hdmimode' must be one of below to configure display resolution within for Sd + USB DROIDC2-UBOOT-CONFIG setenv dtbaddr 0x1000000 setenv loadaddr 0x20000000 usb start fatload usb 0 loadaddr boot.scr source loadaddr fatload mmc 1 loadaddr boot.scr source loadaddr # Resolution Configuration # 'hdmimode' must be one of below to configure display resolution within

You don't need to activate multi-upload, just add a couple of lines to this file to start it. Write what system you want to run , and I'll write what needs to be added to (boot.ini) on eMMC.

Show the contents of the file (boot.ini)

Show the output of the "printenv" and "help" commands from u-boot What result do you want to get (leave Android on eMMC and run other systems with SD\USB) ? Show the list of files on the first eMMC partition (which are used to run Android).

Less believe lies about 8K, this is a fraud. All that this device can do is decode 8K, but it will only show in 4K format

ver 20.05.4 (20200509)

Contact the hardware manufacturer to develop and source the correct DTB for the mainline kernel with support for all devices for your models.

Where did you get the image ? Why did you change the scripts ?

This is already done for the ArmbianTV version. Everything works in it at once, without manual operations and with the kernel 5.7

I don't have this equipment, I don't know what's wrong with it.

I wrote about Armbian. It all works (WiFi BT HDMI analog sound) and uses a common kernel with LE. Including installation on eMMC and installation on NVMe, and run system in USB

Immediately after starting u-boot from the SD card (about 5-10 seconds after power on), you can pull out the SD card. Then the script will only see eMMC. need the UART console log.

Does not have free drivers.

Update. Ver 20200506. add link MEGA https://mega.nz/folder/6tBSzIjK#DdVpxFuFp9_mtxJHSGiJ-w

No, I'm using a different kernel (from LE) with additional patches.

Hm. I have a Nanopc T4 with evo 970 and kernel 5.7 performs LE build (compilation with full load within 5-7 hours), I did not find any problems with stability.

The clock or priority of using cores may have been fixed.

Show the UART log.

In kernel 5.7 without u-boot changes, the startup time is fixed.

update

No, that's not possible. These are completely different kernel. New versions are released as soon as I have the opportunity. If you want, you can build the new version yourself (switch the kernel sources to the new Martin branch).

try all DTBS for rk3328 from the image Masking mode can only be used if the regular loader is blocked from any steps to launch from external media (SD card). In other cases, this is a bad decision. Specifically for the A5X, there is no blocking and for proper operation, you only need to select a dtb for the u-boot build with a full launch without any masking mode. This is easy to do if you have a sample device.

Older versions are not supported.

There are rules for this /delete-property/ pinctrl-0; /delete-property/ simple-audio-card,hp-det-gpio; or /delete-node/ https://developer.toradex.com/device-tree-customization