NEW VIM1 ANDROID image VIM1.Android.Pie_V200317 for krescue
NOTES: this image have special option write without bootup logo
converted from aml-burn-tool image
NEW VIM1 ANDROID image VIM1.Android.Pie_V200317 for krescue
NOTES: this image have special option write without bootup logo
converted from aml-burn-tool image
all previous CE images was removed or rewrited
at this moment we have 4 diff images
curl -sfL dl.khadas.com/.mega | sh -s - -l | grep CORE
https://dl.khadas.com/Firmware/Krescue/images/VIM3x.COREELEC.9.2.2.emmc.kresq
https://dl.khadas.com/Firmware/Krescue/images/VIM3x.COREELEC.9.2.nightly.emmc.kresq
https://dl.khadas.com/Firmware/Krescue/images/VIM12.COREELEC.9.2.2.emmc.kresq
https://dl.khadas.com/Firmware/Krescue/images/VIM12.COREELEC.9.2.nightly.emmc.kresq
curl -sfL dl.khadas.com/.mega | sh -s - -l | grep CORE
VIM3x.COREELEC.9.2.2.emmc.kresq
VIM3x.COREELEC.9.2.nightly.emmc.kresq
VIM12.COREELEC.9.2.2.emmc.kresq
VIM12.COREELEC.9.2.nightly.emmc.kresq
# VIM2
curl -sfL dl.khadas.com/.mega | sh -s - VIM2 VIM12.COREELEC.9.2.2.emmc.kresq > /dev/mmcblk0
curl -sfL dl.khadas.com/.mega | sh -s - VIM2 VIM12.COREELEC.9.2.nightly.emmc.kresq > /dev/mmcblk0
# VIM1
curl -sfL dl.khadas.com/.mega | sh -s - VIM1 VIM12.COREELEC.9.2.2.emmc.kresq > /dev/mmcblk0
curl -sfL dl.khadas.com/.mega | sh -s - VIM1 VIM12.COREELEC.9.2.nightly.emmc.kresq > /dev/mmcblk0
# VIM3
curl -sfL dl.khadas.com/.mega | sh -s - VIM3 VIM3x.COREELEC.9.2.2.emmc.kresq > /dev/mmcblk0
curl -sfL dl.khadas.com/.mega | sh -s - VIM3L VIM3x.COREELEC.9.2.nightly.emmc.kresq > /dev/mmcblk0
# VIM3L
curl -sfL dl.khadas.com/.mega | sh -s - VIM3L VIM3x.COREELEC.9.2.2.emmc.kresq > /dev/mmcblk0
curl -sfL dl.khadas.com/.mega | sh -s - VIM3L VIM3x.COREELEC.9.2.nightly.emmc.kresq> /dev/mmcblk0
So what’s the difference if I install your Krescue CoreELEC image to my VIM3 instead of installing CoreELEC using their ceemmc
tool? Did you do any tweaks/fixes in your images?
One advantage of ceemmc is that it should be possible to dual-boot both Android and CoreELEC from the internal eMMC instead of just dual-booting from different media (didn’t test this yet myself but I will when I have the time).
not big different ! just only khadas IR/RC woks out of box + and no need any additional preparation with dtb + krescue installation dont have any deps from install system - just install and use it
both installations have same coreelec base - without changes
One advantage of ceemmc is that it should be possible to dual-boot both Android and CoreELEC from the internal eMMC instead of just dual-booting from different media (didn’t test this yet myself but I will when I have the time).
krescue rewrite all emmc content every time , but u still posible to use boot from sd or usb other system
Thanks. So no specific U-BOOT modifications or anything? If I install your Android firmware and then use ceemmc I have the same U-BOOT?
all COREELEC emmc images - for krescue was updated - VIM1 VIM2 VIM3 VIM3L
Hope it will be possible to also develop Krescue for Khadas Edge-V in future.
Yes I think he will need to prioritise things. I will be available if there is any tester needed.
So he can concentrate of scripting and testing can be done by someone else.
yes its in our plans already!
im hope too;) porting krescue for rock-chip willbe not hard
@Hyphop I don’t know if you realize how important Krescue is for the Khadas line. It completely changes the game. It would be one of my main selling point of these boards if i was a reseller. We Edge owners and I’m sure I can speak for most of us, always feel left out. No one ever talks big about the edge. The edge-V maybe not as much. But whenever I need something Khadas related It’s always catered to the VIM lines. Now i’m not harping on you because all your amazing hard work is very much appreciated hypop. But I just ask can we please get Krescue on the edge and make it a #1 priority? Seriously, you announced in Nov it’s in the works. I am really starting to regret buying the edge. My kaptain comes in on thursday and i’m just not as excited as I once was. Can we get a timeline at the very least? Maybe an Alpha release
im understand reason of your sad and think we can change this situation for EDGE line
we will start porting krescue for edge - very very soon
and will inform about progress
Thanks @hyphop. Do you have the edge? If not I’m going to buy one for you so maybe next idea you have will start with the edge
bit tnx ! i have enough EDGE boards
Hi,
I have a problem with ethernet on VIM3 Pro with Krescue and other images on kernels 5.x – link down
But with debian 9.11 eth0 is UP.
With kernel 4.x.x seems to working ok like below :
Coreelec 9.2.2 OK
Linux CoreELEC 4.9.113 #1 SMP PREEMPT Mon Apr 13 20:13:06 BST 2020 aarch64 GNU/Linux
[ 0.564225@2] meson6-dwmac ff3f0000.ethernet: no reset control found
[ 0.564229@2] stmmac - user ID: 0x11, Synopsys ID: 0x37
[ 0.567210@4] libphy: stmmac: probed
[ 0.567215@4] eth%d: PHY ID 001cc916 at 0 IRQ POLL (stmmac-0:00) active
[ 0.567218@4] eth%d: PHY ID 001cc916 at 1 IRQ POLL (stmmac-0:01)
[ 0.683354@4] efusekeyname: mac offset: 0 size: 6
[ 13.461554@0] meson6-dwmac ff3f0000.ethernet eth0: fail to init PTP.
[ 14.474768@0] meson6-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Ubuntu 18.04.4 LTS OK
Linux Khadas 4.9.206 #13 SMP PREEMPT Tue Dec 31 00:37:47 CST 2019 aarch64 aarch64 aarch64 GNU/Linux
[ 25.422105] meson6-dwmac ff3f0000.ethernet eth0: fail to init PTP.
[ 28.501201] meson6-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
debian 9.11 OK
Linux Khadas 5.5.0-rc2 #0.8.3 SMP PREEMPT Sun Jan 19 14:10:00 +09 2020 aarch64 GNU/Linux
[ 5.262364] meson8b-dwmac ff3f0000.ethernet eth0: PHY [0.0:00] driver [RTL8211F Gigabit Ethernet]
[ 5.396752] meson8b-dwmac ff3f0000.ethernet: Failed to reset the dma
[ 5.400517] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_hw_setup: DMA engine initialization failed
[ 5.412752] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_open: Hw setup failed
[ 6.028058] meson8b-dwmac ff3f0000.ethernet eth0: PHY [0.0:00] driver [RTL8211F Gigabit Ethernet]
[ 6.044681] meson8b-dwmac ff3f0000.ethernet eth0: No Safety Features support found
[ 6.047920] meson8b-dwmac ff3f0000.ethernet eth0: PTP not supported by HW
[ 6.054680] meson8b-dwmac ff3f0000.ethernet eth0: configuring for phy/rgmii link mode
[ 8.913389] meson8b-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 6.054680] meson8b-dwmac ff3f0000.ethernet eth0: configuring for phy/rgmii link mode
[ 8.913389] meson8b-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Could you give me some advice ?
Please add ethtool to krescue if it’s possible
Regards
YES ! i know about this problem and still try to solve it
ABOUT PROBLEM: legacy kernel NO problem its only mainline linux kernel problem for VIM3 + VIM3L (if mainline kernel start after legacy without poweroff )
SOLUTION: poweroff ( unplug power cable and plug again ) ethernet must works again
Maybe then not enough
I have found no need to unplug / replug power lead. Poweroff and on again with remote works for me most times
It will be better if / when a simple reset is enough.
yes its have same effect !
It will be better if / when a simple reset is enough.
sure but this bug still not fixed in mainline Linux kernel