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

Check that #define-d PIN combinations make sense at compile-time #204

Closed
lurch opened this issue Mar 1, 2021 · 1 comment · Fixed by #1724
Closed

Check that #define-d PIN combinations make sense at compile-time #204

lurch opened this issue Mar 1, 2021 · 1 comment · Fixed by #1724
Milestone

Comments

@lurch
Copy link
Contributor

lurch commented Mar 1, 2021

(as initially suggested in #192)

It might be nice to have a compile-time #error if you give an invalid combination of UART_DEFAULT settings? e.g. setting {PICO_DEFAULT_UART=0, PICO_DEFAULT_UART_TX_PIN=13} (invalid because GPIO13 is UART0 RX) or {PICO_DEFAULT_UART=1, PICO_DEFAULT_UART_TX_PIN=0} (invalid because GPIO0 is UART0 TX).
(with similar things being done for I2C and SPI pins too)

@kilograham
Copy link
Contributor

#1724 has been merged into develop

@kilograham kilograham modified the milestones: 1.8.0, 1.6.0 Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants