STM32 H723: Mcu Mhz and Software SPI Comunication Error

General Discussion
1

Basic Information:

Printer Model: Vzbot235AWD
MCU / Printerboard: Super 8 Pro H723 / Mellow TMC 5160 PRO v1.2
klippy.log
klippy (2).log.zip (1.7 MB)
message.txt (10.9 KB)

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:

Hi, hope to find you all well. Please help me to get my machine working again🥲.
I was running my firmware just fine, because of the klipper updates I wanted to compile new firmware into my mainboard, I followed all the documentation and know I have issues with software Spi when connecting to the Tmc5160, only my extruder works because is a 2209 with Uart comunication. Hardware Spi works fine for some minutes and then shutsdown, but that is a known issue with this mainboard, thats why all the user using this mainboard uses software Spi. I have run software Spi with no issues until I compiled new firmware and the error messages varies, sometimes is X, sometimes the error shows Y, sometimes Z, sometimes is drv_error = 1, sometimes is globalscaler, so I think is an Spi comunication issue. Other important considerations are that klipper notifications shows that the Mhz is 399mhz when it should be 400Mhz, sometimes shows the samr error but with 401Mhz.

Also, the old firmware was compiled with a Rpi3b and this time I compiled with a Raspberry Pi 5 (Bookworm) and no errors while compiling the new firmware with Bookworm.

Thanks for your time!!

20240315_134144
20240315_1341441920×1440 170 KB

…

2

This is just a warning that you can ignore. It has no immediate impact.

  • Make sure you really have configured your board during make menuconfig correctly. There are two different variant. See https://mellow.klipper.cn/#/board/fly_super8_pro/flash
  • Your errors on the TMC are mainly around undervoltage, e.g.
    TMC 'stepper_x' reports GSTAT:      00000005 reset=1(Reset) uv_cp=1(Undervoltage!)
TMC 'stepper_x1' reports GSTAT:      00000005 reset=1(Reset) uv_cp=1(Undervoltage!)
TMC 'stepper_y' reports GSTAT:      00000005 reset=1(Reset) uv_cp=1(Undervoltage!)
TMC 'stepper_x' reports GSTAT:      00000000
Transition to shutdown state: TMC 'stepper_x1' reports error: GSTAT:      00000005 reset=1(Reset) uv_cp=1(Undervoltage!)
  • Check your power supply if it is able to deliver stable 24V
  • Check your old logs, to determine the version that worked before. Although I do not believe that something has changed that would affect this.
3

Hii, @Sineos !! The undervoltage issue is a common thing thats happens to me when the mainboard is powered on before the host computer, thats a known issue. My issue begin after flashing, 100% sure!! My drivers are 4x external 5160 drivers running at 48V for the Awd system, a 5160 stepstick running at 24V for Z. When I home only X, is shows error, if I home Y, shows the error, also for Z, what all of them have in common? SPI comunication!! And why hardware Spi works fine, and software SPI doesnt connect? Maeby a bug?

4

This is the first time I hear this. The typical driver reset due to powering up looks like:

TMC 'stepper_z' reports GSTAT:      00000001 reset=1(Reset)
TMC 'stepper_z' reports GSTAT:      00000000

The driver is resetting and it does not lead to an error.

5

Its solved!!! The error was in compiling firmware with the Raspberry Pi 5 with bookworm, I used a Rpi2w with bullseye and then flash the microcontroller and worked perfect now!!

Also on Vzbot Discord I found that they recommend adding a macro to enable the drivers 1 by 1 with 1 second delay. This is because if all 4 drivers are activated at the same time, because the drivers are externals and have two big capacitors each, it draws too much current when enabled from power off, and that results in a voltage drop that is enough to trigger the error of Undervoltage.

1 Like
6

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