Jump to content

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

balbes150

By balbes150
in General Chat

 Share

Recommended Posts

pisach

pisach

Posted
Posted
53 minutes ago, balbes150 said:

You have the S905W (p281) model and the dtb file from p212 will not work correctly.

 

dtb 1 soc: gxl plat: p281 vari: 2g

Find match dtb: 1

 

But I don't have p281 in the img file at all? I found in one how-to for X96 mini that I have to use p212 and it works fine from the SD card. From where to take the correct dtb file?

 

Thanks 

Link to comment
Share on other sites
pisach

pisach

Posted
Posted
5 hours ago, balbes150 said:

You have the S905W (p281) 

 

I found this in http://freaktab.com

 

Quote

p212:

Amlogic S905X CPU

2GB DDR3

HDMI out x 1

TF Card x 1

Ethernet with internal phy x 1

SDIO WiFi/BT (RTL8189ETV) x 1

SPDIF x 1

USB hub x 2

EMMC x 1

 

 

but my WiFi/BT is ssv6051 not RTL8189ETV

 

Is there some place where all these dtb files/profiles are explained?

 

Thanks!

Link to comment
Share on other sites
pisach

pisach

Posted
Posted (edited)
On 5/30/2018 at 3:50 PM, balbes150 said:

You have the S905W (p281) model and the dtb file from p212 will not work correctly.

 

 

OK, I downloaded gxl_p281_2g.dtb from here https://github.com/AlexELEC/S905-trees/blob/master/S905W/gxl_p281_2g.dtb

 

I used install.sh again:

  

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
tar: boot/dtb/gxl_p281_2g.dtb: time stamp 2018-05-30 23:44:48 is 38944.312353311 s in the future
tar: boot/dtb.img: time stamp 2018-05-30 23:44:48 is 38941.938608371 s in the future
Create DEV
Copy ETC
Copy HOME
Copy LIB
Create MEDIA
Create MNT
Copy OPT
Create PROC
Copy ROOT
Create RUN
Copy SBIN
Copy SELINUX
Copy SRV
Create SYS
Create TMP
Copy USR
Copy VAR
tar: var/log/daemon.log: file changed as we read it
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.77237 s, 43.4 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
*******************************************

Now it looks as the script has finished successfully,  but the it fails to boot again:

Spoiler

  


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
_cmp_iptbl()-599: partition count is not same 14:13
mmc_device_init()-1115: update rsv with dtb!
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 1f77881e, store 1f77881e
_verify_dtb_checksum()-917: calc 1f77881e, store 1f77881e
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]failed to get fb addr for logo
[OSD]use default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[OSD]load fb addr from dts
[OSD]failed to get fb addr for logo
[OSD]use default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[CANVAS]addr=0x3d800000 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 000000001ffff418 ... OK
signature:
fdt_instaboot: no instaboot image

Starting kernel ...

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

 

If looks different if it's run for second time: 

*******************************************
Done copy ROOTFS
*******************************************
Writing new kernel image...
65536+0 records in
65536+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0.777269 s, 43.2 MB/s
/dev/boot: no Android Magic Value
/dev/boot: not a valid Android Boot Image.

/dev/boot: no Android Magic Value
/dev/boot: not a valid Android Boot Image.

/dev/boot: no Android Magic Value
/dev/boot: not a valid Android Boot Image.

/dev/boot: no Android Magic Value
/dev/boot: not a valid Android Boot Image.

done.
Writing new dtb ...
done.
Write env bootargs
*******************************************
Complete copy OS to eMMC parted DATA
*******************************************
root@amlogic:~#

 

Thanks!

Edited by Tido
@pisach, please use SPOILER
Link to comment
Share on other sites
Tido

Tido

Posted
Posted

I have downloaded: Armbian_5.41.1_S9xxx_Ubuntu_xenial_3.14.29_icewm_20180406.img.xz   it comes without KODI ?

I thought all of your images come with KODI.

 

Do I need to install a  .deb?

Link to comment
Share on other sites
Reddwarf

Reddwarf

