Jump to content

Armbian for Amlogic S805 and S802/S812

masteripper

By masteripper
in Amlogic CPU Boxes

 Share

Recommended Posts

Junoxe

Junoxe

Posted
Posted
  On 5/3/2020 at 3:28 PM, balbes150 said:

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

Expand  

Yea, its for old one. But in may be checking it, You could say which old kernel dtb to use? Or its not working that way?

Thanks anyway. :)

balbes150

balbes150

Posted
Posted

Anyone can try the new version of LE 20200503 with the latest version of the kernel from Martin.

 

RaptorSDS

RaptorSDS

Posted
Posted
  On 5/3/2020 at 5:17 PM, balbes150 said:

Anyone can try the new version of LE 20200503 with the latest version of the kernel from Martin.

 

Expand  

thanks to you and martin ; where do you have the image yandisk s8xx ? or yandisk Armbian S812 ?

RaptorSDS

RaptorSDS

Posted
Posted
  On 5/3/2020 at 5:17 PM, balbes150 said:

Anyone can try the new version of LE 20200503 with the latest version of the kernel from Martin.

 

Expand  

i tested it , first try m8s.dtb , HDMI ok , bootscreen and menu works , wlan (externel usb rtl 888x) was detected and wifi found but can not connect to router , mouse/keyboard  are a bit slow like a mini lag  (your 5.7 desktop is more responsive) , too fast clicking (reconnect to wlan ) ended with crash to bootlogo and freeze , i did not see wpa supplicant folder maybe thats the wifi problem , ! anything other i should test inside image ?

Diamond

Diamond

Posted
Posted
  On 5/3/2020 at 6:46 AM, Diamond said:

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)

 

Expand  

Same issue on S805 Armbian_20.05.3_Aml-s812_buster_current_5.7.0-rc3_desktop_20200503.img

uname -a
Linux aml-s805 5.7.0-rc3-aml-s812 #20.05.3 SMP Sun May 3 12:19:42 MSK 2020 armv7l GNU/Linux

 

 

 

Junoxe

Junoxe

Posted
Posted
  On 5/3/2020 at 5:17 PM, balbes150 said:

Anyone can try the new version of LE 20200503 with the latest version of the kernel from Martin.

 

Expand  

Yea. I try to catch to birds at once. First i installed old LE 8.2.5 into NAND. Then i updated to 9.0.2 (3.10.108) using manual update in LE settings.

Then i tried with LE 20200503 (copied to /storage/.update/ folder an img.gz file). But says missing (source) kernel.img or SYSTEM.

Updating with tar (or with 4 files from target folder – OpenELEC way) generates error in check_update. Cannot update to 9.2 to NAND. I run 202004XX version on SD.

@balbes150 Is any way to update 9.0.2 installed on NAND to LE 20200503?

 

Then i will try with Armbian. :)

 

 

RaptorSDS

RaptorSDS

Posted
Posted

@balbes150 i wrote yesterday with martin and he told me that he release a new patch for SDIO/MX/MMC controller on 04.05 or 03.05 please can you inform me when your new Image has this patch inside ?

balbes150

balbes150

Posted
Posted
  On 5/4/2020 at 6:33 PM, Junoxe said:

Is any way to update 9.0.2 installed on NAND to LE 20200503?

Expand  

No, that's not possible. These are completely different kernel.

 

  On 5/5/2020 at 5:55 AM, RaptorSDS said:

i wrote yesterday with martin and he told me that he release a new patch for SDIO/MX/MMC controller on 04.05 or 03.05 please can you inform me when your new Image has this patch inside ?

Expand  

New versions are released as soon as I have the opportunity. If you want, you can build the new version yourself (switch the kernel sources to the new Martin branch).

RaptorSDS

RaptorSDS

Posted
Posted

@balbes150 i found a problem inside 5.7rc4 dts file for m8s error at usb@9c90040000 dr_mode="Peripheral" do not work , old setting dr_mode="host" work (i have wrote Martin already)

RaptorSDS

RaptorSDS

Posted
Posted

