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

Madwyn · July 8, 2017, 10:45pm

Hi Balbes150,

I’m trying to get LibreELEC running for several days, but no success.

My steps:

Flashed “VimPro_DualOS_Marshmallow_Ubuntu-16.04_170124”
Write “17.3_20170705” into SD card using Win32 Disk Imager.
Delete “dtb.img” (skipped this step as there is none in the above image).
Rename “remote.conf.vim” to “remote.conf”.
Try to reboot to LibreELEC. Settings -> About Device -> System updates -> Select -> aml_autoscript.zip -> Update

Then nothing happened, the system reboot and Android started.

balbes150 · July 9, 2017, 8:32am

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

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.

TSING · July 9, 2017, 3:11pm

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

TSING · July 9, 2017, 3:16pm

Hi,VIM GPIO

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

balbes150 · July 9, 2017, 3:38pm

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

github.com

kszaq/linux-amlogic-le/blob/amlogic-3.14.y-new/arch/arm64/boot/dts/amlogic/gxl_p212_2g.dts#L144


      
          		status = "okay";
          		led_gpio = <&gpio GPIODV_24 GPIO_ACTIVE_HIGH>;
          		led_active_low = <1>;
          	};
          
          	meson-vout {
          		compatible = "amlogic, meson-vout";
          		dev_name = "meson-vout";
          		status = "okay";
          	};
          	meson-fb {
          		compatible = "amlogic, meson-fb";
          		memory-region = <&fb_reserved>;
          		dev_name = "meson-fb";
          		status = "okay";
          		interrupts = <0 3 1
          			0 89 1>;
          		interrupt-names = "viu-vsync", "rdma";
          		mem_size = <0x01800000 0x00100000>; /* fb0/fb1 memory size */
          		display_mode_default = "1080p60hz";
          		scale_mode = <1>; /** 0:VPU free scale 1:OSD free scale 2:OSD super scale */

github.com

kszaq/linux-amlogic-le/blob/amlogic-3.14.y-new/arch/arm64/boot/dts/amlogic/gxl_p212_2g.dts#L68


      
          			status = "disable";
          			compatible = "amlogic, aml_secos_memory";
          			reg = <0x0 0x05300000 0x0 0x2000000>;
          			no-map;
          		};
          		pstore:aml_pstore {
          			compatible = "amlogic, pstore";
          			reg = <0x0 0x07300000 0x0 0x100000>;
          			no-map;
          		};
          		fb_reserved:linux,meson-fb {
          			compatible = "amlogic, fb-memory";
          			size = <0x0 0x2000000>;
          			no-map;
          		};
          
          		di_reserved:linux,di {
          			compatible = "amlogic, di-mem";
          			size = <0x0 0x1e00000>; //10x1920x1088x3/2=30M
          			//no-map;
          		};

github.com

kszaq/linux-amlogic-le/blob/amlogic-3.14.y-new/arch/arm64/boot/dts/amlogic/mesongxbb-gpu-mali450.dtsi

/*
 * Amlogic GXBB Platform gpu
 *
 * Copyright (c) 2015-2015 Amlogic Ltd
 *
 * This file is licensed under a dual GPLv2 or BSD license.
 *
 */

/ {
	gpu:mali@d00c0000{
		#cooling-cells = <2>; /* min followed by max */
		compatible = "arm,mali-450";
		interrupt-parent = <&gic>;
		reg = <0 0xd00c0000 0 0x40000>, /*mali APB bus base address*/
		      <0 0xc883c000 0 0x01000>, /*hiubus base address for gpu clk cntl*/
		      <0 0xc8100000 0 0x01000>, /*aobus  base address for gpu pmu domain*/
		      <0 0xc883c000 0 0x01000>, /*hiubus base address for gpu clk cntl*/
		      <0 0xc1104440 0 0x01000>;
		interrupts = <0 160 4>, <0 161 4>, <0 162 4>, <0 163 4>,

This file has been truncated. show original

balbes150 · July 9, 2017, 3:49pm

The question You better ask in these topics.

bbr1729 · July 24, 2017, 10:14am

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!

balbes150 · August 4, 2017, 7:43am

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

Dmitriy · August 4, 2017, 7:53am

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

balbes150 · August 4, 2017, 8:02am

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.

lemmz · August 4, 2017, 8:08am

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

balbes150 · August 4, 2017, 8:14am

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.

ravelo · August 4, 2017, 9:17am

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 ?

balbes150 · August 4, 2017, 9:47am

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).

lemmz · August 4, 2017, 10:07am

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

balbes150 · August 4, 2017, 11:22am

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

lemmz · August 4, 2017, 1:06pm

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

balbes150 · August 4, 2017, 1:39pm

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

lemmz · August 4, 2017, 2:07pm

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

balbes150 · August 4, 2017, 2:14pm

You have not activated multiupload.

bootcmd=run storeboot

If multiboot is enabled, this string should contain

bootcmd=run start_autoscript; run storeboot;