Nofan Tasi

Add new version 20180817.
Add supports USB audio

Information in this topic is very outdated see this topic.
 
 
 
 
 
 
The start system in Coreelec is not compatible with LibreELECE  Armbian  etc. If you run coreelec on your TV box, you will no longer be able to run LE and Armbian normally until the full recovery of the standard firmware via the USB Burn Tool and the new activation of the universal multi-boot, which is used in all new systems.
 
 
The new version 5.55 of images. In this version, images with a single DE (XFCE) and a server in composition are as close as possible to the official versions. Version with a Mate and Icewm will probably be later and the gathering will be from another branch GIT (specially adapted for this DE). Since now all the images will be collected using the main kernel "4.1 x", have a common structure for the entire line of s9xxx and differ significantly in steps when configuring the system, I open a separate topic for this direction.
 
 
https://yadi.sk/d/pHxaRAs-tZiei
 
https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ
 
The primary steps to capture an image, activate multi-boot, and select a dtb file are common with the previous images.
 
 
Please note that starting with the version number version 20180928.
Major change. A new algorithm for the use of the dtb. Starting with this version, you no longer need to copy the dtb files and rename it to "dtb.img." In order to specify which dtb file to use, you need to edit the file 'uEnv.ini" (specify the desired file name for use dtb). This is a plain text file and can be easily edited. This change will make it easy to update the kernel from the "deb" file in the future. The new algorithm is now used in the eMMC system installation script.
 
Be sure to activate multi-boot using the new image. If multiboot previously activated is required to repeat activation using files in a new image.
 
Pay attention. To use the system with
u-boot-2015 (regular firmware Android), you need to edit the file "uEnv.ini"
 
When using
u-boot-2018, you need to edit the file "/extlinux/extlinux.conf"
 
 
For those who doubt or do not know what u-boot is used, you can specify the desired name in both files at the same time.
 
 
To change the used MAC address.
 
1 options
You can add the required parameter to the startup files (uEnv.ini and extlinux.conf). To do this, at the end of the line with the launch parameters, you need to add a parameter specifying the desired MAC address.
For example,
mac=xx:xx:xx:xx:xx 
or
ethaddr=xx:xx:xx:xx:xx
 
 
 
Old info multiboot
 
https://sourceforge.net/p/amlogic-s9xxx/code/ci/master/tree/
 
add info
 
https://medium.com/@vysmol/how-to-install-ubuntu-on-s905w-and-simular-tv-boxes-ru-eng-7aca3e1011a5
 
 
Install Armbian to eMMC.
1. Be sure to activate multi-boot using the new image. If multiboot previously activated is required to repeat activation using files in a new image.
2. Run Armbian from external media, run "ddbr" and create full backup eMMC.
3.  install Armbian on eMMC execute script “/root/install.sh”.
 
Please note, this is a test installation, which was tested only on a few models. Possible errors (Armbian will not boot) when you are working on unverified models which used non-standard distribution of partitions in the eMMC. Therefore, be sure to back up the "ddbr" utility before running the scripts.
 
 

Hello everybody!
I assembled a video player c2play, created by crashoverride, with the possibility of hardware decoding and rendering for a boxes on the S912 SOC. To achieve this, was used EGL and GLES libraries from Android, libhybris, libamcodec and ffmpeg with the support of the above library, as well kernel package with Mali driver for T820 GPU. All this was integrated into the firmware of Ubuntu Armbian 16.04 Mate Desktop, building by balbes150. You can download this firmware from here.
c2play perfectly playing, both local and network video H.264 and H.265 10-bit, checked up to 4K. Declared support of MP4, MKV and AVI containers.
A small help to managing the c2play from the keyboard:
ESC - to finish playing, LEFT - 30 sec. back, RIGHT - 30 sec. forward, DOWN - 10 min ahead, UP - 10 min. back. SPACE - pause.
To play video, open the terminal window or go to the virtual console (Ctrl-Alt-F1). enter the command: c2play <path to your video>. Or, assign c2play as the default application for the desired file type. More details here or here.
In the folder /opt are deb-packages with libhybris and kernel 3.14.29 with the driver Mali.
For those who want to build c2play itself, I bring links to resources on the github.
Libhybris: https://github.com/libhybris/libhybris.
Libamcodec: https://github.com/osmc/libamcodec.
FFMPEG: https://github.com/roman-rybalko/FFmpeg-aml.
c2play: https://github.com/OtherCrashOverride/c2play.
 

The official git armbian\build adds the tvboxes test branch. Everyone is invited to participate in the development , testing and maintenance of different models of TV boxes.
 
https://github.com/armbian/build/tree/tvboxes
 

Image update kernel 4.18 (catalog 5.44).
 
add tv-out  1440x900

Added the image of Armbian Bionic Mate. There are bugs in this image. You need to manually add the panel "Mate Bar". The Bionic-deb directory contains packages with two variants of KODI. For both versions you must install the packages aml and "aml-codec" and "aml-mali7". "aml-amremote" package is needed for remote control operation in KODI-17 version.

All the time (work on this is underway).
 