Posted
Posted
15 minutes ago, Tido said:

I have downloaded: Armbian_5.41.1_S9xxx_Ubuntu_xenial_3.14.29_icewm_20180406.img.xz   it comes without KODI ?

I thought all of your images come with KODI.

 

Do I need to install a  .deb?

If you want KODi you can just install it from the repo.

Link to comment
Share on other sites
yossarian

yossarian

Posted
Posted

New on this forum and looking if somebody can help me :)

Target: Install some kind of linux system on my
K1 plus TV Box
SoC – Amlogic S905 Quad core 64-bit  Cortex A53 Up to 2.0GHz
GPU – Penta-core Mali-450 Up to 750MHZ, OpenGL ES 1.1/2.0 and Open VG 1.1 support
OS – Android 5.1.1
Memory – 1GB DDR3
Storage –  Nand Flash 8GB
Connectivity – Fast Ethernet, 2.4Ghz 802.11 b/g/n/ Wi-Fi, optional Bluetooth 4.0

 

Till now I followed instructions from first page of this tread, but didn't succeed.
I burned card first with linux "Disk image writer" then with "Rufus 3.0p"
I try'd with more images and have same story
Armbian_5.44_S9xxx_Debian_stretch_4.16.1_icewm_20180515.img
Armbian_5.44_S9xxx_Ubuntu_bionic_4.16.1_server_20180523.img
Armbian_5.44_S9xxx_Ubuntu_xenial_4.16.1_mate_20180515.img

I found the way to start process but process stops with message

E: failed to mount /udisk (No such file or directory)
Secure check failed.
Installation aborted
OTA failed! Please power off the device to keep it in this state and file bug report

Recovery is listening adb sideloaded....
Waiting adb sideloaded command...
E:Cannot load volume /misc!

After this fail I try'd to burn card with 
Amlogic SD card maker but when trying to make, got error message
"LC(1005)aml_sdc_burn. UBOOT, and BOOTLOADER.partition all not in pkg"
Don't understand this message.
Can anybody show me the way to go.

1
Link to comment
Share on other sites
Fozzy

Fozzy

Posted
Posted

@balbes150, Hi !

 

I have problems with nand-installing latest builds on my tv-box.

I was trying to nand-install 2 builds (Armbian_5.44_S9xxx_Ubuntu_bionic_4.16.1_icewm_20180523.img and Armbian_5.44_S9xxx_Ubuntu_bionic_4.16.1_icewm_20180515.img) on my Nexbox A95X (with Amlogic S905x SoC).

And I always get error messages. I made a photo of them, they are in the attachment.

 

Why i get this errors?

How can i help you investigate it?

 

 

111.jpg

Link to comment
Share on other sites
pisach

pisach

Posted
Posted
2 minutes ago, balbes150 said:

For all. Kernel 4.16 does not support internal eMMC memory. 

 

Yeah, but it doesn't work for me even with 3.14.29 kernel :-)

Can you help me to troubleshoot what might be wrong, please?

 

Thanks!

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
11 minutes ago, pisach said:

Yeah, but it doesn't work for me even with 3.14.29 kernel :-)

Can you help me to troubleshoot what might be wrong, please?

You have the s905W. I don't have that model, I can't help you. You need to build your version of dtb file. You can try to take the dts sources from the file that you use from Alexelec and adapt them to the Armbian kernel in the part that describes the eMMC parameters.

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
On 5/31/2018 at 10:53 PM, Tido said:

I have downloaded: Armbian_5.41.1_S9xxx_Ubuntu_xenial_3.14.29_icewm_20180406.img.xz   it comes without KODI ?

I thought all of your images come with KODI.

 

Do I need to install a  .deb? 

Yes, install ".deb"

KODI was only a part of the image versions with Mate and XFCE (up to version 5.44). Starting with version 5.44 I no longer include KODI in the images. Because:

1. There are several variants of KODI (17 and 18). Now users decide and install the version they need.

2. Now version Armbian start to use as a regular office PC, which does not need KODI.

1
Link to comment
Share on other sites
zador.blood.stained

