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


Recommended Posts

Armbian is a community driven open source project. Do you like to contribute your code?

On 4/13/2020 at 1:45 PM, Seb_Lz said:

 

 

I have it installed on my Beelik GT1 following stricly those steps (and using qemuarm-64 for the superviser install):

https://www.home-assistant.io/hassio/installation/#alternative-install-home-assistant-supervised-on-a-generic-linux-host
 

Do you guys have a working ethernet connection with your GT1  (I tried khadas-vim2, q200, q201 and many other .dtb but I can only get wifi working, not eth0) ?

 

See 

 

 

Lastest images from Balbes broke some PHYs. I noted the problem is with a patch that it is used on newer Kernels and how the some PHY parameters are parsed from DTBs

 

https://patchwork.kernel.org/patch/10985167/

 

So I reverted those changed on DTB and it worked. Please try attached DTB

 

 

 

 

meson-gxm-q200.dtb

Link to post
Share on other sites
3 hours ago, Juanjo said:

Lastest images from Balbes broke some PHYs. I noted the problem is with a patch that it is used on newer Kernels and how the some PHY parameters are parsed from DTBs

Try not deleting the patch, but increasing this value to the old values (snps,reset-delays-us = <0 10000 1000000>;)

 

reset-deassert-us = <30000>;

 

to

 

reset-deassert-us = <1000000>;

Link to post
Share on other sites
43 minutes ago, Alessandro Salgoni said:

I have install last Armbian release on emmc of my box, now I can found a dtb file with wifi work, how can I update the system?

Copy the file to the /boot directory and configure (uEnv.txt) to the new file. However, note that this file may not work with the current kernel and the system may not start, or it may not work with the new kernel when the kernel is updated. You will need to start the system from an external media and return the settings back.

Link to post
Share on other sites

Hi all

I have a bqeel X8T max box. Last week, starting from the stock firmware, I was able to install armbian image (Armbian_20.02.0-rc1.037_Aml-s9xxx_bionic_current_5.5.0-rc6_desktop_20200205.img).

I had a lot of trouble to configure the dtb file, due to my few experience... but finally I did it (I'm quite sure using meson-gxl-s905x-p212.dtb).

 

Then I decided to try also coreelec image (unfortunately I didn't catch the warning on the first message of this topic)... so when I decided that armbian is better for my needed I was not ablt to come back.

 

Using Amlogic burning tool I was able to install another android firmware (the stock firmware for my box is scarce) but I'm not able to reinstall armbian... also trying all dtb files for s905x.

These are steps that I'm doing:

1. using Etcher (on windows 10) burn the uimage on a USB drive

2. rename u-boot.sd in u-boot.ext

3. edit uEnv.txt with notepad++ and change the row 19 in FDT=/dtb/amlogic/meson-gxl-s905x-p212.dtb

4. save and exit

5. create a file uEnv.ini that is a copy of uEnv.txt (I think that this step is not needed)

6. put the usb drive in the box

7.  Open the app "Update&Backup"
8. Click on "Select" local update and chose the file on the removable media aml_autoscript.zip
9. Start "Update"

 

For each tentative I wait for about 10 minutes.

I also tryed with  "toothpick method" but with no success.

 

I'm quite sure that I'm doing something wrong in the USB preparation.... but I don't know what!!!!!

What can I do?

 

 

 

Thanks

 

Link to post
Share on other sites
12 minutes ago, ggerla said:

(I'm quite sure using meson-gxl-s905x-p212.dtb

You don't need these steps for s905x.

 

12 minutes ago, ggerla said:

2. rename u-boot.sd in u-boot.ext

 

12 minutes ago, ggerla said:

5. create a file uEnv.ini that is a copy of uEnv.txt (I think that this step is not needed)

 

Link to post
Share on other sites
23 minutes ago, balbes150 said:

You don't need these steps for s905x.

 

I forgot to say explicitly that my box is based on s905x chip with 2GB/16GB.

In addition I opened the box and on the board I read CS_905X_TX95_v1.2

 

In any case you are right... the problem was that I did too many steps. I created again the usb and just edited the uEnv.txt. It works!!!


Thanks

 

 

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

Try not deleting the patch, but increasing this value to the old values (snps,reset-delays-us = <0 10000 1000000>;)

 

reset-deassert-us = <30000>;

 

to

 

reset-deassert-us = <1000000>;

 

 

Did that after reverting and didn't work.

 

Reported to Martin and I have to send logs to to linux-amlogic working and not working. Haven't had time to replicate the original incorrect behaviour

 

BTW just been testing X96Max Plus box and it seem it is suffering from the same 

Link to post
Share on other sites

Hi All,

I found that v5.7-rc1 has merged amlogic's vp9 video decoding and h264 decoding codes, but when using VIM1 to test the latest images (Armbian_20.05.2_Arm-64_bionic_current_5.7.0-rc1_desktop_20200423.img.xz), I found that hardware decoding does not seem to work. Is anyone interested in this? Did I miss any steps?
How did I test: When I use the default player to play the mp4 file on the desktop, I find that the CPU usage is significantly higher, but when I use the built-in chrom browser to play YouTube's vp9 video, the CPU usage is close to 100% , It looks like hardware decoding is not working.

Looking forward to help, thank you in advance.

Link to post
Share on other sites

Hello guys. Sadly I'm still limited to 1 post per day so I'll try to make this as complete as possible.

I bought an X96 Air 2/16GB to try armbian on. It seemed like a good box for the price and it has a recent SOC on 12nm.

 

I managed to install armbian with no problems.

I used the Armbian_20.05.0_Arm-64_bionic_current_5.6.0-rc6_20200403 desktop release, then switched back to minimal since I dont need a desktop environment.

 

Everything is fine, ethernet works, but I didnt test wifi or BT since I dont use those.

 

Now comes the part when I started having issues. 

I've read many tutorials and videos on installing to eMMC and I was confindent.

 

So I've made a backup and I tried running nand-sata-install but that command doesnt exist anymore.

I searched a bit more and found the scripts inside the root folder.

Since my box has an Amlogic SOC (the S905X3) I ran the amlogic script.

 

On the first try it failed saying there was no u-boot.sd, so I made a copy of u-boot.ext and renamed it to u-boot.sd.

On the second try it wen fine and said it installed successfully, but the box never booted again. I tried everything!

 

So I had to download the factory firmware the flash it with the toothpick method. Glady it came back to life!

 

So then I tried the S905X script which I thought would work since I have a S905X3. But no... it didnt work and bricked again even though it said it was a success.

 

What am I doing wrong? I'm using the  meson-sm1-sei610-ethfix.dtb and I'm sure the env file is setup correctly.

I really need to install into eMMC

 

@gabe5000 @balbes150 @SteeMan I mentioned you guys because I've seen you talk about the X96 Air and helping people with eMMC installs. I followed your tips but was unsuccessful

 

Thank you for the help!

Link to post
Share on other sites
14 minutes ago, ThatUnknownGuy said:

What am I doing wrong? I'm using the  meson-sm1-sei610-ethfix.dtb and I'm sure the env file is setup correctly.

I really need to install into eMMC

It is good that you have the process of restoring the factory android firmware down as you may need that a few more times as you work through this.

It seems that you are doing things correctly, but it isn't clear from your description that you have ever tried without something going wrong and then needed to retry.  So I would recommend you go back to step one and try again.

1) Reinstall factory android firmware

2) Download a clean copy of the armbian build you want to install (you talk about switching between desktop and minimal so I don't know what build were have been trying)

3) Burn the build to your sd card

4) On the newly created sd card, edit the /boot/uEnv.txt file for the correct dtb and cpu boot (since you are using an Amlogic device, I would recommend removing the Rockchip and Allwinner sections completely)

