balbes150

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.

Gathered a working version of the image armbian (console) for the s805. Checked on my existing Board with S805 (spot i5). The image starts and runs. Due to the lack of work on my Board USB connector, I was unable to test the USB flash drive. To use, you can write the image to the media, copy it to the root of the first (FAT) partition and rename "dtb.img" is needed for the Board file (from the directory dtb of the first partition of the written medium). Order of use 1. to activate your universal multiboot 2. to record an image on the medium 3. to correctly copy and rename on media suitable for Board dtb file. To build dtb files for other models, please provide to me either a dts file from need model, or provide a link to the firmware or to provide a working dtb file from the correct model. In the first stage, you can try to use the files in the dtb (don't forget to copy to the root of the FAT partition and rename to "dtb.img"). https://yadi.sk/d/DnCkh3KBvAFES Multiboot https://yadi.sk/d/c9kY4tuLuPF3Y p.s. Fixed the link to the multiboot

Thank you. When will be the result, which you can check, I'll write.

Update images. Included in the Docker. Autostart the Docker daemon is disabled. To enable you need to uncomment the line in /etc/vegas95_init.sh https://yadi.sk/d/pHxaRAs-tZiei For those who want to build their version. GIT source code for the Assembly. https://github.com/150balbes/lib

Thank you. Yes, this is what I need.

I'm going to check it out.

No, I haven't watched it yet. To the extent possible, I plan to integrate it into your git and build images.

On platforms S805 uses an older version of u-boot and organization of memory is different from s905. Therefore, the algorithms and commands to the external load will be different. I now analyze and test different options. I would be useful to see the output of "help" from Your consoles. What would determine which commands are available in all devices (something you can use).

Universal multiboot (using s905_autoscript) compatible with previous versions and can replace them. It is sufficient to add properly configured the script with the necessary commands in the old system images. Therefore, no conflict of distributions no. I don't recommend using the update script system aml_autoscript to download images in normal conditions. This script is not designed to load distributions, it is necessary for a single refresh data in the internal memory (settings u-boot). Pay attention that the aml_autoscript is a script that must be run once to activate the multi-boot. Further work on the uploading of images is prescribed in the working script s905_autoscript. Which is located on external media and can freely and repeatedly modified to obtain the desired result. These changes as does not affect the contents of the internal memory based on the contents of u-boot). Therefore, even if we assume a critical error in the contents of the external script (s905_), neither of which is not critical, pulled out the carrier and can free to fix it. Unlike the script, the old scheme (which is used to download still images OE LE) makes all the changes to the internal memory and strictly prescribes the same algorithm and file names to load. By default, ddBR prescribed static address 192.168.1.200. It is made specially that it was possible to know exactly the address of the system at the first system startup (something you could go in and change the settings on the right). By the way, to know the address of the system can then download the ddBR, log TV console and give the command "ip a".

If you activate a universal-boot, script s905_autoscript will work automatically. The order of activation can be viewed here . https://github.com/150balbes/Amlogic_s905/wiki/s905_multi_boot 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 By the way, the latest version of LE kszaq added the script s905_autoscript.

In these images there is no activation script multi-download. They need to be downloaded separately. The current version activation universal multi-boot here v_0.5 To record to the internal memory is NOT NECESSARY. These images are intended only for external drives. I was interested in how activated the monitor. Is there a activation monitor (HDMI) problem ? https://yadi.sk/d/XHEJwdLTsWJoH

With a multi-boot system from Alex without making significant changes to the way that Linux will not work. You can try to use a universal multiboot. If you collect the correct script (not difficult), which is responsible for system start, you can try to achieve system operation.

I have not yet S912. So this is just a guess. S912 has a different graphics core. At S905 is mali 450 , S912 mali 820MP3. Perhaps they are compatible from the bottom up, but need to check. Regarding Boxing at the link - what kind of price is suspiciously low. Can specifically with this model have problems ?

Try to run it on you media box this way. It is a system that can be used for full backup and restore the contents of the internal memory, do not pay attention to it (you can find instructions passwords and logins to manage through a terminal with an attached keyboard). Backup and restore you not need to do. I'm interested in how to run this kernel on Your equipment and will operate the monitor\TV. alt_ddBR_multidtb_v0_03_16GB__20160908.img https://yadi.sk/d/lSCHFhd0sYQWX

Hi I have already successfully tried to use zoneminder on NAS with ARMv5. I think s805 is possible to use zoneminder. Soon I should receive a sample TV box with S805 chip, then I'll be able to check it out. Armbian install it in internal memory. In manual mode it works. Need some time to test automatic procedures for installing to the internal memory.

You have a USB flash drive size from 16 GB or more ?

The commands in this script can be commented out. The first team is responsible for activating sound. The second is the launch of the Docker daemon. But how does Docker, if you try to run it after boot from terminal as root ? It seems has not been correctly executed the script the initial system configuration. Perhaps the media has a bad blocks. And You can try to burn it to another media and see how it works ?

Thanks for the clarification, now I understand (sorry, I use computer translation, so may not all understand correctly). Yes, it is possible to have the boot partition on the SD card, and the system on USB. To use this option (or Vice versa, the SD card ROOTFS , USB BOOT). You need to change the script by adding the command to enable SD and USB together (team "usb start" and "mmcinfo"). These commands tell u-boot to activate these systems at boot time. This will allow you to read their information and contact them. Speed USB lower SD cards (even the slowest SD cards). Especially low speed to record. Read USB for downloaded system at an acceptable level.

Have not tested the version of the image to run from removable media to S805. Are you interested ?

If possible, take a screenshot , how to look at the partitions on the USB drive in the gparted program. Then it will be easier to understand. To start you need to have two partitions 1. FAT (labeled "BOOT") 2. section with the system (labeled "ROOTFS"). Copy files to these partitions from the source SD card can regular MC as root. The use of "LABEL" in the mount points and the script just allows you to do copy in any media (which may be different UUID).

Make two images (console and desktop) to SD card or USB flash drive with pre-installed docker. https://yadi.sk/d/pHxaRAs-tZiei

For those who want to try out docker on a TV set-top boxes with Amlogic S905. There is a working version of the binary file : http://forum.odroid.com/viewtopic.php?f=144&t=22703 service.system.docker-7.0.104.aufs.zip Tested on Tronsmart Vega S95 Telos his way Armbian. When running manually all works. If there is interest, we can build a turnkey package or image. A screenshot from running on a media box container by connecting it to the PC. docker run -d -p 80:80 hypriot/rpi-busybox-httpd https://yadi.sk/d/hp1THH-xuXNrF

Hi. Sorry for the delay with the answer. 1. You don't use the activation of the multi-boot, so I renamed the script ? 2. Directories dtb files is a "legacy" copy of the profile. Not yet got around to put in order. 3. The ability to load the dtb file from the root directory need to ensure that in case of problems with the auto-retrieve, you can manually copy the file and use the image in this mode. 4. Frequency control will be included in the next version. 5. USB ports on some models you need to include an additional command (it's built into the firmware, so it works on Android). The topic on freaktabe you have details on this issue. How to enable the port. If you have any more questions, feel free to ask in PM and email (sometimes I may not immediately see messages in the forums).

Updated image, using the automatically load dtb file from the internal memory. After writing it to the media, you need to replace the script s905_autoscript the one to be on the website next to the image. To use the new script s905_autoscript, with the same images, you need to replace script and remove from the first partition (FAT) file of the dtb.img. Armbian_5.17_Vegas95_Debian_jessie_3.14.73_desktop_20160729.img.xz https://yadi.sk/d/pHxaRAs-tZiei This option can be used on any models. Copy the dtb file in the manual as previously required. But keep in mind that sometimes the dtb file from internal memory not operating properly (system not loaded). In these cases, you need to copy the first section finished the dtb file.img as you did previously.