Jump to content

Failing to boot from EMMC

Guest

By Guest
in Rockchip

 Share

Recommended Posts

Guest

Guest

Posted
Posted

Hi, everyone. The Kobo site is kind of difficult to navigate if you're looking for relevant information, but I came to the conclusion that this is the right place for support. Forgive me if I'm mistaken.

 

I was wondering if someone could help me interpret these bootlogs from serial term when trying to boot my Helios64 from the EMMC. Following the instructions on Kobol's site, I flashed their u-boot image to an sd card, booted the Helios64 off of said sd, fetched the latest image of Armbian, unpacked that image, and flashed it from my laptop to the Helios64 via usbc to what I presume is the correct interface. Could it be that I messed up? Here's a quick example of the weird behaviour when I take the sd card out and turn on the machine:

 

  Reveal hidden contents

 

Basicall, it keeps repeating this dialogue but with different files. So, for the one above, it says "Retrieving file: pxelinux.cfg/01-64-62-66-d0-03-42", but then it'll go on and say "Retrieving file: pxelinux.cfg/C0A8018", and so on. It'll keep doing that for a bunch of files, after which there's no boot screen or login prompt or anything. I haven't managed to ssh into it, either, but it may be my mistake that I can't figure out how to do so.

 

If I unplug the ethernet, it looks like this:

  Reveal hidden contents

 

I'm really dreading the idea that I have to take apart the chassis and jump the board so that I can boot from the sd card. I don't understand why the sd card wouldn't be before the emmc in Helios64's boot order. That seems absurd to me.

 

Anyway, here's at least part of the log. I didn't feel like sitting around to let it go through all the files:

  Reveal hidden contents

 

aprayoga

aprayoga

Posted
Posted

@qrthi it seems something wrong during writing to eMMC.

Your log show these lines 

Wrong image format for "source" command
SCRIPT FAILED: continuing...

How did you write the image? We recommend to use Etcher because it has write verification.

 

  On 2/17/2021 at 8:52 PM, qrthi said:

I'm really dreading the idea that I have to take apart the chassis and jump the board so that I can boot from the sd card. I don't understand why the sd card wouldn't be before the emmc in Helios64's boot order.

Expand  

 

The boot mode jumper only needed if for some reason the bootloader corrupted and to fix it you need to completely bypass the boot device.

If the bootloader (u-boot) just fine, it will load Armbian from the sdcard first.

  Quote

Hit any key to stop autoboot:  0 
Card did not respond to voltage select!
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr

Expand  

The "Card did not respond to voltage select" is because you removed the sdcard.

If you put Armbian sdcard, the lines would be 

Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 6 ms (517.6 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1

 

My suggestion,

1. Download latest Armbian image.

2. Since you already have u-boot on your eMMC, no need to download and write the helios64_sdcard_u-boot-only.img.xz into sdcard.

3. Power on and enter UMS recovery mode

4. Write the image using Etcher. No need to extract the image. Etcher can handle it just fine.

5. Reboot Helios64.

 

 

1
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept