Jump to content

ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)


balbes150

Recommended Posts

3 hours ago, talraash said:

 

@shippy What kind of problems do you have in kodi?  I see low cpu usage in h264/1080p so hw decoding and acceleration work correct in armbian/kodi

 

I haven't installed Armbian yet. Trying to gather enough information to decide if I want to install Android on my TV boxes (e.g., Nexbox A95) or Armbian, with S905W or RK3229.

 

Armbian gives me the ability to install and use many more features, e.g., OpenWrt for networking and WiFi.

 

I do want HW acceleration with Kodi, because I plan to run several concurrent Kodi/SPMC instances for h264/720p streams. Maybe even try Ubuntu multi-seat (2-3 instances)! I am assuming VPU can handle this. The Penta GPU should handle Xorg for multiple I/O.

 

I don't have interest in 1080p/4K streaming.

Link to comment
Share on other sites

Hello,

 

i'm using a MeCool M8S Pro + (s905x - 2Gb ram - 16Gb eMMC)

Armbian 5.44 debian stretch server 3.14.29 works fine.

Armbian 5.44 debian stretch server 4.16.1 doesn't work. It's stuck on the MeCool logo after the OTA Update.

 

Does anyone have an idea to help me to use the Kernel 4.16.1 please ?

Thank you.

Link to comment
Share on other sites

Hello,

In s905w kernel 4.16.1 the internal emmc is not recognized. 

I get 

[    1.863928] mmc1: tuning execution failed: -5
[    1.863953] mmc1: error -5 whilst initialising MMC card

 

I recompiled the kernel (balbes150 github),  for usbserial support and all the mmc drivers. The other modules are installed ok, but mmc_core gives error as follow:

mmc_core: Unknown symbol of_node_put (err 0)

 

Does anybody anyone have any idea?

 

Link to comment
Share on other sites

On 5/25/2018 at 10:17 PM, talraash said:

yep, it's just different version of libmali(mali-5...mali-7)

 

 

So a 450 is a Mail-5 GPU? I'm having problems with the images, no matter what version I run from Mali5 directory it gets more and more sluggish and eventually freezes after some 10-15 minutes. Where should I look for error messages or other signs of what goes south?

Link to comment
Share on other sites

On 4/8/2017 at 5:16 PM, tkaiser said:

With latest commits nand-sata-install should also be much more reliable when running on a system with typical services installed. See at the end of http://sprunge.us/FGOD

  

Requires the following of course the next few weeks:


wget -O- "https://raw.githubusercontent.com/igorpecovnik/lib/master/scripts/nand-sata-install/usr/lib/nand-sata-install/nand-sata-install.sh" >/usr/sbin/nand-sata-install

 

 

Hi tkaiser, I'm trying to run X96 mini from eMMC.  I followed the general instructions:


 

su -
(enter passwd root)
./install.sh

or

nand_sata_install

But after reboot (without SD card) nothing happened, blank screen, no boot at all. I managed to recover the main Android image from a backup and the devices started to boot again. Then I downloaded the script from here and started it. They were quite a lot errors, but on the end it said "Shut down". After the shutdown the LED turned to red (from blue)...forever :-) 

 

After multiple attempts to recover it, I connected to the UART port and I saw these messages:

BL2 Built : 14:59:36, Aug  9 2017.
gxl ge8c6a83 - xiaobo.gu@droid12

set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 2
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 912MHz - FAIL
DDR4 chl: Rank0+1 @ 1008MHz - FAIL
DDR init failed...
Reset...
GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;
TE: 122007

I have a feeling that from that point the device is unbrickable..but I have two more :-)   The question is what I did wrong with the install on eMMC?

 

Thank you!

 

 

 

Link to comment
Share on other sites

Hello

I have tested Armbian_5.44_S9xxx_Ubuntu_xenial_3.14.29_mate_20180515.img.


I can not use wifi network.

I tried to use command "modprobe wifi_dummy" as it used to work with previous versions, but this image was not successful. Have tested with the version Armbian_5.44_S9xxx_Debain_stretch_3.14.29_xfce.img and not as successful.


Can anyone tell me how to solve this problem?


Thanks in advance

Link to comment
Share on other sites

1 minute ago, chaijate said:

I have tested Armbian_5.44_S9xxx_Ubuntu_xenial_3.14.29_mate_20180515.img.


I can not use wifi network.

I tried to use command "modprobe wifi_dummy" as it used to work with previous versions, but this image was not successful. Have tested with the version Armbian_5.44_S9xxx_Debain_stretch_3.14.29_xfce.img and not as successful.


Can anyone tell me how to solve this problem?


Thanks in advance

 

what is the model of the TV box?

Link to comment
Share on other sites

@pisach

Thank you very much. This will return home to test the machine at home.

There is another question, I have a searh package in synaptic, which is very long time. Do you know this problem?

Thank again.

Link to comment
Share on other sites

2 hours ago, pisach said:

I have a feeling that from that point the device is unbrickable..but I have two more :-)   The question is what I did wrong with the install on eMMC?

On TV boxes can not use the official script nand-sata-install. It is not working properly and destroys the system. You have destroyed the u-boot and now, to restore, you have to close the contacts on the eMMC chip, that would block not the correct u-boot. In my images there is no NAND-sata-install script. This is actually a symbolic link to the script /root/install.sh.

 

3 hours ago, Reddwarf said:

So a 450 is a Mail-5 GPU? I'm having problems with the images, no matter what version I run from Mali5 directory it gets more and more sluggish and eventually freezes after some 10-15 minutes. Where should I look for error messages or other signs of what goes south?

mali-5 mali-6 mali-7 , this is the libMali library version. All these versions are designed for Mali-450.

Link to comment
Share on other sites

12 minutes ago, balbes150 said:

you have to close the contacts on the eMMC chip

 

Hi bables150,

yes, I had doubts and bad feelings before to run the script :-)

 

Is there some how-to reset the eMMC chip? Here is the board:  https://cdn-images-1.medium.com/max/1600/1*NJSv0Fu6wfB4qFjrTTjmFg.png

 

The eMMC chip seems to not have exposed any pins. They're some interesting connectors on the right side of the NAND, below the UART, but I don't know....

 

Thank you!

Link to comment
Share on other sites

21 minutes ago, balbes150 said:

mali-5 mali-6 mali-7 , this is the libMali library version. All these versions are designed for Mali-450.

Ah thanks a lot :) Any idea what to look for with reg. to system slowing down and freezing or is this a known issue?

Link to comment
Share on other sites

37 minutes ago, pisach said:

The eMMC chip seems to not have exposed any pins. They're some interesting connectors on the right side of the NAND, below the UART, but I don't know....

Look for information on the brand of the chip (if you're lucky) or ask the supplier.

 

35 minutes ago, Reddwarf said:

Ah thanks a lot :) Any idea what to look for with reg. to system slowing down and freezing or is this a known issue?

There can be many reasons, from incorrect dtb to banal overheating.

Link to comment
Share on other sites

2 minutes ago, balbes150 said:

