No klippy log file and MCU not showing

General Discussion
1

Basic Information:

Printer Model: Voron 2.4
MCU / Printerboard: Spider V1.0
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: The MCU is is not detected on the usb. I have tried a number of fixes and can confirm the the Debian bug is not present.

Before loading Klippy the mouse and keyboard worked but these do not seem to be working on the Raspberry Pi now.
dmesg.zip (10.0 KB)
lsusb.zip (1.2 KB)

I can not attach the klippy.log as I can’t find it.
Attached is the output from dmesg and from running lsusb -v.
It’s possible the issue is not related to Klippy and if this is so could you please direct me to an appropriate site.

Thanks
Eric

Update, whilst attempting to ensure bootloader and firmware were on Spider board I used the STM Cube Programmer. I accidently left the jumper on and reconnected and started RPi. The board showed up as FYSETC in DFC mode. Turned off, removed jumper and restarted and the board does not show.
Not sure whether this adds clarity or more confusion.
Regards
Eric
I’ve created the klippy log from the browser window.
klippy.zip (4.5 KB)

…

2

Usually this is not needed and poses the risk that you accidentally kill the bootloader. If anything, only flash the bootloader and carefully stick to the instructions: FYSETC-SPIDER/bootloader at main · FYSETC/FYSETC-SPIDER · GitHub

From the symptoms either:

  • potentially a killed bootloader
  • board not correctly flashed
  • not correctly connected

Carefully follow the pointers given in Issues flashing the printer board

3

Thanks for the reply.
I have installed the bootloader only on the board using the STM Cube Programmer and reconnected to the RPi using the USB cable.
Following instructions at FYSETC-SPIDER/Spider Klipper Firmware Guide.pdf at main · FYSETC/FYSETC-SPIDER · GitHub I’ve got the board ID and have progressed with the printer config file.
Of note in the above guide is to :

  • Choose ‘No bootloader’ when building the flash file
  • Flash the board using the USB cable with jumper between BTO and 3.3v so board is in DFU mode
  • Once the board is flashed to move the jumper to GND/BTO.

Thanks again for your help and I’ll now work through the issues with the printer config file.
Regards
Eric

4

Interesting.
I would not want to work without a bootloader since it makes updating Klipper a pain with direct access to the board and fiddling around with jumpers.

I have a Spider board as well and never had this issue.

Since you have flashed without bootloader, you have effectively overwritten the bootloader flashed earlier.

You might want to try Katapult as an alternative bootloader.

5

I have managed to load the 32k bootloader using the STM Cube Programmer and then flash klipper onto the board using the usb method and retain the connection when running the printer.

Thanks for your help.

6

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