-
Notifications
You must be signed in to change notification settings - Fork 71
Make the M3 example work with Rust stable toolchain #91
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
base: master
Are you sure you want to change the base?
Conversation
b952c1e
to
2ac8548
Compare
env: | ||
RUSTFLAGS: -D warnings # Warnings disabled only in CI | ||
# env: | ||
# RUSTFLAGS: -D warnings # Warnings disabled only in CI |
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.
What is the reason to re-enable warnings?
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.
Because there is no warning now, I think enabling it is better.
key: ${{ runner.os }}-${{ runner.arch }} | ||
- name: Install Rust | ||
uses: dtolnay/rust-toolchain@nightly | ||
uses: dtolnay/rust-toolchain@stable |
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 see this PR also has changes included in the other PR. I'll add my comments from the other PR here in case it makes sense to just merge this one.
It looks like this is changing the overall build to be stable, not the examples. I'm not sure if it makes sense to switch the whole project over to stable at this time. If the goal is to build only some examples with the stable toolchain, maybe it makes sense to make a copy of the examples section that runs only the ones that work on stable?
// delay_n(555); | ||
} | ||
unsafe fn HardFault(_ef: &ExceptionFrame) -> ! { | ||
// Blink 3 times long when exception occures |
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.
Is the comment still correct? I don't see anything that would blink now.
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 deleted the comment, the same as M4. And the function set_led()
is not a very good example. I don't think we should encourage implementation like that.
The STM32L1 crate is too old, so I use F1 instead. I have debugged it, and it works well.
Depends on #90
resolve #66