STM32F407VET6 wont connect

General Discussion
1

Basic Information:

Printer Model: Lotmaxx V2
MCU / Printerboard: stm32F407VET6
klippy.log
klippy-log.txt (21.1 KB)

Fill out above information and in all cases attach your klippy.log file. Pasting your printer.cfg is not needed

Describe your issue:

I have a STM32F407VET6 board that won’t connect. I have tried all sorts of permutations via menuconfig but nothing has worked so far. Marlin can connect so i am fairly sure things are working as they should. At this point I am not sure what next steps should be. The only odd thing that I see between Marlin and Klipper is the offset for the bootloader.

I dont know if it helps or not but this is the env define for Marlin:

platform = ${common_stm32.platform}
platform_packages = ${stm_flash_drive.platform_packages}
extends = stm32_variant
board = genericSTM32F407VET6
board_build.variant = MARLIN_F4x7Vx
board_build.offset = 0x11000
board_upload.offset_address = 0x08011000
build_flags = ${stm_flash_drive.build_flags} -D HSE_VALUE=25000000
build_unflags = ${stm32_variant.build_unflags} -DUSBCON -DUSBD_USE_CDC
debug_tool = stlink
upload_protocol = stlink

Any and all help would be appreciated.

2

Hello @spinixguy !

Are you sure about the serial ?

[mcu]
serial = /dev/ttyUSB0
restart_method = command

Afaik, it should more complex. Like this:

grafik
grafik1212×86 33.8 KB

I took that from this:

3

I have two printers on here and they both have the same id so the /dev/serial/by-id doesn’t work for me.

4

I would suggest using/dev/serial/by-path. That will tie the printers to the physical USB ports where they’re connected.

5

I would agree, but for some reason i dont seem to have those rules in udev as that directory doesnt exist.