Manta M5P not picking up USB devices (i.e. the MCU)

General Discussion
1

I just got a BTT Manta M5P I ordered and I am trying to flash Klipper to the MCU, but for some reason my board just doesn’t go into DFU mode, or at least it is not showing up on my CB1…

I’ve tried everything, holding down the BOOT0 button and the pressing RESET while I have dmesg -HW on my screen in order to see if the USB device gets added, reflashing again and again using a SD card, which seems to work as the LED blinks rapidly and the file on the SD card is renamed to FIRMWARE.CUR. I also found the stock bootloader that’s supposed to come with the board and flashed that to see if it fixes it but that didn’t work either.

After no success from the firmware side, I decided to see if maybe the issue was the USB controller or something similar, and it seems my CB1 is not picking up any USB devices I connect to the board’s USB ports, with no kernel message appearing when I plug in a new device. This makes me think it might be that either my CB1 is not correctly plugged in to the board (is there some way to see if it is?), or that maybe I have a faulty USB controller, though I wanted to see if you guys had any ideas I might test.

Also, I think the ethernet port on the board is not working either, but I’m not sure as my cable is a bit janky.

2

Some questions for you.

  1. What instructions are you following to set up you CB1/M5P?
    1. What OS image are you using?
  3. Are you able to SSH into your CB1? From everything you’re describing I’m not sure - are you using a keyboard and display plugged into the M5P?
  4. If you’re having problems with your Ethernet cable, have you tried making a WiFi connection?
  5. Rather than using dmesg you should be using lsusb and seeing something like:
    image
    image773×100 5.9 KB
    With the 0483:df11 showing up. What do you

I’m not sure what you mean about getting a “kernel message” when you plug in a USB device.

3
  1. I’m following the manual from the github repo ( Manta-M5P/BIGTREETECH MANTA M5P V1.0 User Manual.pdf at master · bigtreetech/Manta-M5P · GitHub )
  2. I am running the latest image release from GitHub - bigtreetech/CB1: OS System image for CB1
  3. Yup, I have SSH access to the board through a WiFi connectio.
  4. Yup
  5. I know, I just wanted to see if maybe there was some error reported by the kernel.

By kernel message I mean something like this:

[Aug 4 23:34] usb 2-2: new SuperSpeed USB device number 3 using xhci_hcd
[  +0.018042] usb 2-2: New USB device found, idVendor=0951, idProduct=1666, bcdDevice= 1.10
[  +0.000005] usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[  +0.000002] usb 2-2: Product: DataTraveler 3.0
[  +0.000002] usb 2-2: Manufacturer: Kingston
[  +0.000002] usb 2-2: SerialNumber: -
[  +0.010308] usb-storage 2-2:1.0: USB Mass Storage device detected
[  +0.000151] scsi host8: usb-storage 2-2:1.0
[  +1.045791] scsi 8:0:0:0: Direct-Access     Kingston DataTraveler 3.0 0000 PQ: 0 ANSI: 6
[  +0.000844] sd 8:0:0:0: [sdc] 121077761 512-byte logical blocks: (62.0 GB/57.7 GiB)
[  +0.000292] sd 8:0:0:0: [sdc] Write Protect is off
[  +0.000004] sd 8:0:0:0: [sdc] Mode Sense: 23 00 00 00
[  +0.000138] sd 8:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[  +0.025257]  sdc: sdc1 sdc2
[  +0.000142] sd 8:0:0:0: [sdc] Attached SCSI removable disk

(taken from my Linux desktop when plugging in a USB stick)

4

What are you getting for lsusb?

5

This is what I get after running lsusb:

biqu@bigtreetech-cb1:~$ lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
6

That means you have a working USB Hub and, most likely, your CB1 is installed correctly.

I presume that you’re getting the same response whether or not you:

  • Press and Hold BOOT0
  • Press and Release RESET
  • Release BOOT0

Which should put you in DFU Mode.

So, the question is whether or not your MCU works.

I’m gonna be a little unorthodox here and have you create a Klipper firmware image on your Linux desktop - you can do it on the CB1 but once you create the firmware image you’ll have to transfer it to the Linux desktop or PC to put on an SD Card.

You might as well install Klipper on the Linux machine and create the SD Card from there.

Open a terminal window on your Linux machine and install KIAUH by following the process:

Next, start KIAUH (./kiauh/kiauh.sh) and “Install” just “Klipper”.

cd ~/klipper and enter make menuconfig and set up the menu with:

image
image1121×632 32.3 KB

Once done, press “Q” followed by “Y” and then:

  • make clean
  • make

This firmware image is basic Klipper with a USB connection and turns on the STATUS LED on the board.

Then set up an SD Card (ideally no larger than 4GB) with FAT32 and 4096 block size and follow the update procedure from the User Manual:

image
image759×347 31.9 KB

So, if everything works, then you’ll have your MCU ID and a lit LED.

Otherwise, you have a problem with your MCU and the board.

7

Thank you for your help, I’ve flashed the firmware built as instructed, and I see no new LED turned on. By looking at the schematic, I gather the LED marked S on the silkscreen, next to the always on one marked P, is supposed to turn on but it does not.

I noticed though that when I perform the sequence to get the MCU onto DFU mode, that LED lights up, but just a little bit, as if only a fraction of the normal current is flowing there. I think this may mean it is in fact the board that is faulty… I’ll have to contact the seller then.

Thank you for your help

8

Sorry, that would be my conclusion to your testing as well.

I hope you don’t have any problems getting a replacement.

9

So… I was in the process of recording video evidence to show the board malfunctioning, when suddenly the MCU showed up after running lsusb, and even after doing the button sequence to get it into DFU mode.

As I was taking pictures before of all the components, I had taken the CB1 out of the Manta mainboard, and later for recording the video I re-installed it, so my guess is that the CB1 was in fact just not properly seated.

Anyways, I’ll see that everything else works properly now, but I think my problem solved itself lol

2 Likes