I am running an TFT35 E3 on a GTR board with Klipper. I DL'd the config.ini from BTT and the Notouchscreen binary "BIGTREETECH-TFT35_V3.0_E3.26.x.bin" and put them on an SD, inserted and restarted. Now it just says ST7920 Ready. Please let me know what I need to change.

Commit: 9e32d731e2bc118e29bcdaf2b2336dc93e847faa Display: BIGTREE_TFT35_V3.0_E3

Only showing "NoTouchFW V1.1" on a otherwise black screen.

Thanks for keeping working on it!

Can you initialize the PS_ON pin to HIGH on boot so that a connected BTT relay 1.2 does not automatically shuts down after 15 seconds? I know there is no point in keeping the relay connected this way, but it's the original wiring.

BIGTREETECH-TouchScreenFirmware/TFT/src/User/API/extend.c

// Power Supply Control pins Initialization
void PS_ON_Init(void)
{
  GPIO_InitSet(PS_ON_PIN, MGPIO_MODE_OUT_PP, 0);
  GPIO_SetLevel(PS_ON_PIN, infoSettings.ps_active_high);
}

So im poking around at the TFT35 E3 V3.0 screen for a few hours now and im stuck...

What i got so far:

• I installed the matching noTouchScreenFirmware in Version 1.2 successfully
• i see on screen "ST7920Emulator ready"

But im not getting any further...

Im using a BTT SKR mini e3 v2 with klipper and my klipper config for the screen looks like this:

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

[display]
lcd_type: st7920
cs_pin: EXP1_7
sclk_pin: EXP1_6
sid_pin: EXP1_8
encoder_pins: ^EXP1_5, ^EXP1_3
click_pin: ^!EXP1_2

Thanks for keeping it up. I can confirm that https://github.com/teeminus/NoTouchScreenFirmware/commit/37e3f05072bee8606ad9ce6f2cb3f8091a147846 works for my setup.

Is it possible to control dimming from within Klipper?

Hi, i tried MKSTFT28.bin on my Artillery Sidewinder X1 with a MKS TFT28 3.2, and it flashed without problems and now displays the "ST7920Emulator ready" screen, but i guess due to how the screen is built into the printer case, all text is upside down. Can you maybe create a version that flips the output vertically?

Amazing work with this firmware, it just works perfectly :)

I'm trying to add brightness support through PWM, but it seems that the screen just blinks instead reducing the brightness. I'm probably doing something wrong as I'm not super familiar with the code.

I'm wondering if this would be something you could add and let the user define in some .h file for supported models?

Thanks a lot for your great work again!

Not an issue, but rather a correction.. Tried connecting my 1.4 Turbo with TFT35 V3 screen, as per the template posted here and it was giving me an error, the values below worked for me ..

`

Hi there,

I wanted to reflash my TFT35 to BTT firmware, and no mater what SD card or USB stick I choose, it does not flash the firmware. I renamed the .bin to firmware.bin, FIRMWARE.bin and took he original name... nothing works.

I followed the previous thread on Klipper where you guided on how to make BTT's firmware to function in Marlin mode. I compiled that one and everything worked, except some wierd menu artifacts and some other small stuff.

However, wanted to confirm the NoTouch working instead. So i have tried both downlaoded the precompiled binary and i have also tried to compile myself. In both cases the LCD is stuck at NoTouchFw V1.2 with ST7920Emulator ready.

Running the same pin config in Klipper as i did with the "original" firmware, reflashed it and that one works. But i want the NoTouch to function instead.

This is what i have in Klipper:

[board_pins]
aliases:
    EXP1_1=P1.30, EXP1_3=P1.18, EXP1_5=P1.20, EXP1_7=P1.22, EXP1_9=<GND>,
    EXP1_2=P0.28, EXP1_4=P1.19, EXP1_6=P1.21, EXP1_8=P1.23, EXP1_10=<5V>,
    EXP2_1=P0.17, EXP2_3=P3.26, EXP2_5=P3.25, EXP2_7=P1.31, EXP2_9=<GND>,
    EXP2_2=P0.15, EXP2_4=P0.16, EXP2_6=P0.18, EXP2_8=<RST>, EXP2_10=<NC

[display]
lcd_type: st7920
cs_pin: EXP1_4
sclk_pin: EXP1_5
sid_pin: EXP1_3
encoder_pins: ^EXP2_5, ^EXP2_3
click_pin: ^!EXP1_2

Any tips?

Now I noticed you have another challenge open in regards to the GTR board, so I am wondering if it may be related to that and not the screen. I did notice some of the GTR pinouts had been confused... So I have more information for this one...

From Marlin -> pinouts -> GTR:

/**
 *               -----                                    -----
 *           NC | · · | GND                           5V | · · | GND
 *        RESET | · · | PB10(SD_DETECT)    (LCD_D7)  PG5 | · · | PG6  (LCD_D6)
 *   (MOSI)PB15 | · · | PH10(BTN_EN2)      (LCD_D5)  PG7 | · · | PG8  (LCD_D4)
 *  (SD_SS)PB12 | · · | PD10(BTN_EN1)      (LCD_RS)  PA8 | · · | PC10 (LCD_EN)
 *    (SCK)PB13 | · · | PB14(MISO)        (BTN_ENC) PA15 | · · | PC11  (BEEPER)
 *               -----                                    -----
 *               EXP2                                     EXP1
 */

#define LCD_PINS_RS                     PA8
#define BTN_EN1                         PD10
#define BTN_EN2                         PH10
#define LCD_PINS_ENABLE                 PC10
#define LCD_PINS_D4                     PG8

The TFT70v3 does work under Marlin with these settings.

From the Klipper GTR Board Config File:

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

EXP1 / EXP2 pins - GTR Board

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

[board_pins] aliases: # EXP1 header EXP1_1=PC11, EXP1_3=PC10, EXP1_5=PG8, EXP1_7=PG6, EXP1_9=, EXP1_2=PA15, EXP1_4=PA8, EXP1_6=PG7, EXP1_8=PG5, EXP1_10=<5V>, # EXP2 header EXP2_1=PB14, EXP2_3=PD10, EXP2_5=PH10, EXP2_7=PB10, EXP2_9=, EXP2_2=PB13, EXP2_4=PB12, EXP2_6=PB15, EXP2_8=, EXP2_10=

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

"RepRapDiscount 128x64 Full Graphic Smart Controller" type displays

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

Display Definitions & Mappings

#display_group: _default_16x4 #cs_pin: LCD_PINS_ENABLE / EXP1_3 / PC10 #sclk_pin: LCD_PINS_D4 / EXP1_5 / PG8 #sid_pin: LCD_PINS_RS / EXP1_4 / PA8 #encoder_pins: BTN_EN1, BTN_EN2 / EXP2_3, EXP2_5 / PD10, PH10 #click_pin: BTN_ENC / EXP1_2 / PA15 #spi_software_sclk_pin: [SCK??|LCD_PINS_D4] / EXP2_2 / PB13 (SCK???) #spi_software_mosi_pin: MOSI / EXP2_6 / PB15 #spi_software_miso_pin: MISO / EXP2_1 / PB14

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

Tried & Did Not Work

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

[display] lcd_type: st7920 #display_group: _default_16x4 cs_pin: EXP1_3 sclk_pin: EXP1_5 sid_pin: EXP1_4 encoder_pins: ^EXP2_3, ^EXP2_5 click_pin: ^!EXP1_2 #kill_pin: ^!EXP2_8

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

#[display] #lcd_type: emulated_st7920 #display_group: _default_16x4 #en_pin: EXP1_3 #spi_software_sclk_pin: EXP2_2 #spi_software_mosi_pin: EXP2_6 #spi_software_miso_pin: EXP2_1 #encoder_pins: ^EXP2_3, ^EXP2_5 #click_pin: ^!EXP1_2

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

Yet To Try

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

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

NOTES:

• I have loaded 1.3 of the firmware onto the TFT70v3 and it does say ST7920 Emulator Ready

Everything works great with the firmware. I searched and looked at the code some and could not find on how to control the LED on the knob itself for a TFT35 E3 v3? Is that something the firmware is set to do?

Used both modes (emulated and not), but in both cases the screen (TFT35-B1 in a Biqu B1) always gets garbled after a little while.

#[display]
#lcd_type: st7920 
#cs_pin: EXP1_4
#sclk_pin: EXP1_5
#sid_pin: EXP1_3
#encoder_pins: ^EXP2_5, ^EXP2_3
#click_pin: ^!EXP1_2

[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

Starting to think it might be some interference going on with the EXP1/EXP2 cables internally, but these issues don't surface when using the normal fw with Marlin mode. This makes me wonder why this implementation suffers from this issue.