Jump to content

Armbian for Amlogic S805 and S802/S812

masteripper

By masteripper
in Amlogic CPU Boxes

 Share

Recommended Posts

Emulti

Emulti

Posted
Posted

Balbes150, thank you for the mailing list link, it's very informative.

For SDHC support on xdarklight's latest kernel on the meson-mx-integration-5.8-20200411 branch, (Linux-5.6.0-367105-ge753682cfb70) it's necessary to enable MMC_MESON_MX_SDHC and COMMON_CLK_MESON_MX_SDHC for SDHC support.

I had made the mistake of using multi_v7_defconfig, which of course does not include such new options. Now I made a meson32 .config from scratch.

 

There is still much work for me to do on the DTB necessary to get regulator, DVFS, frequency scaling and all interrupts working correctly, but the iperf3 tests show about 94 Mbit/sec on 100Mbit link in each direction, with no re-tries.

 

Emulti

RaptorSDS

RaptorSDS

Posted
Posted

@Emulti It looks like you have a lot of experience with DTS/DTB, I'm still trying to activate my wlan chip(RTL8723) that runs on SDIO. I've already taken a lot of information from the DTS in the kernel 3.xx but it's still not recognized(IRQ ; GPIO; SELECT PIN). Have you already read or reached something in this direction ?

balbes150

balbes150

Posted
Posted

Good news. :)

Thanks to the work done by Martin and the developers of Libreelec (Chewitt etc). An early alpha version of Libreelec with a 5.6 core is now available.This version is intended for General evaluation of the system's ability to run on s805\s802\s812. This version uses a new DTB configuration mechanism that is common with the latest Armbian versions for all RK+AW+AML platforms. You need to edit the file to configure it (uEnv.txt). If you want to test this system, I can give you a link to the images (provided that there is a report on the results of the launch). If multi-loading is already enabled on your device, the system should start automatically after setting up DTB.

RaptorSDS

RaptorSDS

Posted
Posted

wow nice to see , please i would like test libreelec , is the change back to ambian without problems ? i read that sometime people start libreelec and than have problems booting armbian again on 3.xx kernel

 

Junoxe

Junoxe

Posted
Posted
  On 4/30/2020 at 10:27 AM, balbes150 said:

Good news. :)

 If multi-loading is already enabled on your device, the system should start automatically after setting up DTB.

Expand  

Good news. :)

Is it possible to test S812H (Wetek Core)? As i understood its version of dualboot LibreElec and Armbian?

 

Little request. Is there any simple step by step guid how to enable multi-boot? I read almost all and there are just links to other links. I didnt find guid how to enable it. Is it one file?

balbes150

balbes150

Posted
Posted
  On 4/30/2020 at 10:33 AM, RaptorSDS said:

is the change back to ambian without problems ? i read that sometime people start libreelec and than have problems booting armbian again on 3.xx kernel

 

Expand  

There are no compatibility problems between Libreelec and Armbian in principle (these are friendly systems that help each other develop). You may have confused it with the launch of corelec. Yes, there is a big problem from this launch on the AML s9xx platform. After that, you need to completely restore the regular Android firmware and re-activate the universal multi-boot.

 

  On 4/30/2020 at 10:48 AM, Junoxe said:

Is it possible to test S812H (Wetek Core)? As i understood its version of dualboot LibreElec and Armbian?

Expand  

This should also work on Wetek (s812).

 

  On 4/30/2020 at 10:48 AM, Junoxe said:

As i understood its version of dualboot LibreElec and Armbian?

Expand  

No, it's not two systems together. This is an option to run both of these systems on S8xx (if multi-boot is enabled). As part of  image LE is files to activate the multi-boot. But for Wetek (if I'm not confused), additional steps are needed (and perhaps add file). Details on how to activate multi-boot on Wetek is on the forum LE in the topic about s812 (there you can also take the necessary file).

 

 

Test Image LE for s8xx (s805 s802 s812) dir *-s8xx

https://yadi.sk/d/8vNYuuxynz1L0w

RaptorSDS

RaptorSDS

Posted
Posted

UART LOG with meson8m2-m8s.dtb

 

  Reveal hidden contents

 

and log file with meson8m2-mxiii.dtb and meson8m2-mxiii-plus.dtb are same

 

  Reveal hidden contents

 

RaptorSDS

RaptorSDS

Posted
Posted
  On 4/30/2020 at 1:55 PM, balbes150 said:

What TV is the device connected to ?

Expand  

first try was headless

 

after you question i connect to my Samsung TV ( FHD 32 inch)

with meson8m2-m8s.dtb it is like above no output , same error

with meson8m2-mxiii-plus.dtb i got libreelec logo and shell but after 30 sek restart and than shutdown (log attached)

