Mars CM USB slave not working

Mars
1

I am trying to flash the bootloader, but the slave USB device isn’t showing up as a device, and there is no USB handshake to the pc. I am using the official cm4 IO board, and i have the jumper for boot connected.

Any idea what i could be doing wrong? Thanks in advance.

1 Like
2

Hi!
I’m not an expert in dealing with Mars CM, but have you followed the guide and at which point you’re experiencing difficulties?

3

As I had stated, plugging in the USB does NOT show any kind of “com” port in the flasher. its not detected in windows. Step 5 is the issue for me.

4

Check your USB-to-TTL converter you had to connect in the step 1.

5

usb to TTL are independent of board, you can check the device manager in windows, make sure no any yellow mark. you may need driver for usb to TTL cable

1 Like
6

okay, let me provide additional clarification.
I am trying to follow this guide to install the driver Boot the Mars CM | Milk-V.

I am able to get to step 8, but step 9… it doesnt show the usb device as starfive. its just “unknown USB device” from the microUSB cable.

i tried installing the driver anyways, but it fails. no error, just says the install of the driver failed.

7

Seems like you’re identified the problem yourself: if the driver package is corrupt or not intended for your OS version, then it may be because:

  1. The file you downloaded is damaged in the source (you need staff to fix it).
  2. The file is fine, you only received it in bad shape (you need to re-download it).
  3. The file is fine, it’s not intended for your specific OS or OS version (you will need a different OS installation, or a different driver package).
  4. The driver is fine, it is only not compatible with your environment (you will have to find out what stops it from installing — you may have insufficient rights, or an aggressive antivirus, or something).

One more thing: please make sure you installed the right version of the bootloader. I wonder why exactly you needed to reflash the bootloader, it may be related to the situation.

8

The bootloader is damaged, hence why i need to reinstall it. I tried reinstalling the zadig thing multiple times, and reinstalling the winusb thing multiple times as well. no change. the OS is windows 10 latest.

9

That’s what you needed to start your story with.

Well, either the flash memory is somehow dysfunctional, or the binary isn’t right, or I’m out of guesses. If you can tell us more, there’s more chance someone else coming by can help you out with this case.

10

I’m very sorry.

I thought that in flashing the boot loader it wouldn’t be necessary to specify if its damaged or not, since im overwriting it regardless.

problem: I try to boot, but it throws up errors in on the uart pins:

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)

no matter the distro, or even if i dont have an SD card installed.
this is the NO EMMC version of the CM mars.

im following the guide to the DOT, and if i am on step 8, as listed above, and i unplug and replug power, the usb goes back to being unrecognized.

hope this helps clear some stuff up.

11

If the bootloader was in this state as you obtained the module, there’s a chance you can do nothing about it.
I said it before and say it again: I don’t have such a module and I’m not related to Milk-V team, parts vendors or anything.

If this happened after you did something, at least we can explain it somehow, because otherwise it looks as if you bought it as is and wanted to revive it before figuring it out what caused it.

By the way, which image pair are you trying to use?

12

It is also mentioned here that you can use this method to revive the bootloader in case you have it overwritten.

13

It looks like the driver is messed up. You may need to uninstall all usb related drivers and try again, or try another host.
or another micro-usb cable