@balbes150 i tested the new LE , first boot my box with m8s.dtb now , HDMI work , wlan0 are detected and load but also the old 2014 driver (there make the problems ) eth0 detected and dhcp work but still no internet access (no add-on repro found / can not connect )  , did you need any logs or infos ?

RaptorSDS

RaptorSDS

Posted
Posted

@balbes150 some more information from  Armbian Update. Ver 20200506 , Sometimes Restart did not work ( it stop with black screen and watchdog0 do not stop or meson@sdhc busy CMD25) another thing is that after screensaver activate (hdmi goes blank and you wake up the box) the screen has a rosa overlay over all and it do not go away ( only with restart of the box) 

RaptorSDS

RaptorSDS

Posted
Posted

@balbes150 i found the clue for wifi (rtl8723bs) problem with my box and maybe i can get a fix with the help from Martin , its abig step to have onboard wifi work in kernel5 for me , please can you make a new  image  when martin and i find the fix , i would like move my linux server  to the kernel 5

RaptorSDS

RaptorSDS

Posted
Posted

i found the clue today and also martin got the infos today ( the r8723 has a 3 state Wlan_disable pin   / low -> sdio on wlan off , open-> sdio off , high -> sdio on wlan on )

balbes150

balbes150

Posted
Posted
  On 5/17/2020 at 2:35 PM, RaptorSDS said:

i found the clue today and also martin got the infos today ( the r8723 has a 3 state Wlan_disable pin   / low -> sdio on wlan off , open-> sdio off , high -> sdio on wlan on )

Expand  

update image ver 20200518

elbuit

elbuit

Posted
Posted (edited)

Hi everyone.

 

I'm trying armbian in an old S805 tv box (Chiptrip MXV).

I tried all dtb but without any success, it shows s805 logo at the beginning  but after a few seconds my monitor says out of range .

So I connected a serial adapter and although it has no hdmi output (out of range) it boots with meson8b-mxq.dtb and detects ethernet.

WIFI seems to be not detected (the chip shows rtl8723bs)

I hope that could be useful for someone and reuse an old cheap TV box for custom projects. I can connect through ssh and configure it.

 

This is my serial output showing the process:

  Reveal hidden contents

 

-Anyone knows if there ara any solution to hdmi and wifi for this device?

 

Thanks

Edited by Igor
spoilers
RaptorSDS

RaptorSDS

Posted
Posted

@elbuit  nice to see that you get a linux on your box , first do use the desktop image ? secound this linux version kernel 5.xx are  beta version  ,also the mwson8b-mxq.dtb file do not start your wlan because still some information for wlan missing inside the dtb ,please can start android and look at serial terminal for wlan pin, irq and clk infos (GPIOX_10 or pin-166 or something)

balbes150

balbes150

Posted
Posted

Update. Version 20200520.

Please note that there would be no confusion, now the image date is equal to the number (date), the version of the source code of the Martin kernel.

 

 

 

  On 5/20/2020 at 5:46 PM, elbuit said:

-Anyone knows if there ara any solution to hdmi and wifi for this device?

Expand  

1. To work with HDMI, you need a TV with a resolution of 1080 (fullHD).

2.  USB WiFi

balbes150

balbes150

Posted
Posted

Update version 20200523.

Good news. Martin solved the color problem. now all the colors in DE are displayed correctly. 

 

 

 

RaptorSDS

RaptorSDS

Posted
Posted

@balbes150 some feedback

1. after screensaver goes active (switch screen black/ off) and back to destktop (wakeup) screen still has rosa overlay

2. bluetooth are on rfkill but i got a two error first: rfkill has bluetooth with softblock ,secound after unblock i got error FW rtl_bt/r8723bs_fw.bin not found ( inside /usr/lib/firmware/rtl_bt/ only r8723b_fw.bin inside ) after rename files bluetooth work ( discover able and connect able )

 

 

also add to /etc/modprobe/r8723bs.conf the line rtw_btcoex_enable=1

elbuit

elbuit

Posted
Posted
  On 5/20/2020 at 8:33 PM, RaptorSDS said:

@elbuit  nice to see that you get a linux on your box , first do use the desktop image ? secound this linux version kernel 5.xx are  beta version  ,also the mwson8b-mxq.dtb file do not start your wlan because still some information for wlan missing inside the dtb ,please can start android and look at serial terminal for wlan pin, irq and clk infos (GPIOX_10 or pin-166 or something)

Expand  

Thanks @RaptorSDS

I've extracted the dtb file from android image (kernel 3.10):

  Quote

dd if=/dev/block/boot of=/sdcard/boot.img

Expand  

and from https://github.com/PabloCastellano/extract-dtb

  Quote

$ ./extract-dtb/extract-dtb.py boot.img
Dumped 00_kernel, start=0 end=2521
Dumped 01_dtbdump_`@0M<p.dtb, start=2521 end=7903232
Dumped 02_dtbdump_m8b_m201_1G.dtb, start=7903232 end=7927808
Dumped 03_dtbdump_m8b_m201_512M.dtb, start=7927808 end=33554432
Extracted 3 appended dtbs + kernel to dtb

Expand  

 

So as my device is a 1gb i think that dtb should be 02_dtbdump_m8b_m201_1G.dtb

so I tried to booting using this dtb but without success.

I also decompiled and compiled again :
 

  Reveal hidden contents

 

But it get stucked on Starting kernel ...   with both dtb, extracted and recompiled.

 

  Reveal hidden contents

                                                       

So I think that I should build a dtb mixing from extracted android and meson8b-mxq.dtb that comes with armbian.

 

  On 5/21/2020 at 12:29 PM, balbes150 said:

Update. Version 20200520.

Please note that there would be no confusion, now the image date is equal to the number (date), the version of the source code of the Martin kernel.

 

 

 

1. To work with HDMI, you need a TV with a resolution of 1080 (fullHD).

2.  USB WiFi

Expand  

Thanks @balbes150 but my monitor supports 1080 (and this resolution works with android and alexelec firmware)

It should be something in dtb, I don't understand dtb files (yet).

do you know if it is possible to change to a newer generic u-boot , or u-boot is specific for each device?

 

Talking about wifi, it  doesn't mind me, I only want to use ethernet and this works fine, but I asume that it should depend on dtb and linux loaded modules.

 

 

by the way, I tried to run docker (apt install docker.io because armbian-config don't install correctly docker) and It shows that /dev/mqueue doesn't exists:

  Reveal hidden contents

 

thanks.

RaptorSDS

RaptorSDS

Posted
Posted

@elbuit nice thanks for that hard work

dtb-> you can not use 3.10 dtb also not recompile version for 5.x image because 5.x has many different names for functions and systems .

pleasae can you attached your decompile dtb ( your dts file) maybe we can you use same  wlan power pin like m8s box

 

there was somebody in this thread ( maybe from last year ) that already test to run docker but there was no new infos maybe you can contact him

 

monitor i think its because kernel do not support menson8b video chip at the moment (or like the wlan do not have the right information), we get last month  the menson8m2 (mali450-chip) working  .

balbes150

balbes150

Posted
Posted
  On 5/24/2020 at 8:21 PM, RaptorSDS said:

monitor i think its because kernel do not support menson8b video chip at the moment (or like the wlan do not have the right information), we get last month  the menson8m2 (mali450-chip) working  .

Expand  

HDMI works on the s805 with all DTBS from the image composition. If there is no image, you need to check the connection and hardware used. I have two TV boxes s805 HDMI works.

s812us

s812us

Posted
Posted

Hello @balbes150

Thank you very much for your hard work and support for breathing life into our old boxes!

 

I just installed latest bionic from your mega drive on my SD card.

My box is titled "OTT M8s+" (S812 2G/8G) and it works almost fully with the included "meson8m2-mxiii-plus.dtb" file - cpu/memory/network all work!

However it seems it cant detect any emmc memory (i have android on emmc and it boots fine).

Is it because the dtb file is wrong or any other cause? (i have uploaded an armbianmonitor log to http://ix.io/2nkl)

also i couldnt find any nand/emmc installation files on the file system (is it because the emmc is not detected or any other reason?)

 

Would be very grateful for any insights,

Thanks again!

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