@vrabac Thank you for testing. I think I have found the reason: dwc_otg needs to be built as a kernel module, not built-in. I am building 8.0.2c right now and it should be fixed.
I know that scanning is very slow, so far I haven’t looked into fixing this as most of the times you go to wireless settings once, connect and never go back unless you change your SSID.
@kszaq with the 8.0.2c and the dtb v2 file, everything is fine here.
No big deal with WiFi settings and Automatic updates. Thank you for letting me know.
My next step would be writing your image to eMMC. I found here script you are using to prepare eMMC. Is this found in this pastelog “standard Amlogic” memory layout?
Also could it be that my microSD is broken? See that above pastelog from line 112.
@zewen so you don’t have Android ROM flashed before? I use Vim_Marshmallow_Root_170303.7z . You need to have Android on eMMC to activate multiboot (by going to Android Menu “update&backup” (settings - about - update&backup - updateLocale-select - aml_autoscript.zip - update), or inside u-boot by running “run update”. Then it should automatically boot LibreELEC from microSD (you may see reboot few times).
Hi vrabac: @vrabac
boot with Vim_Marshmallow_Root_170303.7z in emmc,
1.At Android/Settings/About Device/System/updates, under the UpdateLocale section, click Select, but there have not an selection window, which means i canot select aml_autoscript.zip file
2.Not have an aml_autoscript.zip :in this topic How to boot balbes150 libreelec image? I have know that when you burned LibreELEC.img to microSD, there will be an file named aml_autoscript.zip. But when I do this there have not this file.(my image is compile from the sourced code at khadas github)
How is this going? thank you!
@kszaq
Does this set of u-boot commands activate multiboot on any u-boot ? Here is your s905_autoscript.src
I don’t have anymore Android on eMMC so i can’t do this settings - about - update&backup - updateLocale-select - aml_autoscript.zip - update
I flashed Ubuntu server image from khadas (as android u-boot does not have ext4 boot support), but I don’t know how to activate back that multiboot, to boot your LibreELEC image which is already on microSD and working fine for weeks.
Today I finally got LibreELEC 8 running on my Vim Pro.
The tricky part was how to enter u-boot. I need to use an UART cable, Android build “Vim_Marshmallow_Root_170303”, when rebooting the board, press any key to enter the u-boot.
Hi. I checked out the launch of your latest build LE for VIM Pro. When using dtb c your site, LE does not start. I replaced “dtb.img” on my option, it’s boot and all running (kvim.dtb). This is the source code of dts , which I use to build working file. Maybe it will help you to find the cause of the failure in your file for the new version (8.2) to run on the VIM1.
I checked only the common run, work wired, work audio via BT, I see the WiFi network, tried playing a simple video. Installing to internal memory I haven’t checked (I have installed in eMMC Armbian with KODI that plays a fullscreen video).
I tried yesterday to update for Kszaq-s LE 8.2 with his device tree, and now my Vim does not boot, my device is stop on khadas logo. How can I fix this? Usb burning tool does not see my device, I can not erease EMMC with buttons on the Vim, and I can not boot into upgrade mode with keys mode…
I doubt that the possible transition to another version using the tar file. This is a different version of the kernel 32 or 64 bit. You can burn my image to an external drive, update multiboot (it is universal and can work with all the LE and Linux images, including images Kszaq), and try my way with external media. In this mode you can use both versions of the LE in parallel , as needed.
You can use contact closure “M” of the register, in order to start the process of firmware with a PC.
Thank you, with this method my VIM is working again. I installed LE 8.1.2 with your dtb file and it is working fine from external drive, but when I am using the “installtointernal” command from SSH, my device stop booting, just show the Khadas logo.