Posts by SnT2k

SnT2k

Posting here despite being a bit Lakka-related because I'm trying to compile Lakka using LibreELEC's build system. Also, it seems that experts on the build system hang out here more than at the Lakka forums. Apologies in advance (and be ready to do a facepalm).

So I'm trying to create a Lakka build for my S812 device based on patches from LibreELEC. Since Lakka's build system is basically an older version of LibreELEC's (forked from OpenELEC), the existing project/device contents that I got from LibreELEC doesn't exactly work with Lakka's. So I replaced the scripts and tools folder of Lakka's with LibreELEC's, and replaced the packages/linux/package.mk with LibreELEC's too.

Along the way, there were some build errors because of missing packages which I managed to fix by grabbing the relevant package.mk from LibreELEC and some CMake build problems which I fixed by replacing the config/functions with LibreELEC's too. So right now, I have this frankenstein of a build system that ~sorta~ works.

However, I got stumped when compiling the linux kernel, it encountered errors when compiling the DTS:

Code

make[1]: Entering directory '~/Lakka/build.Lakka-S812.arm-devel/linux-263a24f'
  CHK     include/generated/uapi/linux/version.h
  CHK     include/generated/utsrelease.h
  CC      scripts/mod/devicetable-offsets.s
  GEN     scripts/mod/devicetable-offsets.h
  HOSTCC  scripts/mod/file2alias.o
  HOSTLD  scripts/mod/modpost
scripts/Makefile.build:128: kbuild: Makefile.build is included improperly
make[2]: *** No rule to make target 'dtbs'.  Stop.
~/Lakka/build.Lakka-S812.arm-devel/linux-263a24f/arch/arm/Makefile:319: recipe for target 'dtbs' failed
make[1]: *** [dtbs] Error 2
make[1]: Leaving directory '~/Lakka/build.Lakka-S812.arm-devel/linux-263a24f'
Makefile:12: recipe for target 'image' failed
make: *** [image] Error 2

Display More

Upon inspecting the relevant lines in arch/arm/Makefile:

Code

dtbs: scripts
        $(Q)$(MAKE) $(build)=$(subst $(wildcard $(srctree)//),,$(subst $(join /,$(subst dtb,dts,$@)),,$(firstword $(wildcard $(srctree)/$(boot)/dts/amlogic/$(subst dtb,dts,$@) $(srctree)/$(CUSTOMER_DIR_NAME)/meson/dt/$(subst dtb,dts,$@))))) \
        MACHINE=$(MACHINE) \
        dtbs

It seems that the $(build)=.... gets resolved to obj=, that is, the entire parameter, for some reason, resolves to nothing. I'm out of ideas on how to proceed but I imagine that I have to pull something again from the LibreELEC build system.

EDIT: btw, the Linux version I'm using is this: GitHub - kszaq/linux at 263a24f2e8e17cdd527e5c4aa462240d5e156edb

SnT2k

That's the first thing I actually checked! But that's just for compiling though. I was looking for how the directories are structured (e.g. how do the 'patches' in the packages resolved against the 'patches' in the projects?), how the build scripts interact with each other, and what are the entries in package.mk files which look like OpenWRT's package.mk files but slightly different.

I managed to get most of the info by reading through the scripts and working backwards with the help of nice people here, so all's well and good.

SnT2k · [S812] MIII Plus 2Gb\16Gb eMMC SnT2k December 30, 2016 at 12:05 PM

Hi balbes150, thanks for the effort! However, it seems that the Wifi problem is still present. To elaborate on the problem, the Wifi goes up allowing pinging and ssh as for a long time, but the moment I start downloading something (like addons), it gets cut off.

Just to check if it's a hardware problem, I flashed the stock android firmware on the device and the wifi worked without any problems. I think I'll try looking around other threads to see what are the possible fixes. Though, any suggestion how to start debugging the thing beyond dmesg and lsmod dumps? I've tried scanning the loaded DTBs but it didn't give me much information.

SnT2k

Thanks for your guidance! I have no idea on how the build system is structured since the Kodi wiki (assuming the documentation on the build system is there) seems to be down as of the moment.

SnT2k

Thanks for the guidelines.

Where/how do I "install" it though? Is it alright to do a cp dtbTool $ROOT/tools/dtbTool under makeinstall_host or do I put in under the install target of my makefile?

SnT2k

Hi all!

I have a tool written in C that needs to be compiled for the host buildsystem. It aggregates DTBs for Amlogic devices which is used as one of the build step when generating the device image.

How do I go about integrating this into the build system? For starters, I've tried creating a folder dtbTool under the tools folder, then adding tools/dtbTool/dtbTool.c and tools/dtbTool/Makefile, and finally inserting the make and $ROOT/tools/dtbTool/dtbTool commands in scripts/image. However, when the make executes, it generates the binary for the target platform. I know that this is the wrong way to do it, but I had to start from somewhere.

SnT2k · Multi-DTB splitter/creator SnT2k December 26, 2016 at 5:20 PM

I couldn't find the source code for handling Amlogic's Multi-DTB format so I wrote my own (thankfully, it's simple enough): github: aml-dtbtools
The code is written in portable C and C++11 so those should compile without dependencies (works on 64-bit x86 and 32-bit ARM).

The dtbTool is modified from the dtbTool source of QCOM which is floating around (it requires few modifications, surprisingly) while the splitter is based from reading the u-boot code.

Hope this helps!

SnT2k · [S812] MIII Plus 2Gb\16Gb eMMC SnT2k December 24, 2016 at 3:00 PM

Quote from balbes150

Try to connect via SSH and get the list of modules that you are using (lsmod).

Here's the output:

Code

Module                  Size  Used by
dhd                   658858  0
btsdio                  2434  0
bluetooth             193132  1 btsdio
8021q                  16201  0
hid_logitech_dj         9603  0
wifi_dummy               745  0
mali                  161003  5

Here's the relevant dmesg dumps if it helps:

Code

[ 30.948199@2] Bluetooth: HCI device and connection manager initialized
[ 30.948218@2] Bluetooth: HCI socket layer initialized
[ 30.948225@2] Bluetooth: L2CAP socket layer initialized
[ 30.948240@2] Bluetooth: SCO socket layer initialized
[ 30.950517@2] Bluetooth: Generic Bluetooth SDIO driver ver 0.1
[ 30.955104@0] dhd_module_init: in
[ 30.955112@0] wifi_setup_dt
[ 30.955117@0] wifi_request_32k_clk : ON-->ON for sdio_wifi
[ 30.955121@0] interrupt_pin(133) : sdio_wifi
[ 30.955126@0] sdio_wifi is using the pin GPIOX_21
[ 30.955129@0] wifi_dt : gpio op failed(-16) at line 210
[ 30.955138@0] reg:2620,clearmask=100010,setmask=0
[ 30.955142@0] reg:2622,clearmask=ff,set pin=133
[ 30.955146@0] reg:2623,clearmask=70000,setmask=4
[ 30.955149@0] interrupt_pin(133) : sdio_wifi
[ 30.955152@0] power_on_pin(6) : sdio_wifi
[ 30.955155@0] sdio_wifi is using the pin GPIOAO_6
[ 30.955158@0] wifi_dt : gpio op failed(-16) at line 232
[ 30.955162@0] power_on_pin(6) : sdio_wifi
[ 30.955165@0] power_on_pin2(123) : sdio_wifi
[ 30.955169@0] sdio_wifi is using the pin GPIOX_11
[ 30.955171@0] wifi_dt : gpio op failed(-16) at line 244
[ 30.955175@0] power_on_pin2(123) : sdio_wifi
[ 30.955179@0] ======== bcm_wlan_set_plat_data ========
[ 30.955184@0] host_oob_irq: 100
[ 30.955188@0] host_oob_irq_flags=1044
[ 30.955191@0] dhd_wifi_platform_load: Enter
[ 30.955202@0] Power-up adapter 'DHD generic adapter'
[ 30.955205@0] wifi_platform_set_power = 1
[ 30.955208@0] ======== PULL WL_REG_ON HIGH! ========
[ 30.955212@0] WIFI Disable! 6
[ 31.014431@2] [aml-spdif-dai]enterd aml_spdif_play,set_clock:5,sample_rate=4
[ 31.014440@2] audio_set_958_clk, freq=4,
[ 31.014449@2] IEC958 16bit
[ 31.014454@2] hdmitx: audio: aout notify rate 48000
[ 31.014457@2] hdmitx: audio: aout notify size 16
[ 31.014463@2] aml_i2s_close device type 8
[ 31.155024@0] WIFI Enable! 6
[ 31.663260@0] wifi_platform_bus_enumerate device present 1
[ 31.663272@0] ======== Card detection to detect SDIO card! ========
[ 31.663280@0] sdio_reset_comm():
[ 33.823282@2] btsdio: probe of sdio:0001:3 failed with error -110
[ 33.837281@2] sdio: queuing unknown CIS tuple 0x80 (2 bytes)
[ 33.839026@2] sdio: queuing unknown CIS tuple 0x80 (3 bytes)
[ 33.840763@2] sdio: queuing unknown CIS tuple 0x80 (3 bytes)
[ 33.843895@2] sdio: queuing unknown CIS tuple 0x80 (7 bytes)
[ 33.905139@2] [sdio_reinit] finish
[ 33.905156@3] [sdio_reinit] finish
[ 33.992312@2] bcmsdh_register: register client driver
[ 33.992371@2] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter
[ 33.992626@2] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter
[ 33.992632@2] bus num (host idx)=1, slot num (rca)=1
[ 33.992636@2] found adapter info 'DHD generic adapter'
[ 33.992642@2] 7 bcmdhd_mem_prealloc: wlan_mem_array[section].mem_ptr=c09a95d8, size=139264
[ 33.992646@2] success alloc section 3, size 139264
[ 33.992729@2] alloc static buf at edf40000!
[ 33.992733@2] 1 bcmdhd_mem_prealloc: section=4, wlan_static_skb=c0be11e4
[ 33.992736@2] success alloc section 4, size 0
[ 33.992972@2] dhdsdio_probe : no mutex held. set lock
[ 33.993044@2] F1 signature read @0x18000000=0x16224335
[ 33.995245@2] F1 signature OK, socitype:0x1 chip:0x4339 rev:0x1 pkg:0x2
[ 33.995601@2] DHD: dongle ram size is set to 786432(orig 786432) at 0x180000
[ 33.995642@2] 4 bcmdhd_mem_prealloc: section=7, wlan_mem_array[4]=edf20000
[ 33.995645@2] success alloc section 7, size 19744
[ 33.995669@2] dhd_conf_set_chiprev: chip=0x4339, chiprev=1
[ 33.995702@2] dhd_conf_set_conf_path_by_nv_path: config_path=/lib/firmware/brcm/config.txt
[ 33.996977@2] dhd_conf_read_nv_by_chip: nv_by_chip_count=9
[ 33.996986@2] dhd_conf_read_nv_by_chip: chip=0xa962, chiprev=0, name=nvram_ap6181.txt
[ 33.996991@2] dhd_conf_read_nv_by_chip: chip=0xa962, chiprev=1, name=nvram_ap6210.txt
[ 33.996995@2] dhd_conf_read_nv_by_chip: chip=0xa9a6, chiprev=0, name=nvram_ap6212.txt
[ 33.996999@2] dhd_conf_read_nv_by_chip: chip=0xa9a6, chiprev=1, name=nvram_ap6212a.txt
[ 33.997002@2] dhd_conf_read_nv_by_chip: chip=0x4345, chiprev=6, name=nvram_ap6255.txt
[ 33.997006@2] dhd_conf_read_nv_by_chip: chip=0x4330, chiprev=4, name=nvram_ap6330.txt
[ 33.997010@2] dhd_conf_read_nv_by_chip: chip=0x4339, chiprev=1, name=nvram_ap6335.txt
[ 33.997014@2] dhd_conf_read_nv_by_chip: chip=0x4356, chiprev=2, name=nvram_ap6356.txt
[ 33.997018@2] dhd_conf_read_nv_by_chip: chip=0x4335, chiprev=1, name=nvram_bcm4335.txt
[ 33.997042@2] dhd_conf_read_config: mimo_bw_cap = 1
[ 33.997186@2] dhd_conf_read_config: bcn_timeout = 20
[ 33.997222@2] dhd_conf_read_config: kso_enable = 0
[ 33.997336@2] dhd_conf_read_config: PM = 0
[ 33.997374@2] 7 bcmdhd_mem_prealloc: wlan_mem_array[section].mem_ptr=c09a95c0, size=10416
[ 33.997377@2] success alloc section 0, size 10416
[ 33.997659@2] 2 bcmdhd_mem_prealloc: section=5, wlan_static_scan_buf0=edf30000
[ 33.997664@2] success alloc section 5, size 65536
[ 33.997935@2] wl_create_event_handler(): thread:wl_event_handler:93b started
[ 33.997939@1] tsk Enter, tsk = 0xedf9669c
[ 33.998264@2] dhd_attach(): thread:dhd_watchdog_thread:93d started
[ 33.998292@2] dhd_attach(): thread:dhd_dpc:93e started
[ 33.998300@0] dhd_dpc_thread: set dpc_cpucore 0 from config.txt
[ 33.998316@2] dhd_attach(): thread:dhd_rxf:93f started
[ 33.998327@2] dhd_deferred_work_init: work queue initialized
[ 33.998335@2] 7 bcmdhd_mem_prealloc: wlan_mem_array[section].mem_ptr=c09a95c8, size=10396
[ 33.998338@2] success alloc section 1, size 10396
[ 33.998348@2] 7 bcmdhd_mem_prealloc: wlan_mem_array[section].mem_ptr=c09a95d0, size=65536
[ 33.998351@2] success alloc section 2, size 65536
[ 33.998517@2] dhdsdio_probe_init: set use_rxchain 1 from config.txt
[ 34.005839@2] Dongle Host Driver, version 1.201.59.5 (r506368)
[ 34.005839@2] Compiled in drivers/net/wireless/bcmdhd
[ 34.006185@2] Register interface [wlan0] MAC: 94:a1:a2:48:e7:7b
[ 34.006185@2]
[ 34.006193@2] dhd_prot_ioctl : bus is down. we have nothing to do
[ 34.006231@2] bcmsdh_oob_intr_unregister: Enter
[ 34.006235@2] bcmsdh_oob_intr_unregister: irq is not registered
[ 34.006242@2] dhd_txglom_enable: enable 0
[ 34.006245@2] dhd_bus_devreset: WLAN OFF DONE
[ 34.006286@2] wifi_platform_set_power = 0
[ 34.006289@2] ======== PULL WL_REG_ON LOW! ========
[ 34.006293@2] dhdsdio_probe : the lock is released.
[ 34.006590@0] dhd_open: Enter ef473000
[ 34.006599@0]
[ 34.006599@0] Dongle Host Driver, version 1.201.59.5 (r506368)
[ 34.006599@0] Compiled in drivers/net/wireless/bcmdhd
[ 34.006605@0] wl_android_wifi_on in 1
[ 34.006609@0] wl_android_wifi_on in 2: g_wifi_on=0
[ 34.006612@0] wifi_platform_set_power = 1
[ 34.006615@0] ======== PULL WL_REG_ON HIGH! ========
[ 34.006623@0] WIFI Disable! 6
[ 34.013295@2] dhd_module_init: Exit err=0
[ 34.206431@0] WIFI Enable! 6
[ 34.713229@0] sdio_reset_comm():
[ 34.727076@2] sdio: queuing unknown CIS tuple 0x80 (2 bytes)
[ 34.795378@2]
[ 34.795378@2]
[ 34.795378@2] dhd_bus_devreset: == WLAN ON ==
[ 34.795455@2] F1 signature read @0x18000000=0x16224335
[ 34.797613@2] F1 signature OK, socitype:0x1 chip:0x4339 rev:0x1 pkg:0x2
[ 34.797970@2] DHD: dongle ram size is set to 786432(orig 786432) at 0x180000
[ 34.798116@2] dhdsdio_probe_init: set use_rxchain 1 from config.txt
[ 34.798331@2] dhd_conf_read_nv_by_chip: nv_by_chip_count=9
[ 34.798337@2] dhd_conf_read_nv_by_chip: chip=0xa962, chiprev=0, name=nvram_ap6181.txt
[ 34.798342@2] dhd_conf_read_nv_by_chip: chip=0xa962, chiprev=1, name=nvram_ap6210.txt
[ 34.798346@2] dhd_conf_read_nv_by_chip: chip=0xa9a6, chiprev=0, name=nvram_ap6212.txt
[ 34.798349@2] dhd_conf_read_nv_by_chip: chip=0xa9a6, chiprev=1, name=nvram_ap6212a.txt
[ 34.798353@2] dhd_conf_read_nv_by_chip: chip=0x4345, chiprev=6, name=nvram_ap6255.txt
[ 34.798357@2] dhd_conf_read_nv_by_chip: chip=0x4330, chiprev=4, name=nvram_ap6330.txt
[ 34.798361@2] dhd_conf_read_nv_by_chip: chip=0x4339, chiprev=1, name=nvram_ap6335.txt
[ 34.798365@2] dhd_conf_read_nv_by_chip: chip=0x4356, chiprev=2, name=nvram_ap6356.txt
[ 34.798369@2] dhd_conf_read_nv_by_chip: chip=0x4335, chiprev=1, name=nvram_bcm4335.txt
[ 34.798392@2] dhd_conf_read_config: mimo_bw_cap = 1
[ 34.798536@2] dhd_conf_read_config: bcn_timeout = 20
[ 34.798573@2] dhd_conf_read_config: kso_enable = 0
[ 34.798686@2] dhd_conf_read_config: PM = 0
[ 34.798705@2] dhd_conf_set_fw_name_by_chip: firmware_path=/lib/firmware/brcm/fw_bcm4339a0_ag.bin
[ 34.798709@2] dhd_conf_set_nv_name_by_chip: nvram_path=/lib/firmware/brcm/nvram_ap6335.txt
[ 34.798712@2] Final fw_path=/lib/firmware/brcm/fw_bcm4339a0_ag.bin
[ 34.798715@2] Final nv_path=/lib/firmware/brcm/nvram_ap6335.txt
[ 34.798718@2] Final conf_path=/lib/firmware/brcm/config.txt
[ 30.873259@2] [aml_sdio_print_err] sdio: Timeout error, Cmd8 arg 0x1aa, Xfer 0 Bytes, host->xfer_step=12, host->cmd_is_stop=0, pdata->port=0, virqs=0x13, virqc=0x1f003f00, conf->cmd_clk_divide=177, pdata->clkc=177, conf->bus_width=0, pdata->width=0, conf=0x416270b1, clock=397940
[ 30.873259@2] [aml_sdio_timeout] time_start_cnt:993
[ 30.873259@2] [aml_sdio_print_err] sdio: Timeout error, Cmd52 arg 0x80062000, Xfer 0 Bytes, host->xfer_step=12, host->cmd_is_stop=0, pdata->port=0, virqs=0x13, virqc=0x1f001f00, conf->cmd_clk_divide=1, pdata->clkc=1, conf->bus_width=1, pdata->width=1, conf=0x41727001, clock=35416666
[ 30.873259@2]
[ 34.953292@2] NVRAM version: AP6335_NVRAM_V1.5_03112014
[ 34.953926@2] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
[ 35.132282@2] dhd_bus_init: enable 0x06, ready 0x06 (waited 0us)
[ 35.132450@2] bcmsdh_oob_intr_register: Enter
[ 35.132454@2] bcmsdh_oob_intr_register: HW_OOB enabled
[ 35.132458@2] bcmsdh_oob_intr_register OOB irq=100 flags=414
[ 35.132474@2] bcmsdh_oob_intr_register: enable_irq_wake
[ 35.132478@2] bcmsdh_oob_intr_register: enable_irq_wake failed with -6
[ 35.133325@0] dhd_conf_set_band: Set band 0
[ 35.133464@0] dhd_preinit_ioctls: Set tcpack_sup_mode 0
[ 35.142981@0] Firmware up: op_mode=0x0005, MAC=94:a1:a2:48:e7:7b
[ 35.142987@0] dhd_conf_set_country: Set country CN, revision 38
[ 35.189133@0] Country code: CN (CN/38)
[ 35.189355@0] dhd_conf_set_roam: Set roam_off 1
[ 35.191489@0] dhd_conf_set_mimo_bw_cap: Set mimo_bw_cap 1
[ 35.192071@0] dhd_conf_set_txbf: set txbf 1
[ 35.209797@0] Firmware version = wl0: Dec 6 2013 15:47:10 version 6.37.32.RC23.34.10 (r)
[ 35.209809@0] Driver: 1.201.59.5 (r506368)
[ 35.209809@0] Firmware: wl0: Dec 6 2013 15:47:10 version 6.37.32.RC23.34.10 (r)
[ 35.210073@0] dhd_txglom_enable: enable 1
[ 35.210080@0] dhd_conf_set_disable_proptx: set disable_proptx 0
[ 35.210844@0] dhd_wlfc_hostreorder_init(): successful bdcv2 tlv signaling, 64
[ 35.211203@0] wl_android_wifi_on: Success
[ 35.267334@0] dhd_open: Exit ret=0


........<when trying to connect to the network>....


[ 174.753629@0] Connectting with c0:56:27:41:0d:bb channel (11) ssid "Nijia", len (5)
[ 174.753629@0]
[ 174.809604@0] dhdsdio_rxglom (subframe 1): HW hdr error: len/check 0x7365/0x6843
[ 174.809607@0] dhdsdio_rxfail: abort command, terminate frame, send NAK
[ 174.811018@0] dhdsdio_rxglom (superframe): HW hdr error: len/check 0x0000/0x0000
[ 174.811024@0] dhdsdio_rxglom: got unlikely tx max 0 with tx_seq 112
[ 174.811028@0] dhdsdio_rxfail: abort command, terminate frame, send NAK
[ 174.812421@0] dhdsdio_rxglom (superframe): HW hdr error: len/check 0x0000/0x0000
[ 174.812427@0] dhdsdio_rxglom: got unlikely tx max 0 with tx_seq 112
[ 174.812432@0] dhdsdio_rxfail: abort command, terminate frame, send NAK
[ 174.813863@0] dhdsdio_rxglom (superframe): HW hdr error: len/check 0x0000/0x0000
[ 174.813870@0] dhdsdio_rxglom: got unlikely tx max 0 with tx_seq 112
[ 174.813874@0] dhdsdio_rxfail: abort command, terminate frame
[ 174.824334@2] wl_bss_connect_done succeeded with c0:56:27:41:0d:bb

Display More

Judging from the dmesg log, it seems like it's loading the correct driver?

SnT2k · [S812] MIII Plus 2Gb\16Gb eMMC SnT2k December 24, 2016 at 2:06 PM

Quote from balbes150

Have you tried the version from this directory ?
dF7ASRFGygDMj

Still no Bluetooth, the WiFi works for a bit then stops working (not network activity) like in the 8.0.0 build. It sometimes causes freezes when rebooting but at least it didn't cause the entire device to hang.

SnT2k · [S812] MIII Plus 2Gb\16Gb eMMC SnT2k December 24, 2016 at 10:16 AM

Quote from balbes150

Sorry, I not speak English, I don't understand the question, what You want to do ?

Sorry for the late response, got caught up in something.

Anyway, I tried replacing the dtb from KERNEL myself using mkbootimg (which works) but I see that you have already included the Amlogic Multi-DTB files in your latest builds.

Tried the S812.LAN1000 builds and they work great! While LAN works 100%, Bluetooth is not recognized and the device tends to hang when using WiFi. In the 7.0.2 build, the device eventually hangs, in 8.0.0, network requests fail and the device hangs when a reboot is attempted.
I've checked the WiFi chipset, it's the AP6335 Wireless module.

SnT2k · [S812] MIII Plus 2Gb\16Gb eMMC SnT2k November 30, 2016 at 9:35 AM

Quote from balbes150

Do I understand correctly that You have a dtb file that You want to integrate in the kernel image LE (instead of what is used now) ?
Or do You want to add Your data to an existing image ?

I initially want the latter, but either works. What's more convenient?

SnT2k · [S812] MIII Plus 2Gb\16Gb eMMC SnT2k November 30, 2016 at 8:15 AM

Quote from balbes150

After recording of the image on the media, FAT partition, there is a copy of the dtb file. Dtb data from this file are part of the kernel (kernel.img). This dtb file can be used to separate the kernel, the dtb data initramfs. For separate download of elements need to use another script file s805_autoscript. I checked the option in which dtb data are not part of the "kernel.img". In this embodiment, it is easy to replace the dtb data for any need without having to collect a new image. But it has a drawback. U-boot (which is used in all standard firmware platform S8xx) no support for separate load and store the dtb data in the internal memory. This feature (separate storage of the kernel and dtb data in the internal memory) appeared on the platform S9xx. If make the corresponding changes in u-boot, then can use a separate options storage of the kernel and the dtb data to internal memory.

I see... so that's why it was possible to split the dtb.img on S905 devices. In any case, could you compile into the kernel.img the multi-dtb I uploaded (it actually got extracted from the boot.img file)?
[hr]

Quote from balbes150

This is the correct value, as it should be. A portion of memory to be allocated for the graphics system and it is not displayed in the output.
Anyway, is it possible that the lower ram in my case is due to the same reason as GWR? (Graphics taking up the ram)

SnT2k · [S812] MIII Plus 2Gb\16Gb eMMC SnT2k November 30, 2016 at 5:56 AM

I checked the device RAM, it's only listing a total of 1613952kB instead of 2gB. Is this because of a mismatched DTB file?

In any case, I managed to extract the AMLOGIC multi-dtb file from the image and uploaded it here: Dropbox - probox2ex+.dtb.img
Also, it may be a stupid question, but can the DTB file be replaced post-install? I managed to do it for the RPi but that's a special case, I don't know how to do it for my device or if it's even possible.

SnT2k · [S812] MIII Plus 2Gb\16Gb eMMC SnT2k November 29, 2016 at 5:36 PM

Hi, I managed to install LibreElec on my Probox2 EX+ using the MXIII Plus build: 20161115
Here are the steps:

Download TWRP for MXIII Plus, I found the link here: index.php?t673262-5740.html the exact file is TWRP_MXIII_Plus_S812.img and it has a SHA1 hash: a2eb8d25d47c99a7cb4de4e3c5dfe2134380188d
Rename the file to recovery.img and copy it to the root of a FAT32-formatted MicroSD card.
Download the update ZIP version of LibreElec (look for the one with the filename LibreELEC-S812.MXIII_Plus.arm-[i]W.X.Y.Z[/i]-update.zip) and copy that into the MicroSD card.
Boot the device into the MicroSD card using the toothpick method (exactly the same procedure as the official "TF Card Update" method)
(Maybe optional) Install recovery.img into the recovery partition by going to the command line and issuing the command:
Code
```
dd if=/external_sd/recovery.img of=/dev/block/recovery ;sync;sync
```
(the normal installation procedure does not seem to work). Then reboot into the recovery partition.
Go to install, and select the zip file copied in step (4). The installation should proceed smoothly.

The thing seems to be stable so far, but haven't stress-tested it yet. Will let you know if problems crop up! HUGE thanks for the effort, balbes150!

Posts by SnT2k

Linux/DTB build problems when trying to create a custom build (Lakka-related)

Adding a tool which needs to be compiled for host

[S812] MIII Plus 2Gb\16Gb eMMC

Adding a tool which needs to be compiled for host

Adding a tool which needs to be compiled for host

Adding a tool which needs to be compiled for host

Multi-DTB splitter/creator

[S812] MIII Plus 2Gb\16Gb eMMC

[S812] MIII Plus 2Gb\16Gb eMMC

[S812] MIII Plus 2Gb\16Gb eMMC

[S812] MIII Plus 2Gb\16Gb eMMC

[S812] MIII Plus 2Gb\16Gb eMMC

[S812] MIII Plus 2Gb\16Gb eMMC

[S812] MIII Plus 2Gb\16Gb eMMC