Depends on how to make the dump. If you just do plain dd then it will make 29gb image. If you dd and pipe it to compress image file then it will be compressed version of 10gb.
You will need dd and tar binary to do this.
@hyphop I see last uboot is from 2021-01-27 Is this the latest ?
I plan to update uboot pkgs for khadas devices and prepare new images so you can make new krescue images.
Please name the uboot as per its version so we can come to know without the need of booting into it and finding the uboot version.
@hyphop Please let me know asap else image release will be delayed to next week
Thanks.
You can burn uboot to SPI with Krescue in rescue shell.
I prefer to have Android on my EMMC so I don’t have any other choice now but having legacy uboot
with AML vendor bootloader on my emmc.
But thanks to hyphop and his SPI uboot I can easily run any Linix distros with mainline uboot from SD or USB stick without inverted colors issue. I only need to switch to SPI bootmode in Krescue with KBI switch. If I need loading Android while in SPI bootmode I make three short presses on Function button after powering VIM3 on to start Android. And to return to emmc boot mode I can stop boot sequence by pressing Space at the prompt and typing:
KBI bootmode w emmc
I find it very handy until there is no more elegant solution. At least I couldn’t find.
@Dingo
Wow, that’s great. Thanks for the great tip. I don’t wanna use Android for now, but maybe in a couple of weeks and this will help me prioritize boot as my requirement
Later today I will send you where you can find instructions for burning Uboot to SPI with
rescue shell.
And maybe I’m wrong but you cannot run Linux distros built with legacy uboot if you have
mainline uboot in your emmc. At least I could run this distro from SD:
VIM3_Ubuntu-xfce-bionic_Linux-4.9_arm64_SD-USB_V20191231only with EMMC bootmode
with Android installed and legacy stuff.
Yes I tried to boot coreelec when there is mainline uboot in emmc but it failed to boot while every other mainline Ubuntu and armbian booted successfully.
I can flash legacy uboot to spi and switch boot mode to spi when I need to run android or coreelec from sdcard (this is the opposite of what you’re doing I think)
Thank you again for your support, it is very much appreciated.
i will make update for mainline uboot dl.khadas.com - Index of /firmware/uboot/mainline/ - at the end of this week or begin of next !! - i will make special announce about this (and about new features)
I see last uboot is from 2021-01-27 Is this the latest ?
yes its was last !
Thank you so much for your great work! Will be waiting for new release.
Could you also check if I make correct steps to write your mainline uboot to spi without serial debugging tool. It will be especially interesting to @Yasir_Javed
I used your spi uboot version 0.8 of Jan 27 and copy VIM3.u-boot.spi.bin to my SD card with Krescue
to Dumps partition.
Then I start Krescue and if I go to Image WRITE to… EMMC to browse my dumps then in Rescue Shell I will find my images at /tmp/mounts/dumps/
Or I can go directly to rescue shell and mount mmcblk1p2 to tmp folder for example and check with ls if uboot file is in mounted folder
Then I make MTD on and burn spi uboot using your instructions from here: khadas-rescue/docs/README-rescue-spi-mmc.md at master · hyphop/khadas-rescue · GitHub -
to use SPI + SD:
But in my case I have a different path to uboot file - /tmp/mounts/dumps/ or manually mounted point
I also found the other commands to write uboot to SPI:
spi_boot /tmp/sd/rescue/u-boot.vim2.legacy.spi.bin - write legacy uboot to spi
spi_boot /tmp/sd/rescue/u-boot.vim2.mainline.spi.bin - write mainline uboot to spi
but didn’t try it as mtd write worked fine for me.
I know that it is even easier to switch boot mode but the problem is that when I switch to SPI boot mode with your latest spi uboot I cannot run Krescue as it is stuck at booting and if I need to switch back to EMMC boot mode I can do it only at boot prompt. I stop bootscript by pressing Space and write:
kbi bootmode w emmc
But it is also easy to do.
And this is where Krescue hungs in my case if I switched to SPI bootmode:
If you could add the option to flash uboot to spi through krescue and a basic file manager to copy images from a usb to sdcard dump location, that would be amazing as well
The Wizard menu where we select image to burn on emmc, it would be great if we have copy/paste option there. When we insert a usb, it’s mounted and we can copy images from usb to sdcard dump…
It’s very long time and Krescue image dump on dl.khadas.com is having all very old images.
I would appreciate if khadas team gives it some cleaning / organizing and updates to Ubuntu /manjaro /coreelec /Debian etc images for mainline specially.
I know everything is present in Fenix but Fenix requires a x86 build host (github doesn’t build properly sometimes) and downloading from github is also very very slow. I think many people will appreciate a clean and updated Krescue image list… If it takes too much effort, than no problem, we understand it’s a large task. Thanks again in advance…
Hi all, it’s been a long time and i hope everyone is healthy enough,
@hyphop
please remind me of the best way using krascue and the lowest number of steps for transforming a brand new android based vim3L into a debian buster server booting directly from its emmc ?
Can the method be used if I only can connect to internet via wifi and not ethernet ?
As i wanted to boot on kresc flashed to my sd card, i interupted boot sequence in my serial console and typed ‘store init 3’ and then ‘reset’
but what i get in only this message on screen
LOOP:1;EMMC:0;READ:0;CHK:1F;READ:0;CHK:1F;READ:0;CHK:1F;SD?:0;SD:0;READ:2;USB:8;LOOP:2;EM;
It seems that my only option is to use the amlogic flashing tool to repopulate the emmc, according to VIM3 can't power on - #3 by ru719iz283 after using some chinese to english translator
))