Jump to content

Armbian for Amlogic S905X3

Sergey2k

By Sergey2k
in General Chat

 Share

Recommended Posts

Sergey2k

Sergey2k

Posted
Posted

I try to use image Armbian_19.11.3_Aml-g12_bionic_legacy_5.3.0_desktop_20191126.img for device with S905X3. TV box is called X96 Air.

Unfortunately, I can't make multi boot. I've got error:

-- Install /udisk/aml_autoscript.zip

...

Verifying update package...

E:footer is wrong

Update package verification took 0.1 s (result 1).

E:Signature verification failed

E:error: 21

Installation aborted.

 

How I can do it?

Link to comment
Share on other sites
Sergey2k

Sergey2k

Posted
  • Author
Posted

I've tried. It's right. Probably TV box is beginning booting from USB, because android not start. But I don see anything on display, therefore this image don't work there.

After removing USB storage android have booted good.

How to make Armbian for new Amlogic CPU?

Link to comment
Share on other sites
SteeMan

SteeMan

Posted
Posted

I have a new TX3 box with the s905x3 chip and that box boots with the meson-sm1-sei610.dtb file.  It works fine as a server (i.e. boots, wired ethernet, usb working).  No wifi or bluetooth.  I did also try to install a desktop build and the hdmi output isn't correct, colors are messed up, and sound isn't working. 

Link to comment
Share on other sites
Sergey2k

Sergey2k

Posted
  • Author
Posted
7 hours ago, SteeMan said:

I have a new TX3 box with the s905x3 chip and that box boots with the meson-sm1-sei610.dtb file.  It works fine as a server (i.e. boots, wired ethernet, usb working).  No wifi or bluetooth.  I did also try to install a desktop build and the hdmi output isn't correct, colors are messed up, and sound isn't working. 

What image do you use? Where I can download it?

Link to comment
Share on other sites
Sergey2k

Sergey2k

Posted
  • Author
Posted

offtopic. I tried any linux images and my device started with altlinux_xfce_20190902.img, if it's interesting for anybody) Dtb file is not changed, stays as default, meason-g12b-odroid-n2. USB, keyboard, mouse, HDMI (display) work good. But network displays disconnected state and trying to connect. Bluetooth seems work, I did't check.

[user0@localhost ~]$ uname -a
Linux localhost.localdomain 5.3.0-rc6-aml-g12 #5.94 SMP PREEMPT Sun Sep 1 13:46:49 MSK 2019 aarch64 GNU/Linux

[user0@localhost ~]$ cat /proc/cpuinfo

processor    : 0
model name    : ARMv8 Processor rev 0 (v8l)
BogoMIPS    : 48.00
Features    : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer    : 0x41
CPU architecture: 8
CPU variant    : 0x1
CPU part    : 0xd05
CPU revision    : 0

processor    : 1
model name    : ARMv8 Processor rev 0 (v8l)
BogoMIPS    : 48.00
Features    : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer    : 0x41
CPU architecture: 8
CPU variant    : 0x1
CPU part    : 0xd05
CPU revision    : 0

Link to comment
Share on other sites
Sergey2k

Sergey2k

Posted
  • Author
Posted
9 hours ago, SteeMan said:

You need a 5.4+ kernel, the latest that I can find is at: https://yadi.sk/d/pHxaRAs-tZiei/OLD/5.99/dev

I am running with: Armbian_5.99_Aml-g12_Debian_buster_dev_5.4.0-rc6_20191110.img

Thank you. I try desktop build with meson-sm1-sei610.dtb. Device is booted, wired network don't work (don't see connected cable), wifi works well. Colors on display are messed up too. Also BT and USB work.

04.jpg

Link to comment
Share on other sites
NicoD

NicoD

Posted
Posted
2 hours ago, Sergey2k said:

04.jpg

There should be a patch for this. Can't immediately find it. Using a earlier version of uboot should/could also fix this. I've seen this on other amlogic boards with updated uboot. I expect i to be the same issue. 

