ARMBIAN for Amlogic S905 and S905X
28 28

1172 posts in this topic

Recommended Posts

Image works with SD cards and USB drives.
Regular firmware in the device is NOT CHANGED.
When you replace the dtb file can be run on any device with Amlogic chip S905 s905x s912
 
When you first start the system, the root user password is 1234
 
The minimum media size - 4 GB
 
 
 
Option how to start (Activation multi-boot).
 

****************************************** Manual run Systems ******************************************

Now all images Armbian and LE has all the files for activate the multi-boot. Anything in addition to download and copy to media is not required.

1. Download the desired image
2. Unpack
3. Record an image on the medium
4. to run Android
5. open the app "Update&Backup"
6. Select local update and an archive on removable media (aml_update.zip)
7. Run update
8. System twice to reboot and start running the system from external media.
9. If after 7-10 minutes on the monitor not to receive any messages on system startup. Turn off TV box and add in manual in the first partition (FAT) the file "dtb.img". On the media there is a directory dtb from where you can take the files and copy them to the root of the renaming of "dtb.img".

Need to pick up the option for the file system will run. Pay attention, after you add\change the dtb file, you need to try to run the system and waiting to run 7-10 minutes. If not happened, repeat with a different dtb file.


Attention !!!! On models with S802 S805 S812. Activation multi-boot is possible ONLY with SD card (activation of the USB stick is NOT WORKING). After a one-time activation procedure is multi-boot, run a variety of systems is possible from ANY storage media (SD cards and USB storage devices).

http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/606133-linux-images-for-s802-s805-s812-s905-s905x-s912-sd-usb-emmc
 

 

************************************************** ************************************************** *******

 

The choice of shell to start (Mate\XFCE or KODI).

 

On the screen enter username and password (in lightdm) in the upper right corner of the screen there is a menu where you choose which GUI to run. The list will be three items (two rows with kodi) and the last line mate. Select mate (something opposite mate was the point), then enter the username and password. The system remembers the last selected mode. If at the next login or what not to choose in this menu, system at the entrance will trigger the option that was turning off in the previous session.

 

 

Install to eMMC (NAND)

 

    To install Armbian in the internal memory, you must execute multiple commands. We strongly recommend TO PreRUN create a full backup of the entire contents of the internal memory. This will allow you to return to the current state of the firmware at any time. To create a complete backup you need to execute commands.

 

su -
(enter passwd root)
ddbr

 

The running tip backup script

 

After creating the backup, to install to internal memory (eMMC) of the command being executed
Pay attention, if you not are sure that you will be able to solve possible problems from the installation of the internal memory (eMMC), do NOT PERFORM these commands.

 

su -
(enter passwd root)
./install.sh

or

nand_sata_install

 

 

Setup HDMI out.

 

The configure script video output hdmi.sh reside in a directory on a FAT partition (on a running system, this partition is automatically mounted to the /boot directory). This script can be changed. To change the screen resolution from 720p to 1080p, you need to uncomment the line "#mode=1080p60hz" and comment out the line "mode=720p60hz". Similarly, you can change the color depth from the default 24 to 32 (bpp=24). Note that with 32 bit color significantly changes the desktop. In this script you can place the commands you want to run WebMin , Doker, ask line to run the USB port (if necessary), configure, sound card, etc.

 

On Wifi.

 

run as root user one of these commands in the terminal

An example command to load module “dhd” or “wifi_dummy”

 

modprobe dhd

 

or

 

modprobe wifi_dumm

 

After verification of the selected module, if everything is working correctly, you can add it to the autorun list (add string name of the module in the file /etc/modules).

 

 

Remote control.

 

Added support for remote control. To use it you need to add the correct file “remote.conf” in the /boot directory or /etc/amremote. By default, a part of the image includes several predefined files (in the /boot directory). To use it you need to rename one of the files in “remote.conf”. Additionally uploaded the site to the directory the deb package “amremote.deb” , which can be installed in the old system (do not download the whole image). After installing this package you need to run service “amlogic-remotecfg” and add (rename) the correct file 'remote.conf".

 

 

Additional information

http://forum.khadas.com/t/armbian-kodi-ubuntu-debian-for-sd-usb-emmc/825

 

 

 

Wiki
Information to enable multi-boot on the WiKi is outdated, use to activate the multi-boot description from this post in the beginning.

 

 Other versions of images with different Linux systems.

 

https://yadi.sk/d/5_32km_EsCV2A

Igor, Eng-Shien Wu and mmss like this

Share this post


Link to post
Share on other sites

