7ca1b4376f
* Split PdmaChannel into two * Take &self in PDMA traits * Implement type-erased PDMA channels * Remove Degraded assoc type * Move degrade fns to base trait * Use PeripheralDmaChannel on constructors only * Remove WithDmaAes use * Erase DMA type params * Clean up examples/tests * Remove redundant trait bounds * Remove peripheral-specific DMA traits * Document i2s change * Clean up parl_io * Deduplicate InterruptAccess * Fix cfg * Implement runtime compatibility check * Clean up a bit * Document changes * Swap Channel type params, erase dma channel * Unsplit traits * Remove redundant cfg * Fix docs * Simplify DmaEligible * Remove unsafe code * Revert "Swap Channel type params, erase dma channel" This reverts commit 415e45e44b297fd3cb55b4261c9ce151cca4b9c9. * Allow different degraded DMA types * Allow converting into peripheral-specific DMA channel, use it for compat check * Erase PDMA types without AnyPdmaChannel * Hide degrade fns for now, remove from MG * Clean up SPI slave * Fix QSPI test * Fix mem2mem, fix S3 peripherals * Fix S2 * Remove AnyPdmaChannel * Remove PeripheralDmaChannel * Remove unnecessary degrade call
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