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


Recommended Posts

1 hour ago, xXx said:

If not, where can i find these 5.37 versioned packages?

Almost all deb packages version 5.37, such as 5.34 on the website. The difference is in the packages.

 

firmware-aml

linux-dtb-amlogics905x

linux-image-amlogics905x

linux-xenial-root-amlogic-s905x

 

But they are not significant changes. If needed, I can upload at a time (I have limited space).

Link to post
Share on other sites
Armbian is a community driven open source project. Do you like to contribute your code?

Hello everyone

I have two amlogic boxes one is with s805 and another with s905 processor and neither of them has  mmc slot . In this forum balbes150 has helped me with the boot script from uart . Now i try to boot from usb flash drive  on s905 with following commands :

 

usb start
fatload usb 0 1020000 aml_autoscript
autoscr 1020000

 

but the boot process stucked on this - >  Link

 

Appreciate any help.

 

Link to post
Share on other sites
1 hour ago, balbes150 said:

The startup script works correctly and the kernel starts, but no data correct dtb to the kernel. The reason is not the correct dtb file. Pick the right option dtb file.

 

I think the right dtb for my box is -> gxbb_p201.dtb  (gxb_p201_v1# ) so i set this one as dtb.img and booted unfortunately i got kernel panic . Output is here  . I have tried several other dtb files and neither of them works . Also i am not sure if the box has any  hw problems because it doesn;t boot  Android when left without  USB flash drive.

Link to post
Share on other sites
19 hours ago, verb said:

I think the right dtb for my box is -> gxbb_p201.dtb  (gxb_p201_v1# ) so i set this one as dtb.img and booted unfortunately i got kernel panic . Output is here  . I have tried several other dtb files and neither of them works . Also i am not sure if the box has any  hw problems because it doesn;t boot  Android when left without  USB flash drive.

I understand that this TV box may not start with any systems, including those with Android ?

Link to post
Share on other sites
1 hour ago, balbes150 said:

I understand that this TV box may not start with any systems, including those with Android ?

 

Hello balbes150 the box doesn't boot Android  don;t know if it's some hw or sw problem ( i got some exceptions and the kernel crashes during boot) . I have it from friend of mine so no idea what's wrong with it. I hope it is software problem and that's why i tried to boot armbian. My question is do you find something wrong in the steps i try to boot:

1.Burned the ubuntu server image and copy gxbb_p201.dtb as dtb.img ( booting from uart show this as hostname -> gxb_p201_v1#)

2.after that from uart i tried with this commands ->

usb start
fatload usb 0 1020000 aml_autoscript
autoscr 1020000

i am not sure for this options but i have seen them from aml_autoscript

3.the output is here -> LINK    ( these are the last lines after enter the commands from uart) .Do you recognize them as output from armbian or the box try to boot  Android ???

Link to post
Share on other sites

Try to record on USB image LE. Add correct dtb (to try all that apply). Connect USB media to TV box and check how the system's going to start. To activate the multi-boot is NOT necessary (it is already activated). To execute the commands in the UART is NOT needed (everything has to start automatically). By the way, it is possible that your friend recorded in a TV box is not the correct u-boot and it's not gxbb_p201. Need to try other options gxbb*.

Link to post
Share on other sites

Until some days ago I had installed armbian server based on jessie and everything was working apart the bluetooth.

I decided to try the new armbian server based on stretch and I'm not more able to have the wifi working. I'm using the same dtb that I was using with jessie and I also loaded the module dhd that I used in jessie.

 

What can I do? Some advice?

Link to post
Share on other sites
13 hours ago, fatugazuhati said:

Until some days ago I had installed armbian server based on jessie and everything was working apart the bluetooth.

I decided to try the new armbian server based on stretch and I'm not more able to have the wifi working. I'm using the same dtb that I was using with jessie and I also loaded the module dhd that I used in jessie.

 

What can I do? Some advice?

Try to replace the directory /lib/firmware (copy it from the old version to the new one).

Link to post
Share on other sites
On 1/29/2018 at 7:14 AM, balbes150 said:

Try to replace the directory /lib/firmware (copy it from the old version to the new one).

Well, now everything works.

 

With the firmware directory from jessie the wifi works and I have this :

root@amlogic:# dmesg | grep firmware
[   77.673467] dhd_conf_set_conf_path_by_nv_path: config_path=/lib/firmware/brcm/config.txt
[   78.559879] dhd_conf_set_fw_name_by_chip: firmware_path=/lib/firmware/brcm/fw_bcm40183b2.bin
[   78.559884] dhd_conf_set_nv_name_by_chip: nvram_path=/lib/firmware/brcm/nvram_ap6330.txt
[   78.559888] dhdsdio_download_firmware: set use_rxchain 0
[   78.559891] dhdsdio_download_firmware: set txglomsize 16
[   78.559899] Final fw_path=/lib/firmware/brcm/fw_bcm40183b2.bin
[   78.559902] Final nv_path=/lib/firmware/brcm/nvram_ap6330.txt
[   78.559905] Final conf_path=/lib/firmware/brcm/config.txt

 

With the firmware directory from stretch the wifi doesn't work and I have this :

root@amlogic:~# dmesg | grep firmware
[   53.980967] dhd_conf_set_conf_path_by_nv_path: config_path=/lib/firmware/brcm/config.txt
[   54.869114] dhd_conf_set_fw_name_by_chip: firmware_path=/lib/firmware/brcm/fw_bcm40183b2.bin
[   54.869119] dhdsdio_download_firmware: set use_rxchain 0
[   54.869122] dhdsdio_download_firmware: set txglomsize 16
[   54.869129] Final fw_path=/lib/firmware/brcm/fw_bcm40183b2.bin
[   54.869132] Final nv_path=/lib/firmware/brcm/
[   54.869135] Final conf_path=/lib/firmware/brcm/config.txt
[   54.898305] _dhdsdio_download_firmware: dongle nvram file download failed

 

What could be the problem? How can I correctly solve it?

 

 

Postedit: I solved the problem correctly editing the config.txt

Link to post
Share on other sites
1 hour ago, balbes150 said:

Strange WiFi chip

I only can find a couple of mentions, here in English: http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s905x/639329-m96x-max-4k-hdr-vp9-tv-box-android-6-0-amlogic-s905x-2g-16g-802-11b-g-n-lan-kodi-bluetooth/page4

and here in Russian: http://4pda.ru/forum/lofiversion/index.php?t764777-7200.html

And if you say "Strange" for me thats mean no-wifi on armbian

Thanks!!!

Link to post
Share on other sites
On 1/16/2018 at 10:37 AM, balbes150 said:

While it is not. Soon will release a new image with the updated kernel. Perhaps it will be possible to add BT.

At the moment I have enough free time and if you want I can help to test\debug the bluetooth but you should tell me what to do because I haven't any idea.

I have an s95 telos and an s95 meta and at the moment I'm using the s95 meta that has an ampak ap6330.

Link to post
Share on other sites
8 hours ago, fatugazuhati said:

At the moment I have enough free time and if you want I can help to test\debug the bluetooth but you should tell me what to do because I haven't any idea.

I have an s95 telos and an s95 meta and at the moment I'm using the s95 meta that has an ampak ap6330.

On the Internet there are instructions on how to configure BT. You can try different options to find the cause. May need to try different dtb.

Link to post
Share on other sites
9 hours ago, balbes150 said:

On the Internet there are instructions on how to configure BT. You can try different options to find the cause. May need to try different dtb.

I'm trying but without success. I'm not able to understand if the problem is a wrong dtb, a wrong module or a wrong software configuration.

 

These are my steps to install the bluetooth:

apt-get install bluetooth blueman bluez bluez-tools rfkill libbluetooth-dev

modprobe hci_uart

 

I check that the module is correctly loaded:

lsmod | grep hci_uart
hci_uart               21653  0
bluetooth             242323  1 hci_uart

 

I check that the firmware is correctly loaded:

dmesg | grep firmware
[   15.261423] dhd_conf_set_conf_path_by_nv_path: config_path=/lib/firmware/brcm/config.txt
[   18.800655] dhd_conf_set_fw_name_by_chip: firmware_path=/lib/firmware/brcm/fw_bcm40183b2.bin
[   18.800660] dhd_conf_set_nv_name_by_chip: nvram_path=/lib/firmware/brcm/nvram_ap6330.txt
[   18.800665] dhdsdio_download_firmware: set use_rxchain 0
[   18.800668] dhdsdio_download_firmware: set txglomsize 16
[   18.800675] Final fw_path=/lib/firmware/brcm/fw_bcm40183b2.bin
[   18.800678] Final nv_path=/lib/firmware/brcm/nvram_ap6330.txt
[   18.800681] Final conf_path=/lib/firmware/brcm/config.txt

 

I check the bluetooth status and I start it:

systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset
   Active: inactive (dead)
     Docs: man:bluetoothd(8)

 

systemctl start bluetooth

 

systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset
   Active: active (running) since Wed 2018-01-31 10:11:40 UTC; 1s ago
     Docs: man:bluetoothd(8)
 Main PID: 8845 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─8845 /usr/lib/bluetooth/bluetoothd

Jan 31 10:11:40 amlogic systemd[1]: Starting Bluetooth service...
Jan 31 10:11:40 amlogic bluetoothd[8845]: Bluetooth daemon 5.43
Jan 31 10:11:40 amlogic bluetoothd[8845]: Starting SDP server
Jan 31 10:11:40 amlogic systemd[1]: Started Bluetooth service.
Jan 31 10:11:40 amlogic bluetoothd[8845]: Bluetooth management interface 1.4 ini

 

I attach the HCI adapter:
sudo hciattach /dev/ttyS1 any

 

I re-check the bluetooth status:
service bluetooth status
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2018-01-31 14:58:49 UTC; 7min ago
     Docs: man:bluetoothd(8)
 Main PID: 4459 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─4459 /usr/lib/bluetooth/bluetoothd

Jan 31 14:58:49 amlogic systemd[1]: Starting Bluetooth service...
Jan 31 14:58:49 amlogic bluetoothd[4459]: Bluetooth daemon 5.43
Jan 31 14:58:49 amlogic systemd[1]: Started Bluetooth service.
Jan 31 14:58:49 amlogic bluetoothd[4459]: Starting SDP server
Jan 31 14:58:49 amlogic bluetoothd[4459]: Bluetooth management interface 1.4 initialized
Jan 31 15:06:15 amlogic bluetoothd[4459]: Failed to obtain handles for "Service Changed" characteristic
Jan 31 15:06:15 amlogic bluetoothd[4459]: Sap driver initialization failed.
Jan 31 15:06:15 amlogic bluetoothd[4459]: sap-server: Operation not permitted (1)
Jan 31 15:06:16 amlogic bluetoothd[4459]: hci0 Load Connection Parameters failed: Unknown Command (0x01)


and I have 4 erros.

 

The bluetooth seems active:

 

hcitool dev
Devices:
    hci0    8F:CD:8A:1D:F9:D5

 

rfkill list
0: bt-dev: Bluetooth
    Soft blocked: no
    Hard blocked: no
1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
2: brcmfmac-wifi: Wireless LAN
    Soft blocked: no
    Hard blocked: no
3: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no

 

but I'm not able to see any device or to bee saw from any device:

bluetoothctl
[NEW] Controller 8F:CD:8A:1D:F9:D5 amlogic [default]
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# discoverable on
Changing discoverable on succeeded
[CHG] Controller 8F:CD:8A:1D:F9:D5 Discoverable: yes
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 8F:CD:8A:1D:F9:D5 Discovering: yes
[bluetooth]# exit
[DEL] Controller 8F:CD:8A:1D:F9:D5 amlogic [default]

 

Any advice?

 

Postedit: I was been able to solve the problem with the bluetooth with patchram, now everythings work on my minibox linux :-)

Do you think will be possible install kodi on debian server and have the hardware acceleration working?

Link to post
Share on other sites
14 hours ago, fatugazuhati said:

Do you think will be possible install kodi on debian server and have the hardware acceleration working?

This issue has already been discussed, it is possible but would require a large amount of manual operations (installing all the required packages, configure them, etc.).

Link to post
Share on other sites

Hi @balbes150, a new little problem, on stretch the remote commands doesn't work, I used the same remote.conf that I used in Jessie.

I retried in Jessie and everything works. I'm trying to solve this problem, any advice?

 

This time I really don't have any idea on what to check, everything seems ok but amremote doesn't work. I'have correctly installed aml-amremote-905_5.34_arm64, I have placed in /etc/amremote the same remote.conf that I have correctly used in jessie, I have started the service amlogic-remotecfg and it runs without problems but the remote controller doesn't work.

Every time that I press a remote controller's button in the syslog I have something similar to this:

Feb  2 23:21:40 localhost kernel: [  682.978463@0] remote: Wrong custom code is 0xe718ff00
Feb  2 23:21:41 localhost kernel: [  683.887669@0] remote: Wrong custom code is 0xb946ff00
Feb  2 23:21:42 localhost kernel: [  684.608617@0] remote: Wrong custom code is 0xf906ff00
Feb  2 23:21:42 localhost kernel: [  685.296251@0] remote: Wrong custom code is 0xbd42ff00
Feb  2 23:21:43 localhost kernel: [  686.308314@0] remote: Wrong custom code is 0xfb04ff00
Feb  2 23:21:44 localhost kernel: [  687.122292@0] remote: Wrong custom code is 0xf906ff00
Feb  2 23:21:45 localhost kernel: [  687.820066@0] remote: Wrong custom code is 0xaa55ff00

 

but the factory code in /etc/amremote/remote.conf is already set to factory_code= 0xff000001.

 

I have already tried replacing /lib/firmware with the one from jessie where everythings works.

 

What can I do? Could this be a kernel's problem?

Link to post
Share on other sites

Hi @balbes150, thanks a lot for your work.
 

I have just tried Armbian_5.37_S9xxx_Debian_stretch_4.9.40_server_20180202.img on an s95 meta but I have a black screen and it doesn't boot, I tried using the file gxm_q200_2g.dtb obviously rename as dtb.img, what dtb should I use with my box?

 

About Armbian_5.37_S9xxx_Debian_stretch_3.14.29_server_20180203.img, it works fabulously but I have always to edit the config.txt to make working the wifi and I have to use patchram to make working the bluetooth and I have no way to make working the ir remote, I have the same problems as I described in my previous post.

Could you help me in debugging the problem with amremote, I tried everythings and I have no more idea.

Link to post
Share on other sites

Image update 20180204 kernel 3.14.29 and 4.9.40. Added version of the images with mali-6 (Ubuntu Mate and Debian XFCE). In these images uses a new library libMali r6p3. These images are in the directory mali-6 on the website. In the directory mali-5 are all old images 20180203 (server and desktop variants). Added to the website version of the images with the kernel 4.9.40 a working version of KODI. Pay attention to the images 20180204 c kernel 4.9.40 Mate and XFCE desktops contain a version of KODI 17.3, which can work on models with S905X. Important. The image with the kernel 4.9.40 to run KODI, you need to log on desktop (which would have been on MATE or XFCE) and from it (via the menu) to launch KODI. Only in this mode will work the sound in KODI. When you exit KODI the screen will remain blank (black), for the appearance of the desktop you need to switch to another console with CTRL+ALT+F1 and go back to your desktop CTRL+ALT+F7.

Link to post
Share on other sites
2 hours ago, fatugazuhati said:

thanks a lot for your work.
 

I have just tried Armbian_5.37_S9xxx_Debian_stretch_4.9.40_server_20180202.img on an s95 meta but I have a black screen and it doesn't boot, I tried using the file gxm_q200_2g.dtb obviously rename as dtb.img, what dtb should I use with my box?

 

About Armbian_5.37_S9xxx_Debian_stretch_3.14.29_server_20180203.img, it works fabulously but I have always to edit the config.txt to make working the wifi and I have to use patchram to make working the bluetooth and I have no way to make working the ir remote, I have the same problems as I described in my previous post.

Could you help me in debugging the problem with amremote, I tried everythings and I have no more idea.

In images with kernel 4.9.40 is no support for s905. These images can only run on s905X and S912 (s912 KODI does not work). To work remote need to verify the composition of packages and kernel configuration (I hope to test it next week).

Link to post
Share on other sites
23 minutes ago, balbes150 said:

In images with kernel 4.9.40 is no support for s905. These images can only run on s905X and S912 (s912 KODI does not work). To work remote need to verify the composition of packages and kernel configuration (I hope to test it next week).

Do you thing that the problem with the remote in Stretch is kernel related? Is there something that can I do? In Jessie the remote works.

Can I try to boot stretch with the kernel from Jessie? If I can what files and directories should I replace?

Link to post
Share on other sites
1 hour ago, talraash said:

Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_mate_20180203.img - don't work hw decoding h264

Yes, I've just noticed it, too. The kernel was compiled without CONFIG_V4L_AMLOGIC_VIDEO. So no /dev/video10 and no hardware acceleration. CONFIG_AMLOGIC_IONVIDEO is also not set.

Link to post
Share on other sites
Guest
This topic is now closed to further replies.