Compare commits

..

No commits in common. "main" and "v0.4.0" have entirely different histories.
main ... v0.4.0

4 changed files with 13 additions and 11 deletions

View File

@ -16,9 +16,11 @@ jobs:
override: true
- uses: actions-rs/cargo@v1
with:
use-cross: true
command: check
- uses: actions-rs/cargo@v1
with:
use-cross: true
command: check
args: --examples
@ -52,6 +54,7 @@ jobs:
- run: rustup component add clippy
- uses: actions-rs/cargo@v1
with:
use-cross: true
command: clippy
args: -- -D warnings

View File

@ -11,23 +11,23 @@ keywords = ["no-std", "reb1", "cortex-m", "vorago", "va108xx"]
categories = ["aerospace", "embedded", "no-std", "hardware-support"]
[dependencies]
cortex-m = "0.7"
cortex-m-rt = "0.7"
cortex-m = "0.7.5"
cortex-m-rt = "0.7.1"
embedded-hal = "0.2.7"
dummy-pin = "0.1"
max116xx-10bit = "0.2"
dummy-pin = "0.1.1"
max116xx-10bit = "0.2.1"
[dependencies.va108xx-hal]
version = "0.5"
version = "0.5.1"
features = ["rt"]
[features]
rt = ["va108xx-hal/rt"]
[dev-dependencies]
cortex-m-rtic = "1.1"
cortex-m-rtic = "1.1.2"
panic-halt = "0.2"
nb = "1"
nb = "1.0.0"
[dev-dependencies.rtt-target]
version = "0.3"

View File

@ -58,9 +58,8 @@ A `jlink.gdb` file is provided to allow flashing of the board from the command l
## Debugging with VS Code
The REB1 board features an on-board JTAG, so all that is required to debug the board is a
Micro-USB cable.
The REB1 board features an on-board JTAG, so all that is required to flash the board is a
Micro-USB cable and an
You can debug applications on the REB1 board with a graphical user interface using VS Code with
the [`Cortex-Debug` plugin](https://marketplace.visualstudio.com/items?itemName=marus25.cortex-debug).

View File

@ -21,7 +21,7 @@ pub struct Adt75TempSensor {
current_reg: RegAddresses,
}
#[derive(PartialEq, Eq, Debug, Copy, Clone)]
#[derive(PartialEq, Debug, Copy, Clone)]
pub enum RegAddresses {
Temperature = 0x00,
Configuration = 0x01,