piter75

I believe "apt install linux-dtb-legacy-rk3399 linux-image-legacy-rk3399" is what you really wanted to do ;-)

It is rkspi_loader.img file in /usr/lib/linux-u-boot-${BRANCH}-${BOARD}_${VERSION}_${ARCH} folder but yours will not work anyway. Try this one: https://users.armbian.com/piter75/rkspi_loader-v20.11.2-trunk.img It contains the fix and should work with your board. You can flash it with dd if=... of=/dev/mtdblock0 bs=4K

That's the cultprit - u-boot does not recognise your SPI flash chip. I only enabled XTX flash chips for ROCK Pi 4 as those come preinstalled but I should enable some more of them especially for owners of v1.3 that did the soldering themselves. I will try to squeeze it into v20.11.2

That's interesting. Seems like it is not trying to load u-boot proper from SPI at all. You can short the 23-25 for a short moment during boot to disable SPI and boot with SD to revive your ROCK Pi. Do you know exactly what SPI flash device you have soldered in? What is your ROCK Pi model and version? The SPI model should be printed when booted with the SD card and overlay enabled - be sure to disconnect pins 23-25 as soon as the u-boot starts. It should rather look something like this (with Corsair MP510):

At this point roc-rk3399-pc is the only one with blob-less boot sequence by default but it's certainly possible with some others too https://github.com/armbian/build/blob/master/config/sources/families/rk3399.conf#L19 And it's LPDDR4 too...

Yesterday test was with local minimal build (which does not have alsa-utils installed) and hence the audio enablement script you provided did not work on boot. Retested with official image (Armbian_20.11_Rockpi-4b_buster_current_5.9.10.img.xz) and analog sound works out of the box. To make some NVMe drives working which are known for not working with official SPI. But... I do see your point. I will try to make the mainline SPI / NVMe combo available without breaking compatibility with existing installations of Radxa SPI.

With Armbian v20.11 one can write mainline u-boot image to board's SPI and enjoy booting nvme drives without any mmc devices. Prerequisities: ROCK Pi 4(A/B/C) v1.4 or 1.3 with SPI soldered in (v1.3 comes without SPI flash from the factory). If you already have Radxa's u-boot written to SPI you need to short pins 23 and 25 for Armbian to boot Boot fresh image of Armbian v20.11.x for ROCK Pi 4(A/B/C) Add the following lines to /boot/armbianEnv.txt overlays=spi-jedec-nor param_spinor_spi_bus=1 Reboot If you shorted 23-25 pins in 1.) then: disconnect them after the ROCK Pi 4 fully boot's enable spi-nor by executing (as root): echo spi1.0 > /sys/bus/spi/drivers/spi-nor/bind verify that the SPI mtd interface is enabled by running ls /dev/mtdblock0 if the last command does not list any file then something went wrong between 3.) and 5.) Run nand-sata-install choose option: "Boot from SPI - system on SATA, USB or NVMe" choose NVMe partition, eg. /dev/nvme0n1p1 accept erasing of the choosen partition with "Yes" choose fs type (tested with ext4) wait a few minutes for rootfs transfer to chosen partition choose writing SPI bootloader with "Yes" confirm that you want to flash it with "Yes" wait ~60 seconds for writing choose Exit Reboot Enjoy Armbian booting with SPI / NVMe Why bother with mainline u-boot? It is known to boot some NVMe drives that legacy u-boot from Radxa has issues with, eg. SAMSUNG 970 EVO Plus and SAMSUNG PM981. This does not mean that all NVMe drives are supported, YMMV. Which NVMe drives are known to be working? Corsair MP510 240GB/480GB/960GB Gigabyte SSD M.2 2280 PCIe x2 Model:GP-GSM2NE8128GNTD HP SSD EX900 M.2 NVMe 120GB. Model: 2YY42AA#ABB Intel SSD 660p Model:SSDPEKNW512GB Kingston A1000 SSD 240GB (PHISON PS5008-E8-10) Kingston A2000 M.2 2280 PCIe NVMe PNY 250GB XLR8 CS3030 M.2 NVMe SSD PCIe Gen3 x4 Sabrent Rocket 256GB NVMe PCIe M.2 2280 Samsung 970 EVO Plus SSD 250GB M.2 2280, PCIe 3.0 x4, NVMe, 3500/2300 MB/s Samsung PM981 256GB XPG SX6000 Lite 128GB (ASX6000LNP-128GT-C) Why not using Radxa's u-boot SPI image? Ambian's u-boot configuration is incompatible with Radxa's SPI image Why Armbian is using u-boot that is incompatible with Radxa's? It uses mainline u-boot with Open Source TPL/SPL/proper and BL31 from Rockchip packaged into u-boot and we may switch to using open source ATF instead of the BL31 in the future. Can I boot Radxa's images with Armbian's u-boot written to SPI? Yes. Armbian's SPI u-boot is compatible with Radxa's images available here: https://github.com/radxa/rock-pi-images-released/releases It may not be compatible with some older images (released before July 2020) because of the device tree filename change.

