Hi all,
I am using rockpi4b with hardware V1.4 and building my own images using buildroot. The problem I am facing currently is that I boot successfully from SSD nmve 970 EVOplus 500GB but I am not able to boot when using nvme 970 EVOplus 1TB.
If I boot from an SDcard then the 1TB 970 evoplus is detecetd and mounted correctly. The only problem I have with 1TB SSD is when trying to use them for boot
For information I am using https://dl.radxa.com/rockpi/images/loader/spi/rockpi4b-uboot-trust-spi_2017.09-2681-geb41d9a6ce_20191104.img downloaded from radxa server.
I would like to know if someone have or had same problem.
Someone have nvme SSD 1TB reference that boots correctly with rockpi4B ? If yes It will be appriciated to share this reference.
Thanks you in advance for your support.
PS: The logs I am getting with My 1TB 970 evoplus are:
=============================================================================
aclk_perilp0 266666 KHz
hclk_perilp0 88888 KHz
pclk_perilp0 44444 KHz
hclk_perilp1 100000 KHz
pclk_perilp1 50000 KHz
Net: eth0: ethernet@fe300000
Hit key to stop autoboot(‘CTRL+C’): 0
Device 0: Vendor: 0x144d Rev: 2B2QEXM7 Prod: S4EWNF0M718310M
Type: Hard Disk
Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
… is now current device
Scanning nvme 0:4…
Found /extlinux/extlinux.conf
pxefile_addr_str = 0x00500000
bootfile = /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
reading /extlinux/extlinux.conf
184 bytes read in 1 ms (179.7 KiB/s)
Retrieving file: /hw_intfc.conf
reading /hw_intfc.conf
1809 bytes read in 1 ms (1.7 MiB/s)
dtoverlay number: 0, name:/overlays/console-on-ttyS2.dtbo
hw_conf.valid = 1
hw_conf.pwm0 = 0
hw_conf.pwm1 = 0
hw_conf.uart2 = 0
hw_conf.uart4 = 0
hw_conf.spi1 = 0
hw_conf.spi2 = 0
hw_conf.i2c2 = 0
hw_conf.i2c6 = 0
hw_conf.i2c7 = 0
hw_conf.dts_overlay_count = 1
hw_conf.dts_overlay[0] = /overlays/console-on-ttyS2.dtbo
1: kernel-4.4
Retrieving file: /Image
reading /Image
ERROR: status = 2013, phase = 1, head = 0
Error reading cluster
** Unable to read file /Image **
Skipping kernel-4.4 for failure retrieving kernel