Jump to content

Armbian for Amlogic S805 and S802/S812

masteripper

By masteripper
in Amlogic CPU Boxes

 Share

Recommended Posts

RaptorSDS

RaptorSDS

Posted
Posted

i think thats normal because your stock ones has a GUI and /usr/bin/sh should be your shell (script) that start the GUI ; now you can go forward and start the new 20.05 or the 19.xx armbian image from usb and than you can interact through your serial terminal with the image when it has no GUI

Link to comment
Share on other sites
godfatheroo7

godfatheroo7

Posted
Posted (edited)

That's the point now, this is the log from 20.05 through serial pins.

 

Just checked it:

 

[    0.000000] Booting Linux on physical CPU 0x200
[    0.000000] Linux version 5.6.0-rc2-aml-s812 (root@vbox) (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #trunk SMP Fri Feb 28 14:11:20 MSK 2020
[    0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: MINIX NEO-X8
 

 

At the HDMI port is a sort of snow image, nothing can be done there.

 

The boot process stops at 5:29 :

 

[    5.059398] ehci-exynos: EHCI Exynos driver
[    5.063544] ehci-atmel: EHCI Atmel driver
[    5.067540] tegra-ehci: Tegra EHCI driver
[    5.071530] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    5.077629] ohci-pci: OHCI PCI platform driver
[    5.082052] ohci-platform: OHCI generic platform driver
[    5.087331] SPEAr-ohci: OHCI SPEAr driver
[    5.091286] ohci-st: OHCI STMicroelectronics driver
[    5.096137] ohci-atmel: OHCI Atmel driver
[    5.100440] usbcore: registered new interface driver usb-storage
[    5.108922] i2c /dev entries driver
[    5.122059] meson_wdt c1109900.watchdog: Watchdog enabled (timeout=30 sec, nowayout=0)
[    5.126857] sdhci: Secure Digital Host Controller Interface driver
[    5.131452] sdhci: Copyright(c) Pierre Ossman
[    5.135610] Synopsys Designware Multimedia Card Interface Driver
[    5.141475] sdhci-pltfm: SDHCI platform and OF driver helper
[    5.147806] ledtrig-cpu: registered to indicate activity on CPUs
[    5.152815] usbcore: registered new interface driver usbhid
[    5.157987] usbhid: USB HID core driver
[    5.163779] NET: Registered protocol family 10
[    5.166656] Segment Routing with IPv6
[    5.169903] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    5.176022] NET: Registered protocol family 17
[    5.180183] can: controller area network core (rev 20170425 abi 9)
[    5.186350] NET: Registered protocol family 29
[    5.190754] can: raw protocol (rev 20170425)
[    5.194990] can: broadcast manager protocol (rev 20170425 t)
[    5.200634] can: netlink gateway (rev 20190810) max_hops=1
[    5.206287] Key type dns_resolver registered
[    5.210534] ThumbEE CPU extension supported.
[    5.214584] Registering SWP/SWPB emulation handler
[    5.219504] Loading compiled-in X.509 certificates
[    5.225301] Btrfs loaded, crc32c=crc32c-generic
[    5.237464] hctosys: unable to open rtc device (rtc0)
[    5.238684] Freeing unused kernel memory: 2048K
[    5.298395] Run /init as init process
[    5.298831] process '/usr/bin/sh' started with executable stack
 

And then it just does not accept key-stroke through serial.

 

Edited by godfatheroo7
Link to comment
Share on other sites
RaptorSDS

RaptorSDS

Posted
Posted

do you edit the uEnv.ini with the right dtb ( minix8 or MXiii-plus or m8s) , normally it should get till 40.xxx or 80.xxx with many i2c network things CPU core starting and other stuff

like on page 15 the secound post from "gmytis" the secound hidden content 

there should at start 0.xxx some dtb menu like

Quote

      Multi dtb tool version: v2 .
      Multi dtb detected, support 6 dtbs.
        aml_dt soc: m8 platform: k200 variant: 2gsdhc
        dtb 0 soc: m8                 plat: k200               vari: 2gsdhc          
        dtb 1 soc: m8                 plat: k200               vari: 2gsdio          
        dtb 2 soc: m8                 plat: k200               vari: sdhc            
        dtb 3 soc: m8                 plat: k200               vari: sdio            
        dtb 4 soc: m8m2               plat: n200               vari: 1G              
        dtb 5 soc: m8m2               plat: n200               vari: 2G              
      Find match dtb: 0