That's true. It needs some alsamixer tinkering to get the sound working without the file you provided. Do I get it right that you are talking about ROCK Pi 4B running official Armbian image (for ROCK Pi 4B) with Radxa's u-boot in SPI? It does not work. It is the incompatibility between v2017.09 u-boot based on Rockchip blobs (Radxa SPI) and v2020.07 u-boot (TPL/SPL/proper) with FIT packaging for BL31 blob (Armbian ROCK Pi 4A/B/C) I recommend writing Armbian mainline u-boot to SPI which is compatible with Radxa's OS images. One needs to enable spi-jedec-nor overlay and use nand-sata-install or armbian-config to write u-boot to SPI. I will document the procedure in the download page.

Hi, have your friend tried passing pcie_aspm.policy=powersave to the kernel's command line? It can be done with "extraargs=" stanza in /etc/armbianEnv.txt I use it with all (two ;p) my rk3399 nvme setups and also with my Armbian build server. I remember it lowering both SSD temps and overall power usage. I don't have hard figures on both savings and performance loss and... YMMV depending on the drive but it's worth trying.

Legacy is the only sensible option for ROCK Pi S for now so this was a good choice ;-) This function definitely did not go well. Consult the console output during build (after kernel compilation) to see if there aren't any errors.

Both look perfectly well except for the fact that the latest one does not boot Can you also try one of the v20.02.7 images available in the archive? https://archive.armbian.com/firefly-rk3399/archive/ I'd like to find the most precise point where it stopped working.

Armbian does not use those hardware eMMC partitions. Can you try to boot this image (https://users.armbian.com/piter75/Armbian_20.11.0-trunk_Firefly-rk3399_buster_current_5.9.9_minimal.img.xz) with SD and provide console logs - it should be more verbose that the default one.

IMO it is rather unrelated. The other issue (introduced by me ) affects a single file and causes not updating initramfs after kernel update at all.

This script: https://github.com/armbian/build/blob/master/packages/bsp/common/etc/initramfs/post-update.d/99-uboot does not run or it fails while sourcing /etc/armbian-release. There is no "update-initramfs: Converting to u-boot format" message in your log after "Building cpio...". Is the file /etc/initramfs/post-update.d/99-uboot executable in the output image? Does it exist? Can you provide the content of /etc/armbian-release from the output image?

I remember building the ROCK Pi S image a few day ago and it was working fine. I will build again to verify it. Refer to the output/debug/install.log to see if there are any errors during initramfs build.

To be certain.... Do I understand correctly that it works for you if you transfer the older Armbian (v19.11.7) from SD to eMMC (probably by the means of nand-sata-install) and then run the upgrade? Does the system boot with eMMC after the upgrade? If it boots... does it recognise the SD card that you insert while the system is running (booted with eMMC)?

CP2102 does not support it but FT232RL should, IIRC.

Can you post the serial console output from the failed boot rather than the successful one? ;-)

I took a shortcut and enabled SPI by default for ROCK Pi 4. I verified it with SPI CLK shorted on v1.4 but obviously it was not enough The fix is in master.

That's my primary choice too Current minimal was the fastest to build (to assess if the panic on boot is gone): https://users.armbian.com/piter75/Armbian_20.11.0-trunk_Rockpi-4b_buster_current_5.9.8_minimal.img.xz Legacy desktop is being built right now.

I will build and share an image with a possible fix for you to verify.

What revision of the board you have? Is it 1.4 with SPI or 1.3 without it?

Below sequence would do the trick: armbianmonitor -u --> Garther results from working system sudo nano /etc/armbianEnv.txt --> set verbority to 7 sudo apt-get update && sudo apt-get upgrade sudo reboot (and then it crashes) gather the logs from serial console at this point https://wiki.radxa.com/Rockpi4/dev/serial-console The USB TTL converter you use must support 1.5mbps

Well, without serial console it's difficult to debug the issue as it may happen before the kernel is loaded. Try to gather your current system info with armbianmonitor -u and paste the resulting link here.

I was asking for an initial image that you started your installation with. Please post armbianmonitor -u results of your running system. Can you also post a serial console output after upgrading the system? Preferably with verbosity=7 in /etc/armbianEnv.txt set before the upgrade. u-boot is not "flashed" automatically