Jacob Olness

@royk Done, I was trying to figure out if there was a way to mark the thread as solved or closed, putting it in the title seems obvious now that you say that. The part that was throwing me off is that it was still booting from the SD card. My understanding was that with the NVMe bootloader flashed it will not, under any circumstances, boot from the SD card although this could be outdated or just incorrect.

EDIT: I tried using ext4 rather than btrfs and.. somehow that solved it? I don't understand how the SSD file system would change how the bootloader is flashed because if properly flashed, the SD card shouldn't work at all, unless something has changed. Hey all, I wanted to move to the newest version of armbian (25.2.1) and for whatever reason neither `apt update && apt upgrade` nor `armbian-upgrade` (as a sanity check) worked so I wiped the SPI flash using `mtdtools` as prescribed in the forum post linked on the support page. 1) Booted from SD, installed Armbian and the bootloader. 2) Shut down, removed SD and turned on. Machine hung and never booted from NVMe. 3) Thought somehow I did something wrong or there was an error and used MaskROM mode and `rkdeveloptool` to revert it to boot from SD. 4) Repeated step 2 5) Still won't boot from NVMe but boots from SD (should have tried this first) 6) Tried reinstalling the bootloader to SPI flash, get this message: Processing blocks: 394/394 (100%) diff blocks: 0 Done Which reads like the flash is identical to what would is contained in the installer itself so it isn't overwritten. Wiped again and tried to install bootloader again. Still won't boot from NVMe but boots from SD card normally. Also, forgot to include this in my steps: I formatted the NVMe 3 times total and installed/reinstalled Armbian from the `armbian-install` script as a sanity check. Have had no issues in the past with any of this (I think I was on 24.11 most recently) so my first thought was a bug in the installer but am not seeing anyone else having this issue so figured I would ask here just to be sure. My questions are: 1) Has anyone else tried to use the installer on 25.2? I can't imagine there were any (much less breaking) changes but I am perplexed at this point. 2) Is the bootloader file available separately so I can flash it from `rkdeveloptools` Worst case I can image 24.11 on to the SD and try to install the bootloader that way but again, id be surprised if there were major changes. Thanks in advance!

@drewcephus hold down the maskrom button, plug in the power, then plug in the data cable to your computer. I am running the cli tool so it is rkdeveloptool ld DevNo=1 Vid=0x2207,Pid=0x350b,LocationID=201 Maskrom The light doesn't blink or anything but itll show up as a device there (and when plugged in to the machine initially even)

@MaxT Sweet! I also have a rockpro64 so info about the 3399 is interesting too.

That's a great call. I am gonna do some digging there to find out. I just got this board so it is currently doing nothing of import so if I blow something up, no biggie. Just wanted to have a more solid idea of what I'm going to run and such before moving to the NVMe (harder to flash than an SD card haha). Appreciate the response!

Want to avoid making a new thread for this if possible but on the minimum CPU clock being higher, sounds like that's expected behavior so that's good (I actually flashed two different versions of Armbian with the 6.12 kernel as a sanity check). I don't think it was really touched on if this is the long term plan for newer kernels or why it's set higher than the vendor kernel. I am interested both from a user perspective and from a technical one. At first the idle being so much warmer (I touched the casing and was surprised how warm to the touch it was. About 38ºC/100ºF skin temp vs 32ºC/90ºF on 6.1) was what made me worried something was wrong before looking at the available frequencies.