Merge pull request #81 from embassy-rs/esp32-example

Add example for esp32

.github/workflows/ci.yaml

@@ -31,7 +31,7 @@ jobs:
     needs: build
     strategy:
       matrix:
-        example: [nrf-sdc, serial-hci] #, apache-nimble]
+        example: [nrf-sdc, serial-hci, esp32] #, apache-nimble]
     steps:
       - uses: actions/checkout@v4
       - name: Add dependencies

README.md

@@ -17,9 +17,10 @@ The advantage of this split is that the Host can generally be reused for differe
 TrouBLE can use any controller that implements the traits from `bt-hci`. At present, that includes:
 
 * [nRF Softdevice Controller](https://github.com/alexmoon/nrf-sdc). Use [`nrf-softdevice`](https://github.com/embassy-rs/nrf-softdevice) for the time being if you want a production ready BLE Rust stack for nRF.
-* [Zephyr UART HCI](https://docs.zephyrproject.org/latest/samples/bluetooth/hci_uart/README.html).
+* [UART HCI](https://docs.zephyrproject.org/latest/samples/bluetooth/hci_uart/README.html).
 * [Raspberry Pi Pico W](https://github.com/embassy-rs/embassy/pull/2865) - This is still WIP and largely untested.
 * [Apache NimBLE Controller](https://github.com/benbrittain/apache-nimble-sys).
+* [ESP32](https://github.com/esp-rs/esp-hal).
 
 
 ## Current status

examples/esp32/.cargo/config.toml

@@ -0,0 +1,18 @@
+[target.riscv32imc-unknown-none-elf]
+runner = "espflash flash --monitor"
+
+
+[env]
+ESP_LOGLEVEL="INFO"
+
+[build]
+rustflags = [
+  # Required to obtain backtraces (e.g. when using the "esp-backtrace" crate.)
+  # NOTE: May negatively impact performance of produced code
+  "-C", "force-frame-pointers",
+]
+
+target = "riscv32imc-unknown-none-elf"
+
+[unstable]
+build-std = ["core"]