LibreELEC for Khadas VIM1 VIM2 VIM3 (SD & USB & eMMC)

For firmware versions with DualOS is necessary to update u-boot. Files to update here. This must be done manually (for console UART).

https://yadi.sk/d/gRJa9jXd3FgUBi

I suggested to add support for multi-boot in the firmware (source code level) that would multiboot was download initially users didn’t have to do it, but don’t have it.

HI, how to adjust gpu ram size on your libreELEC ROM ?

On Pi3 in config.txt

Default GPU memory split (do not change if you do not know what you are doing)

gpu_mem=128

Configure GPU memory based on SDRAM size - overrides above setting

gpu_mem_256=112
gpu_mem_512=160
gpu_mem_1024=256

Hi,VIM GPIO

http://docs.khadas.com/images/vim_pinout.png
Please tell me,where are I2S?

All parameters gpu pledged in the dtb file. For example, here’s the data for fb.

The question You better ask in these topics.

im not sure if i did understand this correctly? i cat put that image (via dd) to an sd card and then select from the menu “install to emmc”?

edit: after reading 3rd-Party Ubuntu ROM for Khadas VIM
ah ok i got it. u need to do it as an android update.

but why this way? isnt it possible to burn this with uboot ?

update 2: running marshmallow 20170303
this doesnt work for me. only the VIM logo shows up on screen
i use external reader (wit status led) nothin happens!
uart debug stops at:

InUsbBurn
[MSG]sof
Set Addr 15
Get DT cfg
Get DT cfg
set CFG

update3:
i’ve tried different android images same result

i’ve put all from the tar to sd card and set all the env var from the amt_autoscript but this causes a stop too:

“rsvmem check failed
ee_gate_on …
InUsbBurn
[MSG]sof
Set Addr 33
Get DT cfg
Get DT cfg
set CFG

update: i dont know why, but i did now set the envs from the aml_autoscript again and today it worked fine. i must have made a mistake yesterday
thank you!

Version update 20170801.

https://yadi.sk/d/ysAgoIWT32M9Hn

Pay attention to use this version of the LE into VIM firmware Android 6 need, download and replace the file “dtb.img” on this option. Without a file “dtb.img”, this version of LE will not run on VIM.

https://yadi.sk/d/PTMTLQPs3Lhhr9

1 Like

Thanks for your work. Is the video playing smoothly? I’ll check only in the evening.

The video I tested, working fine. But I have not tested all the options. By the way, maybe it’s a coincidence, but I noticed that the version of the image I see is much more available Wi-Fi networks than on the way from Kszaq. It would be nice if someone had checked this information.

Just to clarify: if i DON’T have Android 6 (aka Marshmellow) on my VIM, i need to download the kvim.dtb from your Yadi.sk folder (20170801) and replace the one included in the image with the one i just downloaded?
– Edit: rename it to dtb.img obv as well :wink:

Yes, you need to download, rename and replace “dtb.img” on the media. I wrote about Android-6 in order to understand how u-boot I test my build. Maybe the firmware with Android 7 (with the data used in u-boot from the firmware) the behavior of the LE will be different, I have not tested it.

hi @balbes150,
why is there no simple img file we can use to flash LE directly to emmc using the same windows and usb-c tool like for ubuntu ?

Using the flash file with USB cable - is dangerous procedure. Running the system from external media in multi-boot mode saves the contents of the internal eMMC and allows the user to preview the system. To check all its functions and to make sure this system suits him. I know a lot of cases when users , after some time of use, refuse from this system, in this case, they really just return to their previous state (without having to perform a potentially dangerous procedure of flashing). Many users use multi-upload that would to have multiple systems (Android + Le + Linux).

Hi balbes,
i had the latest official nugat build (170612) installed on mmc, flashed via manually creating a burncard with u_boot_nugat_170512. Was working ok, but all my PCs run linux, so i wanted linux on my VIM aswell.
I dd’ed your previous LibreElec 20170705.img to my sdcard, renamed dtb.img to _dtb.img_ and renamed remote.vim to remote.conf. Then i ran the Update&restore utility, pointed to the aml_…zip-file and after short the system rebooted.
But it never got out of the boot-animation. So i updated my SDcard with your new image (dd…; ren dtb.img __dtb.img; cp …/…/kvim.dtb dtb.img). I can’t get the image to boot, the system will only boot to the android boot animation and never finish. I have access to uboot, here’s the boot log: https://pastebin.com/q1KmV6iF
As i’m completely new to uboot, what should i do now?
(Oh, and if this is the wrong thread, please move it to another.)
THX :slight_smile:

Show the output of “printenv” from u-boot.

printenv output:
_=/system/bin/printenv
ANDROID_DATA=/data
TMPDIR=/data/local/tmp
ANDROID_ROOT=/system
EXTERNAL_STORAGE=/sdcard
ANDROID_BOOTLOGO=1
ANDROID_ASSETS=/system/app
ASEC_MOUNTPOINT=/mnt/asec
BOOTCLASSPATH=/system/framework/core-oj.jar:/system/framework/core-libart.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/ims-common.jar:/system/framework/apache-xml.jar:/system/framework/org.apache.http.legacy.boot.jar:/system/framework/droidlogic.jar:/system/framework/droidlogic.frameworks.pppoe.jar
HOSTNAME=kvim
DOWNLOAD_CACHE=/data/cache
ANDROID_STORAGE=/storage
PATH=/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
SYSTEMSERVERCLASSPATH=/system/framework/services.jar:/system/framework/ethernet-service.jar:/system/framework/wifi-service.jar

I need the output of this command from u-boot. Stop boot in the UART console and execute the command “printenv”.

sorry, never knew that those where two different env’s :blush:
https://pastebin.com/R19aigsu

You have not activated multiupload.

bootcmd=run storeboot

If multiboot is enabled, this string should contain

bootcmd=run start_autoscript; run storeboot;

1 Like

It works now, thank you :+1: :+1: .
I extracted the text from aml_autoscript and executed all lines manually in the console, b/c none of the env-vars were set.
Now it boots beautifully :smile:
If someone with a similar problem comes along, here’s the script:

setenv bootfromrecovery 0
setenv bootfromnand 0
setenv bootcmd "run start_autoscript; run storeboot;"
setenv start_autoscript "if usb start ; then run start_usb_autoscript; fi; if mmcinfo; then run start_mmc_autoscript; fi;"
setenv start_mmc_autoscript "if fatload mmc 0 1020000 s905_autoscript; then autoscr 1020000; fi;"
setenv start_usb_autoscript "if fatload usb 0 1020000 s905_autoscript; then autoscr 1020000; fi; if fatload usb 1 1020000 s905_autoscript; then autoscr 1020000; fi; if fatload usb 2 1020000 s905_autoscript; then autoscr 1020000; fi; if fatload usb 3 1020000 s905_autoscript; then autoscr 1020000; fi;"
setenv upgrade_step "2"
saveenv
sleep 1
reboot