-
-
Notifications
You must be signed in to change notification settings - Fork 19.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Marlin 2.1.x won't build with BTT_TFT35_SPI_V1_0 after using BigTreeTech repository instructions #26421
Comments
BigTreetech's TFT35 V3.0 is not a TFT35 SPI V1.0. They are standalone computers running their own firmware / G-code senders that talk via serial and emulate Disable |
This Issue Queue is for Marlin bug reports and development-related issues, and we prefer not to handle user-support questions here. (As noted on this page.) For best results getting help with configuration and troubleshooting, please use the following resources:
After seeking help from the community, if the consensus points to a bug in Marlin, then you should post a bug report. |
Thank you for the quick response. I did not see this step as it was in the "marlin-mode" segment of the table of contents, which seems vaguely labeled for people who don't know what marlin emulation is. Regarding support, I understand it takes time to respond and these are not priorities on the team's radar. I will refrain from posting further and take to discord it becomes more complex. I implore you to take one more look for me please. I enabled
Kind regards |
After changing the display type from Linking .pio/build/LPC1769/firmware.elf
Building .pio/build/LPC1769/firmware.bin
Checking size .pio/build/LPC1769/firmware.elf
Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
RAM: [==== ] 43.7% (used 14312 bytes from 32736 bytes)
Flash: [==== ] 42.6% (used 202332 bytes from 475136 bytes)
============================================== [SUCCESS] Took 38.80 seconds ==============================================
Environment Status Duration
------------- -------- ------------
LPC1769 SUCCESS 00:00:38.796
============================================== 1 succeeded in 00:00:38.796 ==============================================
* Terminal will be reused by tasks, press any key to close it. As ellensp stated above, please use the linked resources for further troubleshooting. |
Odd! I tried again this morning and now it compiled. I think VSCode and platformio got closed down at one point and I had to reinit the IDE. It's possible platformio did not configure itself all the way properly when I reopened the project. Thank you again. You both have been great help 🙏 |
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. |
Did you test the latest
bugfix-2.1.x
code?Yes, and the problem still exists.
Bug Description
I have a BTT SKR 1.4 Turbo motherboard and a TFT3.5 v3.0 (non-E variant) touch screen display. I am trying to build Marlin 2.1.x (latest) branch for production. There are many required options needed according to the main bigtreetech repository found here. I've followed these instructions, uncommented the
BTT_TFT35_SPI_V1_0
and I get the following compiler errors:tft_spi.cpp
tft_spi.h
I've double checked that I did not skip over any options that are required as per instructions, and prior to trying to setup the LCD, I could build the firmware without all the display and required options enabled. Please see this link for archive of firmware configuration. its on gdrive because github won't allow <25mb.
Kind regards
Bug Timeline
No response
Expected behavior
No response
Actual behavior
No response
Steps to Reproduce
No response
Version of Marlin Firmware
2.1.x
Printer model
No response
Electronics
No response
LCD/Controller
No response
Other add-ons
No response
Bed Leveling
None
Your Slicer
None
Host Software
None
Don't forget to include
Configuration.h
andConfiguration_adv.h
.Additional information & file uploads
No response
The text was updated successfully, but these errors were encountered: