Posts by johnzhang

Quote from chewitt

Android device tree files work on Android not Linux. On an LE 3.14 kernel they will be similar, but they are not interchangeable.

I had DTS (device tree sources) file, is it possible to build a new dtb file for the new kernel? Thanks!

Quote from balbes150

Where do you get the new dtb ? Have you tried running with the standard dtb from the image ?

I got if from my original Android firmware, I tried standard dtb file too, but the system still reboot again and again, I checked UART log , it looks like:

## ANDROID Format IMAGE

## Booting kernel from Legacy Image at 12000000 ...

Image Name: Linux-3.10.99

Image Type: ARM Linux Kernel Image (lzo compressed)

Data Size: 5519794 Bytes = 5.3 MiB

Load Address: 00208000

Entry Point: 00208000

Verifying Checksum ... OK

Ramdisk start addr = 0x12544800, len = 0x199b83

dectect realtek sdio wifi, config to sdio controller

Multi dtb tool version: v2 .

Multi dtb detected, support 8 dtbs.

aml_dt soc: m8m2 platform: n200 variant: sdio

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

dtb 6 soc: m8m2 plat: n200C vari: 1G

dtb 7 soc: m8m2 plat: n200C vari: 2G

Not match any dtb.

Flat device tree start addr = 0x126de800, len = 0x2000000 magic=0x5f4c4d41

Uncompressing Kernel Image ... OK

uboot time: 5086716 us.

EFUSE machid is not set.

Using machid 0xf81 from environment

error: not a fdt

Loading Ramdisk to 1fe66000, end 1ffffb83 ... OK

ERROR: image is not a fdt - must RESET the board to recover.

resetting ...

then system reboot again.

Here the image I tested is "LibreELEC-S812.LAN_100.arm-8.0.2.img" and "LibreELEC-S812.arm-18.0_20180601-LAN_100.img", and the results are same.

Quote from balbes150

Try to delete the aml_autoscript script after activating multi-boot. It is also desirable (after activation of multi-boot) to check the launch from the USB drive.

