Rust ESP32 Community Meeting 2022-08-09

[georgik]

Please add topics and links to this discussion.

The meeting is scheduled for 9th August 2022 - 3 pm CEST/GMT+2 via Google Meet. The meeting invite is automatically sent to attendees of previous meetings. If you'd like to join, please notify us at https://matrix.to/#/#esp-rs-community-meetins:matrix.org

You can find information from the previous meeting at https://github.com/esp-rs/rust/discussions

If you find a topic exciting, click Arrow Icon or Emoji, and your vote will give the preference to the topic.

[georgik]

Rust Toolchain 1.63.0.0

• official release date changed due to regressions
• new official release of Rust toolchain: 11th August 2022
• our toolchain build finalization is scheduled for the 16th of August
• list of issues which should be solved for the release: https://github.com/esp-rs/rust-build/milestone/7

Experiments

• Spooky maze - bare metal - https://github.com/georgik/esp32-spooky-maze-game
  • fine-tuned Cargo.toml and build files to enable build for different targets/features from one source code
  • supported targets: ESP32, ESP32-S2, ESP32-S3, ESP32-C3
  • supported SPI displays: ST7789, ILI9341
  • note: still work in progress, the app displays just tiles and simple animation
  • idea: might be interesting to add multi-target support to templates, right now templates supports just single target

[ivmarkov]

Some offline updates (likely will not attend next meeting):

General (embedded-svc + esp-idf-*)

• Branching / development policy for the esp-idf-* + embedded-svc crates tightened up:
  • Tags for cargo Publish (thanks, @N3xed)
  • Next breaking versions live in branches named next; merge in master only when ready
  • master gets incremental backward-compatible changes only in-between merges of next
• New feature for all traits: "nightly" (orthogonal to "experimental")
  • Purpose: features (and only those) that require nightly compiler hidden behind this flag (e.g. async traits that need GAT)
• Branches next nearing completion, upcoming merges in a week or two. Likely will lift the "experimental" tags from the new HTTP client & server traits
• embedded-svc lost weight: edge-executor moved to a dedicated crate; all async utils are no longer copied from Embassy, but instead the new embassy-util crate of Embassy should be used by users directly (it is Embassy-executor agnostic)

embedded-nal-async

• FYI: Client TCP trait merged. Used by edge-net (see below)

edge-executor

• Executor suitable for ESP-IDF on top of async-task / smol; previous version used to be part of embedded-svc

edge-net

• Still very much WIP
• Former embedded-svc-impl
• no_std no-alloc async code for HTTP client, server, websockets
• Maybe MQTT in future?
• Optionally implements the embedded-svc traits for HTTP & WS

ESP-IDF async upstreaming

• Initiated upstreaming the custom patches to smol's polling and smol crates, as well as to socket2. For now only a small patch to libc submitted: Socket constants necessary for ESP-IDF support in socket2 rust-lang/libc#2864

Question

Any good ideas for replacing the edge- prefix in edge-frame/edge-net/edge-executor?

• edge- is a bit improper, as this code resides on the IOT device itself. embedded- too dull and implies "trait" crates, which these are not
• Perhaps tiny-?

[SergioGasquez]

Rust installer improvements for 1.63.0.0

• Add more test cases rust-build#126: Adds more test cases to the CI and splits the CI into two sets:
  • Small subset that gets executed on PRs and pushes that install the toolchain and build project templates
  • Big set of tests that get triggered manually (will be done before every release) with a lot more of corner cases covered.

Ferrous System training

• Feature/gitpod std-training#64 got finally merged
• Add wokwi simulation and web flashing support. std-training#89 waiting for review
• There are currently issues with wifi which are trying to solve with fix(bsc): wifi connection; need to wait until the status is right std-training#84

Other

• Devcontainer support, update instructions and environment p2mate/mch2022-rust-app#1: Comunity project for the MCH2022 badge
• Update project IDs MabezDev/wokwi-server#12
  • @MabezDev can we rerun the CI get updated binaries or generate a new release?
• Release Binary Assets failed for release 0.16.0 cargo-generate/cargo-generate#708: cross was making the CI that uploads release binaries assets fail.
  • I've created a PR that removes the failing step: Remove Smoke Test step cargo-generate/cargo-generate#721
    • It got merged but they haven't rerun the failed action
  • Both esp-template and esp-idf-template CI depends on those assets, hence, they are failing since that release.
  • I've created a PR on both templates that uses cargo install cargo-generate if the installation of the binary fails:
    • Update toolchain version to 1.62.1.0 and update cargo-generate installation methods esp-idf-template#50
    • Toolchain update, fix cargo-generate, and fix scripts esp-template#17