5) cp u-boot.sd to u-boot.ext (note copy not move, and I am assuming you are doing this because you have the green screen issue, if you don't have the green screen issue you don't need to do this step,  even if you do have the green screen issue, since you are using this as a server and likely rarely using the hdmi output directly you can also skip this step, perhaps try it both with and without this step)

6) boot with the sd card installed via the toothpick method to install the multi-boot and boot from the sd card

7) go through the initial root login and setup your user while booted from the sd card

8) as root run install-aml.sh

9) you should be installed in emmc at this point reboot

That should work and since you are starting from a known fresh firmware and doing only the minimum steps necessary, you should be eliminating other external factors that could be causing a problem.

Link to post
Share on other sites

Can anyone tell me if it's possible to have audio working on armbian focal kernel 5.7 rc1, 23.04. release, device is khadas vim 3?

 

One more thing i've noticed, can't reboot, it starts reboot process, rebooting is written on the screen, and it stays like this without actually rebooting?

 

 

 

 

Link to post
Share on other sites
On 4/19/2020 at 9:39 PM, almotra said:

 

All work very well before update.

In my previous message, we see that the update removes /boot/initrd.img-5.6.2-arm-64 and recreate /boot/initrd.img-5.7.0-rc1-arm-64

When I put a sd, with in uenv.txt (ROOT_EMMC) the box starts but blocks on mnt/boot and it puts in maintenance

I have this problem with x96max + and H96max +, but not with x96mini.

 

I solved this problem in "armbian-config" puis "system and security setting" and "freeze" disable armbian upgrades

I'm experiencing the same problem here. All was fine after installing to mmc but running apt upgrade results in green screen upon reboot.

 

H96 Max X3 S905X3

Armbian_20.05.2_Arm-64_focal_current_5.7.0-rc1_desktop_20200423.img.xz

meson-sm1-H96max-X3.dtb from: https://forum.armbian.com/topic/12162-single-armbian-image-for-rk-aml-aw/?do=findComment&comment=94317

Link to post
Share on other sites
On 4/23/2020 at 5:55 AM, Juanjo said:

 

See 

 

 

Lastest images from Balbes broke some PHYs. I noted the problem is with a patch that it is used on newer Kernels and how the some PHY parameters are parsed from DTBs

 

