I just received a Rock 2F. Boots fine from SD. I copied the image to NVMe and used a ZDE ZP511 NVMe HAT and a Micron 256 GB SSD. Wnen I go to rsetup to flash the SPI there is ”No compatible bootloader available” so I cannot re-flash the SPI to point to the NVMe. What can I do?
lsblk shows the NVMe just fine. lspci shows the NVMe adapter. If I remove the SD card there is no boot.
What you’re observing is expected. No way to directly boot Rockchip from nvme. To boot from NVME, you would need to flash the bootloader to an SD card or to eMMC. armbian-install can do this (but last time I used it it assigned the full eMMC/SD for the boot partition, I recommend shrinking it later to 2-3 GB maybe.
I have a Rock 2F motherboard and the PCI-e slot isn’t working. I’ve tried two different HATs and nothing works. Which distro are you using? Did you have to enable PCI-e in rsetup? I’m using a 5V 5A power supply and still can’t get anything to work via PCI-e.
radxa@rock-2f:~$ sudo dmesg |grep -i pci
[ 6.942940] vcc3v3_pcie20: will resolve supply early: vin
[ 6.942949] reg-fixed-voltage vcc3v3-pcie20: Looking up vin-supply from device tree
[ 6.942960] vcc3v3_pcie20: supplied by vcc5v0_sys
[ 6.943003] vcc3v3_pcie20: 3300 mV, enabled
[ 6.943157] reg-fixed-voltage vcc3v3-pcie20: vcc3v3_pcie20 supplying 3300000uV
[ 7.989903] PCI: CLS 0 bytes, default 64
[ 8.837873] rk-pcie fe4f0000.pcie: invalid prsnt-gpios property in node
[ 8.837898] rk-pcie fe4f0000.pcie: Looking up vpcie3v3-supply from device tree
[ 8.838854] rk-pcie fe4f0000.pcie: max MSI vector is 8
[ 8.838928] rk-pcie fe4f0000.pcie: host bridge /pcie@fe4f0000 ranges:
[ 8.838967] rk-pcie fe4f0000.pcie: IO 0x00fc100000..0x00fc1fffff → 0x00fc100000
[ 8.838990] rk-pcie fe4f0000.pcie: MEM 0x00fc200000..0x00fdffffff → 0x00fc200000
[ 8.839004] rk-pcie fe4f0000.pcie: MEM 0x0100000000..0x013fffffff → 0x0100000000
[ 8.839210] rk-pcie fe4f0000.pcie: iATU unroll: enabled
[ 8.839223] rk-pcie fe4f0000.pcie: iATU regions: 8 ob, 8 ib, align 64K, limit 8G
[ 9.044008] rk-pcie fe4f0000.pcie: PCIe Linking… LTSSM is 0x0
[ 9.069534] rk-pcie fe4f0000.pcie: PCIe Linking… LTSSM is 0x0
[ 9.099535] rk-pcie fe4f0000.pcie: PCIe Linking… LTSSM is 0x0
[ 9.126208] rk-pcie fe4f0000.pcie: PCIe Linking… LTSSM is 0x0
[ 9.152880] rk-pcie fe4f0000.pcie: PCIe Linking… LTSSM is 0x0
[ 9.179526] rk-pcie fe4f0000.pcie: PCIe Linking… LTSSM is 0x1
[ 9.206223] rk-pcie fe4f0000.pcie: PCIe Linking… LTSSM is 0x0
[ 9.232858] rk-pcie fe4f0000.pcie: PCIe Linking… LTSSM is 0x0
[ 9.259546] rk-pcie fe4f0000.pcie: PCIe Linking… LTSSM is 0x0
[ 9.286201] rk-pcie fe4f0000.pcie: PCIe Linking… LTSSM is 0x0
[ 11.716192] rk-pcie fe4f0000.pcie: PCIe Link Fail, LTSSM is 0x0, hw_retries=0
[ 11.716268] rk-pcie fe4f0000.pcie: failed to initialize host
why we can not just put boot loader to nvme and boot from that directly?is it a problem with drivers?
It’s like this with all rockchip boards. They cannot boot from NVME directly, just eMMC or SPI