[BUG] Display steps through touch calibration autonomously - BOARD_CHITU3D_V6

[MrFrickinFixit]

Did you test the latest bugfix-2.1.x code?

No, but I will test it now!

Bug Description

Using the latest Marlin v2.1.1. with BOARD_CHITU3D_V6 (103 mainboard not 446) and TFT_TRONXY_X5SA. After flashing the firmware to the board, the display goes directly into touch calibration, then goes through all the calibration steps without actually touching the display. It seems to get hung up on the final step then becomes unresponsive. This is the second mainboard and second display, same issue. I flashed the stock chitu firmware back onto the board and the display responds as it should. Thoughts please. I had the same issue running v2.0.9.3, then moved to v2.1.1 after obtaining a new board and display. Configuration.zip

Bug Timeline

Seems to be an old issue. After flashing v2.0.9.3 onto the board.

Expected behavior

After flashing the firmware, the display should enter touch calibration mode, then allow you to push specific areas of the display to step through the calibration.

Actual behavior

The display enters touch calibration mode, steps through the calibration autonomously as if the display is being pressed, then the display becomes unresponsive after it reaches the final step.

Steps to Reproduce

Flash Marlin to mainboard from SD card and wait for splash screen to go away.

Version of Marlin Firmware

Marlin v2.1.1 CONFIGURATION_H_VERSION 02010100

Printer model

TronXY X5SA

Electronics

Stock CXY-V6-191017

Add-ons

BLTouch

Bed Leveling

ABL Bilinear mesh

Your Slicer

Cura

Host Software

OctoPrint

Don't forget to include

• [X] A ZIP file containing your Configuration.h and Configuration_adv.h.

Additional information & file uploads

No response

[ellensp]

provided config does not compile

error "SERVO0_PIN must be defined for your servo or BLTOUCH probe."

[MrFrickinFixit]

provided config does not compile #error "SERVO0_PIN must be defined for your servo or BLTOUCH probe." #define SERVO0_PIN PD12 pins_CHITU3D_common.zip

[thinkyhead]

When it's not clear how an issue cropped up, it may be simplest to use git bisect to find a specific change that caused the problem to manifest. But first you would need to find an older version of Marlin where the bug does not exist.

[github-actions[bot]]

Greetings from the Marlin AutoBot! This issue has had no activity for the last 90 days. Do you still see this issue with the latest bugfix-2.1.x code? Please add a reply within 14 days or this issue will be automatically closed. To keep a confirmed issue open we can also add a "Bug: Confirmed" tag.

Disclaimer: This is an open community project with lots of activity and limited resources. The main project contributors will do a bug sweep ahead of the next release, but any skilled member of the community may jump in at any time to fix this issue. That can take a while depending on our busy lives so please be patient, and take advantage of other resources such as the MarlinFirmware Discord to help solve the issue.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.