I also got the X96 air. But haven't got time to turn it on. I'll check it out in a few weeks. Too much other stuff. Good to see armbian runs on it.

Link to comment
Share on other sites
balbes150

balbes150

Posted
Posted
3 hours ago, Sergey2k said:

Colors on display are messed up too

You can "thank" AML for this.

B)

They broke the u-boot. They put a bunch of crap in it that works exclusively with their old and crappy 4.9 core. For the color to work correctly with the 5.4 kernel, you either need the old u-boot-2015 (from the firmware, before AML broke it) or use u-boot-2019 (removing u-boot-2015 completely).

 

 

Offtopic. The behavior of AML lately has been increasingly frustrating for me. They do not pay any attention to the development of support for their chips in the main core (this work is done by third-party developers). Instead of helping, their new patches create a bunch of problems for the main kernel. I am waiting for the release of new Rockchip chips (or other platform options other than AML), and I hope to completely switch to using them for my development (minimizing support for AML, limiting myself to the chip models I already have).

5
Link to comment
Share on other sites
NicoD

NicoD

Posted
Posted
10 hours ago, balbes150 said:

The behavior of AML lately has been increasingly frustrating for me. They do not pay any attention to the development of support for their chips in the main core (this work is done by third-party developers). Instead of helping, their new patches create a bunch of problems for the main kernel.

I also don't get this. Isn't their goal to sell more chips? Then wouldn't they sell a lot more with good/better software/support?
Seems like they don't want people to use Linux on them. 

 
They do make the most powerful SoC's on cheaper SBC's. I use Amlogic SoC's for video editing. For that you only need a good cpu(multicore+single core), and gpu/vpu is of lesser importance. In power per watt the A311D/S922X are just the best. 
But I'd like to be able to do a lot more than just video editing on them. I loved the Odroid C2 with S905. Was more versatile. But then again they claimed 2Ghz clockspeed. :) 

I can't wait for the RK3358 to show up on a board. That should be able to outmatch the Amlogic SoC's. It is to see what consumption and how much heat it'll produce.
Rockchip used to be worse than amlogic in their support. But they did make that up. Allwinner is no match in performance. But they are very usable boards for lighter tasks. OPi+ is my MP3 player and NAS with a sata hd and 1.5TB USB2 external HD. No other board does that better.

The RK3399's are my most used SBC's for light desktop tasks/surfing/watching video. But no match for video editing. RK3399 can edit/render 1080p videos well. But A311D does 1440p. The C2 used to do 720p. So it did improve quickly last years.

I'm very happy you make these images. Me with a lot of other people. It makes many boards a lot more useful where otherwise they'd be paperweights. I love your efforts in making more compatible images. One of my next videos will be about that. Nobody else ever came so close to universal images as you have. I take my hat off for that.

I just bought the X96 Air since it's S905X3. Made me nostalgic to my Odroid C2 and it was dirt cheap. If only I had the SMD soldering skills, then I could take the 32GB eMMC and 4GB ram from X96 and solder them onto my 2GB+16GB Khadas VIM3. For the 30euro I payed, the 32gb eMMC and 4GB ram are worth it. I just don't want to risk the VIM3.
Cheers.
 

2
Link to comment
Share on other sites
SteeMan

SteeMan

Posted
Posted

I tested the fix for the color issue and it wasn't successful for my box (TX3 x905x3).  Using Armbian_19.11.3_Rk3399-tv_bionic_dev_5.4.1_20191208.img with the downloaded u-boot.ext the box fails to boot.  If I remove the u-boot.ext file the box boots but with the faulty colors.

 

Earlier in this thread it was mentioned the option of installing a newer u-boot to solve the color problem.  Are there relatively simple instructions on how to build a mainline u-boot and install it on an amlogic tv box?  I am assuming you need to replace the shipped u-boot on mmc?

In looking at the mainline u-boot tree, it looks like support for the s905x3 (sm1) has only recently been included, so my thinking is I would likely want to try the latest: v2020.01-rc4.

Link to comment
Share on other sites
Sergey2k

