-
Notifications
You must be signed in to change notification settings - Fork 960
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
[Nucleo L432KC] USER_BTN
is a misleading alias for pin D9
#1726
Comments
Hi @zfields ,
Maybe you are talking about swan board which has accelerometer ? |
Hi, Then after this PR #1091 it has been changed: So the only things we can do is to set it as
|
Where exactly is
I am blown away by this. Using the sketch I provided above with the Nucleo L432KC, the LED, I guess I am proposing that If I'm correct about an onboard accelerometer with an interrupt tied to |
Ther is no accelerometer or sensor on this board. I guess you touch the PA8 pin then it detects a change. |
For sure, no accelerator on the board. |
I found this on the internet and it appears to be correct (at least with regard to So,
I disagree. Literally, this exact situation led me to create this issue on your repository.
While writing this I have discovered the source of my spurious interrupt events. I originally used |
USER_BTN
is misleading name for accelerometer inputUSER_BTN
is misleading alias for pin D9
USER_BTN
is misleading alias for pin D9
USER_BTN
is misleading alias for pin D9
USER_BTN
is misleading alias for pin D9
USER_BTN
is a misleading alias for pin D9
The root cause of this issue, is not the wrong definition of USER_BTN, |
Well, pin This issue will continue to present this issue for anyone who is porting an application to Nucleo L432KC from a different board (e.g. Swan R5) where
|
Describe the bug
There is only one button on the Nucleo L432KC, yet
USER_BTN
is defined in the variant file.Based on my tinkering, I would say the
USER_BTN
is "pressed" by triggering the accelerometer. While I can see this as a handy feature, I think it is very misleading to call itUSER_BTN
, instead ofACCEL_PIN
(or something of that nature).To Reproduce
Complete source code which can be used to reproduce the issue. Please try to be as generic as possible (no extra code, extra hardware,...)
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
From the Product Overview Page:
![image](https://user-images.githubusercontent.com/2801887/170253128-6b716470-de26-470b-ac66-3c9f1c0e86f4.png)
Desktop (please complete the following information):
Board (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: