[INFO] fetching crate embassy-dt-stm32 0.3.0...
[INFO] checking embassy-dt-stm32-0.3.0 against 3154cc1a3e6424e44f438a95007d043ed5ceaaf6+rustflags=-Znext-solver=coherence for pr-133502-30
[INFO] extracting crate embassy-dt-stm32 0.3.0 into /workspace/builds/worker-5-tc1/source
[INFO] started tweaking crates.io crate embassy-dt-stm32 0.3.0
[INFO] removed 0 missing examples
[INFO] finished tweaking crates.io crate embassy-dt-stm32 0.3.0
[INFO] tweaked toml for crates.io crate embassy-dt-stm32 0.3.0 written to /workspace/builds/worker-5-tc1/source/Cargo.toml
[INFO] validating manifest of crates.io crate embassy-dt-stm32 0.3.0 on toolchain 3154cc1a3e6424e44f438a95007d043ed5ceaaf6
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+3154cc1a3e6424e44f438a95007d043ed5ceaaf6" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate crates.io crate embassy-dt-stm32 0.3.0 already has a lockfile, it will not be regenerated
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+3154cc1a3e6424e44f438a95007d043ed5ceaaf6" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded panic-probe v1.0.0
[INFO] [stderr]   Downloaded usbd-hid-macros v0.10.0
[INFO] [stderr]   Downloaded usbd-hid v0.10.0
[INFO] [stderr]   Downloaded usbd-hid-descriptors v0.10.0
[INFO] [stderr]   Downloaded bitfield v0.14.0
[INFO] [stderr]   Downloaded embassy-executor v0.10.0
[INFO] [stderr]   Downloaded embassy-executor-timer-queue v0.1.0
[INFO] [stderr]   Downloaded embassy-net-driver-channel v0.4.0
[INFO] [stderr]   Downloaded stm32-hrtim v0.2.0
[INFO] [stderr]   Downloaded sdio-host v0.9.0
[INFO] [stderr]   Downloaded block-device-driver v0.2.0
[INFO] [stderr]   Downloaded encode_unicode v0.3.6
[INFO] [stderr]   Downloaded embassy-net-driver v0.2.0
[INFO] [stderr]   Downloaded trait-set v0.3.0
[INFO] [stderr]   Downloaded embassy-time-queue-utils v0.3.2
[INFO] [stderr]   Downloaded embassy-executor-macros v0.8.0
[INFO] [stderr]   Downloaded ssmarshal v1.0.0
[INFO] [stderr]   Downloaded embassy-hal-internal v0.5.0
[INFO] [stderr]   Downloaded embassy-dt v0.3.0
[INFO] [stderr]   Downloaded defmt-rtt v1.3.0
[INFO] [stderr]   Downloaded stm32-fmc v0.4.0
[INFO] [stderr]   Downloaded embassy-usb v0.6.0
[INFO] [stderr]   Downloaded embassy-dt-macros v0.3.0
[INFO] [stderr]   Downloaded cortex-m v0.7.7
[INFO] [stderr]   Downloaded embassy-stm32 v0.6.0
[INFO] [stderr]   Downloaded stm32g4 v0.16.0
[INFO] [stderr]   Downloaded stm32-metapac v21.0.0
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-m" "1610612736" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:77db811e55d90add9212f6832c23229e3de5f1c1f9905e8cb07319ea15df73ac" "sleep" "infinity", kill_on_drop: false }`
[INFO] [stdout] 3f8598805def1ff3cff6ea32c93f64ef7c89b5c2cbb1aa45adc4384e019a103a
[INFO] running `Command { std: "docker" "start" "3f8598805def1ff3cff6ea32c93f64ef7c89b5c2cbb1aa45adc4384e019a103a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "3f8598805def1ff3cff6ea32c93f64ef7c89b5c2cbb1aa45adc4384e019a103a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-w" "/opt/rustwide/workdir" "--user" "0:0" "3f8598805def1ff3cff6ea32c93f64ef7c89b5c2cbb1aa45adc4384e019a103a" "/opt/rustwide/cargo-home/bin/cargo" "+3154cc1a3e6424e44f438a95007d043ed5ceaaf6" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "3f8598805def1ff3cff6ea32c93f64ef7c89b5c2cbb1aa45adc4384e019a103a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid -Znext-solver=coherence" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-w" "/opt/rustwide/workdir" "--user" "0:0" "3f8598805def1ff3cff6ea32c93f64ef7c89b5c2cbb1aa45adc4384e019a103a" "/opt/rustwide/cargo-home/bin/cargo" "+3154cc1a3e6424e44f438a95007d043ed5ceaaf6" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stderr]    Compiling defmt v1.1.1
[INFO] [stderr]    Compiling defmt-macros v1.1.1
[INFO] [stderr]    Compiling cortex-m v0.7.7
[INFO] [stderr]     Checking nb v1.1.0
[INFO] [stderr]     Checking void v1.0.2
[INFO] [stderr]    Compiling cortex-m-rt v0.7.6
[INFO] [stderr]     Checking critical-section v1.2.0
[INFO] [stderr]    Compiling heapless v0.9.3
[INFO] [stderr]    Compiling thiserror v2.0.19
[INFO] [stderr]     Checking hash32 v0.3.1
[INFO] [stderr]    Compiling embassy-time-driver v0.2.2
[INFO] [stderr]    Compiling serde_core v1.0.229
[INFO] [stderr]     Checking futures-core v0.3.33
[INFO] [stderr]     Checking embedded-hal v1.0.0
[INFO] [stderr]    Compiling syn v2.0.119
[INFO] [stderr]    Compiling bare-metal v0.2.5
[INFO] [stderr]     Checking nb v0.1.3
[INFO] [stderr]    Compiling embassy-sync v0.8.0
[INFO] [stderr]     Checking vcell v0.1.3
[INFO] [stderr]    Compiling portable-atomic v1.14.0
[INFO] [stderr]    Compiling embedded-hal-async v1.0.0
[INFO] [stderr]     Checking volatile-register v0.2.2
[INFO] [stderr]     Checking embedded-hal v0.2.7
[INFO] [stderr]    Compiling defmt-parser v1.0.0
[INFO] [stderr]     Checking bitfield v0.13.2
[INFO] [stderr]     Checking futures-sink v0.3.33
[INFO] [stderr]    Compiling serde v1.0.229
[INFO] [stderr]    Compiling embedded-io-async v0.6.1
[INFO] [stderr]    Compiling zerocopy v0.8.55
[INFO] [stderr]    Compiling aho-corasick v1.1.4
[INFO] [stderr]    Compiling stm32-metapac v21.0.0
[INFO] [stderr]     Checking embedded-io v0.6.1
[INFO] [stderr]    Compiling ahash v0.8.12
[INFO] [stderr]    Compiling embassy-time-queue-utils v0.3.2
[INFO] [stderr]    Compiling once_cell v1.21.4
[INFO] [stderr]     Checking embassy-futures v0.1.2
[INFO] [stderr]    Compiling embassy-hal-internal v0.4.0
[INFO] [stderr]     Checking as-slice v0.2.1
[INFO] [stderr]     Checking embassy-executor-timer-queue v0.1.0
[INFO] [stderr]     Checking embedded-storage v0.3.1
[INFO] [stderr]    Compiling bitfield v0.14.0
[INFO] [stderr]    Compiling embassy-hal-internal v0.5.0
[INFO] [stderr]     Checking aligned v0.4.3
[INFO] [stderr]     Checking heapless v0.8.0
[INFO] [stderr]     Checking embedded-storage-async v0.4.1
[INFO] [stderr]    Compiling byteorder v1.5.0
[INFO] [stderr]     Checking futures-task v0.3.33
[INFO] [stderr]     Checking futures-util v0.3.33
[INFO] [stderr]    Compiling usbd-hid-descriptors v0.10.0
[INFO] [stderr]     Checking block-device-driver v0.2.0
[INFO] [stderr]    Compiling trait-set v0.3.0
[INFO] [stderr]     Checking embedded-hal-nb v1.0.0
[INFO] [stderr]     Checking stm32-fmc v0.4.0
[INFO] [stderr]     Checking embedded-can v0.4.1
[INFO] [stderr]    Compiling defmt-rtt v1.3.0
[INFO] [stderr]    Compiling embassy-usb v0.6.0
[INFO] [stderr]     Checking rand_core v0.9.5
[INFO] [stderr]     Checking bit_field v0.10.3
[INFO] [stderr]    Compiling embassy-executor v0.10.0
[INFO] [stderr]     Checking encode_unicode v0.3.6
[INFO] [stderr]     Checking sdio-host v0.9.0
[INFO] [stderr]    Compiling panic-probe v1.0.0
[INFO] [stderr]     Checking rand_core v0.6.4
[INFO] [stderr]     Checking cordyceps v0.3.5
[INFO] [stderr]     Checking usb-device v0.3.2
[INFO] [stderr]    Compiling regex-automata v0.4.16
[INFO] [stderr]     Checking ssmarshal v1.0.0
[INFO] [stderr]    Compiling darling_core v0.20.11
[INFO] [stderr]    Compiling cortex-m-rt-macros v0.7.6
[INFO] [stderr]    Compiling embassy-dt-macros v0.3.0
[INFO] [stderr]    Compiling regex v1.13.1
[INFO] [stderr]    Compiling darling_macro v0.20.11
[INFO] [stderr]    Compiling darling v0.20.11
[INFO] [stderr]    Compiling embassy-executor-macros v0.8.0
[INFO] [stderr]    Compiling defmt v0.3.100
[INFO] [stderr]     Checking embedded-io v0.7.1
[INFO] [stderr]     Checking embassy-time v0.5.1
[INFO] [stderr]     Checking embassy-net-driver v0.2.0
[INFO] [stderr]     Checking embedded-io-async v0.7.0
[INFO] [stderr]     Checking embassy-usb-driver v0.2.2
[INFO] [stderr]    Compiling hashbrown v0.13.2
[INFO] [stderr]    Compiling usbd-hid-macros v0.10.0
[INFO] [stderr]     Checking embassy-embedded-hal v0.6.0
[INFO] [stderr]     Checking embassy-usb-synopsys-otg v0.3.3
[INFO] [stderr]     Checking embassy-net-driver-channel v0.4.0
[INFO] [stderr]     Checking usbd-hid v0.10.0
[INFO] [stderr]     Checking embassy-dt v0.3.0
[INFO] [stderr]    Compiling embassy-stm32 v0.6.0
[INFO] [stderr]     Checking embassy-dt-stm32 v0.3.0 (/opt/rustwide/workdir)
[INFO] [stdout] error: unwinding panics are not supported without std
[INFO] [stdout]   |
[INFO] [stdout]   = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding
[INFO] [stdout]   = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: `#[panic_handler]` function required, but not found
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unwinding panics are not supported without std
[INFO] [stdout]   |
[INFO] [stdout]   = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding
[INFO] [stdout]   = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: `#[panic_handler]` function required, but not found
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unwinding panics are not supported without std
[INFO] [stdout]   |
[INFO] [stdout]   = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding
[INFO] [stdout]   = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: `#[panic_handler]` function required, but not found
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unwinding panics are not supported without std
[INFO] [stdout]   |
[INFO] [stdout]   = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding
[INFO] [stdout]   = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: `#[panic_handler]` function required, but not found
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unwinding panics are not supported without std
[INFO] [stdout]   |
[INFO] [stdout]   = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding
[INFO] [stdout]   = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/h723_nucleo.rs:23:1
[INFO] [stdout]    |
[INFO] [stdout] 23 | / device_tree! {
[INFO] [stdout] 24 | |     name "nucleo-h723zi";
[INFO] [stdout] 25 | |     backend stm32;
[INFO] [stdout] 26 | |     chip "stm32h723zg";
[INFO] [stdout] 27 | |     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 28 | | }
[INFO] [stdout]    | |_^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 23 - device_tree! {
[INFO] [stdout] 24 -     name "nucleo-h723zi";
[INFO] [stdout] 25 -     backend stm32;
[INFO] [stdout] 26 -     chip "stm32h723zg";
[INFO] [stdout] 27 -     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 28 - }
[INFO] [stdout] 23 + embassy_dt_stm32
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `embassy-dt-stm32` (example "h723_nucleo") due to 2 previous errors
[INFO] [stdout] error[E0433]: cannot find `PllPDiv` in `rcc`
[INFO] [stdout]   --> examples/f411_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "blackpill-f411ce";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f411ce";
[INFO] [stdout] 18 | |     from "boards/blackpill-f411.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ could not find `PllPDiv` in `rcc`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]    |
[INFO] [stdout] 14 - device_tree! {
[INFO] [stdout] 15 -     name "blackpill-f411ce";
[INFO] [stdout] 16 -     backend stm32;
[INFO] [stdout] 17 -     chip "stm32f411ce";
[INFO] [stdout] 18 -     from "boards/blackpill-f411.dts";
[INFO] [stdout] 19 - }
[INFO] [stdout] 14 + PllDiv
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] error: `#[panic_handler]` function required, but not found
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unwinding panics are not supported without std
[INFO] [stdout]   |
[INFO] [stdout]   = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding
[INFO] [stdout]   = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find `PllQDiv` in `rcc`
[INFO] [stdout]   --> examples/f411_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "blackpill-f411ce";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f411ce";
[INFO] [stdout] 18 | |     from "boards/blackpill-f411.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ could not find `PllQDiv` in `rcc`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]    |
[INFO] [stdout] 14 - device_tree! {
[INFO] [stdout] 15 -     name "blackpill-f411ce";
[INFO] [stdout] 16 -     backend stm32;
[INFO] [stdout] 17 -     chip "stm32f411ce";
[INFO] [stdout] 18 -     from "boards/blackpill-f411.dts";
[INFO] [stdout] 19 - }
[INFO] [stdout] 14 + PllDiv
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unwinding panics are not supported without std
[INFO] [stdout]   |
[INFO] [stdout]   = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding
[INFO] [stdout]   = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `embassy-dt-stm32` (example "h723_embassy_spi") due to 3 previous errors
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/h723_embassy_spi.rs:13:1
[INFO] [stdout]    |
[INFO] [stdout] 13 | / device_tree! {
[INFO] [stdout] 14 | |     name "nucleo-h723zi";
[INFO] [stdout] 15 | |     backend stm32;
[INFO] [stdout] 16 | |     chip "stm32h723zg";
[INFO] [stdout] 17 | |     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 18 | | }
[INFO] [stdout]    | |_^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 13 - device_tree! {
[INFO] [stdout] 14 -     name "nucleo-h723zi";
[INFO] [stdout] 15 -     backend stm32;
[INFO] [stdout] 16 -     chip "stm32h723zg";
[INFO] [stdout] 17 -     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 18 - }
[INFO] [stdout] 13 + embassy_dt_stm32
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find `Clk48sel` in `mux`
[INFO] [stdout]   --> examples/f411_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "blackpill-f411ce";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f411ce";
[INFO] [stdout] 18 | |     from "boards/blackpill-f411.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ could not find `Clk48sel` in `mux`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/h723_embassy_i2c.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-h723zi";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32h723zg";
[INFO] [stdout] 18 | |     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 14 - device_tree! {
[INFO] [stdout] 15 -     name "nucleo-h723zi";
[INFO] [stdout] 16 -     backend stm32;
[INFO] [stdout] 17 -     chip "stm32h723zg";
[INFO] [stdout] 18 -     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 19 - }
[INFO] [stdout] 14 + embassy_dt_stm32
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stdout] error: `#[panic_handler]` function required, but not found
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unwinding panics are not supported without std
[INFO] [stdout]   |
[INFO] [stdout]   = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding
[INFO] [stdout]   = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `embassy-dt-stm32` (example "h723_embassy_i2c") due to 3 previous errors
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/h723_embassy_i2s.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | / device_tree! {
[INFO] [stdout] 13 | |     name "nucleo-h723zi";
[INFO] [stdout] 14 | |     backend stm32;
[INFO] [stdout] 15 | |     chip "stm32h723zg";
[INFO] [stdout] 16 | |     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 17 | | }
[INFO] [stdout]    | |_^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 12 - device_tree! {
[INFO] [stdout] 13 -     name "nucleo-h723zi";
[INFO] [stdout] 14 -     backend stm32;
[INFO] [stdout] 15 -     chip "stm32h723zg";
[INFO] [stdout] 16 -     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 17 - }
[INFO] [stdout] 12 + embassy_dt_stm32
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `USB_OTG_FS` in module `::embassy_stm32::peripherals`
[INFO] [stdout]   --> examples/f411_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "blackpill-f411ce";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f411ce";
[INFO] [stdout] 18 | |     from "boards/blackpill-f411.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ not found in `::embassy_stm32::peripherals`
[INFO] [stdout]    |
[INFO] [stdout] note: similarly named struct `USB_OTG_HS` defined here
[INFO] [stdout]   --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-hal-internal-0.5.0/src/macros.rs:13:17
[INFO] [stdout]    |
[INFO] [stdout] 13 |                 pub struct $name { _private: () }
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: /opt/rustwide/target/debug/build/embassy-stm32/b185b0e296430802/out/_generated.rs:1:1
[INFO] [stdout]    |
[INFO] [stdout]  1 | embassy_hal_internal :: peripherals_definitio...DMA_CH12 , MDMA_CH13 , MDMA_CH14 , MDMA_CH15) ; ...
[INFO] [stdout]    | ---------------------------------------------...--------------------------------------------- in this macro invocation
[INFO] [stdout]    = note: this error originates in the macro `device_tree` which comes from the expansion of the macro `embassy_hal_internal::peripherals_definition` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: a struct with a similar name exists
[INFO] [stdout]    |
[INFO] [stdout] 14 - device_tree! {
[INFO] [stdout] 15 -     name "blackpill-f411ce";
[INFO] [stdout] 16 -     backend stm32;
[INFO] [stdout] 17 -     chip "stm32f411ce";
[INFO] [stdout] 18 -     from "boards/blackpill-f411.dts";
[INFO] [stdout] 19 - }
[INFO] [stdout] 14 + USB_OTG_HS
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `OTG_FS` in module `$crate::interrupt::typelevel`
[INFO] [stdout]    --> examples/f411_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "blackpill-f411ce";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32f411ce";
[INFO] [stdout]  18 | |     from "boards/blackpill-f411.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]     |
[INFO] [stdout] note: similarly named enum `OTG_HS` defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-hal-internal-0.5.0/src/interrupt.rs:105:21
[INFO] [stdout]     |
[INFO] [stdout] 105 |                     pub enum $irqs {}
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/target/debug/build/embassy-stm32/b185b0e296430802/out/_generated.rs:1:4421
[INFO] [stdout]     |
[INFO] [stdout]   1 | ... ; embassy_hal_internal :: interrupt_mod ! (WWD..., FDCAN3_IT0 , FDCAN3_IT1 , TIM23 , TIM24 ,) ; ...
[INFO] [stdout]     |       --------------------------------------------...-------------------------------------------- in this macro invocation
[INFO] [stdout]     = note: this error originates in the macro `device_tree` which comes from the expansion of the macro `embassy_hal_internal::interrupt_mod` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout]  14 - device_tree! {
[INFO] [stdout]  15 -     name "blackpill-f411ce";
[INFO] [stdout]  16 -     backend stm32;
[INFO] [stdout]  17 -     chip "stm32f411ce";
[INFO] [stdout]  18 -     from "boards/blackpill-f411.dts";
[INFO] [stdout]  19 - }
[INFO] [stdout]  14 + OTG_HS
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: `#[panic_handler]` function required, but not found
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unwinding panics are not supported without std
[INFO] [stdout]   |
[INFO] [stdout]   = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding
[INFO] [stdout]   = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `embassy-dt-stm32` (example "h723_embassy_i2s") due to 3 previous errors
[INFO] [stdout] error: `#[panic_handler]` function required, but not found
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unwinding panics are not supported without std
[INFO] [stdout]   |
[INFO] [stdout]   = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding
[INFO] [stdout]   = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: `#[panic_handler]` function required, but not found
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unwinding panics are not supported without std
[INFO] [stdout]   |
[INFO] [stdout]   = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding
[INFO] [stdout]   = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: `#[panic_handler]` function required, but not found
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unwinding panics are not supported without std
[INFO] [stdout]   |
[INFO] [stdout]   = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding
[INFO] [stdout]   = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: `#[panic_handler]` function required, but not found
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unwinding panics are not supported without std
[INFO] [stdout]   |
[INFO] [stdout]   = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding
[INFO] [stdout]   = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/h723_embassy_dac.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | / device_tree! {
[INFO] [stdout] 13 | |     name "nucleo-h723zi";
[INFO] [stdout] 14 | |     backend stm32;
[INFO] [stdout] 15 | |     chip "stm32h723zg";
[INFO] [stdout] 16 | |     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 17 | | }
[INFO] [stdout]    | |_^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 12 - device_tree! {
[INFO] [stdout] 13 -     name "nucleo-h723zi";
[INFO] [stdout] 14 -     backend stm32;
[INFO] [stdout] 15 -     chip "stm32h723zg";
[INFO] [stdout] 16 -     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 17 - }
[INFO] [stdout] 12 + embassy_dt_stm32
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/h723_embassy_usart.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | / device_tree! {
[INFO] [stdout] 13 | |     name "nucleo-h723zi";
[INFO] [stdout] 14 | |     backend stm32;
[INFO] [stdout] 15 | |     chip "stm32h723zg";
[INFO] [stdout] 16 | |     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 17 | | }
[INFO] [stdout]    | |_^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 12 - device_tree! {
[INFO] [stdout] 13 -     name "nucleo-h723zi";
[INFO] [stdout] 14 -     backend stm32;
[INFO] [stdout] 15 -     chip "stm32h723zg";
[INFO] [stdout] 16 -     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 17 - }
[INFO] [stdout] 12 + embassy_dt_stm32
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `embassy-dt-stm32` (example "h723_embassy_usart") due to 3 previous errors
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/h723_embassy_rng.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | / device_tree! {
[INFO] [stdout] 13 | |     name "nucleo-h723zi";
[INFO] [stdout] 14 | |     backend stm32;
[INFO] [stdout] 15 | |     chip "stm32h723zg";
[INFO] [stdout] 16 | |     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 17 | | }
[INFO] [stdout]    | |_^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 12 - device_tree! {
[INFO] [stdout] 13 -     name "nucleo-h723zi";
[INFO] [stdout] 14 -     backend stm32;
[INFO] [stdout] 15 -     chip "stm32h723zg";
[INFO] [stdout] 16 -     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 17 - }
[INFO] [stdout] 12 + embassy_dt_stm32
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `USB` in module `::embassy_stm32::peripherals`
[INFO] [stdout]   --> examples/f072_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-f072rb";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f072rb";
[INFO] [stdout] 18 | |     from "boards/nucleo-f072rb.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ not found in `::embassy_stm32::peripherals`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `DMA1_CHANNEL4_5_6_7` in module `$crate::interrupt::typelevel`
[INFO] [stdout]   --> examples/f072_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-f072rb";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f072rb";
[INFO] [stdout] 18 | |     from "boards/nucleo-f072rb.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `I2C1` in module `$crate::interrupt::typelevel`
[INFO] [stdout]   --> examples/f072_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-f072rb";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f072rb";
[INFO] [stdout] 18 | |     from "boards/nucleo-f072rb.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: consider importing this struct
[INFO] [stdout]    |
[INFO] [stdout]  7 + use embassy_stm32::peripherals::I2C1;
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `DMA1_CHANNEL2_3` in module `$crate::interrupt::typelevel`
[INFO] [stdout]    --> examples/f072_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "nucleo-f072rb";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32f072rb";
[INFO] [stdout]  18 | |     from "boards/nucleo-f072rb.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]     |
[INFO] [stdout] note: similarly named enum `BDMA_CHANNEL2` defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-hal-internal-0.5.0/src/interrupt.rs:105:21
[INFO] [stdout]     |
[INFO] [stdout] 105 |                     pub enum $irqs {}
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/target/debug/build/embassy-stm32/b185b0e296430802/out/_generated.rs:1:4421
[INFO] [stdout]     |
[INFO] [stdout]   1 | ... ; embassy_hal_internal :: interrupt_mod ! (WWD..., FDCAN3_IT0 , FDCAN3_IT1 , TIM23 , TIM24 ,) ; ...
[INFO] [stdout]     |       --------------------------------------------...-------------------------------------------- in this macro invocation
[INFO] [stdout]     = note: this error originates in the macro `device_tree` which comes from the expansion of the macro `embassy_hal_internal::interrupt_mod` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout]  14 - device_tree! {
[INFO] [stdout]  15 -     name "nucleo-f072rb";
[INFO] [stdout]  16 -     backend stm32;
[INFO] [stdout]  17 -     chip "stm32f072rb";
[INFO] [stdout]  18 -     from "boards/nucleo-f072rb.dts";
[INFO] [stdout]  19 - }
[INFO] [stdout]  14 + BDMA_CHANNEL2
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0061]: this function takes 2 arguments but 1 argument was supplied
[INFO] [stdout]   --> examples/f411_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "blackpill-f411ce";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f411ce";
[INFO] [stdout] 18 | |     from "boards/blackpill-f411.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ argument #2 of type `embassy_stm32::crc::Config` is missing
[INFO] [stdout]    |
[INFO] [stdout] note: associated function defined here
[INFO] [stdout]   --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-stm32-0.6.0/src/crc/v2v3.rs:81:12
[INFO] [stdout]    |
[INFO] [stdout] 81 |     pub fn new(peripheral: Peri<'d, CRC>, config: Config) -> Self {
[INFO] [stdout]    |            ^^^
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `EXTI4_15` in module `::embassy_stm32::interrupt::typelevel`
[INFO] [stdout]    --> examples/f072_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "nucleo-f072rb";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32f072rb";
[INFO] [stdout]  18 | |     from "boards/nucleo-f072rb.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ not found in `::embassy_stm32::interrupt::typelevel`
[INFO] [stdout]     |
[INFO] [stdout] note: similarly named enum `EXTI9_5` defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-hal-internal-0.5.0/src/interrupt.rs:105:21
[INFO] [stdout]     |
[INFO] [stdout] 105 |                     pub enum $irqs {}
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/target/debug/build/embassy-stm32/b185b0e296430802/out/_generated.rs:1:4421
[INFO] [stdout]     |
[INFO] [stdout]   1 | ... ; embassy_hal_internal :: interrupt_mod ! (WWD..., FDCAN3_IT0 , FDCAN3_IT1 , TIM23 , TIM24 ,) ; ...
[INFO] [stdout]     |       --------------------------------------------...-------------------------------------------- in this macro invocation
[INFO] [stdout]     = note: this error originates in the macro `device_tree` which comes from the expansion of the macro `embassy_hal_internal::interrupt_mod` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout]  14 - device_tree! {
[INFO] [stdout]  15 -     name "nucleo-f072rb";
[INFO] [stdout]  16 -     backend stm32;
[INFO] [stdout]  17 -     chip "stm32f072rb";
[INFO] [stdout]  18 -     from "boards/nucleo-f072rb.dts";
[INFO] [stdout]  19 - }
[INFO] [stdout]  14 + EXTI9_5
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `EXTI4_15` in module `$crate::interrupt::typelevel`
[INFO] [stdout]    --> examples/f072_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "nucleo-f072rb";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32f072rb";
[INFO] [stdout]  18 | |     from "boards/nucleo-f072rb.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]     |
[INFO] [stdout] note: similarly named enum `EXTI9_5` defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-hal-internal-0.5.0/src/interrupt.rs:105:21
[INFO] [stdout]     |
[INFO] [stdout] 105 |                     pub enum $irqs {}
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/target/debug/build/embassy-stm32/b185b0e296430802/out/_generated.rs:1:4421
[INFO] [stdout]     |
[INFO] [stdout]   1 | ... ; embassy_hal_internal :: interrupt_mod ! (WWD..., FDCAN3_IT0 , FDCAN3_IT1 , TIM23 , TIM24 ,) ; ...
[INFO] [stdout]     |       --------------------------------------------...-------------------------------------------- in this macro invocation
[INFO] [stdout]     = note: this error originates in the macro `device_tree` which comes from the expansion of the macro `embassy_hal_internal::interrupt_mod` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout]  14 - device_tree! {
[INFO] [stdout]  15 -     name "nucleo-f072rb";
[INFO] [stdout]  16 -     backend stm32;
[INFO] [stdout]  17 -     chip "stm32f072rb";
[INFO] [stdout]  18 -     from "boards/nucleo-f072rb.dts";
[INFO] [stdout]  19 - }
[INFO] [stdout]  14 + EXTI9_5
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `InterruptHandler` in module `::embassy_stm32::adc`
[INFO] [stdout]   --> examples/f072_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-f072rb";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f072rb";
[INFO] [stdout] 18 | |     from "boards/nucleo-f072rb.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ not found in `::embassy_stm32::adc`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: consider importing one of these structs
[INFO] [stdout]    |
[INFO] [stdout]  7 + use embassy_stm32::dcmi::InterruptHandler;
[INFO] [stdout]    |
[INFO] [stdout]  7 + use embassy_stm32::dma::InterruptHandler;
[INFO] [stdout]    |
[INFO] [stdout]  7 + use embassy_stm32::dts::InterruptHandler;
[INFO] [stdout]    |
[INFO] [stdout]  7 + use embassy_stm32::eth::InterruptHandler;
[INFO] [stdout]    |
[INFO] [stdout]    = and 7 other candidates
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `ADC1_COMP` in module `$crate::interrupt::typelevel`
[INFO] [stdout]   --> examples/f072_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-f072rb";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f072rb";
[INFO] [stdout] 18 | |     from "boards/nucleo-f072rb.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `USB` in module `$crate::interrupt::typelevel`
[INFO] [stdout]   --> examples/f072_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-f072rb";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f072rb";
[INFO] [stdout] 18 | |     from "boards/nucleo-f072rb.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: `#[panic_handler]` function required, but not found
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unwinding panics are not supported without std
[INFO] [stdout]   |
[INFO] [stdout]   = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding
[INFO] [stdout]   = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/h723_embassy_spi_shared.rs:16:1
[INFO] [stdout]    |
[INFO] [stdout] 16 | / device_tree! {
[INFO] [stdout] 17 | |     name "nucleo-h723zi";
[INFO] [stdout] 18 | |     backend stm32;
[INFO] [stdout] 19 | |     chip "stm32h723zg";
[INFO] [stdout] 20 | |     from "boards/nucleo-h723-spi-shared.dts";
[INFO] [stdout] 21 | | }
[INFO] [stdout]    | |_^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 16 - device_tree! {
[INFO] [stdout] 17 -     name "nucleo-h723zi";
[INFO] [stdout] 18 -     backend stm32;
[INFO] [stdout] 19 -     chip "stm32h723zg";
[INFO] [stdout] 20 -     from "boards/nucleo-h723-spi-shared.dts";
[INFO] [stdout] 21 - }
[INFO] [stdout] 16 + embassy_dt_stm32
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `embassy-dt-stm32` (example "h723_embassy_dac") due to 3 previous errors
[INFO] [stdout] error[E0609]: no field `USB_OTG_FS` on type `Peripherals`
[INFO] [stdout]   --> examples/f411_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "blackpill-f411ce";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f411ce";
[INFO] [stdout] 18 | |     from "boards/blackpill-f411.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ unknown field
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0609]: no field `pll_src` on type `embassy_stm32::rcc::Config`
[INFO] [stdout]   --> examples/f411_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "blackpill-f411ce";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f411ce";
[INFO] [stdout] 18 | |     from "boards/blackpill-f411.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ unknown field
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0609]: no field `pll` on type `embassy_stm32::rcc::Config`
[INFO] [stdout]   --> examples/f411_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "blackpill-f411ce";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f411ce";
[INFO] [stdout] 18 | |     from "boards/blackpill-f411.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ unknown field
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0063]: missing field `source` in initializer of `Pll`
[INFO] [stdout]   --> examples/f411_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "blackpill-f411ce";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f411ce";
[INFO] [stdout] 18 | |     from "boards/blackpill-f411.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ missing `source`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0609]: no field `clk48sel` on type `ClockMux`
[INFO] [stdout]   --> examples/f411_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "blackpill-f411ce";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f411ce";
[INFO] [stdout] 18 | |     from "boards/blackpill-f411.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ unknown field
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find `PllRDiv` in `rcc`
[INFO] [stdout]   --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-g474re";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32g474re";
[INFO] [stdout] 18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ could not find `PllRDiv` in `rcc`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]    |
[INFO] [stdout] 14 - device_tree! {
[INFO] [stdout] 15 -     name "nucleo-g474re";
[INFO] [stdout] 16 -     backend stm32;
[INFO] [stdout] 17 -     chip "stm32g474re";
[INFO] [stdout] 18 -     from "boards/nucleo-g474re.dts";
[INFO] [stdout] 19 - }
[INFO] [stdout] 14 + PllDiv
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `embassy-dt-stm32` (example "h723_embassy_rng") due to 3 previous errors
[INFO] [stderr] error: could not compile `embassy-dt-stm32` (example "h723_embassy_spi_shared") due to 3 previous errors
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/f411_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "blackpill-f411ce";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f411ce";
[INFO] [stdout] 18 | |     from "boards/blackpill-f411.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 14 - device_tree! {
[INFO] [stdout] 15 -     name "blackpill-f411ce";
[INFO] [stdout] 16 -     backend stm32;
[INFO] [stdout] 17 -     chip "stm32f411ce";
[INFO] [stdout] 18 -     from "boards/blackpill-f411.dts";
[INFO] [stdout] 19 - }
[INFO] [stdout] 14 + embassy_dt_stm32
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/f411_driver_bme280.rs:21:21
[INFO] [stdout]    |
[INFO] [stdout] 21 | type Bme280Shared = embassy_dt_bme280::Bme280<
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 21 - type Bme280Shared = embassy_dt_bme280::Bme280<
[INFO] [stdout] 21 + type Bme280Shared = embassy_dt_stm32::Bme280<
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0061, E0063, E0425, E0433, E0609.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0061`.
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `USB` in module `::embassy_stm32::peripherals`
[INFO] [stdout]   --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-g474re";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32g474re";
[INFO] [stdout] 18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ not found in `::embassy_stm32::peripherals`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `DMA1_CHANNEL1` in module `$crate::interrupt::typelevel`
[INFO] [stdout]    --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "nucleo-g474re";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32g474re";
[INFO] [stdout]  18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]     |
[INFO] [stdout] note: similarly named enum `BDMA_CHANNEL1` defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-hal-internal-0.5.0/src/interrupt.rs:105:21
[INFO] [stdout]     |
[INFO] [stdout] 105 |                     pub enum $irqs {}
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/target/debug/build/embassy-stm32/b185b0e296430802/out/_generated.rs:1:4421
[INFO] [stdout]     |
[INFO] [stdout]   1 | ... ; embassy_hal_internal :: interrupt_mod ! (WWD..., FDCAN3_IT0 , FDCAN3_IT1 , TIM23 , TIM24 ,) ; ...
[INFO] [stdout]     |       --------------------------------------------...-------------------------------------------- in this macro invocation
[INFO] [stdout]     = note: this error originates in the macro `device_tree` which comes from the expansion of the macro `embassy_hal_internal::interrupt_mod` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout]  14 - device_tree! {
[INFO] [stdout]  15 -     name "nucleo-g474re";
[INFO] [stdout]  16 -     backend stm32;
[INFO] [stdout]  17 -     chip "stm32g474re";
[INFO] [stdout]  18 -     from "boards/nucleo-g474re.dts";
[INFO] [stdout]  19 - }
[INFO] [stdout]  14 + BDMA_CHANNEL1
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `DMA1_CHANNEL2` in module `$crate::interrupt::typelevel`
[INFO] [stdout]    --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "nucleo-g474re";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32g474re";
[INFO] [stdout]  18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]     |
[INFO] [stdout] note: similarly named enum `BDMA_CHANNEL2` defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-hal-internal-0.5.0/src/interrupt.rs:105:21
[INFO] [stdout]     |
[INFO] [stdout] 105 |                     pub enum $irqs {}
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/target/debug/build/embassy-stm32/b185b0e296430802/out/_generated.rs:1:4421
[INFO] [stdout]     |
[INFO] [stdout]   1 | ... ; embassy_hal_internal :: interrupt_mod ! (WWD..., FDCAN3_IT0 , FDCAN3_IT1 , TIM23 , TIM24 ,) ; ...
[INFO] [stdout]     |       --------------------------------------------...-------------------------------------------- in this macro invocation
[INFO] [stdout]     = note: this error originates in the macro `device_tree` which comes from the expansion of the macro `embassy_hal_internal::interrupt_mod` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout]  14 - device_tree! {
[INFO] [stdout]  15 -     name "nucleo-g474re";
[INFO] [stdout]  16 -     backend stm32;
[INFO] [stdout]  17 -     chip "stm32g474re";
[INFO] [stdout]  18 -     from "boards/nucleo-g474re.dts";
[INFO] [stdout]  19 - }
[INFO] [stdout]  14 + BDMA_CHANNEL2
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `DMA1_CHANNEL3` in module `$crate::interrupt::typelevel`
[INFO] [stdout]    --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "nucleo-g474re";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32g474re";
[INFO] [stdout]  18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]     |
[INFO] [stdout] note: similarly named enum `BDMA_CHANNEL3` defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-hal-internal-0.5.0/src/interrupt.rs:105:21
[INFO] [stdout]     |
[INFO] [stdout] 105 |                     pub enum $irqs {}
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/target/debug/build/embassy-stm32/b185b0e296430802/out/_generated.rs:1:4421
[INFO] [stdout]     |
[INFO] [stdout]   1 | ... ; embassy_hal_internal :: interrupt_mod ! (WWD..., FDCAN3_IT0 , FDCAN3_IT1 , TIM23 , TIM24 ,) ; ...
[INFO] [stdout]     |       --------------------------------------------...-------------------------------------------- in this macro invocation
[INFO] [stdout]     = note: this error originates in the macro `device_tree` which comes from the expansion of the macro `embassy_hal_internal::interrupt_mod` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout]  14 - device_tree! {
[INFO] [stdout]  15 -     name "nucleo-g474re";
[INFO] [stdout]  16 -     backend stm32;
[INFO] [stdout]  17 -     chip "stm32g474re";
[INFO] [stdout]  18 -     from "boards/nucleo-g474re.dts";
[INFO] [stdout]  19 - }
[INFO] [stdout]  14 + BDMA_CHANNEL3
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `DMA1_CHANNEL4` in module `$crate::interrupt::typelevel`
[INFO] [stdout]    --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "nucleo-g474re";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32g474re";
[INFO] [stdout]  18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]     |
[INFO] [stdout] note: similarly named enum `BDMA_CHANNEL4` defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-hal-internal-0.5.0/src/interrupt.rs:105:21
[INFO] [stdout]     |
[INFO] [stdout] 105 |                     pub enum $irqs {}
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/target/debug/build/embassy-stm32/b185b0e296430802/out/_generated.rs:1:4421
[INFO] [stdout]     |
[INFO] [stdout]   1 | ... ; embassy_hal_internal :: interrupt_mod ! (WWD..., FDCAN3_IT0 , FDCAN3_IT1 , TIM23 , TIM24 ,) ; ...
[INFO] [stdout]     |       --------------------------------------------...-------------------------------------------- in this macro invocation
[INFO] [stdout]     = note: this error originates in the macro `device_tree` which comes from the expansion of the macro `embassy_hal_internal::interrupt_mod` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout]  14 - device_tree! {
[INFO] [stdout]  15 -     name "nucleo-g474re";
[INFO] [stdout]  16 -     backend stm32;
[INFO] [stdout]  17 -     chip "stm32g474re";
[INFO] [stdout]  18 -     from "boards/nucleo-g474re.dts";
[INFO] [stdout]  19 - }
[INFO] [stdout]  14 + BDMA_CHANNEL4
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `DMA1_CHANNEL5` in module `$crate::interrupt::typelevel`
[INFO] [stdout]    --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "nucleo-g474re";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32g474re";
[INFO] [stdout]  18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]     |
[INFO] [stdout] note: similarly named enum `BDMA_CHANNEL5` defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-hal-internal-0.5.0/src/interrupt.rs:105:21
[INFO] [stdout]     |
[INFO] [stdout] 105 |                     pub enum $irqs {}
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/target/debug/build/embassy-stm32/b185b0e296430802/out/_generated.rs:1:4421
[INFO] [stdout]     |
[INFO] [stdout]   1 | ... ; embassy_hal_internal :: interrupt_mod ! (WWD..., FDCAN3_IT0 , FDCAN3_IT1 , TIM23 , TIM24 ,) ; ...
[INFO] [stdout]     |       --------------------------------------------...-------------------------------------------- in this macro invocation
[INFO] [stdout]     = note: this error originates in the macro `device_tree` which comes from the expansion of the macro `embassy_hal_internal::interrupt_mod` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout]  14 - device_tree! {
[INFO] [stdout]  15 -     name "nucleo-g474re";
[INFO] [stdout]  16 -     backend stm32;
[INFO] [stdout]  17 -     chip "stm32g474re";
[INFO] [stdout]  18 -     from "boards/nucleo-g474re.dts";
[INFO] [stdout]  19 - }
[INFO] [stdout]  14 + BDMA_CHANNEL5
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `DMA1_CHANNEL6` in module `$crate::interrupt::typelevel`
[INFO] [stdout]    --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "nucleo-g474re";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32g474re";
[INFO] [stdout]  18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]     |
[INFO] [stdout] note: similarly named enum `BDMA_CHANNEL6` defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-hal-internal-0.5.0/src/interrupt.rs:105:21
[INFO] [stdout]     |
[INFO] [stdout] 105 |                     pub enum $irqs {}
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/target/debug/build/embassy-stm32/b185b0e296430802/out/_generated.rs:1:4421
[INFO] [stdout]     |
[INFO] [stdout]   1 | ... ; embassy_hal_internal :: interrupt_mod ! (WWD..., FDCAN3_IT0 , FDCAN3_IT1 , TIM23 , TIM24 ,) ; ...
[INFO] [stdout]     |       --------------------------------------------...-------------------------------------------- in this macro invocation
[INFO] [stdout]     = note: this error originates in the macro `device_tree` which comes from the expansion of the macro `embassy_hal_internal::interrupt_mod` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout]  14 - device_tree! {
[INFO] [stdout]  15 -     name "nucleo-g474re";
[INFO] [stdout]  16 -     backend stm32;
[INFO] [stdout]  17 -     chip "stm32g474re";
[INFO] [stdout]  18 -     from "boards/nucleo-g474re.dts";
[INFO] [stdout]  19 - }
[INFO] [stdout]  14 + BDMA_CHANNEL6
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `USB_LP` in module `$crate::interrupt::typelevel`
[INFO] [stdout]   --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-g474re";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32g474re";
[INFO] [stdout] 18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `embassy-dt-stm32` (example "f411_driver_bme280") due to 15 previous errors
[INFO] [stdout] error: `#[panic_handler]` function required, but not found
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unwinding panics are not supported without std
[INFO] [stdout]   |
[INFO] [stdout]   = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding
[INFO] [stdout]   = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0061]: this function takes 1 argument but 2 arguments were supplied
[INFO] [stdout]    --> examples/f072_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "nucleo-f072rb";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32f072rb";
[INFO] [stdout]  18 | |     from "boards/nucleo-f072rb.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ unexpected argument #2 of type `DtIrqs`
[INFO] [stdout]     |
[INFO] [stdout] note: associated function defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-stm32-0.6.0/src/adc/v4.rs:253:12
[INFO] [stdout]     |
[INFO] [stdout] 253 |     pub fn new(adc: Peri<'d, T>) -> Self {
[INFO] [stdout]     |            ^^^
[INFO] [stdout]     = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/h723_embassy_usb_hid_keyboard.rs:23:1
[INFO] [stdout]    |
[INFO] [stdout] 23 | / device_tree! {
[INFO] [stdout] 24 | |     name "nucleo-h723zi";
[INFO] [stdout] 25 | |     backend stm32;
[INFO] [stdout] 26 | |     chip "stm32h723zg";
[INFO] [stdout] 27 | |     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 28 | | }
[INFO] [stdout]    | |_^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 23 - device_tree! {
[INFO] [stdout] 24 -     name "nucleo-h723zi";
[INFO] [stdout] 25 -     backend stm32;
[INFO] [stdout] 26 -     chip "stm32h723zg";
[INFO] [stdout] 27 -     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 28 - }
[INFO] [stdout] 23 + embassy_dt_stm32
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/h723_custom.rs:23:1
[INFO] [stdout]    |
[INFO] [stdout] 23 | / device_tree! {
[INFO] [stdout] 24 | |     name "custom-h723";
[INFO] [stdout] 25 | |     backend stm32;
[INFO] [stdout] 26 | |     chip "stm32h723zg";
[INFO] [stdout] 27 | |     from "boards/custom-h723.dts";
[INFO] [stdout] 28 | | }
[INFO] [stdout]    | |_^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 23 - device_tree! {
[INFO] [stdout] 24 -     name "custom-h723";
[INFO] [stdout] 25 -     backend stm32;
[INFO] [stdout] 26 -     chip "stm32h723zg";
[INFO] [stdout] 27 -     from "boards/custom-h723.dts";
[INFO] [stdout] 28 - }
[INFO] [stdout] 23 + embassy_dt_stm32
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no associated function or constant named `new` found for struct `Driver<'d, T>` in the current scope
[INFO] [stdout]    --> examples/f072_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "nucleo-f072rb";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32f072rb";
[INFO] [stdout]  18 | |     from "boards/nucleo-f072rb.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ associated function or constant not found in `Driver<'_, _>`
[INFO] [stdout]     |
[INFO] [stdout] note: if you're trying to build a new `Driver<'_, _>` consider using one of the following associated functions:
[INFO] [stdout]       Driver::<'d, T>::new_fs
[INFO] [stdout]       Driver::<'d, T>::new_hs
[INFO] [stdout]       Driver::<'d, T>::new_fs_ulpi
[INFO] [stdout]       Driver::<'d, T>::new_hs_ulpi
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-stm32-0.6.0/src/usb/otg.rs:63:5
[INFO] [stdout]     |
[INFO] [stdout]  63 | /     pub fn new_fs(
[INFO] [stdout]  64 | |         _peri: Peri<'d, T>,
[INFO] [stdout]  65 | |         _irq: impl interrupt::typelevel::Binding<T::Interrupt, InterruptHandler<T>> + 'd,
[INFO] [stdout]  66 | |         dp: Peri<'d, impl DpPin<T>>,
[INFO] [stdout] ...   |
[INFO] [stdout]  69 | |         config: Config,
[INFO] [stdout]  70 | |     ) -> Self {
[INFO] [stdout]     | |_____________^
[INFO] [stdout] ...
[INFO] [stdout] 104 | /     pub fn new_hs(
[INFO] [stdout] 105 | |         _peri: Peri<'d, T>,
[INFO] [stdout] 106 | |         _irq: impl interrupt::typelevel::Binding<T::Interrupt, InterruptHandler<T>> + 'd,
[INFO] [stdout] 107 | |         dp: Peri<'d, impl DpPin<T>>,
[INFO] [stdout] ...   |
[INFO] [stdout] 110 | |         config: Config,
[INFO] [stdout] 111 | |     ) -> Self {
[INFO] [stdout]     | |_____________^
[INFO] [stdout] ...
[INFO] [stdout] 143 | /     pub fn new_fs_ulpi(
[INFO] [stdout] 144 | |         _peri: Peri<'d, T>,
[INFO] [stdout] 145 | |         _irq: impl interrupt::typelevel::Binding<T::Interrupt, InterruptHandler<T>> + 'd,
[INFO] [stdout] 146 | |         ulpi_clk: Peri<'d, impl UlpiClkPin<T>>,
[INFO] [stdout] ...   |
[INFO] [stdout] 159 | |         config: Config,
[INFO] [stdout] 160 | |     ) -> Self {
[INFO] [stdout]     | |_____________^
[INFO] [stdout] ...
[INFO] [stdout] 189 | /     pub fn new_hs_ulpi(
[INFO] [stdout] 190 | |         _peri: Peri<'d, T>,
[INFO] [stdout] 191 | |         _irq: impl interrupt::typelevel::Binding<T::Interrupt, InterruptHandler<T>> + 'd,
[INFO] [stdout] 192 | |         ulpi_clk: Peri<'d, impl UlpiClkPin<T>>,
[INFO] [stdout] ...   |
[INFO] [stdout] 205 | |         config: Config,
[INFO] [stdout] 206 | |     ) -> Self {
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0609]: no field `USB` on type `Peripherals`
[INFO] [stdout]   --> examples/f072_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-f072rb";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f072rb";
[INFO] [stdout] 18 | |     from "boards/nucleo-f072rb.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ unknown field
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `embassy-dt-stm32` (example "h723_embassy_usb_hid_keyboard") due to 3 previous errors
[INFO] [stderr] error: could not compile `embassy-dt-stm32` (example "h723_custom") due to 2 previous errors
[INFO] [stdout] error[E0308]: mismatched types
[INFO] [stdout]   --> examples/f072_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-f072rb";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f072rb";
[INFO] [stdout] 18 | |     from "boards/nucleo-f072rb.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | | ^
[INFO] [stdout]    | | |
[INFO] [stdout]    | |_expected `Option<HSIPrescaler>`, found `bool`
[INFO] [stdout]    |   expected due to the type of this binding
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected enum `Option<HSIPrescaler>`
[INFO] [stdout]               found type `bool`
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0609]: no field `pll` on type `embassy_stm32::rcc::Config`
[INFO] [stdout]   --> examples/f072_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-f072rb";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f072rb";
[INFO] [stdout] 18 | |     from "boards/nucleo-f072rb.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ unknown field
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0560]: struct `Pll` has no field named `src`
[INFO] [stdout]   --> examples/f072_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-f072rb";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f072rb";
[INFO] [stdout] 18 | |     from "boards/nucleo-f072rb.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ `Pll` does not have this field
[INFO] [stdout]    |
[INFO] [stdout]    = note: all struct fields are already assigned
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find `ADCPrescaler` in `rcc`
[INFO] [stdout]   --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "bluepill-f103c8";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f103c8";
[INFO] [stdout] 18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ could not find `ADCPrescaler` in `rcc`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]    |
[INFO] [stdout] 14 - device_tree! {
[INFO] [stdout] 15 -     name "bluepill-f103c8";
[INFO] [stdout] 16 -     backend stm32;
[INFO] [stdout] 17 -     chip "stm32f103c8";
[INFO] [stdout] 18 -     from "boards/bluepill-f103.dts";
[INFO] [stdout] 19 - }
[INFO] [stdout] 14 + AHBPrescaler
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/h723_embassy_input_capture.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-h723zi";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32h723zg";
[INFO] [stdout] 18 | |     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 14 - device_tree! {
[INFO] [stdout] 15 -     name "nucleo-h723zi";
[INFO] [stdout] 16 -     backend stm32;
[INFO] [stdout] 17 -     chip "stm32h723zg";
[INFO] [stdout] 18 -     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 19 - }
[INFO] [stdout] 14 + embassy_dt_stm32
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stdout] error[E0061]: this function takes 1 argument but 2 arguments were supplied
[INFO] [stdout]    --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "nucleo-g474re";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32g474re";
[INFO] [stdout]  18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ unexpected argument #2 of type `AdcConfig`
[INFO] [stdout]     |
[INFO] [stdout] note: associated function defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-stm32-0.6.0/src/adc/v4.rs:253:12
[INFO] [stdout]     |
[INFO] [stdout] 253 |     pub fn new(adc: Peri<'d, T>) -> Self {
[INFO] [stdout]     |            ^^^
[INFO] [stdout]     = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `USB` in module `::embassy_stm32::peripherals`
[INFO] [stdout]   --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "bluepill-f103c8";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f103c8";
[INFO] [stdout] 18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ not found in `::embassy_stm32::peripherals`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `AfioRemap` in module `::embassy_stm32::gpio`
[INFO] [stdout]    --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "bluepill-f103c8";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32f103c8";
[INFO] [stdout]  18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ not found in `::embassy_stm32::gpio`
[INFO] [stdout]     |
[INFO] [stdout] note: found an item that was configured out
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-stm32-0.6.0/src/gpio.rs:751:12
[INFO] [stdout]     |
[INFO] [stdout] 749 | #[cfg(afio)]
[INFO] [stdout]     |       ---- the item is gated here
[INFO] [stdout] 750 | /// Holds the AFIO remap value for a peripheral's pin
[INFO] [stdout] 751 | pub struct AfioRemap<const V: u8>;
[INFO] [stdout]     |            ^^^^^^^^^
[INFO] [stdout]     = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/h723_embassy_can.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-h723zi";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32h723zg";
[INFO] [stdout] 18 | |     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 14 - device_tree! {
[INFO] [stdout] 15 -     name "nucleo-h723zi";
[INFO] [stdout] 16 -     backend stm32;
[INFO] [stdout] 17 -     chip "stm32h723zg";
[INFO] [stdout] 18 -     from "boards/nucleo-h723zi.dts";
[INFO] [stdout] 19 - }
[INFO] [stdout] 14 + embassy_dt_stm32
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/f072_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-f072rb";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f072rb";
[INFO] [stdout] 18 | |     from "boards/nucleo-f072rb.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 14 - device_tree! {
[INFO] [stdout] 15 -     name "nucleo-f072rb";
[INFO] [stdout] 16 -     backend stm32;
[INFO] [stdout] 17 -     chip "stm32f072rb";
[INFO] [stdout] 18 -     from "boards/nucleo-f072rb.dts";
[INFO] [stdout] 19 - }
[INFO] [stdout] 14 + embassy_dt_stm32
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/f072_driver_bme280.rs:21:21
[INFO] [stdout]    |
[INFO] [stdout] 21 | type Bme280Shared = embassy_dt_bme280::Bme280<
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 21 - type Bme280Shared = embassy_dt_bme280::Bme280<
[INFO] [stdout] 21 + type Bme280Shared = embassy_dt_stm32::Bme280<
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0061, E0308, E0425, E0433, E0560, E0599, E0609.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0061`.
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `DMA1_CHANNEL6` in module `$crate::interrupt::typelevel`
[INFO] [stdout]    --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "bluepill-f103c8";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32f103c8";
[INFO] [stdout]  18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]     |
[INFO] [stdout] note: similarly named enum `BDMA_CHANNEL6` defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-hal-internal-0.5.0/src/interrupt.rs:105:21
[INFO] [stdout]     |
[INFO] [stdout] 105 |                     pub enum $irqs {}
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/target/debug/build/embassy-stm32/b185b0e296430802/out/_generated.rs:1:4421
[INFO] [stdout]     |
[INFO] [stdout]   1 | ... ; embassy_hal_internal :: interrupt_mod ! (WWD..., FDCAN3_IT0 , FDCAN3_IT1 , TIM23 , TIM24 ,) ; ...
[INFO] [stdout]     |       --------------------------------------------...-------------------------------------------- in this macro invocation
[INFO] [stdout]     = note: this error originates in the macro `device_tree` which comes from the expansion of the macro `embassy_hal_internal::interrupt_mod` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout]  14 - device_tree! {
[INFO] [stdout]  15 -     name "bluepill-f103c8";
[INFO] [stdout]  16 -     backend stm32;
[INFO] [stdout]  17 -     chip "stm32f103c8";
[INFO] [stdout]  18 -     from "boards/bluepill-f103.dts";
[INFO] [stdout]  19 - }
[INFO] [stdout]  14 + BDMA_CHANNEL6
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `DMA1_CHANNEL7` in module `$crate::interrupt::typelevel`
[INFO] [stdout]    --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "bluepill-f103c8";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32f103c8";
[INFO] [stdout]  18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]     |
[INFO] [stdout] note: similarly named enum `BDMA_CHANNEL7` defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-hal-internal-0.5.0/src/interrupt.rs:105:21
[INFO] [stdout]     |
[INFO] [stdout] 105 |                     pub enum $irqs {}
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/target/debug/build/embassy-stm32/b185b0e296430802/out/_generated.rs:1:4421
[INFO] [stdout]     |
[INFO] [stdout]   1 | ... ; embassy_hal_internal :: interrupt_mod ! (WWD..., FDCAN3_IT0 , FDCAN3_IT1 , TIM23 , TIM24 ,) ; ...
[INFO] [stdout]     |       --------------------------------------------...-------------------------------------------- in this macro invocation
[INFO] [stdout]     = note: this error originates in the macro `device_tree` which comes from the expansion of the macro `embassy_hal_internal::interrupt_mod` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout]  14 - device_tree! {
[INFO] [stdout]  15 -     name "bluepill-f103c8";
[INFO] [stdout]  16 -     backend stm32;
[INFO] [stdout]  17 -     chip "stm32f103c8";
[INFO] [stdout]  18 -     from "boards/bluepill-f103.dts";
[INFO] [stdout]  19 - }
[INFO] [stdout]  14 + BDMA_CHANNEL7
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `DMA1_CHANNEL3` in module `$crate::interrupt::typelevel`
[INFO] [stdout]    --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "bluepill-f103c8";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32f103c8";
[INFO] [stdout]  18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]     |
[INFO] [stdout] note: similarly named enum `BDMA_CHANNEL3` defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-hal-internal-0.5.0/src/interrupt.rs:105:21
[INFO] [stdout]     |
[INFO] [stdout] 105 |                     pub enum $irqs {}
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/target/debug/build/embassy-stm32/b185b0e296430802/out/_generated.rs:1:4421
[INFO] [stdout]     |
[INFO] [stdout]   1 | ... ; embassy_hal_internal :: interrupt_mod ! (WWD..., FDCAN3_IT0 , FDCAN3_IT1 , TIM23 , TIM24 ,) ; ...
[INFO] [stdout]     |       --------------------------------------------...-------------------------------------------- in this macro invocation
[INFO] [stdout]     = note: this error originates in the macro `device_tree` which comes from the expansion of the macro `embassy_hal_internal::interrupt_mod` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout]  14 - device_tree! {
[INFO] [stdout]  15 -     name "bluepill-f103c8";
[INFO] [stdout]  16 -     backend stm32;
[INFO] [stdout]  17 -     chip "stm32f103c8";
[INFO] [stdout]  18 -     from "boards/bluepill-f103.dts";
[INFO] [stdout]  19 - }
[INFO] [stdout]  14 + BDMA_CHANNEL3
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `DMA1_CHANNEL2` in module `$crate::interrupt::typelevel`
[INFO] [stdout]    --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "bluepill-f103c8";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32f103c8";
[INFO] [stdout]  18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]     |
[INFO] [stdout] note: similarly named enum `BDMA_CHANNEL2` defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-hal-internal-0.5.0/src/interrupt.rs:105:21
[INFO] [stdout]     |
[INFO] [stdout] 105 |                     pub enum $irqs {}
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/target/debug/build/embassy-stm32/b185b0e296430802/out/_generated.rs:1:4421
[INFO] [stdout]     |
[INFO] [stdout]   1 | ... ; embassy_hal_internal :: interrupt_mod ! (WWD..., FDCAN3_IT0 , FDCAN3_IT1 , TIM23 , TIM24 ,) ; ...
[INFO] [stdout]     |       --------------------------------------------...-------------------------------------------- in this macro invocation
[INFO] [stdout]     = note: this error originates in the macro `device_tree` which comes from the expansion of the macro `embassy_hal_internal::interrupt_mod` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout]  14 - device_tree! {
[INFO] [stdout]  15 -     name "bluepill-f103c8";
[INFO] [stdout]  16 -     backend stm32;
[INFO] [stdout]  17 -     chip "stm32f103c8";
[INFO] [stdout]  18 -     from "boards/bluepill-f103.dts";
[INFO] [stdout]  19 - }
[INFO] [stdout]  14 + BDMA_CHANNEL2
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `DMA1_CHANNEL4` in module `$crate::interrupt::typelevel`
[INFO] [stdout]    --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "bluepill-f103c8";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32f103c8";
[INFO] [stdout]  18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]     |
[INFO] [stdout] note: similarly named enum `BDMA_CHANNEL4` defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-hal-internal-0.5.0/src/interrupt.rs:105:21
[INFO] [stdout]     |
[INFO] [stdout] 105 |                     pub enum $irqs {}
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/target/debug/build/embassy-stm32/b185b0e296430802/out/_generated.rs:1:4421
[INFO] [stdout]     |
[INFO] [stdout]   1 | ... ; embassy_hal_internal :: interrupt_mod ! (WWD..., FDCAN3_IT0 , FDCAN3_IT1 , TIM23 , TIM24 ,) ; ...
[INFO] [stdout]     |       --------------------------------------------...-------------------------------------------- in this macro invocation
[INFO] [stdout]     = note: this error originates in the macro `device_tree` which comes from the expansion of the macro `embassy_hal_internal::interrupt_mod` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout]  14 - device_tree! {
[INFO] [stdout]  15 -     name "bluepill-f103c8";
[INFO] [stdout]  16 -     backend stm32;
[INFO] [stdout]  17 -     chip "stm32f103c8";
[INFO] [stdout]  18 -     from "boards/bluepill-f103.dts";
[INFO] [stdout]  19 - }
[INFO] [stdout]  14 + BDMA_CHANNEL4
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `DMA1_CHANNEL5` in module `$crate::interrupt::typelevel`
[INFO] [stdout]    --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "bluepill-f103c8";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32f103c8";
[INFO] [stdout]  18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]     |
[INFO] [stdout] note: similarly named enum `BDMA_CHANNEL5` defined here
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-hal-internal-0.5.0/src/interrupt.rs:105:21
[INFO] [stdout]     |
[INFO] [stdout] 105 |                     pub enum $irqs {}
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/target/debug/build/embassy-stm32/b185b0e296430802/out/_generated.rs:1:4421
[INFO] [stdout]     |
[INFO] [stdout]   1 | ... ; embassy_hal_internal :: interrupt_mod ! (WWD..., FDCAN3_IT0 , FDCAN3_IT1 , TIM23 , TIM24 ,) ; ...
[INFO] [stdout]     |       --------------------------------------------...-------------------------------------------- in this macro invocation
[INFO] [stdout]     = note: this error originates in the macro `device_tree` which comes from the expansion of the macro `embassy_hal_internal::interrupt_mod` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: an enum with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout]  14 - device_tree! {
[INFO] [stdout]  15 -     name "bluepill-f103c8";
[INFO] [stdout]  16 -     backend stm32;
[INFO] [stdout]  17 -     chip "stm32f103c8";
[INFO] [stdout]  18 -     from "boards/bluepill-f103.dts";
[INFO] [stdout]  19 - }
[INFO] [stdout]  14 + BDMA_CHANNEL5
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `InterruptHandler` in module `::embassy_stm32::adc`
[INFO] [stdout]   --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "bluepill-f103c8";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f103c8";
[INFO] [stdout] 18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ not found in `::embassy_stm32::adc`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: consider importing one of these structs
[INFO] [stdout]    |
[INFO] [stdout]  7 + use embassy_stm32::dcmi::InterruptHandler;
[INFO] [stdout]    |
[INFO] [stdout]  7 + use embassy_stm32::dma::InterruptHandler;
[INFO] [stdout]    |
[INFO] [stdout]  7 + use embassy_stm32::dts::InterruptHandler;
[INFO] [stdout]    |
[INFO] [stdout]  7 + use embassy_stm32::eth::InterruptHandler;
[INFO] [stdout]    |
[INFO] [stdout]    = and 7 other candidates
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `embassy-dt-stm32` (example "h723_embassy_input_capture") due to 3 previous errors
[INFO] [stdout] error[E0425]: cannot find type `ADC1_2` in module `$crate::interrupt::typelevel`
[INFO] [stdout]   --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "bluepill-f103c8";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f103c8";
[INFO] [stdout] 18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `USB_LP_CAN1_RX0` in module `$crate::interrupt::typelevel`
[INFO] [stdout]   --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "bluepill-f103c8";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f103c8";
[INFO] [stdout] 18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ not found in `$crate::interrupt::typelevel`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: `#[panic_handler]` function required, but not found
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unwinding panics are not supported without std
[INFO] [stdout]   |
[INFO] [stdout]   = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding
[INFO] [stdout]   = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `embassy-dt-stm32` (example "h723_embassy_can") due to 3 previous errors
[INFO] [stdout] error[E0599]: no associated function or constant named `new` found for struct `Driver<'d, T>` in the current scope
[INFO] [stdout]    --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "nucleo-g474re";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32g474re";
[INFO] [stdout]  18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ associated function or constant not found in `Driver<'_, _>`
[INFO] [stdout]     |
[INFO] [stdout] note: if you're trying to build a new `Driver<'_, _>` consider using one of the following associated functions:
[INFO] [stdout]       Driver::<'d, T>::new_fs
[INFO] [stdout]       Driver::<'d, T>::new_hs
[INFO] [stdout]       Driver::<'d, T>::new_fs_ulpi
[INFO] [stdout]       Driver::<'d, T>::new_hs_ulpi
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-stm32-0.6.0/src/usb/otg.rs:63:5
[INFO] [stdout]     |
[INFO] [stdout]  63 | /     pub fn new_fs(
[INFO] [stdout]  64 | |         _peri: Peri<'d, T>,
[INFO] [stdout]  65 | |         _irq: impl interrupt::typelevel::Binding<T::Interrupt, InterruptHandler<T>> + 'd,
[INFO] [stdout]  66 | |         dp: Peri<'d, impl DpPin<T>>,
[INFO] [stdout] ...   |
[INFO] [stdout]  69 | |         config: Config,
[INFO] [stdout]  70 | |     ) -> Self {
[INFO] [stdout]     | |_____________^
[INFO] [stdout] ...
[INFO] [stdout] 104 | /     pub fn new_hs(
[INFO] [stdout] 105 | |         _peri: Peri<'d, T>,
[INFO] [stdout] 106 | |         _irq: impl interrupt::typelevel::Binding<T::Interrupt, InterruptHandler<T>> + 'd,
[INFO] [stdout] 107 | |         dp: Peri<'d, impl DpPin<T>>,
[INFO] [stdout] ...   |
[INFO] [stdout] 110 | |         config: Config,
[INFO] [stdout] 111 | |     ) -> Self {
[INFO] [stdout]     | |_____________^
[INFO] [stdout] ...
[INFO] [stdout] 143 | /     pub fn new_fs_ulpi(
[INFO] [stdout] 144 | |         _peri: Peri<'d, T>,
[INFO] [stdout] 145 | |         _irq: impl interrupt::typelevel::Binding<T::Interrupt, InterruptHandler<T>> + 'd,
[INFO] [stdout] 146 | |         ulpi_clk: Peri<'d, impl UlpiClkPin<T>>,
[INFO] [stdout] ...   |
[INFO] [stdout] 159 | |         config: Config,
[INFO] [stdout] 160 | |     ) -> Self {
[INFO] [stdout]     | |_____________^
[INFO] [stdout] ...
[INFO] [stdout] 189 | /     pub fn new_hs_ulpi(
[INFO] [stdout] 190 | |         _peri: Peri<'d, T>,
[INFO] [stdout] 191 | |         _irq: impl interrupt::typelevel::Binding<T::Interrupt, InterruptHandler<T>> + 'd,
[INFO] [stdout] 192 | |         ulpi_clk: Peri<'d, impl UlpiClkPin<T>>,
[INFO] [stdout] ...   |
[INFO] [stdout] 205 | |         config: Config,
[INFO] [stdout] 206 | |     ) -> Self {
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0609]: no field `USB` on type `Peripherals`
[INFO] [stdout]   --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-g474re";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32g474re";
[INFO] [stdout] 18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ unknown field
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `embassy-dt-stm32` (example "f072_driver_bme280") due to 19 previous errors
[INFO] [stdout] error[E0308]: mismatched types
[INFO] [stdout]   --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-g474re";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32g474re";
[INFO] [stdout] 18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | | ^
[INFO] [stdout]    | | |
[INFO] [stdout]    | |_expected `Option<HSIPrescaler>`, found `bool`
[INFO] [stdout]    |   expected due to the type of this binding
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected enum `Option<HSIPrescaler>`
[INFO] [stdout]               found type `bool`
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0609]: no field `pll` on type `embassy_stm32::rcc::Config`
[INFO] [stdout]   --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-g474re";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32g474re";
[INFO] [stdout] 18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ unknown field
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no variant, associated function, or constant named `PLL1_R` found for enum `Sysclk` in the current scope
[INFO] [stdout]   --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-g474re";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32g474re";
[INFO] [stdout] 18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ variant, associated function, or constant not found in `Sysclk`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: there is a variant with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 14 - device_tree! {
[INFO] [stdout] 15 -     name "nucleo-g474re";
[INFO] [stdout] 16 -     backend stm32;
[INFO] [stdout] 17 -     chip "stm32g474re";
[INFO] [stdout] 18 -     from "boards/nucleo-g474re.dts";
[INFO] [stdout] 19 - }
[INFO] [stdout] 14 + PLL1_P
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0609]: no field `boost` on type `embassy_stm32::rcc::Config`
[INFO] [stdout]   --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-g474re";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32g474re";
[INFO] [stdout] 18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ unknown field
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0609]: no field `adc12sel` on type `ClockMux`
[INFO] [stdout]   --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-g474re";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32g474re";
[INFO] [stdout] 18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ unknown field
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no variant, associated function, or constant named `SYS` found for enum `Adcsel` in the current scope
[INFO] [stdout]   --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-g474re";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32g474re";
[INFO] [stdout] 18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ variant, associated function, or constant not found in `Adcsel`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/g474_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "nucleo-g474re";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32g474re";
[INFO] [stdout] 18 | |     from "boards/nucleo-g474re.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 14 - device_tree! {
[INFO] [stdout] 15 -     name "nucleo-g474re";
[INFO] [stdout] 16 -     backend stm32;
[INFO] [stdout] 17 -     chip "stm32g474re";
[INFO] [stdout] 18 -     from "boards/nucleo-g474re.dts";
[INFO] [stdout] 19 - }
[INFO] [stdout] 14 + embassy_dt_stm32
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/g474_driver_bme280.rs:21:21
[INFO] [stdout]    |
[INFO] [stdout] 21 | type Bme280Shared = embassy_dt_bme280::Bme280<
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 21 - type Bme280Shared = embassy_dt_bme280::Bme280<
[INFO] [stdout] 21 + type Bme280Shared = embassy_dt_stm32::Bme280<
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0061, E0308, E0425, E0433, E0599, E0609.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0061`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `embassy-dt-stm32` (example "g474_driver_bme280") due to 22 previous errors
[INFO] [stdout] error[E0107]: struct takes 2 generic arguments but 3 generic arguments were supplied
[INFO] [stdout]   --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "bluepill-f103c8";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f103c8";
[INFO] [stdout] 18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | | ^
[INFO] [stdout]    | | |
[INFO] [stdout]    | |_expected 2 generic arguments
[INFO] [stdout]    |   help: remove the unnecessary generic argument
[INFO] [stdout]    |
[INFO] [stdout] note: struct defined here, with 2 generic parameters: `T`, `C`
[INFO] [stdout]   --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-stm32-0.6.0/src/timer/simple_pwm.rs:20:12
[INFO] [stdout]    |
[INFO] [stdout] 20 | pub struct PwmPin<'d, T, C, #[cfg(afio)] A> {
[INFO] [stdout]    |            ^^^^^^     -  -
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no associated function or constant named `new` found for struct `Driver<'d, T>` in the current scope
[INFO] [stdout]    --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]     |
[INFO] [stdout]  14 | / device_tree! {
[INFO] [stdout]  15 | |     name "bluepill-f103c8";
[INFO] [stdout]  16 | |     backend stm32;
[INFO] [stdout]  17 | |     chip "stm32f103c8";
[INFO] [stdout]  18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout]  19 | | }
[INFO] [stdout]     | |_^ associated function or constant not found in `Driver<'_, _>`
[INFO] [stdout]     |
[INFO] [stdout] note: if you're trying to build a new `Driver<'_, _>` consider using one of the following associated functions:
[INFO] [stdout]       Driver::<'d, T>::new_fs
[INFO] [stdout]       Driver::<'d, T>::new_hs
[INFO] [stdout]       Driver::<'d, T>::new_fs_ulpi
[INFO] [stdout]       Driver::<'d, T>::new_hs_ulpi
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-stm32-0.6.0/src/usb/otg.rs:63:5
[INFO] [stdout]     |
[INFO] [stdout]  63 | /     pub fn new_fs(
[INFO] [stdout]  64 | |         _peri: Peri<'d, T>,
[INFO] [stdout]  65 | |         _irq: impl interrupt::typelevel::Binding<T::Interrupt, InterruptHandler<T>> + 'd,
[INFO] [stdout]  66 | |         dp: Peri<'d, impl DpPin<T>>,
[INFO] [stdout] ...   |
[INFO] [stdout]  69 | |         config: Config,
[INFO] [stdout]  70 | |     ) -> Self {
[INFO] [stdout]     | |_____________^
[INFO] [stdout] ...
[INFO] [stdout] 104 | /     pub fn new_hs(
[INFO] [stdout] 105 | |         _peri: Peri<'d, T>,
[INFO] [stdout] 106 | |         _irq: impl interrupt::typelevel::Binding<T::Interrupt, InterruptHandler<T>> + 'd,
[INFO] [stdout] 107 | |         dp: Peri<'d, impl DpPin<T>>,
[INFO] [stdout] ...   |
[INFO] [stdout] 110 | |         config: Config,
[INFO] [stdout] 111 | |     ) -> Self {
[INFO] [stdout]     | |_____________^
[INFO] [stdout] ...
[INFO] [stdout] 143 | /     pub fn new_fs_ulpi(
[INFO] [stdout] 144 | |         _peri: Peri<'d, T>,
[INFO] [stdout] 145 | |         _irq: impl interrupt::typelevel::Binding<T::Interrupt, InterruptHandler<T>> + 'd,
[INFO] [stdout] 146 | |         ulpi_clk: Peri<'d, impl UlpiClkPin<T>>,
[INFO] [stdout] ...   |
[INFO] [stdout] 159 | |         config: Config,
[INFO] [stdout] 160 | |     ) -> Self {
[INFO] [stdout]     | |_____________^
[INFO] [stdout] ...
[INFO] [stdout] 189 | /     pub fn new_hs_ulpi(
[INFO] [stdout] 190 | |         _peri: Peri<'d, T>,
[INFO] [stdout] 191 | |         _irq: impl interrupt::typelevel::Binding<T::Interrupt, InterruptHandler<T>> + 'd,
[INFO] [stdout] 192 | |         ulpi_clk: Peri<'d, impl UlpiClkPin<T>>,
[INFO] [stdout] ...   |
[INFO] [stdout] 205 | |         config: Config,
[INFO] [stdout] 206 | |     ) -> Self {
[INFO] [stdout]     | |_____________^
[INFO] [stdout]     = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0609]: no field `USB` on type `Peripherals`
[INFO] [stdout]   --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "bluepill-f103c8";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f103c8";
[INFO] [stdout] 18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ unknown field
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0061]: this function takes 2 arguments but 1 argument was supplied
[INFO] [stdout]   --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "bluepill-f103c8";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f103c8";
[INFO] [stdout] 18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ argument #2 of type `embassy_stm32::crc::Config` is missing
[INFO] [stdout]    |
[INFO] [stdout] note: associated function defined here
[INFO] [stdout]   --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/embassy-stm32-0.6.0/src/crc/v2v3.rs:81:12
[INFO] [stdout]    |
[INFO] [stdout] 81 |     pub fn new(peripheral: Peri<'d, CRC>, config: Config) -> Self {
[INFO] [stdout]    |            ^^^
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0609]: no field `pll` on type `embassy_stm32::rcc::Config`
[INFO] [stdout]   --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "bluepill-f103c8";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f103c8";
[INFO] [stdout] 18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ unknown field
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0560]: struct `Pll` has no field named `src`
[INFO] [stdout]   --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "bluepill-f103c8";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f103c8";
[INFO] [stdout] 18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ `Pll` does not have this field
[INFO] [stdout]    |
[INFO] [stdout]    = note: all struct fields are already assigned
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0609]: no field `adc_pre` on type `embassy_stm32::rcc::Config`
[INFO] [stdout]   --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "bluepill-f103c8";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f103c8";
[INFO] [stdout] 18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ unknown field
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/f103_driver_bme280.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | / device_tree! {
[INFO] [stdout] 15 | |     name "bluepill-f103c8";
[INFO] [stdout] 16 | |     backend stm32;
[INFO] [stdout] 17 | |     chip "stm32f103c8";
[INFO] [stdout] 18 | |     from "boards/bluepill-f103.dts";
[INFO] [stdout] 19 | | }
[INFO] [stdout]    | |_^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the macro `device_tree` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 14 - device_tree! {
[INFO] [stdout] 15 -     name "bluepill-f103c8";
[INFO] [stdout] 16 -     backend stm32;
[INFO] [stdout] 17 -     chip "stm32f103c8";
[INFO] [stdout] 18 -     from "boards/bluepill-f103.dts";
[INFO] [stdout] 19 - }
[INFO] [stdout] 14 + embassy_dt_stm32
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `embassy_dt_bme280` in this scope
[INFO] [stdout]   --> examples/f103_driver_bme280.rs:21:21
[INFO] [stdout]    |
[INFO] [stdout] 21 | type Bme280Shared = embassy_dt_bme280::Bme280<
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `embassy_dt_bme280`
[INFO] [stdout]    |
[INFO] [stdout] help: there is a crate or module with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 21 - type Bme280Shared = embassy_dt_bme280::Bme280<
[INFO] [stdout] 21 + type Bme280Shared = embassy_dt_stm32::Bme280<
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0061, E0107, E0425, E0433, E0560, E0599, E0609.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0061`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `embassy-dt-stm32` (example "f103_driver_bme280") due to 23 previous errors
[INFO] [stderr] warning: unused dependency `embassy-dt`
[INFO] [stderr]  --> Cargo.toml:1:15
[INFO] [stderr]   |
[INFO] [stderr] 1 | [dependencies.embassy-dt]
[INFO] [stderr]   |               ^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: `cargo::unused_dependencies` is set to `warn` by default
[INFO] [stderr] help: consider removing the dependency on `embassy-dt`
[INFO] [stderr] help: to still use for development builds, move to `dev-dependencies`
[INFO] [stderr] warning: unused dependency `embassy-stm32`
[INFO] [stderr]  --> Cargo.toml:7:15
[INFO] [stderr]   |
[INFO] [stderr] 7 | [dependencies.embassy-stm32]
[INFO] [stderr]   |               ^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr] help: consider removing the dependency on `embassy-stm32`
[INFO] [stderr] help: to still use for development builds, move to `dev-dependencies`
[INFO] [stderr] warning: unused dependency `embassy-stm32`
[INFO] [stderr]   --> Cargo.toml:35:19
[INFO] [stderr]    |
[INFO] [stderr] 35 | [dev-dependencies.embassy-stm32]
[INFO] [stderr]    |                   ^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr] help: consider removing the dependency on `embassy-stm32`
[INFO] [stderr] help: to still use for development builds, move to `dev-dependencies`
[INFO] [stderr] warning: `embassy-dt-stm32` (manifest) generated 3 warnings
[INFO] running `Command { std: "docker" "inspect" "3f8598805def1ff3cff6ea32c93f64ef7c89b5c2cbb1aa45adc4384e019a103a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "3f8598805def1ff3cff6ea32c93f64ef7c89b5c2cbb1aa45adc4384e019a103a", kill_on_drop: false }`
[INFO] [stdout] 3f8598805def1ff3cff6ea32c93f64ef7c89b5c2cbb1aa45adc4384e019a103a