error was

[   73.004257] [1087]: Failed to unmount /flash: Device or resource busy
[   73.010621] systemd-shutdown[1]: Failed to finalize  file systems, loop devices, ignoring
[   73.044806]QA9:A;SVN:74E;POC:3FF;STS:0;BOOT:0;INIT:0;READ:0;CHECK:0;PASS:0;

than restart

 

[   76.956916] [1135]: Failed to unmount /flash: Device or resource busy
[   76.963401] systemd-shutdown[1]: Failed to finalize  file systems, loop devices, ignoring

than shutdown

  Reveal hidden contents

 

balbes150

balbes150

Posted
Posted

After the first start and extension of the partition, the system automatically reboots. This is normal behavior. At the second start, the configuration wizard should appear.

RaptorSDS

RaptorSDS

Posted
Posted
  On 4/30/2020 at 5:05 PM, balbes150 said:

After the first start and extension of the partition, the system automatically reboots. This is normal behavior. At the second start, the configuration wizard should appear.

Expand  

i start with a fresh flash of sd card and make a new run

balbes150

balbes150

Posted
Posted
  On 5/1/2020 at 9:03 AM, RaptorSDS said:

its boot to librelec logo and shell  ,no desktop

Expand  

Perhaps the reason is the errors that I see in the u-boot log when it starts (errors of the u-boot itself). What is connected to the USB ports ?

balbes150

balbes150

Posted
Posted

The new version of the images for s8xx (s805\s802\s812) kernel 5.x.

The main feature, there is support for a graphical desktop. Please note that there is no text console. The initial configuration must be performed either via UART or SSH. Starting the desktop takes a long time (until the image appears). The desktop background is dark and the mouse cursor is also dark, so the cursor is not visible on the desktop, it can only be seen if you move it to the menu bar at the top of the screen. This is a very early version and a lot of things don't work in it. This version is only for General evaluation of the HDMI launch.

 

https://yadi.sk/d/-MwoNitZonsRCg

balbes150

balbes150

Posted
Posted

Checked Out Debian. It works better, the cursor is displayed normally. :)

I tried to play a test video file. I used a USB card for sound. When you first connect the USB card, the system started to slow down after 10 seconds. Pulled out and plugged the USB again. The sound has started to work, but sometimes there are distortions. I checked YouTube in  browser. Video works with sound not full-screen, in a normal window. The test sample is Tronsmart MXIII-Plus (S812 2\16 1Gbit LAN + USB FAN + USB sound).

Emulti

Emulti

Posted
Posted

@RaptorSDS No, I am not an experienced Device Tree editor.

But, armed with a copy of the Device Tree specification and fragments of DTB that worked with the old Amlogic kernels and Android,  I hope to be able to learn enough to make some missing features work, if there is support in the code.

RaptorSDS

RaptorSDS

Posted
Posted
  On 5/1/2020 at 3:20 PM, Emulti said:

@RaptorSDS No, I am not an experienced Device Tree editor.

But, armed with a copy of the Device Tree specification and fragments of DTB that worked with the old Amlogic kernels and Android,  I hope to be able to learn enough to make some missing features work, if there is support in the code.

Expand  

OK  i had same idea and use old dts part and take it to new dts for wifi but still no luck

balbes150

balbes150

Posted
Posted

During the tests, I found out that for USB audio to work, the USB card must be included in the TV box before power is turned on. In this mode, it works in Debian and Ubuntu.

 

In the current version, it is not advisable to connect and disconnect USB devices in the working system until the automatic USB management is fully operational. Power failures occur for the SD card and other devices. This causes damage to the file system and you have to write the image again.

Junoxe

Junoxe

Posted
Posted
  On 4/30/2020 at 10:59 AM, balbes150 said:

Details on how to activate multi-boot on Wetek is on the forum LE in the topic about s812 (there you can also take the necessary file).

Expand  

Thank You very much for information. May be You know what is the name of enabling multiboot universal file?

Junoxe

Junoxe

Posted
Posted (edited)

A little succes. Archlinux.

S812_ArchLinux_20170924_3_10_99 has run on my s812H (Wetek Core). So universal multiboot (s805_autoscript <- is it this?) is enabled. At first asks me about alarm login nd password. Any one knows is it alam/alarm i found in net.

 

So i tried some more attemps to run Armbian as i know multiboot is enabled. Unfortunatelly most of Armbian images dont work. @balbes150 is any info i can give that You can tell whats wrong with Armbian and this Wetek (i have 2 boxes so i dont think both are damaged)?

 

Now i try Armbian_20.05.1_Aml-s812_buster_current_5.6.0_20200404.img.

I have to change default dtb_name in uEnv.ini. My box is meson8m2-n200C.dtb but i dont see this in dtb folder. Which meson8m2 i should use instead?

