Booting my RockPro64 from NVMe drive
#1
Hello.

I see some messages that I'm not sure are ok to ignore. Hope someone can tell me something else about them.
This is my boot log from UART (minicom):

Code:
U-Boot TPL 2021.01-09768-gc762ab29b8 (Mar 20 2021 - 13:48:40)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2021.01-09768-gc762ab29b8 (Mar 20 2021 - 13:48:40 +0000)
Trying to boot from SPI
NOTICE:  BL31: v2.4(release):v2.4
NOTICE:  BL31: Built : 13:33:26, Mar 20 2021


U-Boot 2021.01-09768-gc762ab29b8 (Mar 20 2021 - 13:48:40 +0000)

SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 RockPro64 v2.1
DRAM:  3.9 GiB
PMIC:  RK808
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Pine64 RockPro64 v2.1
Net:   eth0: ethernet@fe300000
Hit any key to stop autoboot:  0
Card did not respond to voltage select! : -110
Card did not respond to voltage select! : -110

Device 0: Vendor: 0x144d Rev: 2B2QEXM7 Prod: S4EUNJ0N308323A     
            Type: Hard Disk
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)
... is now current device
Scanning nvme 0:1...
Found U-Boot script /boot.scr
2226 bytes read in 2 ms (1.1 MiB/s)
## Executing script at 00500000
27260800 bytes read in 52 ms (500 MiB/s)
56812 bytes read in 3 ms (18.1 MiB/s)
27165617 bytes read in 54 ms (479.8 MiB/s)
Booting Debian 5.10.0-6-arm64 from nvme 0:1...
Moving Image from 0x2080000 to 0x2200000, end=3ca0000
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to f051e000, end f1f063b1 ... OK
   Loading Device Tree to 00000000f050d000, end 00000000f051ddeb ... OK
incorrect device type in 1

Starting kernel ...

[    3.917989] rockchip-usb2phy ff770000.syscon:usb2-phy@e450: failed to create phy
[    3.924167] rockchip-usb2phy ff770000.syscon:usb2-phy@e450: failed to create phy
[    3.926395] sdhci-arasan fe330000.sdhci: No phy for arasan,sdhci-5.1.
[    3.947158] rk_gmac-dwmac fe300000.ethernet: phy regulator is not available yet, deferred probing
[    3.958031] rockchip-usb2phy ff770000.syscon:usb2-phy@e460: failed to create phy
[    3.958918] rockchip-usb2phy ff770000.syscon:usb2-phy@e450: failed to create phy
[    3.968522] rk_gmac-dwmac fe300000.ethernet: phy regulator is not available yet, deferred probing
[    4.021567] rockchip-usb2phy ff770000.syscon:usb2-phy@e450: failed to create phy
[    4.030784] rockchip-usb2phy ff770000.syscon:usb2-phy@e460: failed to create phy
[    4.033946] rk_gmac-dwmac fe300000.ethernet: phy regulator is not available yet, deferred probing
[    4.049366] rockchip-usb2phy ff770000.syscon:usb2-phy@e450: failed to create phy
[    4.155651] rk_gmac-dwmac fe300000.ethernet: phy regulator is not available yet, deferred probing
[    4.263085] rk_gmac-dwmac fe300000.ethernet: phy regulator is not available yet, deferred probing
[    4.365919] rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed
/dev/nvme0n1p2: clean, 229659/15171584 files, 15424873/60674560 blocks
[    7.720197] sd 0:0:0:0: [sda] No Caching mode page found
[    7.720806] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    9.380672] Bluetooth: hci0: command 0x0c03 tx timeout

Debian GNU/Linux bullseye/sid rockpro64 ttyS2

rockpro64 login: [   17.380860] Bluetooth: hci0: BCM: Reset failed (-110)
  Reply
#2
Hi,
I use Armbian / Focal with a 256G Nvme (PNY)
in my dmesg log I do not see these messages except the one about Bluetooth. I already had this kind of message when I have a problem with the image I flashed (size truncated) but this is probably not your case.
  Reply
