This commit updates the provision command to include the --device-key option. It also adds a second execution of this command with the only difference being the value of the flash-address. I noticed that this is done in ../preprovision.sh, but I don't understand why this is required , but I was not able to get the firmware to work without doing this.

I'm mainly opening this PR as question as I'm curious as to the "double" writing, can anyone help me understand that part?

Signed-off-by: Daniel Bevenius [email protected]

This commit adds a curl command to download the softdevice binary to the flashsd script.

The version of the softdevice has been changed in this commit as well as I was not able to find 7.3.0 in https://github.com/NordicSemiconductor/nRF5-SDK-for-Mesh/tree/master/bin/softdevice.

I'm probably missing something here as I was not able to find the 7.3.0 version and also that the sd binaries are gitignored, but my initial thought was that it would be nice to have the sd used checked in for the hackaton just in case there are any network issues at the venue.

This commit updates the revision of embassy-time and embassy-sync in infra/pre-provision to fix the following compilation error:

error[E0107]: this struct takes 1 generic argument but 2 generic arguments were supplied
  --> /.cargo/git/checkouts/btmesh-e14acedbce757b27/6840160/btmesh-device/src/lib.rs:34:27
   |
34 |     embassy_sync::signal::Signal<embassy_sync::blocking_mutex::raw::CriticalSectionRawMutex, T>;
   |                           ^^^^^^ expected 1 generic argument                                 - help: remove this generic argument
   |
note: struct defined here, with 1 generic parameter: `T`
  --> /.cargo/git/checkouts/embassy-9312dcb0ed774b29/3b58ac1/embassy-sync/src/signal.rs:31:12
   |
31 | pub struct Signal<T> {
   |            ^^^^^^ -

For more information about this error, try `rustc --explain E0107`. error: could not compile `btmesh-device` due to previous error

The commit also adds a rust-toolchain.toml to configure nightly rustc as currently there a number of compilation errors like the following two:

error[E0658]: generic associated types are unstable
   --> /.cargo/git/checkouts/embassy-9312dcb0ed774b29/b7d0944/embassy-sync/src/pipe.rs:450:9
    |
450 | /         type FlushFuture<'a> = impl Future<Output = Result<(), Self::Error>>
451 | |         where
452 | |             Self: 'a;
    | |_____________________^
    |
    = note: see issue #44265 <https://github.com/rust-lang/rust/issues/44265> for more information
    = help: add `#![feature(generic_associated_types)]` to the crate attributes to enable

error[E0658]: where clauses on associated types are unstable
   --> /.cargo/git/checkouts/embassy-9312dcb0ed774b29/b7d0944/embassy-sync/src/pipe.rs:450:9
    |
450 | /         type FlushFuture<'a> = impl Future<Output = Result<(), Self::Error>>
451 | |         where
452 | |             Self: 'a;
    | |_____________________^
    |
    = note: see issue #44265 <https://github.com/rust-lang/rust/issues/44265> for more information
    = help: add `#![feature(generic_associated_types)]` to the crate attributes to enable

   Compiling cargo_metadata v0.15.0
For more information about this error, try `rustc --explain E0658`.
error: could not compile `embassy-sync` due to 18 previous errors
warning: build failed, waiting for other jobs to finish...

• Document hackathon firmware
• Refactor to allow extending with more models and peripherals

Examples

• Enabling microphone and sending noise detection?
• Enabling accelerometer and detecting motion?
• Enable speaker and send sound?

Currently, the following compiler warnings is generated:

$ cargo build --release
   Compiling eclipsecon-gateway v0.1.0 (/eclipsecon-2022-hackathon/infra/gateway)
warning: unused variable: `i`
   --> gateway/src/gateway.rs:170:49
    |
170 | ...                   for i in 0..3 {
    |                           ^ help: if this is intentional, prefix it with an underscore: `_i`
    |
    = note: `#[warn(unused_variables)]` on by default

warning: `eclipsecon-gateway` (lib) generated 1 warning

This commit adds the --flash-address command line option for the provision binary it is a mandatory command line option. I've set this to the storage address of the microbit which seemed to be the right thing to do but hopefully someone will correct me if this is incorrect.

This commit adds instructions as comments to Cargo.toml about how to use a local checkout of drogue-iot/btmesh.

The motivation for this is that it might be helpful for users wanting to investigate the btmesh code by making local updates like adding logging etc.

This commit adds a single info level log statement to the firmware example.

The motivation for this is that I think it might be helpful for users to add their own logging when exploring/developing during the hackaton, and with this change they won't have to think about importing defmt::info.

This commit add an explicit import/use for btmesh_nrf_software::Driver.

The motivation for this is that for someone new it might not be obvious which crate the Driver used in main comes from.

The motivation for this is that these files show up as untracked files:

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	infra/meshd/lib/b67cef0dd1b2451fa54f8d34edba371b/node.json.bak
	infra/meshd/lib/fe8817cb1d0d4250b35de88939277c3a/node.json.bak

Applications should be well documented with a few examples/tasks that need completion by participants.

Key features to show:

• Handling cloudevents in microprofile and quarkus
• Accessing kafka directly?
• Developer experience deploying app to openshift?
• Running as serverless and using knative?