https://patchwork.kernel.org/patch/10985167/

 

So I reverted those changed on DTB and it worked. Please try attached DTB

 

 

 

 

meson-gxm-q200.dtb 28.29 kB · 2 downloads

Thanks a lot @Juanjo ! Your dtb has indeed fixed eth0 interface on my Beelik GT1 (armbian bionic version 5.6.0-rc7-arm-64).

Link to post
Share on other sites
24 minutes ago, graffiti said:

but with legacy kernel

1. The LEGACY version is not intended to be built by regular users (it can only be used by specialists who know its purpose well).

2. According to the log, you have a problem accessing network repositories (problems with the Internet, a large load on servers, and so on). This error does not apply to the build system.

Link to post
Share on other sites
On 4/25/2020 at 12:22 PM, mormegil said:

I'm experiencing the same problem here. All was fine after installing to mmc but running apt upgrade results in green screen upon reboot.

 

H96 Max X3 S905X3

Armbian_20.05.2_Arm-64_focal_current_5.7.0-rc1_desktop_20200423.img.xz

meson-sm1-H96max-X3.dtb from: https://forum.armbian.com/topic/12162-single-armbian-image-for-rk-aml-aw/?do=findComment&comment=94317

I found the source of my problem! Apparently I'm not using a stock dtb and the firmware could not find it anymore since the directory has been renamed to dtb.old. I just had to copy my dtb file into the new dtb directory and my problem goes away.

 

@ramoncio Thank you for your dtb file! My H96 Max X3 4GB 128GB works perfectly with Armbian focal 5.7.0-rc1. Gigabit runs at 1000gbps. Wifi works. Hdmi with sound works. Bluetooth is able to be switched on and I can see devices but I have yet to fully test it out. USB2 and USB3 works at full speed. Getting excess of 100MB/s on my Seagate external USB drive.

Link to post
Share on other sites
4 hours ago, mormegil said:

I found the source of my problem! Apparently I'm not using a stock dtb and the firmware could not find it anymore since the directory has been renamed to dtb.old. I just had to copy my dtb file into the new dtb directory and my problem goes away.

 

@ramoncio Thank you for your dtb file! My H96 Max X3 4GB 128GB works perfectly with Armbian focal 5.7.0-rc1. Gigabit runs at 1000gbps. Wifi works. Hdmi with sound works. Bluetooth is able to be switched on and I can see devices but I have yet to fully test it out. USB2 and USB3 works at full speed. Getting excess of 100MB/s on my Seagate external USB drive.

Hello. I have a H96 Max X3 4GB 128GB like you. I installed the armbian - version you specified with FDT = / dtb / amlogic / meson-sm1-H96max-X3.dtb - and the rest of usual procedure, ... but neither embedded wifi nor bluetooth work. Can you please tell me what else do you do to make them work. Thank you.

PS : I noticed that "unit xrdp.service could not be found", so we cannot activate it directly from armbian-config In "focal" version. It must be installed on command line.

Link to post
Share on other sites

Hi,
I am trying to install ARMBIAN with the image Armbian_20.05.1_Arm-64_buster_current_5.6.2_20200408.img and meson-gxm-q201.dtb on the emmc of my H96pro +. It's the same with meson-gxm-q200.dtb or meson-gxm-khadas-vim2.dtb. It works very well on the SDCARD. I run the install_aml.sh script and everything is copied to the emmc without error with the right partitions.
If I try to boot on emmc I just have the H96pro + screen and nothing.
After some tests I write well on the emmc (new partitions, creation of a file system, new files, ...) without worry. But if I reboot (restart with the remote control) or I turn off the box by cutting the power. I lose all the modifications on the emmc which returns with the original partitioning of Android.
How to keep the modifications on emmc?

Thank you for your help

Link to post
Share on other sites

After working smooth from card, I installed Armbian_20.05.3_Arm-64_bionic_current_5.7.0-rc2_desktop_20200425.img.xz on 3 x96mini 2/16 this afternoon. As expected they all work good, on older pcb revisions(late2017) with eth and audio via hdmi or usb sound card and on the newer ones(Ver.4.0 from jan2020) even with wifi and bt.

 

I also tried same build as focal version. Basic system works nice, but the user had not the proper rights to change language settings and stuff, so I went back to bionic which works always for me flawless..

 

Thanks to Oleg for his hard work and the new 20.05.03-builds!..

 

 

Link to post
Share on other sites
9 hours ago, mormegil said:

I found the source of my problem! Apparently I'm not using a stock dtb and the firmware could not find it anymore since the directory has been renamed to dtb.old. I just had to copy my dtb file into the new dtb directory and my problem goes away.

A word of advice.  Do not put your custom dtb file in the dtb directory.  Everytime the kernel is upgraded via apt, the dtb directory is moved to dtb.old and a new one corresponding to the new kernel is installed.  You should put your custom dtb file in /boot so that it isn't touched by these kernel upgrades.

Link to post
Share on other sites
Guest
This topic is now closed to further replies.