Bigtreetech skr mini can't find mcu id

General Discussion
1

Basic Information:

Printer Model: ender 5 plus
MCU / Printerboard:bigtreetech skr mini e3 v3
Host / SBC
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

…
I have an ender 5+ that I’ve installed a BTT E3 in, and have installed klipper on a pi 3b. I used this guide for the klipper install, https://www.youtube.com/watch?v=h99vGPACB8M. I used the same guide on my 2 ender 3’s and everything works fine on both of them, they’re both using creality boards though.

On the 5 I’ve installed the new board, taken the same steps and do have mainsail running on the pi. I’m using the PI to generate the firmware, using the setting from the generic BTT config file:
"This file contains common pin mappings for the BIGTREETECH SKR mini

E3 v3.0. To use this config, the firmware should be compiled for the

STM32G0B1 with a “8KiB bootloader” and USB communication.

The “make flash” command does not work on the SKR mini E3. Instead,

after running “make”, copy the generated “out/klipper.bin” file to a

file named “firmware.bin” on an SD card and then restart the SKR

mini E3 with that SD card."

Going into kiaua and trying to find the mcu ID I get “No MCU found!
MCU either not connected or not detected!” I’ve tried both USB options, same result.

I’ve redone the firmware many times, the board takes the flash and I get firmware.cur on the SD.

I have 2 spare pi’s right now, I’ve put Klipper on both to see if it’s a PI issue, I get the same result. I bought a new SKR. The 1st was bought 2nd hand I never saw it running so in case I got screwed I bought straight from BTT. Same result.

I’m switching USB cables, I have 2 that came with the boards and 1 I pulled from my working ender 3, same results.

I’m trying to build a hybrid corexy printer with this, all the physical parts of been done for months and I’m just beating my head against a wall trying to get the pi/board to talk to each other. I know I’m missing something, but I don’t know what it is.

2

See BIGTREETECH-SKR-mini-E3/firmware/V3.0/Klipper at master · bigtreetech/BIGTREETECH-SKR-mini-E3 · GitHub and Issues flashing the printer board

3

Thanks, I’ll take a look.

4

Well, no joy. I tried the pre-compiled firmware and got the same results. I then went through the self generated, all the settings appear to be the same as what I had, but redid them anyway and still no change.

The LED on the board does the rapid flash with the new firmware.bin and then does change to firmware.cur. I don’t get it.

The only thing I can think of to try is grab the PI’s off my other 2 machines that are both running klipper and see if I get anything different.

5

And that didn’t work either. I’m out of ideas.

6

We have reports here that some people tried 5 different SD cards or USB cables until one worked. I’m pretty sure that it is something local on your side. The board is well known and usually quite unproblematic.

Unfortunately, this board has no easy way to get into the DFU. It is possible, but involved so I would recommend figuring out what the issue is.

7

I’m pretty sure it’s on my side, I just can’t figure it out. My other 2 machines were unproblematic using the same instructions, but they’re both running creality boards. I’ve swapped sd, cables, pi’s, 2 different skr’s and Im getting the exact same error. I just can’t figure out what I’m doing wrong :laugh:

I have the original board, the v2 2.2. Flashing it seems a little more complex than the SD route but I think I’ll give it a try and hopefully get the machine running. I wanted to upgrade while I was doing the hardware upgrade, but It’s been mocking me for months.

If I can get it up on the stock board, I can keep trying to get the skr and pi to communicate down the road.

8

If anyone is local to my part of Florida and wants to take a swing at this…