-
Notifications
You must be signed in to change notification settings - Fork 229
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
Comments
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: It won't progress from here. Please let me know what to do. |
Contact the manufacturer of the Manta M8. |
Actually I was able to recognize the eMMC eventually. I used this post, whose solution was to use a different USB 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. |
We can at least say it's an incompatibility between the cable, the carrier, and the use case. |
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. |
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
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
The text was updated successfully, but these errors were encountered: