Getting error: Unable to write tmc spi 'stepper_x' register GLOBALSCALER when trying to move motors.

[cray12399]

I was able to successfully get my Stridemax Dual FD to communicate with my Raspberry Pi over CAN using the following make settings:

• Micro-controller Architecture: Raspberry Pi RP2040
• Flash Chip: W25Q080 with CLKDIV 2
• Build Klipper deployment application: 16KiB bootloader
• Communication interface: CAN bus
• CAN RX: 9
• CAN TX: 8
• GPIO pins to be set on bootloader entry: ()

I know the CAN communication is working properly because my Raspberry Pi is able to detect the board and control the neopixel LED's connected to it. However, when I try to move my motors, I immediately get the error: Unable to write tmc spi 'stepper_x' register GLOBALSCALER when trying to move motors. My Klipper configuration matches exactly the one on this Github. The board is being powered by 24v and there are no blown fuses or obviously blown caps. All of the status LEDS are on when I power on the board. I left all of the jumpers in the places that they came from the factory.

What I have tried so far:

• Uplugging the 5v jumper for USB
• Installing with USB communication interface to see if CAN is the issue.
• Switching the MISO and MOSI gpio numbers since there appears to be a discrepancy between the Github and wiki.

Nothing I have tried has come even close to fixing the issue which is why I am posting here. I have attached my klippy.log and printer.cfg for your review.
klippy.zip
printer.zip

If needed, I can take some pictures of my hardware setup so you can review that everything is installed properly.

[cray12399]

I got another board to make sure that this wasn't just a faulty board. It is doing the exact same thing. So, either Fysetc's documentation is worthless, or the product is just a brick. I am beyond annoyed that this product has such little documentation, virtually no tech support, and is such a pain to set up. I tore my printer apart to install this thing and now I am going to have to spend money to get it back to where it was before buying this board.

[eliwong]

We are very sorry for bringing you a bad experience. We have updated the instance configuration on github again and uploaded the AWD configuration that has been verified by customers. We hope it can help everyone.
We will also upload a detailed configuration video to Youtube this week, and we are also building an AWD system for actual testing. You will see the results by then.