Skip to content
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

Set correct number of nvic priority bits available on stm32l0xx #275

Merged
merged 1 commit into from Aug 6, 2019

Conversation

kitzin
Copy link

@kitzin kitzin commented Aug 6, 2019

I was using the stm32l0 crate with RTFM and noticed some funky behavior. The number of NVIC priority bits are two on the m0/m0+, and it was wrong in the SVD file.

Copy link
Member

@adamgreig adamgreig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, thanks!

bors r+

bors bot added a commit that referenced this pull request Aug 6, 2019
275: Set correct number of nvic priority bits available on stm32l0xx r=adamgreig a=kitzin

I was using the stm32l0 crate with RTFM and noticed some funky behavior. The number of NVIC priority bits are two on the m0/m0+, and it was wrong in the SVD file. 

Co-authored-by: Emil Kitti <emil.kitti@outlook.com>
@bors
Copy link
Contributor

bors bot commented Aug 6, 2019

Build failed

@adamgreig
Copy link
Member

hmmm.... what???

bors retry

bors bot added a commit that referenced this pull request Aug 6, 2019
275: Set correct number of nvic priority bits available on stm32l0xx r=adamgreig a=kitzin

I was using the stm32l0 crate with RTFM and noticed some funky behavior. The number of NVIC priority bits are two on the m0/m0+, and it was wrong in the SVD file. 

Co-authored-by: Emil Kitti <emil.kitti@outlook.com>
@bors
Copy link
Contributor

bors bot commented Aug 6, 2019

Build succeeded

@bors bors bot merged commit 35f2bba into stm32-rs:master Aug 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants