-
Notifications
You must be signed in to change notification settings - Fork 6
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
Implement remaining unblocked ADC channels #3
Comments
I'd like to suggest that you further this exercise by opening all GPIO pins and possibilities in the factory objects. |
Hey @consumr . I agree. I think it's an open question as far as how to best expose the many IO possibilities of the H7 at the patcher object level. I'm not satisfied with how it's done in the legacy patcher (there are many things in the current patcher I'm not satisfied with but simply haven't had time to address yet). In general, any pin that is not allocated for some core board function can be a simple digital IO. More complex functions are bound to particular pins, i.e. a particular physical pin has several possible functions. That mapping is defined in the H7 datasheet. The issue is exposing that complexity in a way that is understandable to people who are not necessarily familiar with the low-level firmware details. Which specific IO functions are highest priority from your perspective? |
Any updates on this? It's been quite a while now and this would be nice to have |
ok I will do a PR on this, I see how to change the objects themselves easily enough, will look into the changes to axoloti_board.c and test it out- my only real holdup is to get some pins soldered to the board and make a little proto db up. |
There are six ADC channels that should be relatively easy to add. Pins: C5, F6, F7, F8, F9, H4.
Changes needed at least in
axoloti_board.c
and in the factory analog in object.The text was updated successfully, but these errors were encountered: