hi, im trying to get the reterminal DM to boot via the nvme drive. i’ve followed the guide from It took me 2 months to boot CM4 from NVMe - NotEnoughTech and have done the eeprom update and the cloning to the nvme. however, as far as i can see, it keeps booting from the emmc. is there a better, more specialized guide for the reterminal DM? is there a specific nvme that may need to be used? any additional data i can provide to help with this?
thank you
Hi jindr,
Did you end up getting this to work?
My biggest question is whether the boot switch next to the USB-C port simply disables eMMC boot, or if it bypasses entirely the boot.conf sequence and sends the device into USB-OTG boot (that would be 5 or 3 based on the Raspberry documentation. From what I can gather it’s more the second option, as I’ve tried a USB-A stick boot and it simply did not go anywhere (power led on, nothing happens).
I’ll flash the firmware with my own boot sequence and see what happens.
Cheers,
Jérôme
Hey again,
I’ve changed the boot sequence to use eMMC last (0xf145) and it did something… The ACT led was stuck on, but it still did not boot from USB.I’ll have to delve deeper or post another thread to ask.
Still, I hope you could get it to run to your liking in the end.
Jérôme
Confirm that the EEPROM boot order includes NVMe. You can check and modify the boot order using the following commands:
sudo -E rpi-eeprom-config --edit
Ensure the BOOT_ORDER parameter includes the appropriate value to prioritize NVMe booting.
I just checked, and for my case I do have both usb (4, 5) modes and the nvme (6) before the sd-card (which is the eMMC on the CM4 I believe). I tried various combinations of 0xf1645, 0xf164, and so on, with each of the boot flip switch positions, but could not make the reTerminal DM boot from usb storage.
Hey @jindr,
I’ve found a possible workaround for your issue: if you leave the boot partition on the eMMC, you can move the system partition on the NVMe and simply change the PARTUUID in the cmdline.txt, and this boots fine. It’s a useful trick for our use case, at least. I hope it can serve for your own problem.
Cheers,
Jérôme
I know this is quite an old topic, but as a new user I don’t seem to have the access to create new topic yet.
I just got myself a R1000 with an NVMe. I installed the SSD, it is working, mounted, visible. I also did the steps to change th boot order, and was going through the steps to flash the firmware again.
But in the Raspberry PI Imagers too, I can only see one drive.
And guessing from the 31.3GB size, that is the eMMC driver not the NVMe.
So I still don’t understand how I can flash the NVMe.
Hi there
and welcome here…
So it takes a few posts to build enough forum cred to Post a new topic and othere stuff, Replay a couple more posts and you’ll get there. 
Meanwhile I recall the most success when it was flashed externally, using a external SSD/Nvme drive enclosure YMMV check out some other threads and It’s been covered with pretty successful outcomes
HTH
GL 
PJ 
OK, thanks. I thought maybe there is a trick or something to do that. And once the SSD flashed, boot sequence is updated it will boot from the NVMe and not use the eMMC any more (until the SSD dies…).
Another related question: let’s say I flash the SSD, install the drivers and some of the other apps I usually use. I can take the SSD out and back it up to an entire image to save time setting up the next reComputer?
Hi there,
Ah’, Good question. I would think yes.
probably the best way if your doing multiple units I’m thinking…
HTH
GL PJ
pretty sure there is a seeed engineer post about doing it this way Too