Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CM4 is not being detected as as mass storage #231

Open
drumstick77 opened this issue Jul 11, 2024 · 5 comments
Open

CM4 is not being detected as as mass storage #231

drumstick77 opened this issue Jul 11, 2024 · 5 comments

Comments

@drumstick77
Copy link

Describe the bug

CM4 EMMC 4GB RAM 16GB storage on Manta M8P V2.0. Not being detected by Windows (win 11), as a mass storage (using RpiBoot)

Steps to reproduce the behaviour

  1. Toggle switches 4 (USBOTG) and 3 (RPIBOOT) to ON to enter BOOT mode (on Manta M8P)
  2. Plus USB C from Manta M8P to Windows 11 laptop
  3. Gave the Manta M8P board an external power (PSU) - I can hear the "ding" sound on my laptop
  4. Ran RpiBoot which took a while to install
  5. No Mass Storage detected.

I've uninstall and re-installed RPIBOOT numerous times (with reboots in every uninstallation), and still a no go. not sure where I've gone wrong

Device(s)

Raspberry Pi CM4

Compute Module IO board.

No response

RPIBOOT logs

No response

Kernel logs

No response

Device UART logs

No response

@RavaszEmber
Copy link

Hello,

I'm having the exact same problem with the exact same hardware. Raspberry PI CM4 on Manta M8 V2.0. XPS 7390 laptop with windows 11. The rpiboot installer took a while (it looped on installing a driver).

When I have my CM4 connected to my laptop via USB C (on the manta board) and run rpiboot I get this:
RPIBOOT: build-date Dec 19 2023 version 20221215~105525 62ce49c0
Waiting for BCM2835/6/7/2711/2712...

It won't progress from here. Please let me know what to do.

@pelwell
Copy link
Contributor

pelwell commented Jul 12, 2024

Contact the manufacturer of the Manta M8.

@RavaszEmber
Copy link

Actually I was able to recognize the eMMC eventually. I used this post, whose solution was to use a different USB cable.
In my case I went from using this Anker USB 2.0 C-C cable to the USB 2.0 C-A (with an A-C adapter for my laptop's usb C port). It worked right away after changing the cable.

It's unclear to me if this is an issue with the cable (they're both USB data cables), the USB C implementation on the Manta M8 V2.0, or the rpiboot software. Since changing the cable did the job it's likely on the Manta M8 V2.0.

@pelwell
Copy link
Contributor

pelwell commented Jul 12, 2024

We can at least say it's an incompatibility between the cable, the carrier, and the use case.

@tpups
Copy link

tpups commented Sep 14, 2024

Actually I was able to recognize the eMMC eventually. I used this post, whose solution was to use a different USB cable. In my case I went from using this Anker USB 2.0 C-C cable to the USB 2.0 C-A (with an A-C adapter for my laptop's usb C port). It worked right away after changing the cable.

It's unclear to me if this is an issue with the cable (they're both USB data cables), the USB C implementation on the Manta M8 V2.0, or the rpiboot software. Since changing the cable did the job it's likely on the Manta M8 V2.0.

Thank you for this comment! I was running into the same issue trying to run rpiboot on my MacBook Pro. Tried two different USB-C to USB-C cables and neither worked. Tried a USB-C to USB-A cable with a USB-A to USB-C adapter on the MBP end, and it worked right away.

Very bizarre, but appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants