-
Notifications
You must be signed in to change notification settings - Fork 50
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
Manta M8P + CM4 , no usb connection , not flashing from SD card #42
Comments
You may need to use the SWD interface to program the MCU. |
Also, check that your OS is not dumping any hidden files onto your SD card. macOS does this sometimes and it messes with the bootloader. |
Check what file system your SD card is formatted for. I used a new SD card out of the box, and I didn't check and had the same issue. after I formatted it to FAT32 it worked. |
Hello, Similar problem... though I had to find an old and smaller SD card (2GB) as my 32 GB new SD would not work. |
I had the same issue. Defiantly a smaller card (not 64Gb as I tried for 2 days) formatted in FAT32 was the way to go. Strangely enough I didn't manage to format in FAT32 the bigger cards. |
I have a 2Gb FAT32 sd card, and it is still not working. When trying through DFU i have no serial Id created so I assume it is not working either. I have another board, MantaE3eZ for which it worked perfectly fine. Any more insights on how to solve? |
I found the solution to the problem in a video on YouTube, I'll put it here so you can see |
I have just installed a CM4 onto a (V1.0) M8P
I can SSH into the board just fine and have compiled the firmware.
When I use a SD card to first flash the firmware-usb.bin (renamed to firmware.bin) nothing happens.
I tried renaming the firmware-usb.bin to FIRMWARE.bin to no effect.
Further more when using the command : ls /dev/serial/by-id/* to list the MCU serial the responce is :
No such file or directory.
I have enabled the USB2.0 HUB in the config.txt
To check usb functionality I connected a SKR1.4 to the USB-A connection and running the command again it does find it
So the config.txt is edited Ok i think.
The text was updated successfully, but these errors were encountered: