-# [rp-pico] - Board Support for the [Raspberry Pi Pico]
+# [doa-hallonbrod] - Board Support for the [DoA Hallonbrod]
You should include this crate if you are writing code that you want to run on
-a [Raspberry Pi Pico] - the original launch PCB for the RP2040 chip.
-
-This crate includes the [rp2040-hal], but also configures each pin of the
-RP2040 chip according to how it is connected up on the Pico.
-
-[Raspberry Pi Pico]: https://www.raspberrypi.org/products/raspberry-pi-pico/
-[rp-pico]: https://github.com/rp-rs/rp-hal-boards/tree/main/boards/rp-pico
-[rp2040-hal]: https://github.com/rp-rs/rp-hal/tree/main/rp2040-hal
-[Raspberry Silicon RP2040]: https://www.raspberrypi.org/products/rp2040/
-
-## Using
-
-To use this crate, your `Cargo.toml` file should contain:
-
-```toml
-rp-pico = "0.7.0"
-```
-
-In your program, you will need to call `rp_pico::Pins::new` to create
-a new `Pins` structure. This will set up all the GPIOs for any on-board
-devices. See the [examples](./examples) folder for more details.
-
-## Examples
-
-### General Instructions
-
-To compile an example, clone the _rp-hal-boards_ repository and run:
-
-```console
-rp-hal-boards/boards/rp-pico $ cargo build --release --example <name>
-```
-
-You will get an ELF file called
-`./target/thumbv6m-none-eabi/release/examples/<name>`, where the `target`
-folder is located at the top of the _rp-hal-boards_ repository checkout. Normally
-you would also need to specify `--target=thumbv6m-none-eabi` but when
-building examples from this git repository, that is set as the default.
-
-If you want to convert the ELF file to a UF2 and automatically copy it to the
-USB drive exported by the RP2040 bootloader, simply boot your board into
-bootloader mode and run:
-
-```console
-rp-hal-boards/boards/rp-pico $ cargo run --release --example <name>
-```
-
-If you get an error about not being able to find `elf2uf2-rs`, try:
-
-```console
-$ cargo install elf2uf2-rs
-```
-then try repeating the `cargo run` command above.
-
-### From Scratch
-
-To start a basic project from scratch, create a project using `cargo new project-name`. Within the
-project directory, run `cargo add rp-pico`, `cargo add cortex-m-rt`, and `cargo add panic-halt`. The
-first command will this HAL (Hardware Abstraction Layer), the second is required for the `#[entry]` macro, and _panic-halt_ creates a simple panic function, which just halts.
-
-You'll also need to copy the cargo config file from the [repo](https://github.com/rp-rs/rp-hal-boards/blob/main/.cargo/config). It specifies the target and optimizing flags to the linker. You'll also need to copy [_memory.x_](https://github.com/rp-rs/rp-hal-boards/blob/main/memory.x) to your project root. This file tells the linker the flash and RAM layout, so it won't clobber the bootloader or write to an out of bounds memory address.
-
-The simplest working example, which does nothing except loop forever, is:
-
-```ignore
-#![no_std]
-#![no_main]
-use rp_pico::entry;
-use panic_halt as _;
-#[entry]
-fn see_doesnt_have_to_be_called_main() -> ! {
- loop {}
-}
-```
-
-It can be placed in _/src/main.rs_.
-
-You can use `cargo run` to compile and install it.
-**Note**: You won't see any activity since this program does nothing. You can use the examples provided
-to add more functionality.
-### [pico_blinky](./examples/pico_blinky.rs)
-
-Flashes the Pico's on-board LED on and off.
-
-### [pico_gpio_in_out](./examples/pico_gpio_in_out.rs)
-
-Reads a push button attached to GPIO 15 and drives the on-board LED to match it (i.e. on when pressed, off when not pressed).
-
-### [pico_rtic](./examples/pico_rtic.rs)
-
-Demonstrates the use of the [Real-Time Interrupt-driven Concurrency Framework] on the Raspberry Pi Pico.
-
-[Real-Time Interrupt-driven Concurrency Framework]: https://rtic.rs
-
-### [pico_countdown_blinky](./examples/pico_countdown_blinky.rs)
-
-Another LED blinking example, but using a Timer in count-down mode.
-
-### [pico_pwm_blink](./examples/pico_pwm_blink.rs)
-
-Puts out an analog 'triangle wave' on GPIO 25, using the PWM hardware.
-
-### [pico_pwm_servo](./examples/pico_pwm_servo.rs)
-
-Demonstrates handling a micro servo, using the PWM hardware.
-
-### [pico_usb_serial](./examples/pico_usb_serial.rs)
-
-Creates a USB Serial device on a Pico board.
-
-The USB Serial device will print `HelloWorld` on start-up, and then echo any
-incoming characters - except that any lower-case ASCII characters are
-converted to the upper-case equivalent.
-
-### [pico_usb_serial_interrupt](./examples/pico_usb_serial_interrupt.rs)
-
-Creates a USB Serial device on a Pico board, but demonstrating handling
-interrupts when USB data arrives.
-
-### [pico_usb_twitchy_mouse](./examples/pico_usb_twitchy_mouse.rs)
-
-Demonstrates emulating a USB Human Input Device (HID) Mouse. The mouse
-cursor will jiggle up and down.
-
-### [pico_spi_sd_card](./examples/pico_spi_sd_card.rs)
-
-Example that shows how to use the
-[embedded_sdmmc crate](https://github.com/rust-embedded-community/embedded-sdmmc-rs)
-with the Raspberry Pi Pico.
-
-## Contributing
-
-Contributions are what make the open source community such an amazing place to
-be learn, inspire, and create. Any contributions you make are **greatly
-appreciated**.
-
-The steps are:
-
-1. Fork the Project by clicking the 'Fork' button at the top of the page.
-2. Create your Feature Branch (`git checkout -b feature/AmazingFeature`)
-3. Make some changes to the code or documentation.
-4. Commit your Changes (`git commit -m 'Add some AmazingFeature'`)
-5. Push to the Feature Branch (`git push origin feature/AmazingFeature`)
-6. Create a [New Pull Request](https://github.com/rp-rs/rp-hal-boards/pulls)
-7. An admin will review the Pull Request and discuss any changes that may be required.
-8. Once everyone is happy, the Pull Request can be merged by an admin, and your work is part of our project!
-
-## Code of Conduct
-
-Contribution to this crate is organized under the terms of the [Rust Code of
-Conduct][CoC], and the maintainer of this crate, the [rp-rs team], promises
-to intervene to uphold that code of conduct.
-
-[CoC]: CODE_OF_CONDUCT.md
-[rp-rs team]: https://github.com/orgs/rp-rs/teams/rp-rs
-
-## License
-
-The contents of this repository are dual-licensed under the _MIT OR Apache
-2.0_ License. That means you can choose either the MIT license or the
-Apache-2.0 license when you re-use this code. See `MIT` or `APACHE2.0` for more
-information on each specific license.
-
-Any submissions to this project (e.g. as Pull Requests) must be made available
-under these terms.
+a [DoA Hallonbrod].
name: kb_c8
},
- /// GPIO 10 is connected to keyboard :
+ /// GPIO 10 is connected to keyboard column 7
Gpio10 {
name: kb_c7,
},
- /// GPIO 11 is connected to keyboard :
+ /// GPIO 11 is connected to keyboard column 6
Gpio11 {
name: kb_c6,
},
- /// GPIO 12 is connected to keyboard :
+ /// GPIO 12 is connected to keyboard column 5
Gpio12 {
name: kb_c5,
},
- /// GPIO 13 is connected to keyboard :
+ /// GPIO 13 is connected to keyboard column 4
Gpio13 {
name: kb_c4,
},
- /// GPIO 14 is connected to keyboard :
+ /// GPIO 14 is connected to keyboard column 3
Gpio14 {
name: kb_c3,
},
- /// GPIO 15 is connected to keyboard :
+ /// GPIO 15 is connected to keyboard column 2
Gpio15 {
name: kb_c2,
},
- /// GPIO 16 is connected to keyboard :
+ /// GPIO 16 is connected to keyboard column 1
Gpio16 {
name: kb_c1,
},
- /// GPIO 17 is connected to keyboard :
+ /// GPIO 17 is connected to keyboard row 9
Gpio17 {
- name: kb_r9,
+ name: kb_r9,
},
- /// GPIO 18 is connected to keyboard :
+ /// GPIO 18 is connected to keyboard row 8
Gpio18 {
- name: kb_r8,
+ name: kb_r8,
},
- /// GPIO 19 is connected to keyboard :
+ /// GPIO 19 is connected to keyboard row 7
Gpio19 {
- name: kb_r7,
+ name: kb_r7,
},
- /// GPIO 20 is connected to keyboard :
+ /// GPIO 20 is connected to keyboard row 6
Gpio20 {
- name: kb_r6,
+ name: kb_r6,
},
- /// GPIO 21 is connected to keyboard :
+ /// GPIO 21 is connected to keyboard row 5
Gpio21 {
- name: kb_r5,
+ name: kb_r5,
},
- /// GPIO 22 is connected to keyboard :
+ /// GPIO 22 is connected to keyboard row 4
Gpio22 {
name: kb_r4,
},