VIM3.V13 20094320 KRescue install

I’ve been trying to install KRescue on my Vim3 for a while now and after a lot of failed attempts I started looking through boot.ini for the VIM3.krescue.sd.img and I noticed that there wasn’t an entry for VIM3.V13 in this section:

if test “$hwver” = “”; then

echo “[w] hwver not defined”

else

test “$hwver” = “VIM1.V12” && setenv Cdtb $DTB1

test “$hwver” = “VIM1.V13” && setenv Cdtb $DTB1

test “$hwver” = “VIM1.V14” && setenv Cdtb $DTB1

test “$hwver” = “VIM2.V12” && setenv Cdtb $DTB2

test “$hwver” = “VIM2.V14” && setenv Cdtb $DTB2

test “$hwver” = “VIM3.V10” && setenv Cdtb $DTB31

test “$hwver” = “VIM3.V11” && setenv Cdtb $DTB3

fi

if test “$maxcpus” = “”; then

echo “[w] maxcpus not defined”

test “$hostname” = “arm_gxbb” && setenv Cdtb $DTB3L

test “$hostname” = “KVIM3” && setenv Cdtb $DTB3

test “$hostname” = “kVIM1” && setenv Cdtb $DTB1

test “$hostname” = “KVim” && setenv Cdtb $DTB1

else

echo “[w] detect by maxcpus -$maxcpus-”

test “$maxcpus” = “4” && setenv Cdtb $DTB1

test “$maxcpus” = “4” && test “$hwver” = “VIM3.V12” && setenv Cdtb $DTB3L

test “$maxcpus” = “6” && setenv Cdtb $DTB3

test “$maxcpus” = “8” && setenv Cdtb $DTB2

and I’m wondering if that’s the reason I’m having trouble installing it.

If so could you tell me how to fix it so I can get it working correctly on my VIM3 v13?

Thank you!

HI

plz clarify you situation

i think u just try start krescue from SD yes ?
no need install Krescue to Emmc !!! (its same possible :wink: on for special cases !!! )
which OS/system installed already on emmc

tell me more detail for example UBOOT LOGS , screenshot etc …

If so could you tell me how to fix it so I can get it working correctly on my VIM3 v13?

i will update if it really necessary

Yes, I’m trying to run KRescue so I can easily install other operating systems on it.

It currently has the stock Android Pi on it.

I loaded the KRescue image on an SD card with linux, then mac, then rufus and none of them worked.

then i tried putting it on a usb stick and got the same issue.

I’ve tried them all with the instructions given (power off Vim3, unplug USB-C, insert SD, hold power, insert USB-C, wait for the white light to blink, release power) and after a couple seconds i get a red led with white blinking led and the TS050 shows the Khadas start screen with the right ~1/8th side of the screen being yellow.

I’ve also tried:
3x function button,
hold power, tap reset, release power after 2-3 seconds,
tweezers to short “M” and tapping reset,
holding function and turning the power on,
booting into the android boot menu and inserting sd card,
and pretty much any combo of the buttons and power that i could find.

None of them give me the KRescue boot screen i see on the walk throughs.

Hello! Write down the Krescue that is for your vim, in your case strictly for vim3, then I just insert the sd card into the slot, turn on the power and voila, Krescue is running, I don’t do any manipulations.
I wish you good luck!
:slightly_smiling_face:

You may also want to try a different SD card, some do not work well for booting Krescue or other OS.

in your case ! need just insert sd card !!!

  1. which android pi images was installed ?
  2. show me some boot logs !!!?
  3. may be try another SD cards

PS: i need something like this

cfgload: start ...
cfgload: reading /boot.ini from mmc 0:1 ...
card in
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 400000
co-phase 0x2, tx-dly 0, clock 40000000
init_part() 282: PART_TYPE_DOS
[mmc_init] mmc init success
reading /boot.ini
7968 bytes read in 4 ms (1.9 MiB/s)
cfgload: applying boot.ini...
[#] Script a:73d19960 l:7938 c:0 s:0 - run
saradc: 0x28a, hw_ver: 0x32 (VIM3.V12)
** KRESCUE START hwver: VIM3.V12 hostname: arm_gxbb maxcpus:  fdt:  source: :**
[i] scan rescue device
[i] scan rescue device 0 test 
reading /rescue/80_user_env.txt
1175 bytes read in 5 ms (229.5 KiB/s)
[i] rescue loaded 
[w] maxcpus not defined
**KRESCUE LOAD by fatload mmc 0 FROM // + post:  // VIM3.V12 // VIM3.V12**
load env
fatload mmc 0 0x32000000 /rescue/80_user_env.txt
reading /rescue/80_user_env.txt
1175 bytes read in 4 ms (286.1 KiB/s)
env import -t 0x32000000 497
load logo
fatload mmc 0 0x30000000 /splash.bmp
reading /splash.bmp
13321 bytes read in 5 ms (2.5 MiB/s)
There is no valid bmp file at the given address
BMP KO
fatload mmc 0 0x30000000 /rescue/splash.bmp.2.gz
reading /rescue/splash.bmp.2.gz
** Unable to read file /rescue/splash.bmp.2.gz **
unzip 0x30000000 0x7f800000
Uncompressed size: 518454 = 0x7E936
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
KRESCUE_TIME: 1608026509
KRESCUE_DATE: Tue 15 Dec 2020 10:01:49 AM UTC
KRESCUE_VER : 201215_400
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
addrs:  UIMAGE_ADDR ::  UINITRD_ADDR ::  DTB_ADDR
addrs: 0x1080000 :: 0x8000000 :: 0x1000000
setenv kernel_addr_r ; setenv ramdisk_addr_r ; setenv fdt_addr_r ;
:::::::::::::::
load dtb
fatload mmc 0 0x1000000 /rescue/fdt.kresq/amlogic/meson-sm1-khadas-vim3l.dtb
reading /rescue/fdt.kresq/amlogic/meson-sm1-khadas-vim3l.dtb
48474 bytes read in 11 ms (4.2 MiB/s)
libfdt fdt_path_offset() returned FDT_ERR_BADPATH
load packed initrd
fatload mmc 0 0x8000000 /rescue/uInitrd
reading /rescue/uInitrd
9052224 bytes read in 496 ms (17.4 MiB/s)
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
[i] bootargs: root=/dev/ram0 rw init=/init.squashf panic=10 net.ifnames=0 loglevel=4 fbcon=font:TER16x32 video=HDMI-A-1:1920x1080@60e kresq_type=sd config_test=sd booted= hwver=VIM3.V12 console=tty0 console=ttyAML0,115200n8 console=ttyS0,115200n8 no_console_suspend consoleblank=0 vout=576cvbs,enable hdmitx=,444,8bit hdmimode=1080p60hz cvbsmode=576cvbs osd_reverse=0 video_reverse=0 jtag=disable reboot_mode=cold_boot ddr_size= dtb=/rescue/fdt.kresq/amlogic/meson-sm1-khadas-vim3l.dtb 
[i] bootcmd:  run storeboot
load packed kernel
bootm 0x1080000 0x8000000 0x1000000
fatload mmc 0 0x1080000 /rescue/uImage
reading /rescue/uImage
6065398 bytes read in 335 ms (17.3 MiB/s)
avb2: 0
ee_gate_off ...
avb2: 0
## Booting kernel from Legacy Image at 01080000 ...
   Image Name:   kernel
   Image Type:   AArch64 Linux Kernel Image (gzip compressed)
   Data Size:    6065334 Bytes = 5.8 MiB
   Load Address: 0f080000
   Entry Point:  0f080000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 08000000 ...

Are you on a v13 Vim3?

I’ve tried this and I just get a red LED with a blinking white LED and the TS050 shows “Khadas” with about 1/8th of the screen corrupted with yellow then this slowly fades to all black. I’ll add a picture to this post so you can see.

Are you on a v13 Vim3?

yes i have check it - works fine

I’ve tried this and I just get a red LED with a blinking white LED

its right !!! RED LED is ON WHITE BLINK == display what Krescue was started

TS050 shows “Khadas”

Krescue works only with HDMI !!! at this moment

PS: headless users in any case can get access via network http://krescue/ or ssh root@krescue

WELLCOME

2 Likes