Hi,

 

with the how-to from http://www.cnx-software.com/2015/12/06/how-to-run-headless-linux-on-amlogic-s905-devices-such-as-mini-mx-or-k1-plus/#it was possible to boot the Odroid C2 Image on a Mini M8S ( s905 2GB Ram).

 

The Mini M8S stock u-boot does not support CFGLOAD, so I had to change some parameter from the boot.ini to bring them to the ENV.

 

The Boot Priority is different from the Odroid C2, it will only check the EMMC, does someone knows if this is more a hardware or software configuration?

 

 

If someone has interest I will post a small how-to.

 

Thank you for your hard work for this open system.

 

br tpc010

balbes150 and Igor like this

Share this post


Link to post
Share on other sites

@tpc010 Please do, I bought this box precisely for this purpose. Thx @balbes150 for obviating the need for a USB/TTL cable!

Share this post


Link to post
Share on other sites

Thx.

​

I'm about to convert my MXQ PRO+ to Linux, which needs just the standard, automated method. Is M8s mini much different?

Share this post


Link to post
Share on other sites

you have to open the case and search for the UART connectors, the Mini M8S has easy accessible connectors, I fond Mini MX III PCB pictures there is a really hidden UART Port, and I didn't find a PCB Image for the MXQ Pro+, so you have to search for it.

Share this post


Link to post
Share on other sites

@tpc010 Have you tried adapting the automated method of changing the boot procedure using Android's "Update&Backup"? According to one user it already works on MXQ PRO+.

 

But yeah, I've got the cable and would love to try the dirty method on M8s :)

Share this post


Link to post
Share on other sites

No, I uses the how-to from cnx-software, but at the moment the manual way, I will automate it and describe how to change the right things, so the Android will work and if you boot with a SD card it will boot from this.

 

Important is, the cable have to be 3,3 Volt like for the raspberry pi, so I use a converter with an CP2102, this is 3,3 and 5V tolerant. The Odroid UART Kit has a CP2104 with 1,8 to 3,3 Volt http://www.hardkernel.com/main/products/prdt_info.php?g_code=G134111883934.

Share this post


Link to post
Share on other sites

Hi,

 

with the how-to from http://www.cnx-software.com/2015/12/06/how-to-run-headless-linux-on-amlogic-s905-devices-such-as-mini-mx-or-k1-plus/#it was possible to boot the Odroid C2 Image on a Mini M8S ( s905 2GB Ram).

 

The Mini M8S stock u-boot does not support CFGLOAD, so I had to change some parameter from the boot.ini to bring them to the ENV.

 

The Boot Priority is different from the Odroid C2, it will only check the EMMC, does someone knows if this is more a hardware or software configuration?

 

 

If someone has interest I will post a small how-to.

 

Thank you for your hard work for this open system.

 

br tpc010

 

In C2 use your Odroid u-boot, which added to the boot.ini as a startup script. You can use another option that uses standard features of u-boot. The script for the command autoscr. Not a lot of details can be seen here.

 

http://amlinuxmedia.com/forum/index.php?topic=223.msg2117#msg2117

tpc010 likes this

Share this post


Link to post
Share on other sites

@balbes150 About the yandex hosting service - I'm unable to download anything, neither with Chromium nor with Firefox. Does the service require any particular cookie or javascript settings?

Share this post


Link to post
Share on other sites

@Shimon

On the right side, click on the post-1228-0-55289400-1466698800_thumb.png

:)

 

And this is the uart-serial port for the beelink m18 (same as mx64)

 

post-1228-0-54081100-1466698896_thumb.jpg

Share this post


Link to post
Share on other sites

E@Fritz LOL! That's exactly what I meant  - the button causes some browser javascript activity but the download never starts. (and the button remains greyed)

​

​EDIT:

​

post-1511-0-76362000-1467073730_thumb.jpg

Share this post


Link to post
Share on other sites

@Shimon
What do you need?
You can download it from https://github.com/150balbes/Amlogic_s905/tree/master/script/S905_UBOOT/s905_uboot its the same aml_autoscript as in yandex and the s905_uboot_multi_version_v2.zip contains the same aml_autoscript but in a update_uboot folder.
Probably this will update the u-boot environment to enable to boot from the SD card for those firmwares who not allows it.
If you prefer you can do this manualy from the u-boot console with the serial cable and setenv/saveenv commands (probably what @tpc010 means) or as suggested by @balbes150 use the "automatic" update procedure, don't know if this works for all firmwares.
The automatic procedure changes the u-boot environment. Once changed on reboot u-boot first checks if sd-card is present then it loads s905_autoscript from the the sd card and execute it.s905_autoscript loads uImage and ....
aml_autoscript and s905_autoscript are nothing more then a boot.scr (u-boot commands compiled with mkimage).
for converting a aml_autoscript.txt to a aml_autoscript if you need to make changes use mkimage as usual with boot.cmd vs. boot.scr:
mkimage -C none -A arm -T script -d aml_autoscript.txt aml_autoscript (same for s905_autoscript.txt vs. s905_autoscript)

That's it

:P
 

Share this post


Link to post
Share on other sites

I believe the Update&Backup procedure was successful on my MXQ Pro+, and it seems the device is trying to boot from SD or USB, but the image I used (Debian-Jessie64-1.0~RC2-2016-03-10-MXQPRO4K.img plus my own dtb) doesn't bring up anything on the screen. It probably stops booting after ca. 10 seconds (led stops flashing).

 

Any suggestions of a different minimal image? (2G card) How do I set 1280x1024 DVI resolution like on my Odroid?

Share this post


Link to post
Share on other sites
As far as I remember, this way when you first start trying to enlarge the second partition and erase the boot loader. Use caution with the launch of this image. In order to test You multiboot or not, I recommend to take other images.

 


What files are now on the first partition (the FAT partition) card ?

Share this post


Link to post
Share on other sites

Thanks for the suggestion @balbes150, I have been bitten by using USB port no.4 (otg) on MXQ PRO+.

 

Using other ports and your own universal Ubuntu image without resizing the ext4 partition (16G card), having added an appropriate dtb.img file, it works! Done the same on M8S mini, changing the dtb file and it also seems to work.

 

post-1511-0-99776800-1466804588_thumb.jpg

 

There's one snag, though. HDMI cable must NOT be connected during boot or my DVI/SXGA monitor never leaves low power mode. Is it a firmware problem? On my Odroid switching to HDMI mode produces broken picture but the monitor definitely switches on.

 

Thanks so much, this is so great!

 

post-1511-0-20764900-1466810299_thumb.jpg

Share this post


Link to post
Share on other sites

Yes, it is. It was rather lucky to discover booting the box headless made a difference cause I was about to draw wrong conclusions :)

Share this post


Link to post
Share on other sites
In Android, the monitor turns on normally ? I have several different consoles Amlogic S905. Several different adapter (VGA\HDMI not DVI) . Multiple monitors. Each connecting console\adapter\monitor everything works. Perhaps the reason for the peculiarities of the transition between the HDMI - to-DVI ?

Share this post


Link to post
Share on other sites

Definitely the problem is about HDMI -> DVI, but curiously, both Android systems boot just fine (incl. Google splash screen).

 

Is there a way to implement VESA modes from odroid's boot.ini? At the moment, both in Android and Linux, 720p doesn't display correctly (ca. 1/4 of the screen lies outside of the visible area).

Share this post


Link to post
Share on other sites

What is your monitor model ? What resolution and refresh rate it supports ? If you need other boot parameters (different from those that are in the current file s905_autoscript). The settings are easy to change. Clone the git to select or create a new text file with the necessary set of commands (with extension txt). Make a new script s905_autoscript (it's a binary file). Copy the new file instead.

Share this post


Link to post
Share on other sites

It's an LG Flatron, 1280x1024 @ 60 Hz DVI/VGA monitor. I'll try replacing the script according to your suggestion and report back. Any idea if this resolution could be enabled for Android?

Share this post


Link to post
Share on other sites

@balbes150 since you got c2 image run on MXQ PRO. What about docker and kodi. Cos MXQ PRO has the same s905 with c2. I guess docker and kodi should run on MXQ PRO too

Share this post


Link to post
Share on other sites

It's an LG Flatron, 1280x1024 @ 60 Hz DVI/VGA monitor. I'll try replacing the script according to your suggestion and report back. Any idea if this resolution could be enabled for Android?

I don't know Android. We can assume that Android is aimed at the TV settings. There is this screen resolution is not. You will need to get into codes video driver.

Share this post


Link to post
Share on other sites

@balbes150 since you got c2 image run on MXQ PRO. What about docker and kodi. Cos MXQ PRO has the same s905 with c2. I guess docker and kodi should run on MXQ PRO too

 
I use computer translation. Sorry, I may not understand Your question. You asked about KODI. What he had in mind ? KODI works on Android. Is there a version of Openelec that you can run on MXQ PRO. Please specify what "docker", give the link.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

28 28

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.