Sergey2k

Posted
  • Author
Posted
9 hours ago, balbes150 said:

 

I tried to fix u-boot with Armbian_5.99_Aml-g12_Debian_buster_dev_5.4.0-rc6_20191110.img on my X96Air. Device don't boot, green screen only.

Next I tried to boot with new Armbian_19.11.3_Rk3399-tv_buster_dev_5.4.1_desktop_20191208.img withot fix u-boot. Colors on display are messed up.

And I added u-boot.ext. Again device dont' boot with green screen.

Link to comment
Share on other sites
Sergey2k

Sergey2k

Posted
  • Author
Posted
1 hour ago, balbes150 said:

what media is used ?

USB flash drive 16Gb SunDisk

  

> lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0781:5591 SanDisk Corp. Ultra Flair
Bus 001 Device 005: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 001 Device 004: ID 04d9:1503 Holtek Semiconductor, Inc. Keyboard
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

 

 

Link to comment
Share on other sites
balbes150

balbes150

Posted
Posted

It is preferable to use an SD card for the correct operation of the patch. This is due to the features of the TV boxes and the curvature of the original u-boot (firmware) in the eMMC from the device vendor. On many models, the fix does not work when starting from USB media. I recommend that you download the latest version of the fix.

(update all three files that are used in the patched startup process)

 

s905_autoscript

boot.ini

u-boot.ext

 

Pay attention, the file "boot.ini" do not edit. Configure the used DTB only in "uEnv.ini" and "extlinux.conf"

Link to comment
Share on other sites
Sergey2k

Sergey2k

Posted
  • Author
Posted
1 hour ago, balbes150 said:

On many models, the fix does not work when starting from USB media

You are right. I extracted image on SD card and system booted normally (see photo below). Thank you.

Next problem is wired network (wifi works good).
There is log of errors: 

Dec 09 10:45:37 rk3399 kernel: meson8b-dwmac ff3f0000.ethernet: IRQ eth_wake_irq not found
Dec 09 10:45:37 rk3399 kernel: meson8b-dwmac ff3f0000.ethernet: IRQ eth_lpi not found
Dec 09 10:45:37 rk3399 kernel: dwc3 ff500000.usb: Failed to get clk 'ref': -2
Dec 09 10:45:37 rk3399 kernel: gpio-keys gpio-keys: Unable to get irq number for GPIO 0, error -6
Dec 09 10:45:37 rk3399 kernel: debugfs: Directory 'ff800280.cec' with parent 'regmap' already present!
Dec 09 10:45:38 rk3399 kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
Dec 09 10:45:39 rk3399 kernel: meson8b-dwmac ff3f0000.ethernet eth0: no phy at addr -1
Dec 09 10:45:39 rk3399 kernel: meson8b-dwmac ff3f0000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
Dec 09 10:45:39 rk3399 dhclient[655]: send_packet: Network is down
Dec 09 10:45:39 rk3399 dhclient[655]: dhclient.c:2445: Failed to send 300 byte long packet over eth0 interface.
Dec 09 10:45:39 rk3399 dhclient[655]: receive_packet failed on eth0: Network is down
Dec 09 10:45:40 rk3399 kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
Dec 09 10:45:41 rk3399 kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
Dec 09 10:45:47 rk3399 dhclient[655]: send_packet: Network is down
Dec 09 10:45:47 rk3399 dhclient[655]: dhclient.c:2445: Failed to send 300 byte long packet over eth0 interface.
Dec 09 10:45:49 rk3399 bluetoothd[829]: Sap driver initialization failed.
Dec 09 10:45:49 rk3399 bluetoothd[829]: sap-server: Operation not permitted (1)
Dec 09 10:45:50 rk3399 NetworkManager[846]: ((src/settings/nm-settings.c:899)): assertion '<dropped>' failed
Dec 09 10:45:50 rk3399 kernel: meson8b-dwmac ff3f0000.ethernet eth0: no phy at addr -1
Dec 09 10:45:50 rk3399 kernel: meson8b-dwmac ff3f0000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)

 

