-
-
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] Anycubic Predator config based on the example stuck on Status screen and doesn't continue to info screen #19691
Comments
@NuClearArrow112 I posted a pull request to fix this yesterday, but closed it because it overlaps with other TFT work that is in-progress. You can use the change from this closed PR to fix that read_buttons warning for now. It will be fixed in |
So the solution is patience. Well, I have a lot of that. Thank you very much! |
It's fixed in bugfix. @NuClearArrow112 can you test it? Note that the Configuration got updated! Thanks! |
Still has the following warnings: In file included from Marlin\src\lcd\tft_io\tft_io.cpp:30:0: C:.platformio\packages\framework-arduinoststm32-maple\STM32F1\libraries\STM32ADC\src\utility\util_adc.c:10:30: warning: 'adc_result' initialized and declared 'extern' C:.platformio\packages\framework-arduinoststm32-maple\STM32F1\libraries\FreeRTOS701\utility\port.c: In function 'xPortStartScheduler': HOWEVER, it works like a charm, I tested the TFT rotation 180° as well, no problems there either. #define XPT2046_X_CALIBRATION 12316 But I can rotate the whole display physically, so problem solved. Thanks. |
Try this: #19710 |
You will also need the change from this PR (in the config repo) for the Predator example: I haven't actually tested that configuration change. but at least it compiles. Feedback about whether or not it works is welcome. |
This issue has been silent, so I am presuming it has been fixed. We have another Predator user who said there was still another issue and added a new PR to fix the screen rotation: Since it seems the only outstanding issue was screen rotation, I'm presuming the reported issue here is resolved, and will close this. |
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. |
#3766 # Bug Description
I downloaded the latest 2.0.7.1 bugfix branch and the bugfix example configurations. I made some minor modifications to configuration.h and configuration.h also added a custom bootscreen (not mine). I used an up to date VS Code with Auto Build Marlin. I was able to successfully compile but with these (I guess) warnings (yellow lines):
C:.platformio\packages\framework-arduinoststm32-maple\STM32F1\libraries\STM32ADC\src\utility\util_adc.c:10:30: warning: 'adc_result' initialized and declared 'extern' extern volatile unsigned int adc_result = 0;
C:.platformio\packages\framework-arduinoststm32-maple\STM32F1\libraries\FreeRTOS701\utility\port.c: In function 'xPortStartScheduler':
C:.platformio\packages\framework-arduinoststm32-maple\STM32F1\libraries\FreeRTOS701\utility\port.c:178:2: warning: implicit declaration of function 'systick_attach_ca
.pio/build/trigorilla_pro/src/src/MarlinCore.cpp.o: In function
se.pio/build/trigorilla_pro/src/src/MarlinCore.cpp.o: In function
setup()':C:\Marlin 2.0.7.1 Anycubic Predator/Marlin\src/MarlinCore.cpp:1094: warning: undefined reference to
TouchButtons::init()' .pio/build/trigorilla_pro/src/src/lcd/ultralcd.cpp.o: In function
MarlinUI::update()':C:\Marlin 2.0.7.1 Anycubic Predator/Marlin\src\lcd/ultralcd.cpp:888: warning: undefined reference to `TouchButtons::read_buttons()'
I tried to upload it to the board, and that was successfull as well, custom bootscreen worked, status screen worked, but it did not continue the info screen. The touchscreen doesn't work. I tried to connect to it with Pronterface but that didn't work. Please hep me, I have absolutely what did I do wrong.
My Configurations
bug submit.zip
Expected behavior:
Marlin boots and show the info screen after the custom bootscreen and status screen
Actual behavior:
Stuck on the status screen, the touchscreen doesn't work, cannot communicate with it via USB.
The text was updated successfully, but these errors were encountered: