I have followed the instructions from the FAQ and getting started guides to flash a non-SEEED OS image to a micro-SD card, but cannot get the board to boot. I’m not sure if it’s an issue with the image (and maybe missing drivers) or an issue with the board.
I’ve inserted the SD card and tried rebooting with the boot toggle switch in both positions. With the toggle “up” it boots from the eMMC. With the toggle “down”, it just sits idle with a blank screen. Tried connecting to ethernet in case it was just a case of screen drivers, but it never shows up on the network.
Seems like others are having issues using a generic image flashed to the eMMC, although in theory I think that is supposed to work as well. Anyone else have any luck?
I will offer you further guidance in this matter. First of all, if you are using the CM4 eMMC version on the reTerminal, you cannot use SD cards. This is because the eMMC is internally connected to the SD card interface. It is also mentioned in the official Raspberry Pi documentation. You can check the section Flashing the Compute Module eMMC in the above document and it mentions there. When you flash OS to SD card, it won’t boot from the SD card because it will only prioritize the eMMC and only boot from eMMC.
However, if you want to boot the OS from an SD card, you need to use a CM4 module without the eMMC onboard. This way reTerminal will directly boot from SD card.
Also, I saw that you mentioned about non-SEEED OS image. Could you flash this on to the eMMC of the reTerminal and let me know? Please use this guide to flash the OS.
Hello there @lakshan . I also have a problem regarding flashing OS to the device. The device that I used is reTerminal DM. At first, I was succeeded to flash the OS to the eMMC drive. But because of my fault, I executed this command:
sudo chmod -R 755 /
The reason I executed it is because I want to download python package to the device, I found it is working but ended up with unusable sudo. I can’t execute command with sudo and also its SSH. So I decided to re-flash the OS image again.
But why the process always failed at 40% of writing process. When the process is around 30% or similar, there is a warning message states “Switched to compatibility mode - write continuing”. But the process is still running until around 40%. In addition, when it is around 40%, there is a pop up Error message which says "Writing stalled - no progress for 60 seconds. Please check your storage device and try again as described on provided images. I already did this twice and got the same error and symptoms. I would be glad if you can help me to overcome this problem based on your knowledge and experiences.