IMG_20191209_153715427_HDR.jpg

1
Link to comment
Share on other sites
Sergey2k

Sergey2k

Posted
  • Author
Posted
29 minutes ago, balbes150 said:

You deal with DTB (choose a working one or create your own).

It isn't secret.)

I've extracted dtb from android update image for my TV Box. And I'm thinking how use it)
Cut from it about ethernet: 

    ethernet@ff3f0000 {
        compatible = "amlogic, g12a-eth-dwmac", "snps,dwmac";
        reg = <0xff3f0000 0x10000 0xff634540 0x8 0xff64c000 0xa0>;
        reg-names = "eth_base", "eth_cfg", "eth_pll";
        interrupts = <0x0 0x8 0x1>;
        interrupt-names = "macirq";
        status = "okay";
        clocks = <0x2 0x38>;
        clock-names = "ethclk81";
        pll_val = <0x9c0040a 0x927e0000 0xac5f49e5>;
        analog_val = <0x20200000 0xc000 0x23>;
        pinctrl-names = "internal_eth_pins";
        pinctrl-0 = <0x11>;
        mc_val = <0x4be04>;
        internal_phy = <0x1>;
        phandle = <0x97>;
    };

This cut from meson-sm1-sei610.dtb and it isn't work on X96Air: 

        ethernet@ff3f0000 {
            compatible = "amlogic,meson-axg-dwmac", "snps,dwmac-3.70a", "snps,dwmac";
            reg = <0x0 0xff3f0000 0x0 0x10000 0x0 0xff634540 0x0 0x8>;
            interrupts = <0x0 0x8 0x4>;
            interrupt-names = "macirq";
            clocks = <0x5 0x26 0x5 0x2 0x5 0xd>;
            clock-names = "stmmaceth", "clkin0", "clkin1";
            rx-fifo-depth = <0x1000>;
            tx-fifo-depth = <0x800>;
            status = "okay";
            power-domains = <0x6 0x6>;
            phy-handle = <0x7>;
            phy-mode = "rmii";

            mdio {
                #address-cells = <0x1>;
                #size-cells = <0x0>;
                compatible = "snps,dwmac-mdio";
                phandle = <0x10>;
            };
        };

 

Link to comment
Share on other sites
NicoD

NicoD

Posted
Posted
On 12/3/2019 at 10:38 AM, Sergey2k said:

-- Install /udisk/aml_autoscript.zip

...

Verifying update package...

E:footer is wrong

Update package verification took 0.1 s (result 1).

E:Signature verification failed

E:error: 21

Installation aborted.

Hi @Sergey2k . I finally managed to get my X96 air out of the box. I tried armbian, but got this same message. I tried different images, but I'm unable to upload the bootloader. 
I've got the same error message after the reboot of the update. I ain't got no buttons on mine, someone said something of using the reset button. Ain't got that I guess. 
How did you fix this please? Cheers.

Link to comment
Share on other sites
NicoD

NicoD

Posted
Posted
58 minutes ago, amirul said:

toothpick in the AV jack?

 

57 minutes ago, Sergey2k said:

Reset button into audio jack. You can use toothpick, for example.

Thank you. That works. Cheers
Edit : 
Thanks @balbes150 for the images and fix. 
I couldn't start earlier with it(Jetson Nano), now I start with it I can immediately do all my tests. Thanks for the awesome work.

Link to comment
Share on other sites
NicoD

NicoD

Posted
Posted
6 hours ago, Sergey2k said:

What components do work? What DTB file do you use? I can't see worked WIFI and wired ethernet simultaneously.

Everything works for me. I'm using meson-sm1-sei610.dtb. And the fix of Balbes for the color.
I don't have ethernet to test. But wifi works well, colors are good. Temperature is shown. It can get toasty in the box. I let it go up to 90.5C in a 1h maxed out test. So no throttling happening. But it's not going to go any higher. 
I'll do some ethernet tests when I installed x11vnc.

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept