43 43
balbes150

Single Armbian image for RK + AML + AW (aarch64 ARMv8)

Recommended Posts

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.

 

 

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

 

Spoiler

 

In the "U-BOOT" directory on the site there are versions of files for writing to a universal image for these models, to run the system from an SD card on the AML, RK and AW platform. I pay attention, u-boot records need to be performed after writing the image to the SD card, with two commands (to save the existing partition table).

 

 

 Write u-boot to SD card. U-boot replacement is performed by two commands.


dd if=u-boot-<model>.img of=/dev/<SD_card> conv=fsync bs=1 count=442

dd if=u-boot-<model>.img of=/dev/<SD_card> conv=fsync bs=512 skip=1 seek=1

 

u-boot file for support model

https://yadi.sk/d/PIGjwjZ4m4HKqg

 

 

 

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.

 

 

 

 

Share this post


Link to post
Share on other sites

Armbian_5.99_Rk3399-tv_Debian_buster_next_5.4.0-rc7-next-20191115 and desktop images boot on a km8p (2/16gb) with several gxm dtb, but I think that gxm-q200.dtb the best one since only fast ethernet. As expected, wifi not recognized. For the desktop version, X11 does not launch properly and there is nothing in Xorg log file. I was able to launch manually startx as root and it worked a few minutes before freezing.

With the server image, I face kernel panics. I'll try another image with a more stable kernel to be sure the hardware is ok.

Share this post


Link to post
Share on other sites

Armbian_5.99_Rk3399-tv_Ubuntu_bionic_next_5.4.0-rc7-next-20191115_desktop

g12b-ugoos-am6 X88 King s922x - whole screen blue-green tint, no usb power

Share this post


Link to post
Share on other sites

With an Armbian 5.98 g12 image, I have no kernel panic with my s912 km8p. The soc temperature seems also cooler with ~47°C for kernel 5.3 5.98 against ~57°C for latest generic 5.4 next image.

Share this post


Link to post
Share on other sites

Tested with Nexbox A95X S905x 1GB (meson-gxl-s905x-nexbox-a95x.dtb) and Magicsee N5 S905x 2GB  (meson-gxl-s905x-p212.dtb) and Buster Desktop Image

 

Dev 20191118 on both Boxes boot OK

HDMI Sound OK

3D Acceleration OK (glxgears)

LAN OK

Wifi on A95X (RTL8189ETV) no Adapter etc. found

Wifi on N5 (QCA9377) is found but dmesg says "ath10k_sdio...Unsupported hardware version: 0x5020001"

BT on N5 not found

 

Next 20191119 on booth Boxes boot OK

HDMI Sound - No Sound

3D Accreleration OK

LAN OK

Wifi on A95X (RTL8189ETV) no Adapter etc. found

Wifi on N5 (QCA9377) is found but dmesg says "ath10k_sdio...Unsupported hardware version: 0x5020001"

BT on N5 not found

Share this post


Link to post
Share on other sites
On 11/18/2019 at 2:19 PM, balbes150 said:

New image DEV 20191118

20191120

Magicsee N6 Max rk3399  rk3399-rock-pi-4.dtb - boot up after a while, no wifi 

Share this post


Link to post
Share on other sites
15 hours ago, nylonatathep said:

Dev 20191118 and Next 20191119 on LaFrite (meson-gxl-s805x-libretech-ac.dtb) r5 Firmware

No boot, stucks at Starting kernel ...

Official Armbian boots up.

Do you have a UART log ?

Share this post


Link to post
Share on other sites
1 hour ago, balbes150 said:

Do you have a UART log ?

Same with meson-gxl-s805x-p241.dtb

 

I added the log from armbian 19.11.3 Kernel 5.3.11 too

 

Armbian_5.99_Aml-g12_Debian_buster_default_5.3.0_20191122 boots

Armbian_5.99_Aml-g12_Debian_buster_default_5.3.0_desktop_20191122 ended up with kernel panic

 

output_2019-11-23_09-22-34.log armbian19.11.3.log

Armbian_5.99_Aml-g12_Debian_buster_default_5.3.0_desktop_20191122.log Armbian_5.99_Aml-g12_Debian_buster_default_5.3.0_20191122

Share this post


Link to post
Share on other sites

1. Your Board starts using u-boot-2019, which uses the "extlinux.conf" configuration file. For the UART console to work, you need to change the settings with

 

append: root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff1a0000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

 

to

 

append: root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

 

Then show the output of the UART.

 

2. You need to check the startup with all DTBS of the S905x group.

Share this post


Link to post
Share on other sites
1 hour ago, nylonatathep said:

Okay that makes sense, i thought the log was very short^^

Armbian_5.99_Rk3399-tv_Debian_buster_dev_5.3.0_desktop_20191123

Here is the log, same error on other x905x dtb's.

hwacom and khadas dtb does not boot at all no log.

hope it helps

Alas, I have no such equipment and I can only speculate. If the console version starts normally, and the DE version gives an error, there may be a problem with the software. For a quick test of the source of the problem-you can remove the entire directory with kernel modules (/lib/modules) from the media. If the error persists, try replacing the kernel and modules by taking them from the production system.

Share this post


Link to post
Share on other sites

Here is the output of armbianmonitor -u with the latest dev image on km8p (vim2 dtb): http://ix.io/22ER

The experience is similar to the recent g12 only images, ie. wifi and bluetooth not working (using an rtl8188eu usb dongle to get internet).

Share this post


Link to post
Share on other sites

Okay, succsess! The images are okay for LaFrite.

Was my fault :(

There was an error message that only appeared on screen not on UART messages. That message says that one module file cannot be loaded (bad ELF header)...

After some investigaton I testet my USB drive's an both of them have some bad sectors and these are not affected when I flash a minimal image.

I think they are corrupted between the many new flashes by testing the images.

When I use an new USB drive erverything is booting correctly with 5.3 and 5.4 Images but with 5.4 there is no Audio.

Thanks for your work and the help with the console output etc.

 

Share this post


Link to post
Share on other sites

The AML-g12-legacy images are universal. They can be run on the RK platform.  :)

 

If the eMMC has a u-boot version that supports direct USB startup, it is sufficient to configure the file (extlinux.conf) and the system can run on RK. If the eMMC does not support USB startup, you can use the combined method. Write to SD card micro image u-boot for the desired model of the RK chip. Write an Armbian image to a USB drive, configure (extlinux.conf), connect both media to the device and turn on the power. The system will automatically start from the USB drive.

 

The images themselves are in directories with a new label (current version 19.11.3) at this link.

 

https://yadi.sk/d/pHxaRAs-tZiei

 

U-boot micro-images available for use.

https://yadi.sk/d/PIGjwjZ4m4HKqg

 

 

A list of available images can be found in this post.

 

 

 

Share this post


Link to post
Share on other sites
On 11/30/2019 at 1:43 PM, balbes150 said:

add new image 20191130 kernel 5.4 (Buster and Bionic)

Magicsee N6 Max rk3399-rock-pi-4

Boots desktop ok, no wifi

Share this post


Link to post
Share on other sites
8 hours ago, balbes150 said:

Add new image DEV 20191207 kernel 5.4.1

Armbian_19.11.3_Rk3399-tv_bionic_dev_5.4.1_desktop_20190217

Magicsee N6 Max rk3399-rock-pi-4.dtb

Boots (faster) to desktop, no wifi

Share this post


Link to post
Share on other sites

Hi,

 

I'm trying to get the sound out of SPDIF on AMLG12 without success.

First, maybe there is an error in the g12_sound.sh script. If I remove the redirection to /dev/null, I've got the next error:

amixer: Unable to find simple control 'SPDIFOUT Playback',0

 

$ amixer | grep SPDIF
Simple mixer control 'SPDIFOUT',0
Simple mixer control 'SPDIFOUT Playback Channels Mix',0
Simple mixer control 'SPDIFOUT Playback Gain Enable',0
Simple mixer control 'SPDIFOUT SRC SEL',0
Simple mixer control 'SPDIFOUT_B',0
Simple mixer control 'SPDIFOUT_B Playback Channels Mix',0
Simple mixer control 'SPDIFOUT_B Playback Gain Enable',0
Simple mixer control 'SPDIFOUT_B SRC SEL',0
Simple mixer control 'TOHDMITX SPDIF SRC',0

 

Is anyone able to get sound out of SPDIF/TOSLINK?

 

"speaker-test -c2" execute without error, but without sound to.

 

