example: fix the compilation target to Cortex-M4F using hard floats

This fixes the issue of mismatched binary of Cryptocell310 and the nRF compilation target, making cryptocell310-based backend work in this example, as well. Using now the cryptocell310 backend by default.
openwsn-berkeley · Oct 25, 2024 · 7a6d147 · 7a6d147
1 parent d806f7a
commit 7a6d147
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/examples/lakers-nrf52840/.cargo/config.toml b/examples/lakers-nrf52840/.cargo/config.toml
@@ -3,7 +3,7 @@
 runner = "probe-rs run --chip nRF52840_xxAA"
 
 [build]
-target = "thumbv7em-none-eabi"
+target = "thumbv7em-none-eabihf"
 
 [env]
 DEFMT_LOG = "trace"
diff --git a/examples/lakers-nrf52840/Cargo.toml b/examples/lakers-nrf52840/Cargo.toml
@@ -34,7 +34,7 @@ cortex-m-rt = "0.7.0"
 panic-probe = { version = "0.3", features = ["print-defmt"] }
 
 [features]
-default = [ "crypto-psa", "ead-none" ]
+default = [ "crypto-cryptocell310", "ead-none" ]
 crypto-cryptocell310 = [ "lakers-crypto/cryptocell310" ]
 crypto-psa = [ "lakers-crypto/psa-baremetal" ]
 ead-none = [ ]