Struggling to get BTT Manta M5P to connect to Klipper

Basic Information:

Printer Model: Custom
MCU / Printerboard: Manta M5P
Host / SBC: Computer running Ubuntu Server 24.04.03 LTS
klippy.log

klippy (3).log (92.6 KB)

Describe your issue:

My BTT Manta refuses to connect to klipper. I am using KIAUH to install klipper. For the firmware of my Manta I am able to configure it and successfully flash it as the file is renamed from “firmware.bin” to “FIRMWARE.CUR” and the Manta’s lights flash showing that it is flashing. I have even downloaded and flashed the premade firmware file from BTT found here. Also I know that the Manta has two SD card readers, 1 full size and 1 micro, I am using the full size one for flashing. When running ls /dev/serial/by-id/* I get the id “/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0” which I plugged into my config. Even after reflashing several times I get this error.

I know it is not the software on the computer as I have a BTT Kraken and I was able to set up the firmware and it was able to connect to Klipper with no issue. It is also not a bad usb cable as I have tried several including the one that worked with the Kraken. The only difference I can see between the Kraken and Manta was that when the manta was flashed the device id didn’t change. It was the same as before the flash “/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0”. I have also tried reinstalling KIAUH and completely reinstalled Ubuntu.

For the firmware for the Manta I am setting it up as the manual describes.

I am at a complete lost as this is the second prolong period of time I have dedicated to solving this issue. The first time I have tried to solve this was a few months ago.

Any help will be greatly and appreciated.

If ls /dev/serial/by-id is returning usb-1a86_USB_Serial-if00-port0 then you’re not burning Klipper into the M5P MCU’s Flash.

You should be seeing something like usb-klipper_stm32g0b1xx_1A003E00105050505933383420-if00

Can you please go through what kind of SD Card (size is most important parameter here) along with the steps that you are taking to load the SD Card with the firmware that you are building?

Please be as exact as possible, ideally providing screenshots of the actions along with the responses that you are getting.

Thanks for responding

I have been using 3 different SD cards to see if that is the issue. A 4gb SD card, a 8gb MicroSD card through an adaptor, and a 64gb through an adaptor (although when formatted only 2gb are in use). All of the SD cards have been formatted to FAT32 or FAT.

image

After running the make command I use a program called Termius to extract the “klipper.bin” file from the Linux computer to my computer.

From there I renamed the file to “firmware.bin” transfer it to the SD card.

image

Than I take the SD card out of my computer and into the Manta, hit the reset button. After that the light does it blinking thing and I take out the card to confirm that it got renamed to “FIRMWARE.CUR” which it always does.

image

Through out the entire process no errors or issues occurred, or any response. It just did what I told it to do. If I am missing any more information please tell me.

Rather than using an SD Card, could you try using DFU Mode, as outlined in the Esoterical Guide for the M5P.

Use this page for specifying how you configure make menuconfig as well as putting the M5P’s MCU into DFU Mode:

Once you’re in DFU Mode, follow the instructions here for loading Katapult and then Klipper.

The problem with using a utility for downloading a file to a PC and then copying it onto an SD Card, you can’t always tell if something gets modified along the way - an area to watch out for is how what the program things are new lines, does it add a CR character to a NL or delete the CR character if it detects a CR-NL combination.

Using DFU to Flash the M5P’s MCU directly from the Host, without using an SD Card, is easier and less prone to having problems.

I have tried to use DFU Mode in the past and just tried again now but it never seems to work for me. Even after following the instructions to but the MCU into DFU it is unable to go into that mode. When I run lsusb to confirm that the MCU is in DFU mode I get this.

image

To even double check I tried to install the firmware via KIUAH it is not able to detect an MCU via DFU.

Here is also a video of me doing it in case I am making a mistake

I am certainly no expert, so somebody correct me if I am wrong…

Is the manta M5p useable with an external host for klipper, or do you have to use the onboard slot for a computing module?
I wasn’t able to get it up and running with a raspberry pi, but I didn’t try as tirelessly as you have. I gave up and used a CB1 computing module (not that I would recommend that)

@Idontlikesoftware

Thanx for the video, but I can’t quite see how the buttons are being pressed.

Personally, I use the fingernails of my left and right index fingers or a couple of small screwdrivers to press down BOOT0 and then RESET.

Could you do a power cycle and then try it again? Sometimes, if the MCU has gone through different Flash cycles, you can’t get it into DFU Mode.

It is only usable with an SBC Host that is in the Raspberry Pi CM4 format and plugged into the two 100 pin connectors.

When you say “Raspberry Pi”, do you mean something like a Raspberry Pi 4B and not a CM4?

A CB1 should run fine - I’m using one on one of my printers with a Manta M8P right now.

@Idontlikesoftware

I glossed over your “HOST/SBC” entry in the original post, thinking that you knew that you had to have something like a Raspberry Pi CM4 plugged into the 100pin connector - you cannot conned to the Manta M5P’s MCU with anything other than an SBC that has the Raspberry Pi CM4 form factor.

Same result, nothing. In regards to the video you can’t see it due to my thumb but if you turn the volume up you can here the buttons being pressed and released.

So just to make sure, the only way to have communication to the Manta is through the Raspberry Pi CM4 or BTT own raspberry computer? Or is that just for DFU?

The only way to communicate with the Manta M5P’s MCU is by a Raspberry Pi CM4 or equivalent form factor SBC plugged into the two 100pin connectors on the board.

The USB C connector is used for loading the eMMC on Raspberry Pi CM4s or equivalent form factor SBCs that have eMMC.

It’s not explicitly stated in the sales information or the User Manual, but the way the USB hub is wired on the PCB, there’s no way to connect to the MCU except using a CM4 or equivalent form factor SBC plugged into the two 100pin connectors.

Ok, got it. Thank you for your help. At least I got an MCU for my next 3D printer which I will build maybe someday :smiley:.

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.