SKR MINI E3 V2 AND BIGTREE TFT E3 V3

[Talha909]

I have fallowing hard ware

SKR MINI E3V2
BIGTRE TFT 35 V3
RASPBERY PI ZERO

My lcd is not working. There is garbage on the screen. I have done pi zero with spi . There is any solution for that.

[oldman4U]

And you believe the problem is in the firmware of the TFT because...?

Check the troubleshooting section of the ReadMe.

[radek8]

Please send Maelin configuration, TFT configuration.
Send some photos with TFT connection with SKR.
As Oldman4U writes, the problem is not in the FW of the display, but in the configuration or connection.

[Talha909]

HI. It was working good in marlin. But it does not work in klipper.

[radek8]

You didn't write that it was Klipper.
Klipper is probably not fully supported yet ...
#705

[bigtreetech]

https://www.klipper3d.org/Config_Reference.html#emulated_st7920-display
Did you set the klipper here to adapt the simulation ST7920

[Talha909]

Yes

[Talha909]

#[board_pins]
#aliases:
# EXP1 header
#EXP1_1=PB5, EXP1_3=PA9, EXP1_5=PA10, EXP1_7=PB8, EXP1_9=,
#EXP1_2=PA15, EXP1_4=, EXP1_6=PB9, EXP1_8=PB15, EXP1_10=<5V>

See the sample-lcd.cfg file for definitions of common LCD displays.

#[display]
#lcd_type: emulated_st7920
#spi_software_miso_pin: EXP2_1
#spi_software_mosi_pin: EXP1_3
#spi_software_sclk_pin: EXP1_5
#en_pin: EXP1_4
#encoder_pins: ^EXP2_3, ^EXP2_5
#click_pin: ^!EXP1_2

[bigtreetech]

######################################################################

BigTreeTech TFT TouchScreen emulated 12864 mode

######################################################################

[display]
lcd_type: emulated_st7920
spi_software_miso_pin: PA13 # status led, Virtual MISO
spi_software_mosi_pin: PB15
spi_software_sclk_pin: PB9
en_pin: PB8
encoder_pins: ^PA10, ^PA9
click_pin: ^!PA15

[output_pin beeper]
pin: PB5

Hello, I can display normally with this configuration on SKR-mini-E3-V2.0

[Talha909]

I tried these but did not work. Can you please check again. I have skr mini e3 with with tft 3e v3 and rapi zero with spi connections.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

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.