this works, only flash img to nvme, do nothing armbianEnv.txt or boot.cmd, no sdcard
Intel 660p
Armbian_20.02.1_Rockpi-4a_buster_legacy_4.4.213.img
.......................
Hit key to stop autoboot('CTRL+C'): 0
Device 0: RKPARM: Invalid parameter part table
Vendor: 0x8086 Rev: 002C Prod: BTNH90820C73512A
Type: Hard Disk
Capacity: 488386.3 MB = 476.9 GB (1000215216 x 512)
... is now current device
Scanning nvme 0:1...
Found U-Boot script /boot/boot.scr
2940 bytes read in 5 ms (574.2 KiB/s)
## Executing script at 00500000
Boot script loaded from nvme 0
189 bytes read in 6 ms (30.3 KiB/s)
6758686 bytes read in 67 ms (96.2 MiB/s)
19752968 bytes read in 171 ms (110.2 MiB/s)
93124 bytes read in 23 ms (3.9 MiB/s)
** File not found /boot/dtb/rockchip/overlay/rockchip-fixup.scr **
.............................
Kingston 2000 and Gigabyte
this works, armbianEnv.txt add fdtfile=rockchip/rk3399-rock-pi-4.dtb
Armbian_20.02.7_Rockpi-4a_buster_current_5.4.28.img
.................
Hit key to stop autoboot('CTRL+C'): 0
Device 0: RKPARM: Invalid parameter part table
Vendor: 0x2646 Rev: S5Z42102 Prod: 50026B72823F1B89
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/boot.scr
2940 bytes read in 4 ms (717.8 KiB/s)
## Executing script at 00500000
Boot script loaded from nvme 0
189 bytes read in 4 ms (45.9 KiB/s)
7287636 bytes read in 69 ms (100.7 MiB/s)
20787712 bytes read in 184 ms (107.7 MiB/s)
72736 bytes read in 11 ms (6.3 MiB/s)
2698 bytes read in 6 ms (438.5 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
................................................................................
These NVME not works, tested , many scripts, there is errors
kingston A1000
Armbian_20.02.7_Rockpi-4a_buster_current_5.4.28.img
.................
Hit key to stop autoboot('CTRL+C'): 0
Device 0: RKPARM: Invalid parameter part table
Vendor: 0x2646 Rev: E8FK11.R Prod: 50026B76826C0418
Type: Hard Disk
Capacity: 228936.5 MB = 223.5 GB (468862128 x 512)
... is now current device
Scanning nvme 0:1...
Found U-Boot script /boot/boot.scr
2985 bytes read in 7 ms (416 KiB/s)
## Executing script at 00500000
Boot script loaded from nvme 0
189 bytes read in 5 ms (36.1 KiB/s)
ERROR: status = 13, phase = 1, head = 1
** fs_devread read error - block
ERROR: status = 13, phase = 0, head = 1
** fs_devread read error - block
72736 bytes read in 22 ms (3.2 MiB/s)
2698 bytes read in 10 ms (262.7 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
................
PNY CS3030 250GB
.........................
Armbian_20.02.7_Rockpi-4a_buster_current_5.4.28.img
....................
Hit key to stop autoboot('CTRL+C'): 0
Device 0: RKPARM: Invalid parameter part table
Vendor: 0x1987 Rev: CS303224 Prod: PNY35190025670102900
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/boot.scr
2940 bytes read in 6 ms (478.5 KiB/s)
## Executing script at 00500000
Boot script loaded from nvme 0
189 bytes read in 5 ms (36.1 KiB/s)
ERROR: status = 2013, phase = 1, head = 1
** fs_devread read error - block
ERROR: status = 2013, phase = 0, head = 1
** fs_devread read error - block
72736 bytes read in 13 ms (5.3 MiB/s)
2698 bytes read in 11 ms (239.3 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
...............................
Samsung 970 EVOPlus
Armbian_20.02.7_Rockpi-4a_buster_current_5.4.28.img
....................
Hit key to stop autoboot('CTRL+C'): 0
Device 0: RKPARM: Invalid parameter part table
Vendor: 0x144d Rev: 1B2QEXM7 Prod: S4EUNG0M122756V
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/boot.scr
2940 bytes read in 5 ms (574.2 KiB/s)
## Executing script at 00500000
Boot script loaded from nvme 0
189 bytes read in 3 ms (61.5 KiB/s)
ERROR: status = 2013, phase = 1, head = 1
** fs_devread read error - block
ERROR: status = 2013, phase = 0, head = 1
** fs_devread read error - block
72736 bytes read in 15 ms (4.6 MiB/s)
2698 bytes read in 7 ms (376 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
.................................
This upgrade is changing kernel branch names and first upgrade is not done via regular apt-upgrade process, but you have to login as root or get super user privileges with sudo su. Than do the following:
apt update
apt upgrade
armbian-config
-> system -> Other -> select either legacy or current with v19.11.3
Choose latest version of 19.11.x and select upgrade according to this scheme:
Odroid XU4 default, next or dev -> legacy (stock 4.14.y)
Allwinner default, next, dev -> legacy (4.19.y), current (5.3.y)
Odroid C2 and other meson64 boards -> current (5.3.y)
Odroid N2 -> legacy (4.4.y), current (5.3.y)
Tinkerboard and other rockchip boards -> legacy (4.4.y), current (5.3.y)
Cubox and Udoo -> imx6 current (5.3.y)
Helios 4 and Clearfog -> mvebu legacy (4.14.y), current (4.19.y)
Espressobin -> mvebu64 legacy (4.14.y), current (4.19.y)
Those upgrades were tested manually:
Note: upgrade will replace your boot script. In case you made changes, you can find a backup in /usr/share/armbian
Main build system changes
Due to changes in branch names and removal of all legacy kernels < 4 your predefined automatic scripts might need updating. Temporally quick fix is to add
LIB_TAG="v19.08"
to your build config file which by default is:
userpatches/config-default.conf
Then run your script as you did before.
Thanks to all who are contributing their time to Armbian in various forms and especially developers who contributed to this release. Also thanks to the greater kernel developers community which are playing great role in this.
In case you want to participate, you are more then welcome. Step up and start making changes! In case you run into the troubles or find a bug, forum is the place for talking about while fixes you are welcome to prepare and send here.
Note: some images will be missing today and tomorrow from the download section. Missing one are being created and uploaded but this takes time ... Most of the images were manually tested for booting, upgrades as stated above, but we can't afford to make stability, functional or just boot auto tests on industrial scale. Not with our ultra tiny resources. Perhaps in the future if "you" will support that.