What parameters do you need,
.configure files, full kernel sources?
If we had the proper dtb file would it work?
Isn't it possible to extract and convert the dts/dtb file from android as root to use in armbian and LE? Or maybe it's not that simple?
Magicsee N6 Max rk3399
Armbian_19.11.4_Arm-64_bionic_dev_5.5.0-rc2_desktop_20191228 with rk3399-rock-pi-4.dtb tweaked to cpuspeed 1.70 & 2.01 GHz
Boots to desktop , usable with some artifacts - will test again upon kernel update
Build the first version of Armbian 20191221 19.11.4 kernel 5.5.0-rc2 for Allwinner H6 (Tanix TX6).
The system normally starts from the SD card. Works sound and USB devices (BT WiFi USB media etc), but there is a serious drawback until the wired network works. I have not yet figured out the reason why the wired network does not work, so I publish only two test images of Ubuntu and Debian, for a General assessment of the health of the system on Tanix TX6.
https://yadi.sk/d/GJbDt3-FjQ-dQA
With appropriate configuration, this version can be used on other platforms RK and AML. On RK and AML everything works as in the previous images.
I pay attention, for those who used these images on RK3399 from SD card, it is necessary to add correct u-boot. In these images, u-boot and settings for Allwinner h6 Tanix TX6 are enabled by default.
Update version 20191218 kernel 5.5.
Fixed support for sound on g12 platform. now the sound works as usual, after removing pulseaudio and running the script "g12_sound.sh".
Update Armbian images 5.99_20191121 to rk3399.
DEFAULT - kernel 4.
Please note, in the future I plan to completely switch to using kernel 5 for all images. The kernel 4 version will no longer be released.
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 deleted. 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
Now you can download the latest versions of images and DEB packages from the official Armbian resource via the link.
https://users.armbian.com/balbes150/
*********************************************************************************************************************************
Pay attention. Starting from version 20.08 (20200814), the configuration order for the used DTB changes.
Please note that the algorithm for initial configuration of the system for startup has changed. Instead of a file "uEnv.txt", the file "/extlinux/extlinux.conf " is now used. The rules for editing a file remain the same.
All Amlogic models now need the "u-boot.ext" file.
Before launching on Amlogic, you must copy or rename one of the existing files "u-boot-*" to "u-boot.ext".
For s905 (not X) - used u-boot-s905
For s905x and s912 - used u-boot-s905x-s912
For s905x2 and s922 - used u-boot-s905x2-s922
For g12a\g12b models, a single file is now used (files u-boot.sd and u-boot.usb now replaces one u-boot-s922 file).
For the Allwinner platform, you no longer need to rename the scripts "boot.scr".
All "boot.scr" scripts have been canceled and are not used.
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 , run the script (sound.sh). You need to run the script
sudo sound.sh
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.
I'm opening a new direction-universal image (ver dir NEXT and DEV) for Amlogic+Rockchip+Allwinner. Details can be found in this topic. Please try the new option to run on AML (first of all I am interested in using USB media).
I'd like to, and I started working on a script that would compile the latest versions of the software for a specific distro. Let's see if I can find some time to finish it.
I checked the latest DEV and NEXT images on N6. The system starts and works with dtb rock-pi-4.
Only need to wait 4-5 minutes until the system starts (a picture will appear on the screen).
By the way, I just checked, on N6 starts LE with 5 core, but you need to wait more than 5 minutes until the setup wizard starts.
Armbian_5.91_Rk3399-tv_Ubuntu_bionic_default_4.4.154_desktop_20190716
Bumped up max cpu speed to 1.99 and 1.51. Stable so far with active cooling @45 degrees
So I got tired of my fan platform (see above) being always on even when I did not need the cooling, so I built a simple controller using a USB relay module.
I stripped off part of the USB cable for the fan platform, cut the red wire and connected it to the relay like this. The black wire is untouched. Connections to COM, and NO of the relay module (no soldering needed).
The USB->Serial adapter showed up in lsusb but not as /dev/ttyUSB0. I needed to enable CONFIG_USB_SERIAL_CH341=m based on this post.
I am running a version of 4.4.154 and luckily enabling this module worked.
Now I can turn the fan on and off using a script as described here.
I wrote a simple shell script wrapper around it which looks at the temperature from
/sys/devices/virtual/thermal/thermal_zone0/temp in a loop and turns the fan on/off based on it. By trial and error I set the limits, I turn it on at 80C and wait for the temperature to fall below 70C to turn it off.
It does use an extra USB port (a USB port splitter might work) but works fine now. Normally the fan is off. If I start the script, no fan, until I mpv the "lubimaya lubimaya video" the temperature goes up and then the fan starts and stays on until I close mpv. Would be good if I could tie it to the temperature trip points in the dtb, but I don't know how.
amirul reacted to ramoncio in X88 King S922X TV Box for Armbian
amirul got a reaction from NicoD in Build Armbian with Panfrost