zador.blood.stained

Posted
Posted
1 hour ago, balbes150 said:

I'm tired of saying the same thing.

 

For all. Kernel 4.16 does not support internal eMMC memory. Do not attempt to install to the eMMC. You get problems.

You could add a check for the kernel version in your eMMC installation script, i.e. like this (requires the "linux-base" package installed) 

if linux-version compare $(uname -r) gt 4.0 ; then
  echo "Installation to internal storage is not supported on this kernel version"
  exit 1
fi

or you could check if /dev/data exists if this path is common for all TV boxes.

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
38 minutes ago, zador.blood.stained said:

You could add a check for the kernel version in your eMMC installation script, i.e. like this (requires the "linux-base" package installed)

Good tip, I will do so in the next versions.

 

But this does not solve the second problem - when users still try to do it and then ask questions.  :)

Link to comment
Share on other sites
Tido

Tido

Posted
Posted
1 hour ago, balbes150 said:

Yes, install ".deb"

KODI was only a part of the image versions with Mate and XFCE (up to version 5.44).

hmm, but I have downloaded from the folder:  5.41.1_KODI-17.6  and only Mate & XFCE come with it :blink:

To have 2 folder like:  a KODI,   an Armbian   would help to navigate.

Link to comment
Share on other sites
umiddelb

umiddelb

Posted
Posted
3 hours ago, balbes150 said:

I'm tired of saying the same thing.

 

For all. Kernel 4.16 does not support internal eMMC memory. Do not attempt to install to the eMMC. You get problems.

Have you tried to reduce the eMMC frequency, see here and here? 

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
3 hours ago, Tido said:

hmm, but I have downloaded from the folder:  5.41.1_KODI-17.6  and only Mate & XFCE come with it :blink:

To have 2 folder like:  a KODI,   an Armbian   would help to navigate. 

KODI was part of version <5.44. In Version 5.44, it is not in the default image.

 

2 hours ago, umiddelb said:

Have you tried to reduce the eMMC frequency, see here and here?  

In addition, there are other problems.

Link to comment
Share on other sites
Reddwarf

Reddwarf

Posted
Posted

Has anyone managed to get Bluetooth working on Mini M8S or Mini MXIII boxes? I have downloaded the driver RTL8723AS + RTL8723BS_BT and followed the instructions but when I select Adapters in BT menue it is empty. I'm pretty sure I have the correct dtb 'cause wifi and audio is working. I run the Mate image from Mali7.

Link to comment
Share on other sites
tediwildan

tediwildan

Posted
Posted
2 hours ago, balbes150 said:

The question is not clear.

Sorry for my bad english , I mean if I want to to reimage this distribution with already configured for my need, how can I do that ?  I hope you understand what I'm ask, many thanks.

Link to comment
Share on other sites
Reddwarf

Reddwarf

Posted
Posted
4 minutes ago, tediwildan said:

Sorry for my bad english , I mean if I want to to reimage this distribution with already configured for my need, how can I do that ?  I hope you understand what I'm ask, many thanks.

Maybe you should explain why you want to reimage and what you want to do with the new image?

1
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
11 hours ago, belaid38 said:

hi @balbes150   plz compile libreelec with kernel 4.17   . i need tested this i have wetek play 2 

What do you want to check ? I am using LE version with kernel 4.16 for Khadas VIM. The main functions work but there is no HW decoding yet.

Link to comment
Share on other sites
La Otra Cuenta

La Otra Cuenta

Posted
Posted

Hi, there. I have a problem with the Armbian_5.44_S9xxx_Ubuntu_Ubuntu_bionic_4.16.1_server_20180523.img I get the following message the first time I start from microSD:

Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev)
The device is Mini MX s905 2GB/16GB GbE
I tried meson-gxbb-p200.dtb which is the one that starts.

Thank you

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
11 hours ago, La Otra Cuenta said:

The device is Mini MX s905 2GB/16GB GbE
I tried meson-gxbb-p200.dtb which is the one that starts.

Try using a USB flash drive. Perhaps this dtb does not work correctly SD card.

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