Edited by Junoxe
Additional question.
Diamond

Diamond

Posted
Posted

I am using S805 box. I am testing Armbian_20.05.3_Aml-s812_buster_legacy_5.6.0_desktop_20200501.img with meson8b-ec100.dtb. The box can boot and start GUI

- It can recognize USB devices

However, there is error:

Message from syslogd@localhost at May  3 06:40:02 ...
 kernel:[  284.025994] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:12]

  

[  284.029429] CPU: 0 PID: 12 Comm: kworker/0:1 Not tainted 5.6.0-aml-s812 #20.05.3
[  284.029556] Hardware name: Amlogic Meson platform
[  284.030073] Workqueue: events dbs_work_handler
[  284.030453] PC is at skb_put+0x0/0x50
[  284.030880] LR is at stmmac_napi_poll_rx+0x8dc/0xca8
[  284.031070] pc : [<c0ebcb7c>]    lr : [<c0d00b04>]    psr: 400f0113
[  284.031242] sp : c02b3a60  ip : 00000000  fp : ed95c580
[  284.031413] r10: ed95d580  r9 : 000005e2  r8 : ec5029c0
[  284.031609] r7 : 00001fe0  r6 : ed95c580  r5 : 00000000  r4 : 000005e2
[  284.031802] r3 : 5ed5f3a9  r2 : 00000000  r1 : 000005e2  r0 : ec5029c0
[  284.032031] Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
[  284.032236] Control: 10c5387d  Table: 2b42c04a  DAC: 00000051
[  284.032513] CPU: 0 PID: 12 Comm: kworker/0:1 Not tainted 5.6.0-aml-s812 #20.05.3
[  284.032630] Hardware name: Amlogic Meson platform
[  284.032938] Workqueue: events dbs_work_handler
[  284.033685] [<c030f744>] (unwind_backtrace) from [<c030ab3c>] (show_stack+0x10/0x14)
[  284.034116] [<c030ab3c>] (show_stack) from [<c0a67020>] (dump_stack+0xc0/0xd4)
[  284.034559] [<c0a67020>] (dump_stack) from [<c03f0e64>] (watchdog_timer_fn+0x20c/0x280)
[  284.035014] [<c03f0e64>] (watchdog_timer_fn) from [<c03ad114>] (__hrtimer_run_queues+0x154/0x200)
[  284.035453] [<c03ad114>] (__hrtimer_run_queues) from [<c03ad950>] (hrtimer_interrupt+0x11c/0x2ac)
[  284.035896] [<c03ad950>] (hrtimer_interrupt) from [<c030e3a8>] (twd_handler+0x30/0x38)
[  284.036372] [<c030e3a8>] (twd_handler) from [<c0397d44>] (handle_percpu_devid_irq+0x78/0x138)
[  284.036885] [<c0397d44>] (handle_percpu_devid_irq) from [<c0391c50>] (generic_handle_irq+0x34/0x44)
[  284.037377] [<c0391c50>] (generic_handle_irq) from [<c039224c>] (__handle_domain_irq+0x5c/0xb4)
[  284.037928] [<c039224c>] (__handle_domain_irq) from [<c0a7ed20>] (gic_handle_irq+0x3c/0x78)
[  284.038397] [<c0a7ed20>] (gic_handle_irq) from [<c0300b0c>] (__irq_svc+0x6c/0x90)
[  284.038583] Exception stack(0xc02b3a10 to 0xc02b3a58)
[  284.038901] 3a00:                                     ec5029c0 000005e2 00000000 5ed5f3a9
[  284.039320] 3a20: 000005e2 00000000 ed95c580 00001fe0 ec5029c0 000005e2 ed95d580 ed95c580
[  284.039660] 3a40: 00000000 c02b3a60 c0d00b04 c0ebcb7c 400f0113 ffffffff
[  284.040147] [<c0300b0c>] (__irq_svc) from [<c0ebcb7c>] (skb_put+0x0/0x50)
[  284.040559] [<c0ebcb7c>] (skb_put) from [<00000000>] (0x0)

 

balbes150

balbes150

Posted
Posted

The new version 20200503. There is support for the text console. Now all settings can be made on the device itself.

balbes150

balbes150

Posted
Posted
  On 5/3/2020 at 2:35 PM, Junoxe said:

None of dtb working with Wetek Core. May be You can look into dtb from Wetek Core that K200_Noob extracted? Its in pasted post.

I tried it as well (on both boxes i have), but no success.

Expand  

Extracted files for the old kernel, they are not suitable for kernel 5.

 

 

For all. Added images of Focal and Bullseye. On Focal and Bulseye, the desktop runs close to the colors.

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