RISC-V Reddit

Milk-V Megrez trouble with The bootloader

I wanted to get in touch again about my Milk-V Megrez.

First of all, the start of the image of Rockos worked very well in the end. I've never had it before that I unzip an image over several zip files, so I was overwhelmed at first. Actually, I should have read it better. I was able to start the system well and also Internet via cable works. The WLAN stick from me could also be set up, so far so good.

My bigger problem is that I had now tried to install Fedora (I didn't think anything would break). I had looked to the instructions and made the settings on Uboot (probably not quite right). Now Uboot has crashed and I can't restart the computer, no matter which image I use (Neither Rockos or Fedora can boot via the SD card). I'm really clumsy and don't know if I can heal it again.

I have now seen that I could save the whole thing over a UART/USB cable. (Updating/Re-Flashing U-Boot When U-Boot is Available)

https://milkv.io/docs/megrez/getting-started/boot

I hope I understand that correctly:

1. ⁠The board must be switched to recovery mode (the small unswitch at the top).
2. ⁠I simply pack the file "bootloader_milkv-megrez-2025-0224.bin" on a USB stick with EXT4 file format and plug it into any USB slot.
3. ⁠I plug the UART/USB cable into the board and into any other PC. When I turn on the board afterwards, the drive appears as "ESWIN-2030".

I have this information now from Gemini:

4. On the PC I can write down the path where the cable is listed via the Linux terminal with the command "dmesg | grep tty". I can then, when I have installed Minicon, simply open the configuration menu in the terminal "sudo minicom -s /dev/ttyUSB0 (customize path accordingly).

5. I select "Serial port setup". Then I give the path to the serial device (but here I wonder why I have to do this twice). Than I set the baud rate to „115200“. Data bits to „8“, the parity to „N“ (None) and the stop bits to „1“.

6. I choose "Save setup as dfl" to save the settings as default and leave the configuration menu again with "Exit".

7. I press Ctrl + A and then Q to finish.

I have no idea how the board behaves, whether it switches itself off or I can take it off the power. It should then work again after I have switched the recovery mode back to normal.

I now assume that this can also work easily via the Linux terminal of my Raspberry Pi.

I have seen this on Amazon. Do you think it can be work? https://amzn.eu/d/e68hL7

Did I understand the whole thing correctly? Have any of you had experience with this? Is there perhaps a much easier way that I am currently overseeing?

Many thanks for your help! <3

Sorry. Unfortunately, I'm pretty clueless. :-/

https://redd.it/1kkmzuj
@r_riscv

milkv.io

Milk-V Megrez Install OS | Milk-V

Boot Instructions

www.tgoop.com/r_riscv/3300

11 viewsMay 12 at 08:24

Milk-V Megrez trouble with The bootloader

I wanted to get in touch again about my Milk-V Megrez.

First of all, the start of the image of Rockos worked very well in the end. I've never had it before that I unzip an image over several zip files, so I was overwhelmed at first. Actually, I should have read it better. I was able to start the system well and also Internet via cable works. The WLAN stick from me could also be set up, so far so good.

My bigger problem is that I had now tried to install Fedora (I didn't think anything would break). I had looked to the instructions and made the settings on Uboot (probably not quite right). Now Uboot has crashed and I can't restart the computer, no matter which image I use (Neither Rockos or Fedora can boot via the SD card). I'm really clumsy and don't know if I can heal it again.

I have now seen that I could save the whole thing over a UART/USB cable. (Updating/Re-Flashing U-Boot When U-Boot is Available)

https://milkv.io/docs/megrez/getting-started/boot

I hope I understand that correctly:

1. ⁠The board must be switched to recovery mode (the small unswitch at the top).
2. ⁠I simply pack the file "bootloader_milkv-megrez-2025-0224.bin" on a USB stick with EXT4 file format and plug it into any USB slot.
3. ⁠I plug the UART/USB cable into the board and into any other PC. When I turn on the board afterwards, the drive appears as "ESWIN-2030".

I have this information now from Gemini:

4. On the PC I can write down the path where the cable is listed via the Linux terminal with the command "dmesg | grep tty". I can then, when I have installed Minicon, simply open the configuration menu in the terminal "sudo minicom -s /dev/ttyUSB0 (customize path accordingly).

5. I select "Serial port setup". Then I give the path to the serial device (but here I wonder why I have to do this twice). Than I set the baud rate to „115200“. Data bits to „8“, the parity to „N“ (None) and the stop bits to „1“.

6. I choose "Save setup as dfl" to save the settings as default and leave the configuration menu again with "Exit".

7. I press Ctrl + A and then Q to finish.

I have no idea how the board behaves, whether it switches itself off or I can take it off the power. It should then work again after I have switched the recovery mode back to normal.

I now assume that this can also work easily via the Linux terminal of my Raspberry Pi.

I have seen this on Amazon. Do you think it can be work? https://amzn.eu/d/e68hL7

Did I understand the whole thing correctly? Have any of you had experience with this? Is there perhaps a much easier way that I am currently overseeing?

Many thanks for your help! <3

Sorry. Unfortunately, I'm pretty clueless. :-/

https://redd.it/1kkmzuj
@r_riscv

BY RISC-V Reddit