Share this post


Link to post
Share on other sites

X hangs on Armbian_19.11.3_Aml-g12_buster_current_5.4.0_desktop_20191130.img.xz

 

cat /var/log/Xorg.0.log|grep EE
[    20.595] Current Operating System: Linux DEALDIG-BOXD6 5.4.0-aml-g12 #19.11.3 SMP PREEMPT Sat Nov 30 14:48:45 MSK 2019 aarch64
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    22.532] (EE) modeset(0): glamor initialization failed

 

System:    Host: DEALDIG-BOXD6 Kernel: 5.4.0-aml-g12 aarch64 bits: 64 compiler: gcc v: 7.4.1 Console: tty 1
           Distro: Armbian GNU/Linux 10 (buster)
Machine:   Type: ARM Device System: Amlogic Meson GXM (S912) Q201 Development Board details: N/A
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 Plus charge: N/A status: N/A
CPU:       Topology: 8-Core (2-Die) model: N/A variant: cortex-a53 bits: 64 type: MCP MCM arch: ARMv8 rev: 4
           features: Use -f option to see features bogomips: 0
           Speed: 1512 MHz min/max: 100/1512:1000 MHz Core speeds (MHz): 1: 1512 2: 1512 3: 1512 4: 1512 5: 1000 6: 1000
           7: 1000 8: 1000
Graphics:  Device-1: meson-gxm-dw-hdmi driver: meson_dw_hdmi v: N/A bus ID: N/A
           Device-2: meson-gxm-mali driver: panfrost v: kernel bus ID: N/A
           Display: server: X.org 1.20.4 driver: fbdev,modesetting tty: 164x33
           Message: Advanced graphics data unavailable in console for root.
Audio:     Device-1: meson-gxm-dw-hdmi driver: meson_dw_hdmi bus ID: N/A
           Sound Server: ALSA v: k5.4.0-aml-g12
Network:   Device-1: meson-gxbb-dwmac driver: meson8b_dwmac v: N/A port: N/A bus ID: N/A
           IF: eth0 state: down mac: 98:13:39:bd:48:17
           Device-2: pwm-clock driver: pwm_clock v: N/A port: N/A bus ID: N/A
           Device-3: ASIX AX88179 Gigabit Ethernet type: USB driver: ax88179_178a bus ID: 1-2:3
           IF: eth1 state: up speed: 1000 Mbps duplex: full mac: 00:0e:c6:f9:e7:6d
           IF-ID-1: wlan0 state: up mac: 10:d0:7a:bb:b9:ab

Share this post


Link to post
Share on other sites

Good news. Managed to find a way to work around the color issue on G12 platform + kernel =>5.4  with corrupted AML u-boot. You need to download and copy all the files from this directory to the media. New versions 20191208 already have some of the necessary files, you only need to add one  file u-boot.ext

 

Additional file download and copying (u-boot.ext) only need if your device screen color is not correct.

 

https://yadi.sk/d/MC2brPBu5bmW2Q

Share this post


Link to post
Share on other sites

I noticed that the Build_Armbian git tree had a new set of changes merged in a couple of days ago.  I tried it out last night and there is one issue that I have seen so far.  I did a build of 'Armbian_19.11.3_Aml-g12_bionic_current_5.4.0.img and the debs and img are missing the dtb files.  I will copy the dtb's from another build to further test, but wanted to let you know of this issue.  I noticed a lot of code restructuring in this set of build changes, and since it hasn't been announced yet, I suspect I am trying things before they are ready.

 

Share this post


Link to post
Share on other sites
5 minutes ago, SteeMan said:

I noticed a lot of code restructuring in this set of build changes, and since it hasn't been announced yet, I suspect I am trying things before they are ready.

The fix is already there, but they will be published later.

Share this post


Link to post
Share on other sites

New image DEV 20191209 kernel 5.4.1

 

Pay attention. This version changes the setting of the DTB for the Odroid models N2. Now all tuning principles are common to all models (files uEnv.ini and extlinux.conf). For models based on g12 (s905x2 s922), if you do not have the right color, you need to use the dual boot mode. To do this, use the SD card and add the "u-boot.ext" file to the Sd card. You can download this file from the site or rename an existing in  image u-boot.new to u-boot.ext.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
43 43