Unable to write tmc spi 'stepper_x' register

General Discussion
1

Basic Information:

Printer Model: Voron 2.4 350mm
MCU / Printerboard: BTT Octopus Max EZ
klippy.log
klippy.log (67.4 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:

I have been using the Octopus Max EZ with the 5160 drivers for over 6 months now it seems, I was attempting to reattach a BTT SFS (filament sensor) to my printer and updated the Klipper to latest HEAD, and than did a firmware update for the main MCU.

After attaching the SFS sensor to the mainboard and powering back up started seeing this error Unable to write tmc spi.

I disconnected the SFS, and tried downgrading Klipper, and then tried uploading the firmware directly to the SD card instead of over the USB connection. The other issues I looked at it seem to be due to a config value. But this was working previously with some early version of 0.12.0~

2 
DUMP_TMC stepper_y
========== Write-only registers ==========
GLOBALSCALER: 00000060 globalscaler=96
IHOLD_IRUN: 00061f1f ihold=31 irun=31 iholddelay=6
MSLUT0:     aaaab554 mslut0=2863314260
MSLUT1:     4a9554aa mslut1=1251300522
MSLUT2:     24492929 mslut2=608774441
MSLUT3:     10104222 mslut3=269500962
MSLUT4:     fbffffff mslut4=4227858431
MSLUT5:     b5bb777d mslut5=3048961917
MSLUT6:     49295556 mslut6=1227445590
MSLUT7:     00404222 mslut7=4211234
MSLUTSEL:   ffff8056 w0=2 w1=1 w2=1 w3=1 x1=128 x2=255 x3=255
MSLUTSTART: 00f70000 start_sin90=247
TPWMTHRS:   000fffff tpwmthrs=1048575
COOLCONF:   00020000 sgt=2
DRV_CONF:   00000400 bbmclks=4
PWMCONF:    c40c001e pwm_ofs=30 pwm_autoscale=1 pwm_autograd=1 pwm_reg=4 pwm_lim=12
TPOWERDOWN: 0000000a tpowerdown=10
========== Queried registers ==========
GCONF:      00000000
CHOPCONF:   00000000 mres=0(256usteps)
GSTAT:      00000000
DRV_STATUS: 80000000 stst=1
FACTORY_CONF: 00000006 factory_conf=6
IOIN:       10000040 sd_mode=1 version=0x10
LOST_STEPS: 00000000
MSCNT:      00000000
MSCURACT:   00730000 cur_b=115
OTP_READ:   00000006 otp_fclktrim=6
PWM_SCALE:  00000000
PWM_AUTO:   0000000c pwm_ofs_auto=12
TSTEP:      0007ffff tstep=524287
DUMP_TMC stepper_x
========== Write-only registers ==========
GLOBALSCALER: 00000060 globalscaler=96
IHOLD_IRUN: 00061f1f ihold=31 irun=31 iholddelay=6
MSLUT0:     aaaab554 mslut0=2863314260
MSLUT1:     4a9554aa mslut1=1251300522
MSLUT2:     24492929 mslut2=608774441
MSLUT3:     10104222 mslut3=269500962
MSLUT4:     fbffffff mslut4=4227858431
MSLUT5:     b5bb777d mslut5=3048961917
MSLUT6:     49295556 mslut6=1227445590
MSLUT7:     00404222 mslut7=4211234
MSLUTSEL:   ffff8056 w0=2 w1=1 w2=1 w3=1 x1=128 x2=255 x3=255
MSLUTSTART: 00f70000 start_sin90=247
TPWMTHRS:   000fffff tpwmthrs=1048575
COOLCONF:   00020000 sgt=2
DRV_CONF:   00000400 bbmclks=4
PWMCONF:    c40c001e pwm_ofs=30 pwm_autoscale=1 pwm_autograd=1 pwm_reg=4 pwm_lim=12
TPOWERDOWN: 0000000a tpowerdown=10
========== Queried registers ==========
GCONF:      00000000
CHOPCONF:   00000000 mres=0(256usteps)
GSTAT:      00000000
DRV_STATUS: 80000000 stst=1
FACTORY_CONF: 00000004 factory_conf=4
IOIN:       10000040 sd_mode=1 version=0x10
LOST_STEPS: 00000000
MSCNT:      00000000
MSCURACT:   00730000 cur_b=115
OTP_READ:   00000004 otp_fclktrim=4
PWM_SCALE:  00000000
PWM_AUTO:   0000000c pwm_ofs_auto=12
TSTEP:      0007ffff tstep=524287
3

See TMC drivers - Klipper documentation

If you are using the EZ5160 modules, they are having a bad history of dying easily.

Usually updating Klipper is not causing such issues and AFAIK nothing in the code has changed recently that would affect this area (otherwise this place would be full of similar reports).

Potentially your hardware tinkering has caused some issues. Especially when not powering down the board (like I typically do) but even with a powered down board, you are having quite large capacitances on such a board that might carry enough current to fry stuff.

4

No everything was powered down off before doing anything with the electronics. It just seems seem weird that with everything powered off and the only I did was plug in additional connector, but again not sure what else could be wrong either.

5

After getting this error, I switched out my board with a spare Octopus Pro thinking one of the drivers went bad. I finally got a round to ordering a replacement, and after some back and forth realized there had been a software change that caused this. At some point the SPI bus on the Max Ez board changed.

1 Like
6

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