• Add projects awesome-esp-rust#3
  • Are we missing any interesting projects on awesome-esp-rust
• @dcoles is working on a Rust on ESP32 talk!

[N3xed]

esp-idf-sys

• Build extra components specified in manifest metadata esp-idf-sys#114
  • allow setting build configuration in Cargo.toml metadata
  • support building and generating bindings for extra esp-idf components
    • can be specified in Cargo.toml metadata
    • can be used to only build a component or to extend esp-idf bindings without building a component
• support to trim the esp-idf build by specifying the list of components to be built
  • Feature/specify built components esp-idf-sys#115
• improve documentation and README
• release 0.31.7
• started investigating esp-idf v5.0 build

embuild

• small additions for extra components feature
• release 0.30.2

esp-idf-svc, embedded-svc, esp-idf-hal

• add automatic release tagging on Publish action
• push release tags scraped from prior Publish runs
• rmt: Add support for transmitting rust iterators esp-idf-hal#113

[bjoernQ]

esp-hal

• PR to fix the issue reported here: SmartLedAdapter.write() hangs when using more than one LED esp-hal#120

  • Problem: RMT doesn't work if the pulse codes don't fit into one memory block
  • Only ESP32-C3 / ESP32-S3
  • PR: Make RMT TX larger than one block work on ESP32-C3 and ESP32-S3 esp-hal#143

• refactor SPI constructor

  • it was very inconvenient to leave out optional pins
  • also SCK is now optional

• user reported a problem with configuring pull-down on ESP32-C3 for some pins

  • did a fix which should fix that - the user still reports one pin to act funny but it works fine for me

• fix LEDC

  • user reported: the resulting frequency was totally different from what was configured
  • types were not exported in the HALs
  • now also lower frequencies are possible by using REF-TICK instead of APBClock when needed (done automatically)

esp-wifi

• looked into support for embassy-net

  • we should wait until embassy-net uses a compatible version of smoltcp

• various smaller changes

  • mainly replacing code with functionality we now have in esp-hal

esp-template

• update xtensa-lx-rt to 0.13.0

[MabezDev]

esp-wifi

• Fix order of magnitude error when creating timestamp esp-wifi-sys#44 - This means smoltcp timeouts / back-offs now work properly meaning DHCP etc should be more reliable.
• I also opened Handling AP disconnects esp-wifi-sys#45 to discuss making the examples more robust
• Side note, I'm not sure enough people are aware that we have bare metal wifi support, I still see it asked - maybe a separate post just about bare metal esp-wifi would be a good idea?

esp-hal

• perf: vectored interrupt improvements esp-hal#121
• Periodic support for SYSTIMER & TIMG is in the works but ran into an S2 issue [esp32s2] systimer example doesn't work esp-hal#140
• Discussion about where to implement the e-h-a traits - thanks for all the input! -Where should `embedded-hal-async` traits be implemented? esp-hal#126 (comment). I think async is a different paradigm to blocking + interrupts. I.e we should always offer a future-based approach to any event a user may wish to listen for. This probably means putting the async stuff behind a future.

compiler

• https://github.com/rust-lang/rust/tree/stable 1.63 release commit just got merged, will rebase the compiler after this meeting

[jessebraham]

ESP-HAL

• Eliminate the dependency on esp32c3-hal in esp-backtrace
  • only the TrapFrame struct was used, so we copied it (because it shouldn't change much, or at all)
  • Include the TrapFrame struct and eliminate dependency on esp32c3-hal esp-backtrace#2
• Refactored LEDC driver to reduce duplicated code
  • Refactor the LEDC driver to reduce duplicated code esp-hal#130
• Add jobs to the esp-hal CI workflow to verify the MSRV
  • Add jobs to the CI workflow to verify the MSRV esp-hal#133

ESPFLASH

• Merged "Consistently support binary partition tables"
  • Consistently support binary partition tables espflash#212
• Bumped some dependencies and fixed resulting build errors
  • Bump dependencies and fix resulting build errors espflash#213
• Check if a new version is available upon invocation
  • Check if a new version if available upon invocation espflash#214