vpu driver detect cpu type: m8

 

Link to comment
Share on other sites
RaptorSDS

RaptorSDS

Posted
Posted
2 hours ago, godfatheroo7 said:

While using MXIII-dtb on my minix, I got some further... the shell in a matter of fact... no eth0 unfortunately

 

meson8b-dwmac c9410000.ethernet: ignoring dependency for device

 

 

eth0 does not exist...

 

thats look like a promising way ; maybe you can make a hardware list with some commands ->Hardware list commands

Link to comment
Share on other sites
godfatheroo7

godfatheroo7

Posted
Posted

 

Interesting, trying the MXQ file and i get this when trying to ifup eth0

 

 

None of the LS hardware tools are present btw..

 

Quote

 

root@aml-s812:~# ifup eth0
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

[  154.488638] meson8b-dwmac c9410000.ethernet eth0: PHY [stmmac-0:00] driver [SMSC LAN8710/LAN8720] (irq=41)
[  154.598261] meson8b-dwmac c9410000.ethernet: Failed to reset the dma
[  154.598984] meson8b-dwmac c9410000.ethernet eth0: stmmac_hw_setup: DMA engine initialization failed
[  154.607996] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Hw setup failed
RTNETLINK answers: Device or resource busy
Listening on LPF/eth0/da:b3:cb:bb:ad:f3
Sending on   LPF/eth0/da:b3:cb:bb:ad:f3
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
send_packet: Network is down
dhclient.c:2445: Failed to send 300 byte long packet over eth0 interface.
receive_packet failed on eth0: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
send_packet: Network is down
dhclient.c:2445: Failed to send 300 byte long packet over eth0 interface.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16

 


 

Link to comment
Share on other sites
godfatheroo7

godfatheroo7

Posted
Posted

Nah... it says the same:

 

[  180.208446] meson8b-dwmac c9410000.ethernet eth0: PHY [stmmac-0:00] driver [SMSC LAN8710/LAN8720]
[  180.318098] meson8b-dwmac c9410000.ethernet: Failed to reset the dma
[  180.318821] meson8b-dwmac c9410000.ethernet eth0: stmmac_hw_setup: DMA engine initialization failed
[  180.327839] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Hw setup failed
 

After some googling:

 

https://forum.khadas.com/t/vim2-ethernet-problem-with-mainline-kernel/5817

 

And a possible out-of-date u-boot:

 

Link to comment
Share on other sites
RaptorSDS

RaptorSDS

Posted
Posted (edited)

@balbes150 please can you answer my question , can you  insert the rtl8723bs driver in the 20.xx image ?

  i found that the bin files are inside the image already only the .ko file missing .

is it possible to activate the SDIO that the kernel recognize the Wireless card ? or can i copy the old .ko file from 3.10 kernel image ?

 

 

R8723BS Driver -> 1x at github torvalds tree and 1xanother  https://github.com/muhviehstah/r8723bs

Edited by RaptorSDS
new information
Link to comment
Share on other sites
balbes150

balbes150

Posted
Posted

version 20200331 with 5.6 core for s805 and s812 (HDMI does not work). Before I had time to write the announcement, I had already submitted the verification report .... :)

 

 

 

 

 

On 3/26/2020 at 10:01 PM, RaptorSDS said:

can you answer my question , can you  insert the rtl8723bs driver in the 20.xx image ?

Without adding support to the DTB, there is no point in the driver.

Link to comment
Share on other sites
RaptorSDS

RaptorSDS

Posted
Posted
36 minutes ago, balbes150 said:

Without adding support to the DTB, there is no point in the driver.

while searching for the driver i found an entry by Jerome Brunet from the kernel team (Spinics.net) Kernel Patch meson CLK cycle from 2017 where he says that he has got RTL8723bs running on mxiii plus s812 ( but i think with the old 3.10 ) i have already sent him an EMAIL but still no answer if he has activated the card with the new kernel
which DTSI /DTS file did you use for the DTB m8s ? i usually try to copy the GPIO pins from the old (3.10) DTS files to the new one

the r8723bs.ko file missing in net/wireless respectively drivers/staging folder  ( i can not build it from torvald linux no rules in makefile)
 

Translated with www.DeepL.com/Translator (free version)

Link to comment
Share on other sites
balbes150

balbes150

Posted
Posted
7 minutes ago, RaptorSDS said:

the r8723bs.ko file missing in net/wireless respectively drivers/staging folder  ( i can not build it from torvald linux no rules in makefile)

I will try to enable the driver, but I doubt it will help.

Link to comment
Share on other sites
nirkon

nirkon

Posted
Posted (edited)

Hi @balbes150, first off thanks for all the great work!

 

I've been trying to get my "OTT M8S" android box to boot into armbian a couple of times over the years, since the quarantine I have some more time now.

 

but I couldn't for the life of me get it working, first off with microsd card it boots to logo and then black screen or straight to android.

With USB I had more luck

 

I tried both the old armbian versions (pre kernel v5) and the newest release, probably tried all the relevant DTB files multiple times (meson8m2_n200_2G,k200b,m8s,mxiii,n200c etc....)

The furthest I've got is this:

using latest version from your yandex with "meson8m2-m8s.dtb" (changed in uEnv.ini and copied and renamed to dtb.img) , the logo shows up, and is then replaced by a multi-colored pixelated screen, then it hangs.

However, something did happen while the screen is pixelated/grainy since the armbian_first_run.txt was renamed to armbian_first_run.old and I think the dtb.img was gone.

 

This is a pic of my android box hardware

https://ibb.co/Vw6ftnP

 

Any ideas? are the DTB files incorrect for this model? how do I go about getting logs/creating my own dtb etc..

As far as I'm concered, this thing either get linux or donated to science, no need for the android on it (so maybe it can be flashed directly to the EMMC somehow)

 

thanks!!

Edited by nirkon
Link to comment
Share on other sites
RaptorSDS

RaptorSDS

Posted
Posted
1 hour ago, balbes150 said:

Version 20200404. Added the WiFi modules. But I doubt it will help launch the built-in wifi.

thanks a lot ; i added some Gpio and uart settingd from dts 3.10 to the dts from 5.6 maybe that solve it ;

Link to comment
Share on other sites
RaptorSDS

RaptorSDS

Posted
Posted

@nirkon most all 5.x Kernel version (20.xx and NEXT) are without HDMI !! , its normal to have pixel logo because they only work with Ethernet(SSH) and/or Serial Console (SSH) also 5.x(20.xx ) and 4.x Version (19.xx) version need more time for first startup like 3 till 8 minutes , ( most times goes to timeframe 19.xxx secound and than you have to wait till login show up) ; for 20.xx and 19.xx version only need to edit uENV.ini !!.

at the old kernel 3.10 (version 5.xx) you need for hdmi the desktop versions and also have time for first start about 5 -10 minutes, this are the ones that use the rename to dtb.img trick !!

1
Link to comment
Share on other sites
nirkon

nirkon

Posted
Posted
43 minutes ago, RaptorSDS said:

@nirkon most all 5.x Kernel version (20.xx and NEXT) are without HDMI !! , its normal to have pixel logo because they only work with Ethernet(SSH) and/or Serial Console (SSH) also 5.x(20.xx ) and 4.x Version (19.xx) version need more time for first startup like 3 till 8 minutes , ( most times goes to timeframe 19.xxx secound and than you have to wait till login show up) ; for 20.xx and 19.xx version only need to edit uENV.ini !!.

at the old kernel 3.10 (version 5.xx) you need for hdmi the desktop versions and also have time for first start about 5 -10 minutes, this are the ones that use the rename to dtb.img trick !!

I see, thanks for clarifying.

OK I will try to connect ethernet and see if I get an IP to SSH to.

Though I think I need video output for my uses, I couldn't get it to work with the old kernel (hang on black screen), would the DTB files from 5.xx be able to work on 3.xx?

 

thanks

Link to comment
Share on other sites
RaptorSDS

RaptorSDS

Posted
Posted
9 hours ago, nirkon said:

I see, thanks for clarifying.

OK I will try to connect ethernet and see if I get an IP to SSH to.

