-
-
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] TOUCH_UI_FTDI_EVE Error on 32 Bit boards and the newest bugfixes #16534
Comments
All those pastebins posts and not a one example config file for us to try and replicate this with... |
i will add example files . Configuration_advSKR PRO_Bugfix.zip i will add the other configs in a few hours. |
config files are the first requirement, its also listed in the issue template if you read that one :-/ |
just tried Ramps1.4 + MMU2 + TOUCH_UI_FTDI_EVE (+min requirements, EXTRUDERS 5, NOZZLE_PARK_FEATURE, LCD_HAOYU_FT800CB , OTHER_PIN_LAYOUT and ADVANCED_PAUSE_FEATURE) and it compiled without issues. But BOARD_BIGTREE_SKR_V1_3, after adjusted MMU2_SERIAL compile fails with the same error 'strcat_P' was not declared in this scope. BIGTREE_SKR_PRO with your configs also gives same error you posted "no matching function for call to 'min(int, uint8_t&)'" The last two issue have nothing to do with MMU2 just TOUCH_UI_FTDI_EVE on those boards. |
strange it wont work on my config with ramps. With wich branch did you compile succesfully any idea how to fix it for skr pro |
I tried with an SKR 1.3/ |
i hope the filenames are not confusing Confi_2.0.x_fysetcS6_NoSucces.zip Confi2.0.x_ramps_withMMu2NoSucces.zip |
did you received already your ftdi display ? i think i read in a post you had ordered one |
I picked up a 5" FTDI EVE FT810/800x480 TFT and that's what I was trying to get working a while ago. I don't remember the specific errors, but pins were fully defined. |
also from HAOYU? did you tried it with a arduino and ramps. With ramps compiling is succesfully |
I managed to get SKR 1.3 and TOUCH_UI_FTDI_EVE to compile.. but can't test it. I did have to use software SPI. |
Took your "Confi_bugfix2.0.x_ramps_noSucces.zip" and it compiles fine with a few warnings. Edit: nope editor switched back to stable.. I see the error now. |
Confi2.0.x_ramps_withMMu2NoSucces.zip does not compile. You also enabled BABYSTEPPING. and that is causes it not to compile. This seems to be a bug in src/lcd/extensible_ui/lib/ftdi_eve_touch_ui/screens/nudge_nozzle_screen.cpp line 75 should be "#if HOTENDS > 1" not "#if EXTRUDERS > 1" |
regarding TOUCH_UI_FTDI_EVE on lpc1768 (eg skr 1.3).
It will now compile, but I cant test it (I don't have this display :( ) |
I'll see if I can break out the screen tomorrow and test on an SKR 1.3/1.4. Thanks! |
With wich branch did you use test bugfixes or stable?
I hope my Display arrives in 2 or 3 weeks. |
@TB1405 "With wich branch did you use test bugfixes or stable?" The wrong one... stable. sigh... I need new glasses.. |
As "punishment" for my blindness I have tracked down fixed the issue with bugfix not compiling with ftdi_eve_touch_ui. src/lcd/extensible_ui/lib/ftdi_eve_touch_ui/marlin_events.cpp is missing a new event OnPidTuning |
@ellensp thank you :) compiling with skr does now also works. |
Got TOUCH_UI_FTDI_EVE to compile on BOARD_BIGTREE_SKR_PRO_V1_1 It now compiles and for both software and hardware SPI ( CLCD_USE_SOFT_SPI defined or not) |
@ellensp For fysetc S6 i got a eeprom error but is also without #define TOUCH_UI_FTDI_EVE i think that is a problem with my branch i tried also to compile with #define MMU2_MENUS without succes but i think that isnt supported yet in combination with FTDI_eve. |
Compiling & flashing an SKR 1.4 with |
@thisiskeithb maybe you could try it with a example code on a arduino and example from the eve libary. If it wont work the Display is probably defective |
It doesn't even light up with 5v applied, so it's probably DOA. Too bad I waited so long to test it because now I can't get a refund. Oh well! |
@thisiskeithb oh thats bad. |
Yes |
There is a online chat for techsupport on the website, if you explaine the Situation maybe they will send one again. |
@TB1405 so still a bit left on this one before its solved? |
@boelle None of us have a working screen to test on yet. |
@marciot: Have you tried |
i had now ordered a FTDI EVE FT800 Display 4,3" VM800B43A-PL from germany. should arrived maybe this week. |
I got TOUCH_UI_FTDI_EVE compiling on LPC1768/9 with hardware SPI to compile. If someone wants to try it. You still need to apply #16540
In src/lcd/extensible_ui/lib/ftdi_eve_touch_ui/ftdi_eve_lib/basic/spi.cpp
In regards to SPI_MODE0 it is only referenced once in src/lcd/extensible_ui/lib/ftdi_eve_touch_ui/ftdi_eve_lib/basic/spi.cpp |
today arrived my FTDI EVE FT800 Display 4,3" VM800B43A i tried it with enabled i tried it with S6 and SKR 1.3
#endif` tomorrow I will check if it is because the VM800B35A is a 3.5 inch tft. mine is 4,3 inch. @thisiskeithb maybe your display isnt doa. if i connect mine to 5v and ground there is nothing light up. only if the control is successful it goes on |
I had hoped that was the case, but hadn't looked into it since I got sucked into another project. I'll keep watching this issue and help out when I can. |
why SPI Mode 3 i think the LPC only have SPI_0 and SPI_1 SPI_1 is used for onboard i think so. |
alright i was able to repair my old arduino mega. |
i dont if this a marlin problem or it isnt enough to set the correct resolution for the VM800B43A Display. EDIT: Okay i think it isnt a marlin problem. it doesnt matter wich one from the FTDI display i choose in the config.adv the "Release to begin screen calibration" is displayed always correct. |
EDIT: Connected now the display to my printer (using a SKR Pro) everything on the display works so far. |
i close this i opened a new issue with a more detailed description i think this wasnt only a compiling issue. |
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. |
i ordered today a 4.3" Graphical LCD Touchscreen, 480x272, SPI, FT800 from HAOYU STAR.
i tried to comlile the marlin 2.0.x and marlin 2.0.x bugfixes fromt today (11.01.2020).
Lets start with the issue on the 2.0.x branch
compiling is possible with ramps and Fysetc F6. (mega2560)
but if i activate the mmu2 feature following error message comes up
is it maybe because we have to activate 5 extruders ?
Marlin\src\lcd\extensible_ui\lib\ftdi_eve_touch_ui\screens\nudge_nozzle_screen.cpp: In static member function 'static void NudgeNozzleScreen::onRedraw(draw_mode_t)': Marlin\src\lcd\extensible_ui\lib\ftdi_eve_touch_ui\screens\nudge_nozzle_screen.cpp:76:54: error: 'getNozzleOffset_mm' was not declared in this scope format_position(str, getNozzleOffset_mm(X, E1), getNozzleOffset_mm(Y, E1), getNozzleOffset_mm(Z, E1)); ^ Compiling .pio\build\megaatmega2560\src\src\lcd\extensible_ui\lib\ftdi_eve_touch_ui\screens\screens.cpp.o *** [.pio\build\megaatmega2560\src\src\lcd\extensible_ui\lib\ftdi_eve_touch_ui\screens\nudge_nozzle_screen.cpp.o] Error 1
if i try to compile the 2.0.x branch with SKR PRO or Fysetc S6 this Error appears. (all extra features deactivatet)
https://pastebin.com/tRVjJH4e
now to the 2.0.x bugfixes branch from today. Compiling isnt possible anymore.
with ramps
https://pastebin.com/F9ZbKkgw
with skr pro
https://pastebin.com/7g7HfQtr
with skr 1.3
https://pastebin.com/uv3W4YzM
The text was updated successfully, but these errors were encountered: