balbes150

@martinayotte Do you have the ability to do a simple check of one system on K2 ?

you can try activating the multi-upload manually. Execute these commands. usb start fatload usb 0 1020000 aml_autoscript autoscr 1020000

Yes, the MBR, when placing a u-boot on eMMC, is in the u-boot zone , but there are ways around this.

u-boot has a fixed size, and the current MBR partition table will be replaced with it ( with the loss of all data).

This file should be written to eMMC with the dd command . Or replace this file with the one located in the /root/boot/u-boot-s905 directory and perform a new installation.

File with the new u-boot for s905-eMMC, the size of the first partition increased to 500MB. https://yadi.sk/d/NGrJwf3SXi1boA

Launch from an external media GPARTED and resize it to fit your needs.

console UART command setenv mac yor_MAC saveenv

show fdisk -l

To run with eMMC, the name must be s905_autoscript. If you need to run Armbian from an SD card, you start the system from eMMC and rename /boot/s905_autoscript on eMMC to any name. After starting from the SD card, do not forget to return the name on eMMC to s905_autoscript, otherwise there will be no system startup from eMMC.

By the way, it will be interesting to check with, delete the FAT partition and resize EXT4 partition for the entire eMMC and check whether u-boot can work or not.

If you have everything working correctly, this is not necessary. The main thing is that on K2 this version works almost correctly with eMMC and will allow you to easily install Armbian in eMMC and run it fully without any SD cards.

Hmmm You have 2 GB, I have only1 GB of RAM on Telos . It's interesting why I don't correctly determine the RAM size.

Try creating links from /boot to the desired files in the mmc 0:2 root . Hmmm Why this address ? It is better to use addresses from a closer area. It is proven and guaranteed to work on s905 https://github.com/150balbes/Build-Armbian/blob/master/config/bootscripts/boot-aml-s912_ENV.cmd#L9

I have u-boot normally stops on the "space" key (pressed the key , hold it, turn on the power, u-boot stopped and allows you to execute any commands in the UART console)

An additional bug was detected when installing on S905 in eMMC. Starting Armbian from the SD card will stop working correctly. To work around it , you either need to start the system from USB, or rename the s905_autoscript file on eMMC (for the time of starting from the SD card).

Check which partitions were created on eMMC and what state they are in.

This topic is outdated , all relevant information in this topic.

@martinayotte How much RAM does u-boot show on your K2 ? Can you show the UART log of the u-boot start from eMMC ?

Test version of the image (20200314) for installation in eMMC on s905 chips with a 5.6 core . Please note that this is only a test version, which has a number of disadvantages. The amount of RAM available after installation will be 1 GB (including for systems launched from external media). After installation, you need to manually expand the ROOT_EMMC partition, after installation it will be approximately 8GB. There may be other bugs. I checked the installation mode on the Vega S95 Telos S905. My system starts normally from eMMC. To install it you need to run the script from the root user (install-aml-s905-emmc.sh).

You need to write this u-boot image to eMMC with a simple command dd. After recording, check the General launch of u-boot (control via the UART console). If it starts, write the last image of Armbian-TV 20200314 to USB (this will allow you to immediately check the possibility of starting systems from USB media), configure DTB and start the system from USB. After writing the new u-boot to eMMC, you will have an MBR table with two partitions that you can use to install any system in eMMC (for example, using a ready-made script install-aml-s905-emmc.sh from the Armbian-TV image). If you want, you can install your system in eMMC, but keep in mind that you will need a set of scripts from Armbian-TV to run it. https://yadi.sk/d/FieAroFgp9b-qQ

I may have found a solution to install the system in eMMC for s905. For verification, I need a "Guinea pig" ( a user who has K2 and an eMMC module).

for this core to work on aml, additional patches or processing with the mkimage utility are required (information is available on the forum in several topics). make Image dtbs -j 4

You do not configure the system correctly, you need to configure the dtb in the file (uEnv.txt). This file armbian_first_run.txt is not used and can be deleted .

In theory, the 3.10 core could work with NAND and you can try to manually install the system in NAND (with a bunch of complex manual openrations and if you have a UART console), but I have never checked this (I do not have such hardware). There is no General documentation for this, it is a creative process, perform steps , view the result and select the next step based on the result of the previous one. Yes, you can run it from an SD card, but you need a working DTB specifically for your model. If the TV box uses its own specific parameters and the available DTB is not suitable, you will have to create a DTB yourself. This is not possible, the main core does not support NAND. If you write the NAND driver yourself , then you can install it in NAND. As far as I know, these u-boot variants are not suitable for TV boxes. But I think the system itself can be tried to run. Take the CentOS image and adapt it to run on the TV box ( add the necessary scripts to run in universal multi -loading mode). I 've done this before for running ArchLinux and OpenSUSE, and it should work for Fedora as well .