Though I think I need video output for my uses, I couldn't get it to work with the old kernel (hang on black screen), would the DTB files from 5.xx be able to work on 3.xx?

 

thanks

No thats not possible because they use different describe for everything,

Link to comment
Share on other sites
balbes150

balbes150

Posted
Posted

 

15 hours ago, nirkon said:

Any ideas?

To get logs, you need the UART console.

 

15 hours ago, nirkon said:

creating my own dtb

Search the forum for information about the DTC utility.

 

 

Link to comment
Share on other sites
Nikeb

Nikeb

Posted
Posted

Hi guys

 

I m sorry, i try to read all the pages and follow the instructions, but i m trying to make my minix neo x8-h plus to work with the aml_autoscript.zip

 

I downloaded the brand new image updated yesterday 04/04 for the s812 Armbian_20.05.1_Aml-s812_bionic_current_5.6.0_20200404.img

Flashed into a USB stick

insert it into the minix usb

boot it with the recovery button

when ask to update with EXT it finds the aml.autoscript.zip but said

 

Opening update package
verifyng update package
footer is wrong
signature verification failed
Installation aborted.

 

I saw some posts, i download the boot.src file and put in the root of the usb but still same error.

I try to copy the dbt image (try some of them) rename them to dtb.img and place them in the root but still same error

 

What do you think i could do to make it boot with usb?

 

Thanks in advantage.

 

Nikeb

 

Link to comment
Share on other sites
Nikeb

Nikeb

Posted
Posted
33 minutes ago, RaptorSDS said:

@nikeb first if the autoscript did not install also no sd or usb boot ; secound like my answer to nikron 20.05 you must edit uENV.ini not rename dtb also 20.05 have no HDMI  !!!!!

maybe start  with the 5.xx version (kernel 3.10)  -> under OLD balbes150 ROMS

 

Hi Raptor thanks for your answer,

 

I tried to download 5.78 (the latest of the OLD folder) but i get the same error.

I correct the uENV.ini pointing to the dtb of the minix but getting always the footer wrong error again.

I even try to copy the dtb of minix in the root folder but nothing change.

 

Is that because i m using a USB ? I m feeling that all writing images could have corrupted it

Today i should get the brand new A1 SD Card so i would try those, but my USB is a good one.

 

Maybe i could use his USB Burning Tool to put on the NAND directly the OS but i didn't find anything about it

I can even connect to my minix via SSH if it helps (has Android 4.4.2 atm)

 

Don't know what to do

Thanks for your help

 

Link to comment
Share on other sites
Nikeb

Nikeb

Posted
Posted
4 hours ago, balbes150 said:

 

s812 activation multi-boot is possible only with SD card

 

 

 

 

Hi guys

 

I made the config on the SD Card and the minix is correctly booting on it (without pressing any button)

 

 download 5.78 (the latest of the OLD folder)

 correct the uENV.ini pointing to the dtb of the minix

 copy the dtb of minix in the root folder

 

All i can see on the TV after the android splash screen is first the noise tv screen for a moment, then it switch to one color.

First boot was grey, after that orange, the third boot is now yellow.

 

I repeat all with a new SD Card, same results.

If i take off the SD the minix OS boot correctly.

 

Should i check something?

Thanks 

 

 

Link to comment
Share on other sites
ntux

ntux

Posted
Posted

hello @balbes150, thanks again for your work on this platform, it's highly appreciated.

 

I installed your 2020/03/31 build of Buster Armbian, and I'm trying to build a custom kernel to have all it takes to be able to run docker on my Minix X8-H Plus (S812). It's booting fine using your kernel, but as soon as I try to build a kernel either from your sample config (the one at /boot/config-***) or one I make myself (make multi_v7_defconfig), after reboot I don't have the ethernet interface loading anymore at boot time, and get these errors (that's the only ones related to ethernet):

  

[    2.204672] meson8b-dwmac c9410000.ethernet: ignoring dependency for device, assuming no driver
[    2.208060] stmmaceth c9410000.ethernet: ignoring dependency for device, assuming no driver

 

And of course I don't get network connectivity any more, I had to check that using uart.

 

Do you know of any particular config you had to make in order to make your kernel working?

 

Thanks a lot in advance

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