-
Notifications
You must be signed in to change notification settings - Fork 4
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
Pd cc bms mci changes (new boards + new fsm) #275
Conversation
13270f6
to
921ffad
Compare
state = ((val2 & 8) != 0) ? GPIO_STATE_HIGH : GPIO_STATE_LOW; | ||
gpio_set_state(&display->D2, state); | ||
// state = ((val2 & 8) != 0) ? GPIO_STATE_HIGH : GPIO_STATE_LOW; | ||
// gpio_set_state(&display->D2, state); |
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.
These need the un-remap right?
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.
yesh from what i understand debug logging uses PB7 (d2) which is already a remapped pin. Disabling the remap wont work either since those pins are used too (PA8/PA9 on datasheet). Maybe a smoke test without any logging/uart implementation would be useful to verify this? I do have a seg_display smoke but log is being initialized there. Best workaround for the future is probably asking Forest to remove that pin from the schematic so its never used again 😭
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.
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.
e34c274
to
25273b6
Compare
No description provided.