Look for information on the brand of the chip (if you're lucky) or ask the supplier.

 

 

Actually I'm more interested how to run this box from the eMMC. Why if doesn't work on TV boxes? Is there a separate how-to for TV boxes? The rest works just fine, I'm very satisfied...again thanks!  

Link to comment
Share on other sites

41 minutes ago, balbes150 said:

Look for information on the brand of the chip (if you're lucky) or ask the supplier.

 

There can be many reasons, from incorrect dtb to banal overheating.

Overheating maybe, I think I have the correct dtb,  is there a gadget I can install that shows temp. cpu load etc?

Link to comment
Share on other sites

3 minutes ago, balbes150 said:

 

 

 

This is what I used in the beginning:

 

su -
(enter passwd root)
./install.sh

or

nand_sata_install

 

 

 

but it didn't do anything. After the end of the script, I stopped the box, removed the card and it didn't boot, just blank screen. After that I managed to restore from backup.

Link to comment
Share on other sites

5 hours ago, pisach said:

mecool M8S pro has SV6051 WiFi. You need to do the following:

 

ln -s /lib/firmware /usr/lib/firmware

modprobe ssv6051

add ssv6051 in /etc/modules

reboot


Unsuccess ~~~~ It's not work. I searched the M8S Pro wifi chipset from the internet. It is labeled as WiFi Chip: QCA9377.

http://www.fn-link.com/a-b-g-n-ac-wi-fi-bt-module/8223a-sr.html

Link to comment
Share on other sites

2 hours ago, Reddwarf said:

Overheating maybe, I think I have the correct dtb,  is there a gadget I can install that shows temp. cpu load etc?

You should use armbianmonitor command (look at the doc for the options, i don't remeber them) or directly run: cat /sys/class/thermal/thermal_zone*/temp

Link to comment
Share on other sites

17 minutes ago, balbes150 said:

modprobe wlan 

 

 

Thank you very much

 

21 minutes ago, balbes150 said:

modprobe wlan 

 

 


It's work .....
thank you very much @balbes150.

You are exellent!

Link to comment
Share on other sites

9 hours ago, balbes150 said:

Look for information on the brand of the chip (if you're lucky) or ask the supplier.

 

There can be many reasons, from incorrect dtb to banal overheating.

 

After I shorter some pins I managed to get to U-boot from the UART. A'm not very familiar with U-boot.  Could you tell me what is the fastest way to recover the device from here?

 

U-Boot 2015.01-g2d1a155-dirty (Oct 08 2017 - 12:02:50)
aarch64-none-elf-gcc (crosstool-NG linaro-1.13.1-4.8-2013.11 - Linaro GCC 2013.10) 4.8.3 20131111 (prerelease)
GNU ld (crosstool-NG linaro-1.13.1-4.8-2013.11 - Linaro GCC 2013.10) 2.23.2.20130610 Linaro 2013.10-4

 

Thanks! 

Link to comment
Share on other sites

1 hour ago, pisach said:

Could you tell me what is the fastest way to recover the device from here? 

 

 

He, fixed! I used "Burn Card Maker" with which I burned a stock FW on SD card and somehow it flashed the TV box. Now I can go to bed :-)

Link to comment
Share on other sites

@balbes150
sorry again.

Yesterday i used the "modprobe wlan" command, which it works. But after I added the wlan into file /etc/modules  and reboot again. I Can't see any wifi anymore. I tried to help myself. But it was not successful. Do you have any recommendations for this?

Link to comment
Share on other sites

13 minutes ago, chaijate said:

sorry again.

Yesterday i used the "modprobe wlan" command, which it works. But after I added the wlan into file /etc/modules  and reboot again. I Can't see any wifi anymore. I tried to help myself. But it was not successful. Do you have any recommendations for this?

Look at the topic on the link, the user describes a similar problem and its solution.

Link to comment
Share on other sites

On 5/28/2018 at 1:32 PM, balbes150 said:



 

 

Hi, it's again me. 

 

From my point if view the install.sh script doesn't work..at least for my device. 

 

Here is the output from the script:

root@amlogic:~# ./install.sh
Start copy system for DATA partition.
Formatting DATA partition...
umount: /dev/data: not mounted
/dev/data contains a ext4 file system
        last mounted on /data on Thu Jan  1 00:00:10 2015
Suggestion: Use Linux kernel >= 3.18 for improved stability of the metadata and journal checksum features.
e2fsck 1.43.4 (31-Jan-2017)
/dev/data: clean, 11/767040 files, 74788/3066368 blocks
done.
Copying ROOTFS.
Copy BIN
Copy BOOT
Create DEV
...
...
Copy VAR
Copy fstab
*******************************************
Done copy ROOTFS
*******************************************
Writing new kernel image...
65536+0 records in
65536+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0.78898 s, 42.5 MB/s
writing boot image config in bootimg.cfg
extracting kernel in zImage
extracting ramdisk in initrd.img
reading kernel from /boot/zImage
Writing Boot Image /dev/boot
reading ramdisk from /boot/initrd.img-3.14.29
Writing Boot Image /dev/boot
done.
Writing new dtb ...
done.
Write env bootargs
*******************************************
Complete copy OS to eMMC parted DATA
*******************************************
root@amlogic:~#

Here is the boot:

Spoiler

 


BL2 Built : 11:04:41, Jan 26 2018.
gxl g034b32c - xingyu.chen@droid12-sz

set vcck to 1120 mv
set vddee to 1070 mv
Board ID = 2
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0 16bit @ 792MHz

bist_test rank: 0 20 00 40 3d 1c 5e 24 00 48 40 1b 65 35 35 35 34 34 34 34 34 34 35 35 35 590
Rank0: 2048MB(auto)-2T-11
AddrBus test pass!
-s
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600
Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x0002c600
Load bl33 from eMMC, src: 0x00050200, des: 0x01000000, size: 0x00065e00
NOTICE:  BL3-1: v1.0(release):35dd647
NOTICE:  BL3-1: Built : 15:20:30, Feb  7 2018
[BL31]: GXL CPU setup!
NOTICE:  BL31: BL33 decompress pass
mpu_config_enable:ok
[Image: gxl_v1.1.3243-377db0f 2017-09-07 11:28:58 qiufang.dai@droid07]
OPS=0xa4
6 2b b9 5f 9b 22 35 59 c8 9e e9 69 [0.401203 Inits done]
secure task start!
high task start!
low task start!
ERROR:   Error initializing runtime service opteed_fast


U-Boot 2015.01-gd4767ac-dirty (Mar 02 2018 - 09:52:42)

DRAM:  2 GiB
Relocation Offset is: 76eb3000
register usb cfg[0][1] = 0000000077f5aa08
[CANVAS]canvas init
boot_device_flag : 1
Nand PHY Ver:1.01.001.0006 (c) 2013 Amlogic Inc.
init bus_cycle=6, bus_timing=7, system=5.0ns
reset failed
get_chip_type and ret:fffffffe
get_chip_type and ret:fffffffe
chip detect failed and ret:fffffffe
nandphy_init failed and ret=0xfffffff1
MMC:   aml_priv->desc_buf = 0x0000000073eb36b0
aml_priv->desc_buf = 0x0000000073eb59d0
SDIO Port B: 0, SDIO Port C: 1
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
init_part() 293: PART_TYPE_AML
[mmc_init] mmc init success
dtb magic edfe0dd0
      Amlogic multi-dtb tool
      Single dtb detected
start dts,buffer=0000000073eb8200,dt_addr=0000000073eb8200
      Amlogic multi-dtb tool
      Single dtb detected
parts: 11
00:      logo   0000000002000000 1
01:  recovery   0000000002000000 1
02:       rsv   0000000000800000 1
03:       tee   0000000000800000 1
04:     crypt   0000000002000000 1
05:      misc   0000000002000000 1
06: instaboot   0000000020000000 1
07:      boot   0000000002000000 1
08:    system   0000000040000000 1
09:     cache   0000000020000000 2
10:      data   ffffffffffffffff 4
init_part() 293: PART_TYPE_AML
eMMC/TSD partition table have been checked OK!
check pattern success
mmc env offset: 0x27400000
In:    serial
Out:   serial
Err:   serial
reboot_mode=cold_boot
[store]To run cmd[emmc dtb_read 0x1000000 0x40000]
_verify_dtb_checksum()-917: calc 9123433c, store 9123433c
_verify_dtb_checksum()-917: calc 9123433c, store 9123433c
dtb_read()-1039: total valid 2
dtb_read()-1106: do nothing
      Amlogic multi-dtb tool
      Single dtb detected
vpu: clk_level in dts: 7
vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300)
vpu: vpu_clk_gate_init_off
vpp: vpp_init
hpd_state=0
cvbs performance type = 6, table = 0
Net:   dwmac.c9410000amlkey_init() enter!
[EFUSE_MSG]keynum is 4
[BL31]: tee size: 0

Start read misc partition datas!
info->attemp_times = 0
info->active_slot = 0
info->slot_info[0].bootable = 1
info->slot_info[0].online = 1
info->slot_info[1].bootable = 0
info->slot_info[1].online = 0
info->attemp_times = 0
attemp_times = 0
active slot = 0
wipe_data=successful
wipe_cache=successful
upgrade_step=0
[OSD]load fb addr from dts
[OSD]fb_addr for logo: 0x7d851000
[OSD]load fb addr from dts
[OSD]fb_addr for logo: 0x7d851000
[CANVAS]addr=0x7d851000 width=3840, height=2160
amlkey_init() enter!
amlkey_init() 71: already init!
[EFUSE_MSG]keynum is 4
[BL31]: tee size: 0
[KM]Error:f[key_manage_query_size]L507:key[usid] not programed yet
[KM]Error:f[key_manage_query_size]L507:key[mac] not programed yet
[KM]Error:f[key_manage_query_size]L507:key[deviceid] not programed yet
gpio: pin GPIOAO_2 (gpio 102) value is 1
saradc - saradc sub-system

Usage:
saradc saradc open <channel>    - open a SARADC channel
saradc close    - close the SARADC
saradc getval   - get the value in current channel
saradc test     - test the SARADC by channel-7
saradc get_in_range <min> <max> - return 0 if current value in the range of current channel

InUsbBurn
noSof
Hit Enter or space or Ctrl+C key to stop autoboot -- :  0
(Re)start USB...
USB0:   USB3.0 XHCI init start
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 1 **
** Bad device usb 2 **
** Bad device usb 3 **
card out
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
emmc/sd response timeout, cmd1, status=0x1ff2800
Err imgread(L252):Fmt unsupported!genFmt 0x0 != 0x3
InUsbBurn
noSof
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
emmc/sd response timeout, cmd1, status=0x1ff2800
[MSG]mmcinfo failed!
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
emmc/sd response timeout, cmd1, status=0x1ff2800
(Re)start USB...
USB0:   USB3.0 XHCI init start
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
ee_gate_off ...
## Booting Android Image at 0x01080000 ...
reloc_addr =73f383d0
copy done
Kernel command line: buildvariant=userdebug
load dtb from 0x1000000 ......
      Amlogic multi-dtb tool
      Single dtb detected
   Uncompressing Kernel Image ... OK
   kernel loaded at 0x01080000, end = 0x021dd470
   Loading Ramdisk to 73974000, end 73ea0252 ... OK
   Loading Device Tree to 000000001fff3000, end 000000001ffffef6 ... OK
signature:
fdt_instaboot: no instaboot image

Starting kernel ...

uboot time: 5934040 us
domain-0 init dvfs: 4

 

It seems it doesn't see the boot partition on the eMMC. Are the any other steps?

 

Thanks!

Edited by Tido
added spoiler
Link to comment
Share on other sites

9 hours ago, pisach said:

It seems it doesn't see the boot partition on the eMMC. Are the any other steps?

The script works correctly. All data is written to the eMMC without errors. When launched from the eMMC, the new kernel is loaded without errors and started. The reason is dtb data.  This is the behavior I see when dtb data is incorrect (the kernel cannot start correctly). What dtb is used when starting from SD card ?

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines