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
I think it makes sense to move towards merging board crates similar to what we're doing with HAL crates in #94. In specific, I want to create a single arduino-hal crate with features for the specific devices. The goal should be to provide an API that allows very easily switching from one board to another. This means we should abstract all board-specific details into a common layer, as far as that is reasonably possible.
The text was updated successfully, but these errors were encountered:
Create a unified crate for all arduino boards, to combat code
duplication in the current design. As a start, add very basic support
for Arduino Uno.
Ref: #117
Create a unified crate for all arduino boards, to combat code
duplication in the current design. As a start, add very basic support
for Arduino Uno. This includes GPIO pins and USART communication for
now.
Additionally, include a `prelude` for reexporting commonly needed traits
again.
This crate, similarly to atmega-hal, exposes its own `Peripherals`
struct. This struct uses fields and types more fitting for the selected
board. For example, the `pins` field has subfields for each of the
boards external pins, named appropriately instead of relying on the MCU
pin names.
Ref: #117
I think it makes sense to move towards merging board crates similar to what we're doing with HAL crates in #94. In specific, I want to create a single
arduino-hal
crate with features for the specific devices. The goal should be to provide an API that allows very easily switching from one board to another. This means we should abstract all board-specific details into a common layer, as far as that is reasonably possible.The text was updated successfully, but these errors were encountered: