balbes150

If you add on the SD card with LE this file, You will receive a run of images kszaq with the use of universal multi-boot. Ie can use images of LE and Linux. https://yadi.sk/d/tmcGzE2NuoozK

There is another option to get the files you need. When building image LE, You will have a directory with collected ready files and source code. In these subdirectories You can find the files you need. Do not spend the time to build the entire image, You can specify the build command, only the desired packages.

Describe more precisely what steps You are doing. Activate the multi-boot should be held on S905X same as S905. You can use the SD card (they are very naughty). S905 work fine with USB flash drives.

mdelThe correct command to UART minicom -D /dev/ttyUSB0 -b 115200 -8 If you can interrupt the start-up, the signal from the keyboard to the TV box is transmitted. If the text is displayed correctly, the contacts are connected correctly. The first time I see such behavior that would interrupt the start and then there was the reaction. You can show pictures as the connected contacts to the PCB and the module for UART. And it is desirable to see output at the moment of stopping the run. By the way, interruption of the run, you can do the "space" key, just press it repeatedly since the start of u-boot. What kind of system is used on a PC ? If you can, try to pull out of working system OE, the configuration of the kernel. dilligafThe activation script (aml_autoscript) multi-boot same for the entire line s805. v06 is a script to S905 (that's another architecture). It is not suitable for the s805. Describe more precisely what steps You are doing.

To support Wi-Fi maybe not enough firmware. You can try to copy to disk are all available to S905 (to take them from the image LE).

Added another script. It uses the value of screen resolution and color depth of the memory u-boot. These values in u-boot are installed from firmware Android. Thus, if in Android, set the resolution to 720 , then the strata Armbian will be used 720. If set to 1080 to 1080 to be used. Firefox need to rebuild under ARMv8. I still use midori for the web. There are other browsers.

I uploaded the two directories 720_24 and 1080_24. They are scripts for the two types of screen resolution. For those who have not is a normal system start, I recommend to try to use instead the script that is the default version of the file from the directory 720_24. Another try from the beginning to load the standard firmware (Android) to connect media, and select Android in mode restart (NOT shutdown). I found that on many consoles have changed the bootloader. When enabled, does not activate the monitor (video output) to u-boot, have to reboot, then the monitor turns on and the image Armbian normal start.

The update from a USB takes a long time, sometimes up to 10 minutes. At this time there is an active exchange and may stop responding. Keep in mind that when you first start the system, you need a lot of time to expand the second partition to the whole drive and create the initial settings. It may take a lot of time and need to logon under the root login, wait until you see the text about creating a swap partition. This is usually the final line in the log on screen when you first start. You have , in the end of the log "kernel panic". This is possible with the right parameters in the DTB. Try hq18 dtb from the dtb from the catalog.

Yes, the variables I see that all necessary settings are present. Here's a piece of fragment download from external media to S905. It doesn't matter what the other chip. When you start from external media should be a line indicating that the uploaded script s805_autoscript and lists the commands that are executed. If there are errors in the script, they the same will show that the command cannot be executed. In Your log I don't see any indication that the script is loaded. It is advisable to try to use a USB drive, they are usually slower, but better and more stable start. For tests they are better suited. Through what program You control the console UART ? In Linux you can use "minicom -D /dev/ttyUSB0 -b 115200" Bus Width: 4-bit reading s905_autoscript 618 bytes read in 4 ms (150.4 KiB/s) ## Executing script at 01020000 ########## cmd=setenv m "720p60hz" setenv mbpp "32" setenv bootargs "root=LABEL=rootfs rootwait rw console=ttyS0,115200n8 console=tty0 no_console_suspend hdmimode=${m} m_bpp=${mbpp} net.ifnames=0" setenv boot_start booti 0x11000000 0x13000000 0x1000000 if fatload mmc 0:1 0x13000000 uInitrd; then if fatload mmc 0:1 0x11000000 Image; then if fatload mmc 0:1 0x1000000 img.dtb; then run boot_start;fi;fi;fi; if fatload usb 0:1 0x13000000 uInitrd; then if fatload usb 0:1 0x11000000 Image; then if fatload usb 0:1 0x1000000 img.dtb; then run boot_start;fi;fi;fi; reading uInitrd 8559168 bytes read in 747 ms (10.9 MiB/s) reading Image 12812704 bytes read in 1110 ms (11 MiB/s) reading img.dtb 32991 bytes read in 7 ms (4.5 MiB/s) ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (uncompressed) Data Size: 8559104 Bytes = 8.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Amlogic multi-dtb tool Single dtb detected load dtb from 0x1000000 ...... ## Flattened Device Tree blob at 01000000 Booting using the fdt blob at 0x1000000 Loading Ramdisk to 73698000, end 73ec1a00 ... OK Loading Device Tree to 000000001fff4000, end 000000001ffff0de ... OK signature: fdt_instaboot: get header err Starting kernel ... uboot time: 6513208 us

You can try this option. To record to external media the version of Ubuntu that You have collected. To copy the dtb file from Your firmware to the media with the name "dtb.img" onto the FAT partition. To activate the multi-boot TV box. Try to start the system from external media. To include directly in the way of Your data (dtb and the kernel configuration), you need to make changes in build scripts.

In the Assembly LE , in the options specified. https://github.com/150balbes/LibreELEC.tv/blob/Amlogic-S905-kszaq/projects/S905/options # additional Firmware to use (dvb-firmware, misc-firmware, wlan-firmware) # Space separated list is supported, # e.g. FIRMWARE="dvb-firmware misc-firmware wlan-firmware" FIRMWARE="misc-firmware wlan-firmware dvb-firmware brcmfmac_sdio-firmware-aml rtl8723bs_bt" The description of the Assembly https://github.com/150balbes/LibreELEC.tv/tree/Amlogic-S905-kszaq/projects/S905/packages/linux-firmware

How have You organized multiboot ? In the log I don't see the activation script s805_autoscript. Which settings and which program (system) are You using for the UART ?

If You have a working system based on LE (which has WiFi). You can try to copy files and firmware from it.

Updated the images on the website. Added to the website image with simple system to create a full backup of the internal memory (ddBR) based on the console version Armbian + webmin. WebMin can be installed on any image independently. https://yadi.sk/d/DnCkh3KBvAFES P. S. I Propose to rename this topic "Armbian for Amlogic S805"

Added a few new images from Ubuntu. https://yadi.sk/d/5_32km_EsCV2A https://yadi.sk/d/pHxaRAs-tZiei

U-boot for the boards, there are no command "autosrc usb mmc emmc bootp" ? The tester, who does not know that it is happening in the system (which carriers and why they are used) ????? Better not to have such testing. About the pros and cons of LABEL. Suppose such a scenario. Recorded image on the SD card of 16 GB . Checked. Works. Decided to move on the USB flash drive of size 8 GB. When using LABEL. Simply copy all the directories and files (as is) to a new medium. And assign a LABEL. Made changes to the system during testing. Created archive. Then deployed on any medium, even smaller (considering the size of the files). Can be easily transferred to testing by other users of the entire system "as is" for any media. I do not impose. I just share information. By the way, if the console UART, write and debug the script - not difficult. When you work (if using) on other boards it is rarely necessary to edit (console UART is not needed). Enough to rule the working scripts, which defines all the features of the system startup (which you can change). This algorithm is already well established.

IMHO This is only theoretical reasoning. To start the system, it is enough to have a small, static (not changed) u-boot on any carrier (that supports the fee). Creating and debugging such a minimum bootloader (with source) not a difficult task. In normal use the Board user - use your (not limited) media may large capacity, fast and expensive media. Testing the second (separate) media (with a simple, small and cheap) with a predetermined and virtually unchangeable by the loader. To start the predefined script with possible media (flash drive, network, etc.). Survey \ activate predefined list of carriers (in order of priority) and look up the script with a predetermined name. Finds a script to it. His task is complete. This is the principle of the BIOS. And the scripts start the test images\system - can change forever. Loader itself and its variables are not changed (except the upgrade test system), and then resource it read-only. Perhaps I am mistaken, but as far as I remember - network support long been integrated into u-boot and is supported by all manufacturers boards (this is a common debugging tool and development). For testing and debugging the UUID is not the best solution, it greatly limits the possibility of a simple copy of the rootfs and other partitions on arbitrary media. This area is better suited LABEL. On the one hand is the uniqueness of the determined desired media, on the other - is easily managed and edited by conventional means.

Interesting to see the list of boards\models needed to participate in the testing (which must tested). IMHO Sorry, I may not know much and write nonsense regarding the features discussed in this topic boards\models. If you do not need to test specifically work with SD\eMMC. For tests does not necessarily need SD\emmc carriers in large numbers, they can replace the cheap USB flash drives or drives (separate partitions). One SD\eMMC will be needed to start the boot loader (if the Board is not able to boot from USB). Alternatively, you can use TFTP . U-boot is able to start the system from the network. Linux Live-CD (x86\amd64) USB stick with the configured TFTP and a set of test images\system (for arm\boards aarch64\models) for normal PC + microops to SD\eMMC with this TFTP configured bootloader.

I uploaded the new images. Try them. You need to try everything available in the catalog of dtb files (from all models). I have oddly enough, the i5 is better earned the console image file from hq18. When using native dtb files (from version) i5) was the problem. The system did not boot (had a kernel panic) with the native tether 1Gb, which runs Android. With dtb file 512MB the system was started and worked, but was determined only 350 MB of memory. And file from hq18, it works correctly, the memory was 790 MB and the system was stably run. By the way, I downloaded the desktop Ubuntu image. It works for me, there is a Desk XFCE , but the colors are not correct and can not see the cursor. Have to move the fly at random. I downloaded the firmware for the MXQ S85 and soon will try to get all dtb files and I'll post it on the website.

If Your version of OE has a utility fw_setenv all easy to solve, using one add env variable in u-boot. If utilities do not, all can be realized through the creation of the file. IMHO you should start with debugging separate options systems. After You check each system individually. Enough to combine their logical connection check the value of a variable or file exists. An example implementation of the selective startup of different systems depending on the value of a variable (which is set of OE) can be viewed here. By the way, to start (with serial key check values of variables) is not limited number of systems and not only with the internal memory and external media. Sorry for my English, I use machine translation. If not clear, write, I will try to describe in detail with examples. https://github.com/150balbes/Amlogic_s905/blob/master/script/S905_LIBREELEC/s905_libreelec_v7/s905_autoscript.txt https://github.com/150balbes/LibreELEC.tv/blob/Amlogic-S905-kszaq/projects/S905/filesystem/usr/sbin/rebootfromrecovery https://github.com/150balbes/LibreELEC.tv/blob/Amlogic-S905-kszaq/projects/S905/filesystem/usr/sbin/rebootfromrecovery

In your u-boot does not support file upload command (ext4load) of partition ext4 ?

Share the link to Your dtb file. It is necessary to try to collect all variant dtb file based on the Assembly environment and the kernel sources , which in Armbian. Maybe it will help to start the system. It is advisable to try all the dtb files that are in the directory and on the website. Sometimes it helps initial boot (not all hardware will work, but the main thing is to find a basic piece of data). In the last images added two scripts to perform a full backup and restore the entire internal memory (ddBR). It is convenient to use in front of various experiments with the contents of the internal memory.

This is a common mistake. Usually it is associated with a media error. Sometimes this error is related to a bad download of the file (error when downloading). First check how to prepare the media. Must be FAT system. The media is better to have no more than 2 GB. For the S805 is better to use SD card, because in many models of u-boot S805 not working install updates from a USB. They can only use the SD card activate the multi-boot. Alternatively, download the special image at the link. Burn it to the media. To replace the files on those that are designed to S805. PLEASE NOTE the files in the original image state is designed to S905 they need to replace the files for the S805. https://yadi.sk/d/FcNyXwmhurN2D Added in GIT a few new dtb files for multiple models (which found in free access). Please to those who have the opportunity to check their performance on these models. MXQ HD180 M808 M201. https://github.com/150balbes/Amlogic_s905/tree/master/dtb_file/S805

Upload a revised version. Fixed extension section in the firstrun script. Armbian_5.17_Vegas85_Debian_jessie_3.10.102_20160915.img

Method using the standard firmware. This procedure needs to be performed once. 1. to format the SD card to FAT 2. to download two of the file aml_autoscript aml_autoscript.zip 3. to record these files on a prepared map 4. start TV box 5. to connect the prepared map (with two files) 6. open the installed app Update&Backup 7. to choose as a local update files on the SD card (aml_autoscript.zip) 8. Run update 9, TV box to reboot two times and again will load the regular firmware. 10. pull the card From that moment on the TV console activated universal multiboot and you can run it on a different system from external media. The internal system remains unchanged and no it does not suffer from this. To use the image Armbian. 1. Download image 2. Write him a special program on the carrier 3. copy and rename "dtb.img" in the root of the FAT partition media that is appropriate for your set-top box dtb file (from the directory of the first partition dtb prepared media). At the moment there are three files, you can try all three files. If the system fails to boot, you need to collect suitable for your TV box new dtb file. For this you need to send me the relevant information. On these links, you can read the details on how you can capture the image on the medium. http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s905/tronsmart-ac/firmware-roms-tools-at/565449-running-linux-from-sd-card-or-usb-flash-drive-using-balbes150-method-and-files If you have any questions, feel free to ask questions, I will try to explain.