#3
(05-01-2021, 02:14 PM)LMM Wrote: Hi,
  I use Armbian / Focal with a 256G Nvme (PNY)
  in my dmesg log I do not see these messages except the one about Bluetooth. I already had this kind of message when I have a problem with the image I flashed (size truncated) but this is probably not your case.

Yeah, the bluetooth is expected because I'm not using any BT module, but apparently the CRC message is non-critical and it seems to show up to other users too. And about the card not responding to voltage, seems to be from eMMC and SD card interfaces when you're not using any of them.

Edited;
There is still one message I have no idea:
Code:
Loading Device Tree to 00000000f050d000, end 00000000f051ddeb ... OK
incorrect device type in 1
  Reply
#4
my boot sequence :

Code:
U-Boot 2021.01-09768-gc762ab29b8 (Mar 20 2021 - 13:48:40 +0000)

SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 RockPro64 v2.1
DRAM:  3.9 GiB
PMIC:  RK808
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Pine64 RockPro64 v2.1
Net:   eth0: ethernet@fe300000
Hit any key to stop autoboot:  0
Card did not respond to voltage select! : -110
Card did not respond to voltage select! : -110

Device 0: Vendor: 0x1987 Rev: CS303320 Prod: PNY4720003194010479F
            Type: Hard Disk
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)
... is nowScanning nvme 0:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 2 ms (1.5 MiB/s)
## Executing script at 00500000
Boot script loaded from nvme 0
166 bytes read in 2 ms (81.1 KiB/s)
15335962 bytes read in 32 ms (457 MiB/s)
28582400 bytes read in 55 ms (495.6 MiB/s)
75809 bytes read in 4 ms (18.1 MiB/s)
2698 bytes read in 3 ms (877.9 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
Moving Image from 0x2080000 to 0x2200000, end=3de0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data SizAddress: 00000000
   Entry Point:  00000000
   Verifying CheckOK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to f1066000, end fOK
   Loading Device Tree to 00000000f0feb000, end 00000000f1065fff ... OK

Starting kernel ...

[    8.210542] OF: graph: no port node found in /i2c@ff3d0000/typec-portc@22
[   10.094840] systemd[1]: Failed to start Raise network interfaces.
[   10.688541] Bluetooth: hci0: command 0x0c03 tx timeout
[   18.912586] Bluetooth: hci0: BCM: Reset failed (-110)

Armbian 21.02.3 Focal ttyS2

I have not activated much log (verbosity =2 in armbianEnv.txt)

Code:
incorrect device type in 1
Perhaps due to your second partition nvme0n1p2 ?
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Mainline U-Boot with SPI, NVMe and SATA boot support sigmaris 104 50,860 11-20-2021, 02:33 PM
Last Post: efetrioy
  rockpro64 emmc GreyLinux 8 524 11-08-2021, 01:56 PM
Last Post: GreyLinux
  ROCKPro64 sometimes doesn't Power On Pete Tandy 2 668 08-24-2021, 05:50 AM
Last Post: Pete Tandy
  Tutorial request: overclocking a rockpro64 Mentaluproar 1 582 08-15-2021, 01:35 PM
Last Post: dukla2000
  Did I brick my RockPro64 somehow? snarfel 1 775 07-20-2021, 01:40 PM
Last Post: dukla2000
  RockPro64 - EN62368 m.ekstrom 0 599 06-02-2021, 04:55 AM
Last Post: m.ekstrom
  RPI4 Vs Rockpro64 Performance help? Mangled 0 739 05-25-2021, 03:38 PM
Last Post: Mangled
  Unusable ROCKPRO64 drenedo 3 1,959 03-24-2021, 06:47 AM
Last Post: GuyNoIRQ
  ROCKPro64 (4 GB) "In stock (can be backordered)" TRS-80 3 1,089 03-19-2021, 04:53 PM
Last Post: TRS-80
  Troubleshooting ROCKPro64 alephnull 3 1,867 03-04-2021, 03:58 AM
Last Post: alephnull

Forum Jump:


Users browsing this thread: 1 Guest(s)