No feature "FPU" about drone-stm32-map HOT 7 CLOSED

Hi @FrozenDroid, thanks for your interest!

This is a bug in the new project template. I will fix it soon. If you don't want to wait, you can change your generated Cargo.toml from this:

drone-cortex-m = { version = "0.10.0" }
drone-stm32-map = { version = "0.10.0", features = ["stm32l4x6", "fpu"] }

To this:

drone-cortex-m = { version = "0.10.0", features = ["fpu"] }
drone-stm32-map = { version = "0.10.0", features = ["stm32l4x6"] }

from drone-stm32-map.

Fixed in drone v0.10.1

Please update it with cargo +nightly install drone --force.

from drone-stm32-map.

Thanks for the quick response! Which nightly are you running? I'm getting an error from futures-util. I'll elaborate more when I'm home.

from drone-stm32-map.

I'm currently using nightly-2019-09-05. I will check with the recent nightly soon. Thanks for the report.

from drone-stm32-map.

I checked with nightly-2019-09-27 and it builds without errors on my machine. I wonder what was the error you got. Generally it should be ok to use the latest nightly with all available components according to this table: https://rust-lang.github.io/rustup-components-history/

from drone-stm32-map.

With the latest nightly as of today (rustc 1.40.0-nightly (22bc9e1d9 2019-09-30)), I'm getting multiple errors such as:

error: <inline asm>:1:19: error: brackets expression not supported on this target
        strexb %al, %al, [%rcx]
                         ^

   --> ~/.cargo/registry/src/github.com-1ecc6299db9ec823/drone-cortex-m-0.10.1/src/reg/atomic.rs:204:17
    |
204 | /                 asm!($strex
205 | |                      : "=r"(status)
206 | |                      : "r"(self), "r"(address)
207 | |                      :
208 | |                      : "volatile"
209 | |                 );
    | |__________________^
...
218 |   atomic_bits!(u8, "ldrexb $0, [$1]", "strexb $0, $1, [$2]");
    |   ----------------------------------------------------------- in this macro invocation

from drone-stm32-map.

Never mind, I'm silly. I did cargo build instead of just build

from drone-stm32-map.