Unable to Boot Milk-V Compute Module Due to Corrupted U-Boot and Filesystem Issues

Hi All,

I am currently unable to boot the Milk-V Compute Module as the u-boot seems to have been corrupted and there are issues with the filesystem.

Here’s what I’ve tried so far:

  • I’ve used the CH341A module to externally reprogram the SPI chip extensively.
  • Unfortunately, I cannot write to the SPI chip using the CH341A USB module.
  • I have also tried to write the SPI flash with Mars-UsbFlashTool-v2.4-Windows but wit no sucess.

From my understanding, there might be an issue with the SPI chip partition table that needs to be followed. Could anyone guide how to configure and write to the SPI chip properly?

Thank you for your assistance.

-Anand

current console logs

Terminal ready
Main section boot fail,use backup section
All section boot fail,please check your Image
BOOT fail,Error is 0xffffffff
Main section boot fail,use backup section
All section boot fail,please check your Image
BOOT fail,Error is 0xffffffff
1 Like

When I am trying Mars-UsbFlashTool-v2.4-Windows and following the instructions

Boot the Mars CM | Milk-V

I am getting the following logs

Serial port is open: True
open Serial<id=0x1e51f0b39d0, open=True>(port='COM3', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=None, xonxoff=False, rtscts=False, dsrdtr=False)
sending file: C:/Users/Moon/Downloads/Mars-UsbFlashTool-v2.4-Windows/update/usbprog-mars-230510.out, 153104 bytes
sending complete
loaded: C:/Users/Moon/Downloads/Mars-UsbFlashTool-v2.4-Windows/update/usbprog-mars-230510.out

program EMMC:0x0:ALLINONE_IMAGE, E:/vision/mars-cm_debian-desktop_sdk-v3.6.1_cm4-io-board_emmc_v1.0.6.img

  0%|          | 0.00/4.19G [00:00<?, ?B/s]Error occurred during file transfer: 'NoneType' object has no attribute 'ctrl_request'
Complete

  0%|          | 0.00/4.19G [00:00<?, ?B/s]
1 Like

The log output seems as if any and all bootloaders are missing. Have you tried uploading bootloader as well?

Thanks, Yes,I have tried, but it seems to me that the SPI flash is erased and it does not have the partitions to write to specific offsets, I guess so.

Can someone share the full image for the SPI flash, so that I can try to write to SPI, to make the board boot again?

1 Like

Is there any way to flash the SPI image via Fastboot or a USB cable?

1 Like

I think, in the docs you short the pins 1 and 2 of J12 and connect to microUSB (J11) — steps 2 and 3 here, I guess. And it is likely very much the same as doing it via an external USB-to-TTL converter.

If I see it right, you will need the «Allinone» option, if you have the full image. But I don’t have neither the CM, nor a wINDOWS machine to confirm this guess based on reading the docs.

Here are some issues discussed with the CM board that have bad Eprom, and lead board corruption.

https://patchwork.ozlabs.org/project/uboot/patch/20250209152329.187194-5-heinrich.schuchardt@canonical.com/

1 Like

In case of a faulty product, try contacting your seller, I guess?