Update from my side regarding rockpi4b-rk-u-boot-latest_2017.09-2681-geb41d9a6c
Since I already had SPI flashed and was unable to flash it via Windows 10 PC I updated the SPI by starting from scratch via this topic:
I’ve followed step 1, did sudo apt-get update && sudo apt-get upgrade*, followed by step 2
*: in the CLI I noticed rockpi4b-rk-u-boot-latest_2017.09-2681-geb41d9a6ce, so it updated the u-boot package.
Via sftp I transfered two ARMbian images, the one provided by Radxa (v5.67) and the latest Debian Stretch version from the ARMbian website (v5.90).
First I DD’ed the ARMBian-“official” image via:
sudo dd if=’ your image path’ of=’ your NVME SSD device path’ bs=1M
This didn’t boot.
Second I DD’ed the Radxa-ARMbian. This version is able to boot. I assume because this image is gpt instead of ARMbians mbr.
Also, when I run lsblk I see a different “structure” as I would expect from https://wiki.radxa.com/Rockpi4/Linux_system_runs_on_M.2_NVME_SSD. (I noticed that I should do lsusb instead of lsblk, I’ll try that this afternoon/evening.
Please let me know what I can test to help solving this issue.
Another thing, maybe related to the issue:
root@rockpi4b:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
zram0 254:0 0 50M 0 disk /var/log
nvme0n1 259:0 0 477.9G 0 disk
└─nvme0n1p1 259:1 0 472.2G 0 part /
Another thing 2, maybe related to the issue:
In the Linux system runs on M.2 NVME SSD instruction it is mentioned to:
Modify file, /boot/hw_intfc.conf. Uncomment these lines. Thus we can use SPI Flash device (/dev/mtd0)
intfc:uart4=off
intfc:spi1=on
intfc:dtoverlay=spi1-flash
But in all Radxa images that I experimented with these options are already uncommented. Maybe this step is not required anymore and can be removed from that Wiki?