Fix SPI TFT Compile Errors on SKR V3/EZ & V2 - #26041
Conversation
|
|
|
Even fully reverting If I drop the 3ea87ad / #25784 commit completely, this combination works fine. After more testing & trying out the original commit in #25784 (before everything was rebased / updated), I still get a white screen with a Seems that SPI TFT support on STM32F4 was broken while updating for STM32H7. |
We'll need to confer with @jmz52 about those changes and see what still needs patching there. |
|
These pins are similarly configured in |
From my testing, SPI TFTs have never worked on LPC, so they should probably be removed.
I also pinged them in #25784 |
|
I'll look into it, but I can't test H7 code right now, my H7 board is out of the reach. |
SPI TFT's work on STM32H7. They're broken on STM32F4 now. |
d6c36d6 to
427040b
Compare
|
427040b fixes the SKR 2 pins similar to how I fixed the SKR V3 pins. This still doesn't work, but it'll compile now. |
The changes in #25784 affecting F4 are very few. You can try reverting just those few things (particularly in pin_PullConfig(get_GPIO_Port(STM_PORT(digitalPinToPinName(TFT_SCK_PIN))), STM_LL_GPIO_PIN(digitalPinToPinName(TFT_SCK_PIN)), GPIO_PULLDOWN);And also this was removed (although it is called as part of HAL_SPI_Init(&SPIx);Even if these were intentional removals, maybe there is something about them that helps with F4. |
|
As for SPI TFT support on LPC: I went allllll the way back to #21794 and tested the PR as-is again. MKS' TS35 V2.0 does not work on the SKR 1.3, so those changes can be dropped. I remember trying to get both BTT's and MKS' SPI TFTs working on LPC before and couldn't, so I'm not sure they ever worked. We still have |
|
CI is still failing due to 1792608. |
b9d961f to
0051698
Compare
Verified on an SKR V3.0 EZ with a BTT TFT35-SPI V1.0 and MKS TS35 V2.0
TFT supports on STM32F4 is still broken, but this will at least compile.
0051698 to
b083d8c
Compare
|
I cherry picked changes from #26052 into this PR and the
See #26052 (comment) for the fix and more info. There are still some major glitches going on, so this still isn't entirely fixed. |
b083d8c to
557fa70
Compare
557fa70 to
9e2fddd
Compare
Did we narrow down the definite culprit in this issue? Does reverting the STM32H7 stuff fix everything, or is some other set of changes involved? I made a number of TFT case changes that were not intended to change any behavior, but there could still be a typo hiding in there. |
Nope.
Yep. If I roll back to the commit prior (c483fe7) to the SPI TFT on STM32H7 (3ea87ad) commit, all these issues go away for STM32F4 (at least on the B1 SE Plus / SKR2 / BTT TFT35 SPI). If this can’t easily be fixed, I think doing a full revert on these recent SPI TFT on H7 commits and combining them in #26052 (or a new PR) for more testing would be better than breaking existing support on F4. |
Co-authored-by: Scott Lahteine <thinkyhead@users.noreply.github.com>
Co-authored-by: Scott Lahteine <thinkyhead@users.noreply.github.com>
This reverts commit fef772e.
This reverts commit fef772e.
Co-authored-by: Scott Lahteine <thinkyhead@users.noreply.github.com>
This reverts commit fef772e.
This reverts commit fef772e.
This reverts commit fef772e.
This reverts commit fef772e.
Description
Followup to #25784 since enabling an SPI TFT on an SKR 3/EZ & V2 would throw several errors about variables not being declared:
This reverts later changes in the original PR to be more like what I had originally.
Verified on an SKR V3.0 EZ with a BTT TFT35-SPI V1.0 and MKS TS35 V2.0
Requirements
SKR V3/EZ with a BTT TFT35-SPI V1.0 or MKS TS35 V2.0
Benefits
Config will compile
Configurations
#define MOTHERBOARD BOARD_BTT_SKR_V3_0or#define MOTHERBOARD BOARD_BTT_SKR_V3_0_EZwith:#define MKS_TS35_V2_0or#define BTT_TFT35_SPI_V1_0.Related Issues