-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
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] "always_inline function might not be inlinable": warning / [FR] STM32F103RC_creality_maple
added to Creality_V4+
#26336
Comments
I did a quick test using having said, it uses |
maple is obsolete going back to it is so wrong on so many levels. It is not the correct way to support GD32 |
Greetings from the Marlin AutoBot! Disclaimer: This is an open community project with lots of activity and limited |
just wanted to mention that I heard it might be possible to update the bootloader to accept |
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
since the recent commit 🩹 Remove extraneous 'inline'
See #26085
I receive this warning using the stmf1-maple.ini
env: STM32F103RE_creality_maple
file in question...
src/HAL/STMF1/MarlinSerial.cpp
side note (Feature Request):
env: STM32F103RC_creality_maple
should be added to the CREALITY_V4...422/427 in src/pins.h fileBug Timeline
new, since 🩹 Remove extraneous 'inline'
Expected behavior
I do not expect a warning to appear.
Actual behavior
warning when focing "inline" removed
Steps to Reproduce
STM32F103RE_creality_maple
as default_envs in platformio.iniEnder3V2Configs.zip
Version of Marlin Firmware
bugfix-2.1.x
Printer model
Voxelab Aquila
Electronics
No response
Add-ons
No response
Bed Leveling
UBL Bilinear mesh
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: