esp-hal/examples
Easyoakland 30276e1609
implement wifi event handling with data (#2453)
* implement event handling for apsta{,dis}connect and probe

add to wifi_access_point example

* hide internal `Option` to simplify api

* move handler call logic to event.rs

* update_handler_leak

* - Add comments

- match simpler api from `std::panic::update_hook`

- do not assume size_of in prelude

- make all events handleable

- box static instead of leak

* update changelog

* elide lifetime on default handler

* newtypes for all event types.

* add doc to newtypes

* fix previous doc example

* - `get_handler` -> `handler`
- pass critical section to event handlers
- comment on perf of Box<ZST>
- don't pass `prev` in `update_handler`, instead call previous handler first unconditionally

* pass cs to dispatch_event_handler

* don't print "unhandled event" for handled events.
2024-11-13 08:49:41 +00:00
..
.cargo Expose CSI API in esp-wifi (#2422) 2024-11-08 16:33:13 +00:00
src implement wifi event handling with data (#2453) 2024-11-13 08:49:41 +00:00
build.rs Include ROM API symbols (#2374) 2024-10-22 10:02:49 +00:00
Cargo.toml Remove the integrated blocking networking stack (#2488) 2024-11-12 11:43:01 +00:00
README.md Improve and use timer abstractions (#1753) 2024-07-09 15:59:38 +00:00
rustfmt.toml Unify: Remove the chip-specific HAL packages, adapt esp-hal for direct use [1/?] (#1196) 2024-02-27 14:10:11 +00:00

Examples

This package contains a number of binary applications demonstrating the use of various hardware peripherals found within ESP32 the family of devices.

Each device has its own unique set of peripherals, and as such not every example will run on every device. We recommend building and flashing the examples using the xtask method documented below, which will greatly simplify the process.

To check if a device is compatible with a given example, check the metadata comments above the imports, which will list all supported devices following the //% CHIPS: designator. If this metadata is not present, then the example will work on any device supported by esp-hal.

As previously stated, we use the cargo-xtask pattern for automation. Commands invoking this tool must be run from the root of the repository.

Building Examples

You can build all examples for a given device using the build-examples subcommand:

cargo xtask build-examples esp-hal esp32

Note that we must specify which package to build the examples for, since this repository contains multiple packages.

Running Examples

You can also build and then subsequently flash and run an example using the run-example subcommand. With a target device connected to your host system, run:

cargo xtask run-example esp-hal esp32c6 hello_world

Again, note that we must specify which package to build the example from, plus which example to build and flash to the target device.

Adding Examples

If you are contributing to esp-hal and would like to add an example, the process is generally the same as any other project.

One major difference in our case is the metadata comments which state the compatible devices and required features for an example. Both of these designators are optional; if //% CHIPS: is omitted then all devices considered to be supported, and if //% FEATURES: is omitted then no features are enabled at build time.

To demonstrated, in src/bin/embassy_hello_world.rs you will see the following:

//% CHIPS: esp32 esp32c2 esp32c3 esp32c6 esp32h2 esp32s2 esp32s3
//% FEATURES: embassy esp-hal-embassy/integrated-timers

Another thing to be aware of is the GPIO pins being used. We have tried to use pins available the DevKit-C boards from Espressif, however this is being done on a best-effort basis.

In general, the following GPIO are recommended for use, though be conscious of whether certain pins are used for UART, strapping pins, etc. on some devices:

  • GPIO0
  • GPIO1
  • GPIO2
  • GPIO3
  • GPIO4
  • GPIO5
  • GPIO8
  • GPIO9
  • GPIO10