I tried your new release "LibreELEC-S812.arm-9.0-devel-20180622135859-5287365-LAN_100" after setup muti-boot(due to the box don't have reset button, so I input "reboot update" in adb connection, then the system reboot and go to boot logo. ) and a new dtb.img, I removed aml_autoscript and aml_autoscript.zip one by one, but the system still reboot again and again, if you need UART log, I'll paste it later.

Hi,Balbes150,

I tried "

Test variants of Libreelec KODI-18 (Leia) images for s812.

"

Hardware is S812, 1G ram, 100M lan.

I followed procedure to burn the img to TF card, but the system reboot all the time. I don't know what happened.

Hi,balbes150,

I have a box hardware is S812, 1G ram, 4G Nand, 100M lan, RTL8189 WIFI, I tried the ROM you provide in the thread, but it can not boot up, I burned it in TF card, but the sytem reboot all the time, evenI replaced the dtb file from original Android ROM.

Could you it possible to compile a ROM if I provide the dtb file?

Or I have to build it by myself according to your source code. thanks!

the dtb file link:

https://drive.google.com/drive/folders/1yh31djzzzsxvmxtk4efihs2jixvkfbtq?usp=sharing

Below is the documents link:

https://drive.google.com/drive/folders/1yh31djzzzsxvmxtk4efihs2jixvkfbtq?usp=sharing

Hi,Everybody,

Recently I got a box with S812, 1G Ram, 4G Nand, RTL8189 wifi,100M lan, I tried to boot from SD card with libreelec, but I can not find a useful DTB file due to the box is not popular.

I searched by Google, and got a script called " split_bootimg.pl" according to instruction from website:How to Extract a Device Tree File from Android Firmware Files. but the script reported error

" Android Magic not found in boot.img. Giving up."

I searched again found some boo.img don't have some kind of character so the script can not identify it so it can not split dtb.img from boot.img.

then I tried another script from below website:

GitHub - PabloCastellano/extract-dtb: Extract device tree blobs (dtb) from kernel images

it works but it split many files with suffix "dtb".

./extract-dtb.py /home/pi/b860a/boot.img -o /home/pi/test

Dumped 00_kernel, start=0 end=2617

Dumped 01_dtbdump_`@0M<p.dtb, start=2617 end=7188576

Dumped 02_dtbdump_m8m2_n200_2gsdhc.dtb, start=7188576 end=7211104

Dumped 03_dtbdump_m8m2_n200_2gsdio.dtb, start=7211104 end=7233632

Dumped 04_dtbdump_m8m2_n200_sdhc.dtb, start=7233632 end=7256160

Dumped 05_dtbdump_m8m2_n200_sdio.dtb, start=7256160 end=7279336

Extracted 5 appended dtbs + kernel to /home/pi/test

the dtb files look like:

total 7120

-rw-r--r-- 1 pi pi 2617 Jun 11 21:47 00_kernel

-rw-r--r-- 1 pi pi 7185959 Jun 11 21:47 01_dtbdump_`@0M<p.dtb

-rw-r--r-- 1 pi pi 22528 Jun 11 21:48 02_dtbdump_m8m2_n200_2gsdhc.dtb

-rw-r--r-- 1 pi pi 22528 Jun 11 21:48 03_dtbdump_m8m2_n200_2gsdio.dtb

-rw-r--r-- 1 pi pi 22528 Jun 11 21:48 04_dtbdump_m8m2_n200_sdhc.dtb

-rw-r--r-- 1 pi pi 23176 Jun 11 21:48 05_dtbdump_m8m2_n200_sdio.dtb

I know normally for libreelec system there have only one dtb.img. but here have 5 files named with dtb.

Here I don't know what the next step is. combine these files or something?

Could someone help to give me some instruction?

Thanks!

Hi,Adamg,

Thanks for your quick reply!

I will try your method later!

Hi,I followed instruction like below:

1. Firstly we need to stop Kodi and Lirc so SSH to your device and type the following commands
2.  
3. systemctl stop kodi
4. systemctl stop eventlircd
5.  
6. Next we need to scan for the IR codes
7.  
8. ir-keytable -t

but system reported error like below:

CoreELEC:~ # ir-keytable -t

No devices found

Could someone help to indicate what wrong with here?

Thanks!

I tried to search about the error, but can not found same issue on google.

I checked system log found there have log like:

[ 280.062140@0] remote: Wrong custom code is 0x4bb41608

[ 280.692492@0] remote: Wrong custom code is 0x4cb31608

[ 281.383970@0] remote: Wrong custom code is 0x48b71608

[ 281.854115@0] remote: Wrong custom code is 0x4ab51608

Quote from kszaq

Amlogic 4.9 kernel is not fully functional.

Thanks for your remind!

Quote from mmpp

USB device support in the amlogic kernel 3.14 is limited. There currently is no newer kernel version available. If your box has no digital audio connector, you could try using an hdmi audio extractor to connect your receiver.

Hi,mmpp,

Thanks for your reply!

Currently I can use optic fiber(SPDIF), I can wait update about the kernel, thanks!
[hr]

Quote from johnzhang

Hi,mmpp,

Thanks for your reply!

Currently I can use optic fiber(SPDIF), I can wait update about the kernel, thanks!

I just checked Amoglic website, it looks like they have released new kernel for S905, may be we need to waiting to implement to compile the new kernel.

arm-Kernel Info - Amlogic openlinux
8. 2017-03-31 released：

• Kernel Source：
  
  
  • Support GXBB(S905)/M8b(805)
  • kernel4.9
  • buildroot-2017-03-31

Hi,Everybody,

First thanks  kszaq's hard work so we can use the good Libresystem for S905 TV box,
The TV box I used hardware is S905M, 1G RAM, 8G ROM, 100M lan, 8189 Wifi.
system is Libre ELEC 8.0.1C for S905/S905X.

I used optic fiber before it works well, then I tried amanero combo384 usb audio to receive audio, here I found the sound have some strange noisy, like crackles along with normal sound, I compared the latest system 8.0.1C , it improved than old version, but still have some crackles sound, I tried to fix it, but I don't know why and so there I can not find a way to fix it.

I checked wiki of kodi, found a stence, the decription looks like the issue I met, but I'm not sure, I seached google and I didn't find out solution.

6.5 Known issues

When your audio is much too fast or crackles a lot or passthrough only produces noise, you might have a broken driver in use. If this is the case, try to add tsched=0 to the udev loading section in /etc/pulse/default.pa to read like:load-module module-udev-detect tsched=0Audio devices are disappearing with pulseaudio 8.0 (Ubuntu 16.04) especially while running kodi and while using Adjust Refreshrate to match video. This is an issue with the module-switch-on-port-available module and will be fixed with pulseaudio 9.0, the fix sadly won't probably make it into Ubuntu 16.04. As a workaround please disable that feature by editing /etc/pulse/default.pa and commenting or removing load-module module-switch-on-port-available and reboot the system.

I grab system log and wish you could found something it, I checked the log and found audio log didn't include the audio card information of amanero, so I used aplay -L to get the information and attached it in below:

LibreELEC:~/.config # aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
default:CARD=AMLM8AUDIO
AML-M8AUDIO,
Default Audio Device
sysdefault:CARD=AMLM8AUDIO
AML-M8AUDIO,
Default Audio Device
front:CARD=AMLM8AUDIO,DEV=0
AML-M8AUDIO,
Front speakers
surround21:CARD=AMLM8AUDIO,DEV=0
AML-M8AUDIO,
2.1 Surround output to Front and Subwoofer speakers
surround41:CARD=AMLM8AUDIO,DEV=0
AML-M8AUDIO,
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=AMLM8AUDIO,DEV=0
AML-M8AUDIO,
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=AMLM8AUDIO,DEV=0
AML-M8AUDIO,
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=AMLM8AUDIO,DEV=0
AML-M8AUDIO,
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
hdmi:CARD=AMLM8AUDIO,DEV=0
AML-M8AUDIO,
HDMI Audio Output
default:CARD=Amanero
Combo384 Amanero, USB Audio
Default Audio Device
sysdefault:CARD=Amanero
Combo384 Amanero, USB Audio
Default Audio Device
front:CARD=Amanero,DEV=0
Combo384 Amanero, USB Audio
Front speakers
surround21:CARD=Amanero,DEV=0
Combo384 Amanero, USB Audio
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=Amanero,DEV=0
Combo384 Amanero, USB Audio
4.0 Surround output to Front and Rear speakers
surround41:CARD=Amanero,DEV=0
Combo384 Amanero, USB Audio
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=Amanero,DEV=0
Combo384 Amanero, USB Audio
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=Amanero,DEV=0
Combo384 Amanero, USB Audio
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=Amanero,DEV=0
Combo384 Amanero, USB Audio
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=Amanero,DEV=0
Combo384 Amanero, USB Audio
IEC958 (S/PDIF) Digital Audio Output

Please help to tell me how to solve it, just need to adjust ALSA configuration or need kernel modification, I'm not sure about it, thanks for your support!