07-23-2024, 12:41 PM
I have been struggling with trying to get debian installed and booting on my rock64 v2 via emmc.
So far, the most current method I have tried is this guide. Everything seemed to go fine until the install finished and I rebooted. Upon boot-up I saw the following on serial console:
I am able to run the installer and install to an SD card without any issues. Reboot will result in a working system. If I pull the EMMC card out and mount it on a separate machine via adapter, the files and partition layout look like what I would expect, the dtb seems to be in place and correct for the hardware, etc. I poked around a bit in the busybox shell but didn't have a solid plan for what I was trying to achieve other than basic investigation.
Does anyone here have any idea where I should look next? I've gone through this setup/install process multiple times and the result is the same each time. I did have arch linux running on this board for a month or so but updates broke it twice and both times I just reinstalled. I got tired of that since this is normally a headless system in a place where I don't want to have to remove it over and over.
So far, the most current method I have tried is this guide. Everything seemed to go fine until the install finished and I rebooted. Upon boot-up I saw the following on serial console:
Code:
U-Boot TPL 2023.01+dfsg-2+deb12u1 (Apr 18 2024 - 22:00:21)
LPDDR3, 800MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2023.01+dfsg-2+deb12u1 (Apr 18 2024 - 22:00:21 +0000)
Trying to boot from MMC2
NOTICE: BL31: v2.8(debug):
NOTICE: BL31: Built : 06:31:44, Nov 25 2022
NOTICE: BL31:Rockchip release version: v1.2
INFO: ARM GICv2 driver initialized
INFO: plat_rockchip_pmu_init: pd status 0xe
INFO: BL31: Initializing runtime services
INFO: BL31: cortex_a53: CPU workaround for 855873 was applied
WARNING: BL31: cortex_a53: CPU workaround for 1530924 was missing!
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9
U-Boot 2023.01+dfsg-2+deb12u1 (Apr 18 2024 - 22:00:21 +0000)
Model: Pine64 Rock64
DRAM: 2 GiB
PMIC: RK8050 (on=0x50, off=0x10)
Core: 228 devices, 24 uclasses, devicetree: separate
MMC: mmc@ff500000: 1, mmc@ff520000: 0
Loading Environment from MMC... Card did not respond to voltage select! : -110
*** Warning - No block device, using default environment
In: serial@ff130000
Out: serial@ff130000
Err: serial@ff130000
Model: Pine64 Rock64
Net: eth0: ethernet@ff540000
Hit any key to stop autoboot: 0
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2904 bytes read in 4 ms (709 KiB/s)
## Executing script at 00500000
32688064 bytes read in 848 ms (36.8 MiB/s)
36095 bytes read in 10 ms (3.4 MiB/s)
30462286 bytes read in 775 ms (37.5 MiB/s)
Booting Debian 6.1.0-23-arm64 from mmc 0:1...
Moving Image from 0x2080000 to 0x2200000, end=41d0000
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Working FDT set to 1f00000
Loading Ramdisk to 7b20f000, end 7cf1c14e ... OK
Loading Device Tree to 000000007b203000, end 000000007b20ecfe ... OK
Working FDT set to 7b203000
Starting kernel ...
[ 4.349873] rockchip-pm-domain ff100000.syscon:power-controller: failed to get ack on domain 'hevc', val=0x88220
[ 6.195026] rockchip-pinctrl pinctrl: pin gpio0-2 already requested by vcc-host-5v-regulator; cannot claim for vcc-host1-5v-regulator
[ 6.196127] rockchip-pinctrl pinctrl: pin-2 (vcc-host1-5v-regulator) status -22
[ 6.196802] rockchip-pinctrl pinctrl: could not request pin 2 (gpio0-2) from group usb20-host-drv on device rockchip-pinctrl
[ 6.197825] reg-fixed-voltage vcc-host1-5v-regulator: Error applying setting, reverse things back
[ 7.526011] mmc1: mmc_select_hs200 failed, error -110
[ 7.526497] mmc1: error -110 whilst initialising MMC card
[ 8.488081] mmc1: mmc_select_hs200 failed, error -110
[ 8.488567] mmc1: error -110 whilst initialising MMC card
[ 9.452265] mmc1: mmc_select_hs200 failed, error -110
[ 9.452753] mmc1: error -110 whilst initialising MMC card
[ 10.489412] mmc1: mmc_select_hs200 failed, error -110
[ 10.489902] mmc1: error -110 whilst initialising MMC card
Gave up waiting for suspend/resume device
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/d08756f8-8dcd-41f0-b02b-c4ff2da5e68b does not exist. Dropping to a shell!
BusyBox v1.35.0 (Debian 1:1.35.0-4+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)I am able to run the installer and install to an SD card without any issues. Reboot will result in a working system. If I pull the EMMC card out and mount it on a separate machine via adapter, the files and partition layout look like what I would expect, the dtb seems to be in place and correct for the hardware, etc. I poked around a bit in the busybox shell but didn't have a solid plan for what I was trying to achieve other than basic investigation.
Does anyone here have any idea where I should look next? I've gone through this setup/install process multiple times and the result is the same each time. I did have arch linux running on this board for a month or so but updates broke it twice and both times I just reinstalled. I got tired of that since this is normally a headless system in a place where I don't want to have to remove it over and over.