To All
Upgrade images 20180426 with kernel 4.17_rc2_-next.

Image update Armbian kernel next 4.17-rc1 20180420 (directory “test” on the website). Now in the mainline kernel works HDMI, USB, wired network.

Test image Debian + KODI-18.
 
https://yadi.sk/d/goZiDfto3UV8UU
 
To run KODI-18 , you need to perform additional configuration of the system.
1. you need to remove the package “pulseaudio”
2. Switch to the test repository (disable all other repositories and enable "test" in the sourceslist file). Then install a new version of libc6-2.27 from the test repository).
After these steps, you can use KODI-18 as usual.

In this survey discussed the use of u-boot that goes into the composition of the image Armbian, which is recorded on the SD card. When i'm create an Armbian image, the build system automatically adds the u-boot image. This u-boot (from the SD card) is used to start the system only when there is no u-boot loader in the TV box itself or it is corrupted. In all other cases, u-boot is not used on the SD card. There are several variants of u-boot for different platforms (s905 s905x s912). On the SD card when building the image (in the image Armbian)  can only include one option. To use other options, you need to write it manually (replace the current one). Now, when i'm  create an image, it gets a variant of u-boot for s912. This option can only work on models with s912. Therefore, I want to exclude from the u-boot image. If the user needs (when he has a serious problem with his TV box, when the regular u-boot does not work from the internal memory), he will be able to download the desired option (just for his platform) and write it to the SD card.
 
 
In this embodiment, is used a regular u-boot from internal memory. This means your answer to question 2.

Image update Armbian 20180323 kernel 4.14.11 .
Works wired network, USB, monitor (you can change the screen resolution on the fly). The images are in the "test"directory.

Update image kernel 4.9.40 20180315

Yes that is my thoughts also, may be we are gona need help from @balbes150 ? to give us some hints about this ?

New image Armbian 20171211 with a light shell IceWM DE.

It is compatible with previous versions of the scripts and has additional functionality (additional scripts can be placed in a special section of "multiboot" in eMMC). New u-boot can be build from latest GIT for Armbian. It can collect yourself from the GIT sources from here.
 
https://github.com/150balbes/u-boot

I recently got some new SD cards. When try using them, I found a strange behavior of these SD cards. They allow you to create ONLY one partition on it. When you try to burn the image, the image is written correctly, no error messages. With this SD card, you can activate the multi-boot. But when I try to start the system or to verify the data in the second partition on the SD card, I discover that the partition is created but data is not available (section is blank, no file system). If a single partition (the whole size of the SD card), the data be read and written to the entire size of the SD card. So for all who have problems running from an SD card or Armbian Librelec, I recommend to check the data on the second partition, the Second partition should be mounted well and the data should be easy to read and enroll.

Update test image kernel 4.13.0-next_20170915.

Version update TEST kernel 4.13.0_next_20170907. Added support for sound for all models S905X and S912. Pay attention to one feature of the work of sound - on the desktop has to be set 1920x1080 resolution. Not clear to me yet why the sound only works in this screen resolution.
For some recent images to use these additions, you can only download the kernel and dtb files (deb packages are in the directory TEST\deb) to install in the existing system (don't forget to update the file "dtb.img" to a new version).

Thank you for your attention. Yes, I mean 4.13.0.
In images enabled sound via HDMI to s912 (and s905x). Work sound tested on a Tronsmart Vega S96 (s912). Sound works through HDMI on test files from the image. Once again - you need to have 1920x1080 resolution (you can go into desktop settings in the tools menu and select directly in the working system needs a permit).

Update TEST images  kernel 4.13.0-next_20170905. In these images there is USB support for S905X and S912.

New image 20170901  kernel 4.13.0-rc6 and next-4.13.0-rc7 for S905X.  Working USB.
 

New image 20170828  kernel 4.12.9.
In this way there is support for USB on the platform S905X. You can run the system from SD cards and USB flash drives. Changed the activation system monitor, now it is built into the kernel itself. To change the screen resolution, you need to use standard tools from control monitor on a desktop. The resolution changes on the fly (directly on desktop). Not working yet WiFi. There are problems with the dtb files (requires the edit and debug under different models). For s905x recommend to use a file meson-gxl-s905x-nexbox-a95x or meson-gxl-s905x-khadas-vim1. For the model s905 - meson-gxbb-odroidc2.

Perhaps in the future it will be. Now it is not.

Image Yocto with kernel 4.12 (for S905X).  (v20170825)
To download the image. Unzip. To record on the SD card. Rename the /boot partition file of the dtb to the "dtb.img". To download the script s905_autoscript. Add on the SD card in the /boot partition. On TV Boxing should be informed (with other images) is activated multiboot. Connect the SD card to TV box. To turn the power on. After running the screen is in hibernation (from your watch) for desktop display you have to press a key on the keyboard or moving the mouse.
 
https://yadi.sk/d/f5HsAL913HYksf
 
 
USB works in the kernel 4.12.9 (kernel source Neil Armstrong).

Version update to 5.32 (20170820).
In connection with the transition to a new version of an Assembly environment, there are different bugs (which are not yet discovered).