balbes150

Test image for rk3188
Download, unpack and burn the ArmbianTV image to your SD card.
Connect to the TV box and turn on the power. The system will start automatically.
 
https://yadi.sk/d/YXA09tNfyRhDIw

parametr.img
 
votparametr.img

Test image for rk3188
Download, unpack and burn the ArmbianTV image to your SD card.
Connect to the TV box and turn on the power. The system will start automatically.
 
https://yadi.sk/d/YXA09tNfyRhDIw

Good news. Using sources with patches from knaerzche,  it was possible to get the initial launch of the kernel 5 with an HDMI output for rk3188 (Ugoos UT2). Now I can see what messages the kernel gives out and I can move on, add the necessary options and Initrd for a full start of the system.
 

Good news. It turned out to fully launch Armbian with core 5 on Ugoos UT2 (rk3188) from an SD card. 
 
Question. Are there users with models running on the rk3188 platform ?

My images use u-boot-2020 (for rk3288), it only works if there is no u-boot in eMMC\NAND. Rk3188 needs its own version of u-boot-2020 (I don't have this option yet). But there is also good news, when performing a number of manual steps, it turned out to run the core 5 on rk3188 (but without HDMI output, network, etc.), there is only the inclusion of indicators and reaction to the combination CNTR+ALT+DEL (the system reboots). 
 
 
To all
New image 20200623-dev kernel 5.8-rc2

Ver 20200623-dev kernel 5.8-rc2

To make it more clear, can add the CPU type discussed here to the topic title.

Please contact the administration to move this topic to the TV box section. I would like to (as far as possible) continue this direction (native Armbian build directly on ARM devices). For skeptics. Recently, I completely moved the LivreELEC build to the ARM platform (i.e. the entire process of creating LE images and Addons now takes place on ARM rk3399\s922x devices). My dream is (perhaps) to try to transfer the ArmbianTV build completely to the ARM platform and get rid of the x86 dependency.

Please contact the administration to move this topic to the TV box section. I would like to (as far as possible) continue this direction (native Armbian build directly on ARM devices). For skeptics. Recently, I completely moved the LivreELEC build to the ARM platform (i.e. the entire process of creating LE images and Addons now takes place on ARM rk3399\s922x devices). My dream is (perhaps) to try to transfer the ArmbianTV build completely to the ARM platform and get rid of the x86 dependency.

Hello balbes150 , I do have a rkm802IV ( the 'old' model )stick , I can boot the old linuxium linux image from sd ,
(from this post http://www.linuxium.com.au/how-tos/tastytreats ) . Because it's almost 10 years ago my memory of
what I read and did has become a bit rusty so I downloaded this image again and burned it to sd using balenaEtcher on Debian
and indeed it booted immediately. I tried a few of your 32 images the same way ,burned them to sd but they won't boot .
( Armbian_20.05.6_Arm-32_focal_current_5.4.43_desktop_20200604.img and Armbian_20.05.6_Arm-32_focal_current_5.7.2_desktop_20200613.img ) ,the system boots to android nand .Then I tried to flash the bootloader from your link
using rkAndroidtool under windows 10 ,but that was refused by the program .(check chip not ok) , well .it's a rk3188 so it refuses a
rk3288 loader . In the past I read a lot of linuxium's posts and he had many solutions for booting . Not all these posts exist anymore ,
google+ has dissappeared so it's a bit tricky finding everything back .The next few days I'll try to refresh my knowledge .(I don't
know what happened here but i've gone Italic !!)

Ethernet works: http://ix.io/2pla
 

I did a quick hack (stupid value replacement
TEXT_OFFSET 
0x0 -> 0x01080000
 

Ver 20200616-dev
"clean" kernel (no patch) 5.8-rc1

1. I don't owe anything.
2. if you Want to get detailed documentation and dedicated resources for posting materials for download, pay 5000 to donate Armbian.
3. I have a very negative attitude to those who use someone else's development for free (in which a lot of work\money\time of different people is invested), absolutely do not help this project in any way and at the same time make claims.

1. I don't owe anything.
2. if you Want to get detailed documentation and dedicated resources for posting materials for download, pay 5000 to donate Armbian.
3. I have a very negative attitude to those who use someone else's development for free (in which a lot of work\money\time of different people is invested), absolutely do not help this project in any way and at the same time make claims.

Version 20200612.
Kernel 5.7.2.
updated the build system, supported build on aarch64 Focal.

Version 20200612.
Kernel 5.7.2.
updated the build system, supported build on aarch64 Focal.

Checked the transition from Bionic to Focal with the command (do-release-upgrade). The system was updated from the beginning to Eoan and then upgraded to Focal. Please note that this is a potentially dangerous procedure and you must first save all your valuable data.

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.
 
Questions that do not specify exact details (the exact image version, TV box model, detailed steps that were performed for DTB settings, and so on) will be ignored and deleted.
 
For all. I don't support s905x3. I don't have this equipment. All messages about this platform will be transferred to another topic. What works or doesn't work from this equipment - I don't know. I do not give any answers or comments on the s905x3 chip.
 
The build and publication of unified test images with a common core for the Rockchip Amlogic Allwinner platform begins.
 
Y-disk
 
https://yadi.sk/d/_rQgn_FosYuW0g
 
MEGA
 
https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ
 
 
How to run these images on the Amlogic platform .
Now all images Armbian and LE has all the files for activate the multi-boot. Anything addition to download and copy to media is not required.
 
1. Download the image for your device
2. Unpack
3. Burn the image on the medium
4. Configure in the file (uEnv.txt) launch parameters for the desired platform and model (uncomment the desired lines and comment out or delete unused ones)
 
If universal multi-upload has not yet been activated on this device, you need to activate it once. There are several options for activating multi-loading.
 
option A
- Connect the prepared media to the device and turn on the power, boot into Android
- Open the app "Update&Backup"
- Click on "Select" local update and chose the file on the removable media aml_autoscript.zip
- Start "Update"
- System will reboot twice and start running the system from external media.
 
option B
-  try using the "toothpick method"
 
 
How to run these images on the Rockchip and Allwinner platform .
1. Download the image for your device
2. Unpack
3. Burn the image on the medium
4. Configure in the file (uEnv.txt) launch parameters for the desired platform and model (uncomment the desired lines and comment out or delete unused ones)
5. If your device does not support USB startup , you can only use SD cards and you need to add the correct u-boot to the SD card (for details on how to add it, see the text of this message)
6. Connect the prepared media to the device and turn on the power
 
Please note that the DTB configuration order has changed.
Now a single configuration method is used for all Rockchip Allwinner Amlogic platforms. The file (uEnv.txt) is used for configuration DTB all platforms. 
Now a single configuration method is used for all platforms, using the file (uEnv.txt). You need to edit this file to configure it. You need to uncomment the two lines that are responsible for your platform and specify the correct DTB for your model. If you use this image to run on the one platform, you can delete it from the settings file (uEnv.txt) strings from other platforms.
 
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.
 
Pay attention.
The installation algorithm in eMMC has changed. My recommend that you perform a clean installation in eMMC. Be sure to make a full backup of eMMC before installing it in eMMC.
The system installation scripts in eMMC have changed accordingly. If you have a system with eMMC core 5 installed on RK33xx, it is advisable to perform a clean installation in eMMC to upgrade to the new version. 
 
For the aw H6 platform, all scripts are already in the image (which have the ending aw). You need to rename the files with the replacement (remove the ".aw" ending).
 
Fix for correct color to G12 (Amlogic S905X2 S922X)
For models based on g12 (s905x2 s922), which have a problem not the correct color , 
If you are starting the system from an SD card, you need to copy file  u-boot.sd to u-boot.ext,
If you are starting the system from an USB, you need to copy file  u-boot.usb to u-boot.ext
When installing in eMMC, you do not need to do anything with your hands, the installation script itself will perform the necessary system configuration and when running from eMMC, the system will work with the correct color.
 
Please note, this version for the transition to the release of a single image for the platform Rockchip + Amlogic + Allwinner. The new image after writing to external media and after configuring the used dtb (and if necessary adding the desired u-boot option to run from the SD card on the Rockchip and Allwinner) can be used simultaneously on AML (s9xxx), RK (rk3399 and rk3328) and AW (H6). If the TV boxes RK (rk3328 and rk3399) and AW (H6) in eMMC installed a new version of u-boot  with support for starting the system with USB, adding u-boot to SD card is not required, the system will automatically start on with USB.
 
Important change. With this version (>= 20200218), you can easily add the desired u-boot on any PC (including Windows) .
 
To do this, new versions of u-boot are downloaded on the site.
 
https://yadi.sk/d/lTbXkrmZN5Hf6g
 
Rules for using the new u-boot option. Download, Armbian image, unpack. Write image Armbian to the SD card. Download and write the desired version of the u-boot file to SD card. Configure the DTB and the launch string (APPEND) in (uEnv.txt) for the desired model\platform.
 
Pay attention. Now you don't need to write u-boot with complex commands, you write the u-boot image with the same program as you usually write an Armbian image. This allows you to configure the system to run (including writing a u-boot image) on any PC (including Windows).
 
Pay attention. The new version changed the size of the partitions that are obtained when writing an image (all images have a fixed size of 5GB).  This u-boot entry option only applies to the new version 20200218 and subsequent versions. Don't try this for old images. This will not work on older images.
 
OLD add u-boot
 
 
 
For RK33xx
if you have windows and can't use the add u-boot commands to the SD card, use the SD+USB combination , write only the new u-boot to the SD card, and write the Armbian image to a USB storage device. And connect them together to the TV box.
 
To turn on the sound on models AML
where it is not present after the initial start. To enable audio on g12  (s905x2 s922x), you only need to run the script (g12_sound.sh) or for GX\GXM models, run the script (gx_sound.sh).  You need to run the script
 
sudo /root/g12_sound.sh
 
For gxbb\GXL\GXM models (S905\S905X\S912), if there is no sound, you need to try running the script (gx_sound.sh)
 
sudo /root/gx_sound.sh
 
For those who still use older versions of images (up to 20200323), for the sound to work correctly on g12, you must first (before running the script g12_sound.sh) delete PULSEAUDIO.
 
Odroid N2
When starting from an SD card on Odroid N2, you must, after recording the image, write uboot to the SD card, configure uEnv.txt, additionally rename the script (boot.scr.aw) in (boot.scr). To be able to start any system from any media (USB SD eMMC), i'm recommend using the updated version of u-boot-SPI. Details about u-boot-SPI for Odroid N2 can be found here.
 
 
 
 

OK.  Boots, gets to desktop, plays the test video, sound via HDMI works, my RTL8821CU wifi was properly recognized. 
 
Only thing I see is no fan control, and the LED is just blinking at 1 Hz for no known reason.
 
LibreELEC: same, boots, audio, etc.  [edit]  it did not recognize the wifi adapter.
 
Now to dig up my Ugoos and stuff this on it. 
 
 

@TonyMac32  Did I remember correctly that you have a MIQI Board (rk3288) ?

The new version 20200609. In it, I switched to using the u-boot version 2020.04 (source shared with universal images for aarch64). This version has long implemented the function of starting the system from USB media. Now rk3288 also has the option to start the system from USB media. Minimal Bionic and Buster images have also been added to the site.
 
Starting from USB is available on both systems (Libreelec and Armbian). For example. You can write to an Armbian SD card, and write to a Libreelec USB flash drive. When you connect both media, LE will work, and when you disable the USB flash drive, Armbian starts.
 
 
p.s. The correct installation of these systems in eMMC is currently being tested.