-
-
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?] get warning: 'EEPROM' defined but not used [-Wunused-variable] with SKR2.0 #22243
Comments
I wasn't able to reproduce this. Can you upload your configuration files? |
Thanks for the quick response. |
The warning can be ignored. It was introduced with PR #22054. |
Thanks again for your quick response! |
Yep, it will be fine. The EEPROM.h header was added for USB support but not all parts of it are used, hence the warning. |
Then I close this issue now |
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.0.x
code?Yes, and the problem still exists.
Bug Description
When compiling with SKR 2.0 Rev. B (newest Marlin 2.0.9.1) I get the following warning:
libraries\EEPROM\src/EEPROM.h:250:20: warning: 'EEPROM' defined but not used [-Wunused-variable]
As it is my first SKR I don't know if that is an important warning.
I never got this warning using Arduino 2560 Boards like RAMPS or stock Creality Boards.
So I wonder what is the reason for this and what does this means to my compiled firmware (as it completed compiling)?
Is there a need to change some config or is this some bug like the LCD problem I had as well (#22239)?
Bug Timeline
No response
Expected behavior
I expected no warning because I didn't do changes concerning EEPROM.
Actual behavior
I got the warning... .
Steps to Reproduce
Use SKR 2.0 Rev. B board.
Version of Marlin Firmware
2.0.1.9
Printer model
Creality CR-10 V2
Electronics
BTT SKR 2.0
Add-ons
No response
Your Slicer
No response
Host Software
No response
Additional information & file uploads
No response
The text was updated successfully, but these errors were encountered: