ROCK64 not booting
#1
Hi, I'm trying to boot Armbian on a ROCK64 4GB but I'm stuck.
I flashed "Armbian_5.90_Rock64_Debian_stretch_default_4.4.182_desktop.img" on a MicroSD card with Etcher.
From the serial output I get this

Code:
DDR version 1.13 20180428 ID:0xFFF In LPDDR3 786MHz Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB ddrconfig:7 OUT U-Boot SPL 2017.09-rockchip-ayufan-1065-g95f6152134 (Aug 26 2019 - 12:40:32) board_init_sdmmc_pwr_en setup_ddr_param  1 booted from SPI flash Trying to boot from SPI NOTICE:  BL31: v1.3(debug):9d3f591 NOTICE:  BL31: Built : 14:39:02, Jan 17 2018 NOTICE:  BL31:Rockchip release version: v1.3 INFO:    ARM GICv2 driver initialized INFO:    Using opteed sec cpu_context! INFO:    boot cpu mask: 1 INFO:    plat_rockchip_pmu_init: pd status 0xe INFO:    BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR:   Error initializing runtime service opteed_fast INFO:    BL31: Preparing for EL3 exit to normal world INFO:    Entry point address = 0x200000 INFO:    SPSR = 0x3c9 U-Boot 2017.09-rockchip-ayufan-1065-g95f6152134 (Aug 26 2019 - 12:41:04 +0000) Model: Pine64 Rock64 DRAM:  4 GiB MMC:   rksdmmc@ff520000: 0, rksdmmc@ff500000: 1 SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB *** Warning - bad CRC, using default environment In:    serial@ff130000 Out:   serial@ff130000 Err:   serial@ff130000 Model: Pine64 Rock64 misc_init_r cpuid=55524b503039303231000000000f222c serial=556d7db57902d0a Net:   eth0: ethernet@ff540000 Hit any key to stop autoboot:  0 Card did not respond to voltage select! mmc_init: -95, time 9 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2949 bytes read in 21 ms (136.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 102 bytes read in 18 ms (4.9 KiB/s) 4460994 bytes read in 234 ms (18.2 MiB/s) 19044360 bytes read in 897 ms (20.2 MiB/s) 73888 bytes read in 126 ms (572.3 KiB/s) ** File not found /boot/dtb/rockchip/overlay/rockchip-fixup.scr ** ## Loading init Ramdisk from Legacy Image at 04000000 ...   Image Name:   uInitrd   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)   Data Size:    4460930 Bytes = 4.3 MiB   Load Address: 00000000   Entry Point:  00000000   Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000   Booting using the fdt blob at 0x1f00000   Loading Ramdisk to fcac0000, end fcf01182 ... OK   reserving fdt memory region: addr=1f00000 size=78000   Loading Device Tree to 00000000fca45000, end 00000000fcabffff ... OK Starting kernel ... [    0.000000] Booting Linux on physical CPU 0x0 [    0.000000] Initializing cgroup subsys cpuset [    0.000000] Initializing cgroup subsys cpu [    0.000000] Initializing cgroup subsys cpuacct [    0.000000] Linux version 4.4.182-rockchip64 (root@nightly) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f8e1a2eed33b1edc85d4] (Linaro GCC 7.4-2019.02) ) #1 SMP Fri Jun 28 17:34:00 CEST 2019 [    0.000000] Boot CPU: AArch64 Processor [410fd034] [    0.000000] earlycon: Early serial console at MMIO32 0xff130000 (options '') [    0.000000] bootconsole [uart0] enabled ERROR:   suspend_mode_handler: unhandled sip (0x1) ERROR:   suspend_mode_handler: unhandled sip (0x4) [   44.727910] reboot: Restarting system INFO:    PSCI Power Domain Map: INFO:      Domain Node : Level 2, parent_node -1, State ON (0x0) INFO:      Domain Node : Level 1, parent_node 0, State ON (0x0) INFO:      Domain Node : Level 0, parent_node 0, State ON (0x0) INFO:      Domain Node : Level 0, parent_node 0, State ON (0x0) INFO:      CPU Node : MPID 0x0, parent_node 1, State ON (0x0) INFO:      CPU Node : MPID 0x1, parent_node 1, State ON (0x0) INFO:      CPU Node : MPID 0x2, parent_node 1, State ON (0x0) INFO:      CPU Node : MPID 0x3, parent_node 1, State ON (0x0)
while on the screen I get this
[Image: 3FRQEGi.jpg]
and then it reboots and does all this all over again and again...
Could someone help me?
Thanks in advance
#2
I don't have a rock64. From the screen output, I gain the impression that there is an initrd booted off /boot. It does not find an root partition. Can you attach micro SD card to another linux computer and check the sanity of SD card, e.g.


check the partition table via

fdisk /dev/XXX

then mount all partitions.

Does that all work?
#3
A bad image or SD card looks like your problem. Download the image again and write the image to a different SD card to rule both out.
#4
(09-06-2019, 05:45 PM)Der Geist der Maschine Wrote: I don't have a rock64. From the screen output, I gain the impression that there is an initrd booted off /boot. It does not find an root partition. Can you attach micro SD card to another linux computer and check the sanity of SD card, e.g.


check the partition table via

fdisk /dev/XXX

then mount all partitions.

Does that all work?
It all seems normal to me
[Image: C0A5zHf.png]

(09-06-2019, 05:59 PM)Rocklobster Wrote: A bad image or SD card looks like your problem. Download the image again and write the image to a different SD card to rule both out.
I downloaded again the Armbain Stretch image, checked the SHA256 and changed MicroSD card from a known good SanDisk Ultra 16GB to a known good Samsung EVO 16GB.
I also tried writing the image with Win32DiskImager but the behavior I get it's still the same as before.
#5
With an old image like "stretch-minimal-rock64-0.6.37-221-arm64.img" I can get it to boot a bit further, but the ending is the same.
Boot log here (too long to fit in this reply)
#6
Uhh. I have no idea what goes wrong in mounting the root filesystem. A desperate attempt would be replacing in boot/armbianEnv.txt 

rootdev=UUID=XXX

with

rootdev=/dev/mmcblk0p1
or
rootdev=/dev/sda1
#7
(09-07-2019, 01:37 PM)Der Geist der Maschine Wrote: Uhh. I have no idea what goes wrong in mounting the root filesystem. A desperate attempt would be replacing in boot/armbianEnv.txt 

rootdev=UUID=XXX

with

rootdev=/dev/mmcblk0p1
or
rootdev=/dev/sda1

I'm still using "stretch-minimal-rock64-0.6.37-221-arm64.img".
The content of boot/extlinux.conf (edited with /dev/sda1) is the following
Code:
timeout 30 default kernel-latest menu title select kernel label kernel-latest    kernel /Image    initrd /initrd.img    fdt /dtb    append rw root=/dev/sda1 rootwait rootfstype=ext4 panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 label kernel-previous    kernel /Image.bak    initrd /initrd.img.bak    fdt /dtb.bak    append rw root=/dev/sda1 rootwait rootfstype=ext4 panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
On the screen i get only the messages with the timestamp at the beginning of the line.
Boot log with /dev/mmcblk0p1 here
Boot log with /dev/sda1 here

Installed latest u-boot and booted no problem from USB with "Armbian_5.90_Rock64_Debian_stretch_default_4.4.182_desktop".
Boot log here 
Why doesn't it boot from MicroSD?!  Angry
I noticed that all 3 LEDs that are present on the board (DC in, PWR, STBY) stay lit all the time, is it normal?
#8
Maybe someone else can help you, but I think you are doomed to help yourself. Perhaps rebuild initrd and include busybox. Then boot into the busybox shell and look around.
#9
Read this Wiki carefully. The presence of uboot may be your problem https://wiki.pine64.org/index.php/NOOB

All LEDs remain lit on the board.
#10
(09-08-2019, 01:42 PM)Rocklobster Wrote: Read this Wiki carefully. The  presence of uboot may be your problem https://wiki.pine64.org/index.php/NOOB

All LEDs remain lit on the board.

Trying to boot "Armbian_5.90_Rock64_Debian_stretch_default_4.4.182_desktop" from MircoSD.
Boot log with u-boot here and without u-boot here.
As you can see I'm not able to boot in either case and on the screen I get the same things as in the photo in the first post.

While flashing/erasing the SPI flash with the tools provided here I should see the LEDs blinking but instead I get error messages regarding setting the LEDs status and all the LEDs stay lit. Is this a bug of the software or is it a problem with my board?
Erasing log here and flashing log here.


Possibly Related Threads…
Thread Author Replies Views Last Post
  Rock64 v2.0 u-boot SPI issues ju0n 1 1,767 09-25-2026, 11:19 PM
Last Post: mysy
  Rock64 No Audio @ Debian 12 dmitrymyadzelets 2 6,599 04-08-2024, 06:47 AM
Last Post: dmitrymyadzelets
  OpenWRT on the Rock64 CanadianBacon 14 30,158 04-03-2024, 08:48 AM
Last Post: helpmerock
  Rock64 bricked shawwwn 7 17,609 03-17-2024, 12:22 PM
Last Post: dmitrymyadzelets
  Rock64 won't boot luminosity7 10 19,932 03-16-2024, 08:33 AM
Last Post: dmitrymyadzelets
  Rock64 doesn't boot dstallmo 1 5,201 03-16-2024, 08:29 AM
Last Post: dmitrymyadzelets
  How well does Rock64 deal with HDR and Atmos on Kodi? drvlikhell 3 10,523 04-29-2023, 04:24 AM
Last Post: newestssd
  Rock64 board not working, no HDMI no Ethernet. EDited 3 11,500 01-17-2023, 02:31 PM
Last Post: Flagtrax
  ROCK64 v3 can it boot from USB? Tsagualsa 4 10,912 11-29-2022, 11:31 AM
Last Post: Macgyver
  rock64 v3 spiflash Macgyver 0 5,256 11-28-2022, 02:18 PM
Last Post: Macgyver

Forum Jump:


Users browsing this thread: 1 Guest(s)