-
Notifications
You must be signed in to change notification settings - Fork 119
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
Fix forward declaration of HardwareSerial for megaAVR architecture #2006
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fixtures are not updated, but otherwise LGTM
ec12240
to
11754af
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder why workspace/big-patch/__fixtures__/arduino.cpp
has changed the node order (is it flanky?), but what’s about the PR itself:
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, no, there’s a better way. Wait for a minute, I’ll explain. For now, I’m vetoing the merge
Take a look at the core used by Nano Every (https://github.com/arduino/ArduinoCore-megaavr). Namely, to the file https://github.com/arduino/ArduinoCore-megaavr/blob/master/cores/arduino/UART.h. See: #include "api/HardwareSerial.h"
using namespace arduino; What the
Go there. Read:
Whoa! Some classic cores already use the new API wich has So the proper way of fixing the issue would be |
11754af
to
23f6207
Compare
23f6207
to
45381b4
Compare
@nkrkv done! |
The fixtures do not match |
a94ccce
to
b3f2ec0
Compare
b3f2ec0
to
9d9c65f
Compare
…no:megaavr architecture
9d9c65f
to
2eb72f6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There is no issue.
The problem was reported on the forum: https://forum.xod.io/t/nano-every-upload-issue/4198