mmss

A test version of the image Armbian for TV boxes on the basis of RK3328. Tested on MVR9
http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/653167-bqeel-mvr9-rk3328-quad-core-64bit-cortex-a53-android-7-2-16gb-2-4ghz-wifi-bt4
 
All basic functions work. For running. Download. Unpack. To record on the SD card. Connect the SD card to TV box, connect a keyboard and mouse. To turn the power on the TV box. The system should start within 2-3 minutes. You must perform the initial configuration of Armbian.

https://yadi.sk/d/DSO6euzB3ahemo
 
https://mega.nz/#F!zoZywCTQ!9sNfXIAB3m_DyLl5I8P94w
 
The system of choosing the correct dtb has changed.
Please note, now it should be done on a different principle (files do not need to be copied).
To select the desired dtb, you need to change the line in the text file "/extlinux/extlinux.conf". In the line "FDT" you need to change the name of the file that the system will use at startup. The list of available files (names to specify in the configuration) can be found in the "dtb"directory. If you do not know exactly what file you need , you can enter all available names in turn and check the operation of the system. In accordance with this, the system installation script in eMMC has been changed. The steps to install the system on the eMMC remain the same.
 
Added a utility to full backup and restore the entire eMMC "ddbr". Checked mode the backup MVR9. Now if you try to check the recovery mode.
 
The order of installation in eMMC.
 
1. Download, unzip and burn the image to SD card.
2. Start Armbian on the TV box and perform the initial setup of the system.
3. If the system works correctly and you are satisfied, run the utility "ddbr" and create a full backup of eMMC (this is a prerequisite).
4. Rename the file "/boot/mvr9-uboot.img" in "/boot/uboot.img".
5. Run as user "root" script "/boot/create-mbr-linux.sh"
6. To run the script "/root/install.sh"
 
Pay attention to the correct operation of the installation procedure need to comply strictly with the order of the steps.

Yes, in order to build without any problems (the fact is that the download from openlinux.amlogic.com is constantly broken), you need to use any tool with the ability to download the following packages of large sizes:
http://openlinux.amlogic.com:8000/deploy/CodeSourcery.tar.gz
http://openlinux.amlogic.com:8000/deploy/gcc-linaro-aarch64-none-elf-4.8-2013.11_linux.tar
http://openlinux.amlogic.com:8000/deploy/arc-4.8-amlogic-20130904-r2.tar.gz
And put them in the folder:
~/buildroot-openlinux-20170310/buildroot/dl
 

RTL8723BS is used on the Tinkerboard (also used on Pine64 or NextThing's CHIP) so all that's needed is throwing in a patch for the driver, adjusting DT and adding this to the board's config:
MODULES="hci_uart rfcomm hidp 8723bs"  

Openlinux.amlogic finally laid out the buildroot buildroot-openlinux-20170310.tar.gz  (S912 S905X S905 S905D S812 S805 S802), size 1.8G
 
 
http://openlinux.amlogic.com:8000/download/ARM/filesystem/

No need.

And another RK3288 device, maybe doing a few things better (eg. barrel plug for DC-IN and not crappy Micro USB, no internal USB hub, mounting holes for large heatsink):
 

 
 
 
http://linksprite.com/wiki/index.php5?title=PcDuino9#Hardware_specifications 
 
Well, my last attempt to deal with Linksprite's software was shocking

The new backup/restore script is ready and tested.
Not a new script really, just some usefull additions.
Some proof here
You can download it from here
All the changes are in the script's comments as usual.
Hope it helps.

Hey all,
I've been using Allwinner boards for the last couple of years and Armbian+forums have made this a workable thing that I promote to my friends as being The Way To Go instead of being a big fat waste of time. 
Igor + Tkaiser (and anyone else forgive me if I didn't give you a shout) - You fucking rock.  You really do; you've all provided amazing amounts of support for multiple kernels and userspaces and in the face of (at least) bullshit from the chip vendors, yet you are absolutely crucial to them being taken seriously.
The work from Armbian has (for me) made the difference between BananaPi, OrangePi, etc all being an unusable washout of #ShitDidn'tWork, to being something I am excited to build into things and personally promote.
 
Igor, Tkaiser; I've never met you but your work speaks for itself; you give a shit and you keep giving and shit and THANK YOU FOR THAT.
I just donated you some $. If you're still reading this and you're using their work, you might think about doing same.   FWIW; what turned my head is seeing Igor and crew putting _years_ of work into this. 
 
Anyway, much, much, much appreciated. From one to another; good job.
DrTune

Image update 20170302. Now, all the images should work the procedure for installing to the internal memory. To use setup, you must consider a number of nuances. 1. Before installation we strongly recommend to do a full backup of the internal memory (e.g. team dd_backup_x) and move the copy to another storage medium (e.g. on a PC). 2. Be sure to check all devices (wifi, sound etc etch). 3. If all the required works when run from external media, you can start the installation. To start the terminal. To switch to the superuser "root" to execute the command "su -" (su "space", "minus"). Run as root the command "./install.sh" . The procedure is not fast, as there is a complete copy of the operating system from external media in memory (eMMC). Notice for owners of TV boxes with 8 GB of eMMC. When you install the desktop versions (MATE and XFCE) TO START the installation, optimize system. To reduce the amount of programs installed for example to uninstall office packages. What would be the size occupied by the system on external drive was less of the size of the internal memory (partition /dev/data). By default , desktop take more seats than the existing partition in the internal memory (/dev/data). Therefore, the system will fail to start.

Yesterday entangled and trying things I loaded .
I gave it to try to install it on a SSD Corsair 32g external Sata 2 gives me better data in reading and writing than the usb pendriver  3.0 USB and it works without problem in Q912 , in case anyone is interested.
A greeting.

Update.
I think I found the cause of the fall core at a temperature of 70 degrees. In the new test image (Test 20170228) is fixed. Please check the system behavior under load , when the temperature rises to 70-75 degrees.

I hope you like the upgrade, which was done on urgent notice due to database failure and we started from this morning's backup. We apologise for some deleted posts and users, wrong settings and possible bugs.

Since our previous forum was 5-6 years old, upgrade is tremendous but we will try to keep it similar on function level. There was a plan for redesign but this will be done once in the future.
 
Enjoy! 

Information in this topic is very outdated see this topic.