You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we are assigning roles (analog input, digital output, PWM, etc...) to pins. However, as we could switch to another MCU while keeping the MCU - board interface intact, we should declare our hardware intention with Pin names and its configuration, and then this configuration should be applied to an MCU.
Benefit of this approach is that when we select a new MCU, those configurations would be applied to new pins without making the detailed pin configuration again. This will save time and prevent human errors.
If we select the MCU first and then configure pins, the upper abstraction (pinNames vs. configuration) should be automatically separated.
The text was updated successfully, but these errors were encountered:
Currently we are assigning roles (analog input, digital output, PWM, etc...) to pins. However, as we could switch to another MCU while keeping the MCU - board interface intact, we should declare our hardware intention with Pin names and its configuration, and then this configuration should be applied to an MCU.
Benefit of this approach is that when we select a new MCU, those configurations would be applied to new pins without making the detailed pin configuration again. This will save time and prevent human errors.
If we select the MCU first and then configure pins, the upper abstraction (pinNames vs. configuration) should be automatically separated.
The text was updated successfully, but these errors were encountered: