Rust ESP32 Community Meeting 2024-05-23

[SergioGasquez]

Please add topics and links to this discussion.

The meeting is scheduled for 23th May 2024 - 5 pm CET/GMT+1 (a.k.a. Brno time) 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 Releases

• 1.77.0.0 - latest release with LLVM 17 and GCC 13 - https://github.com/esp-rs/rust-build/releases/tag/v1.77.0.0
• 1.78.0.0 - still as pre-release with LLVM 17 and GCC 13 - 29th May 2024 - scheduled promotion to latest release
  • Windows MSVC version cause problems in build, it was necessary to move head using master, so it contains more features than regular 1.78.0
• 1.79.0.0 - planned release with LLVM 17 - 15th June 2024

ESP-IDF Releases

• Available releases of ESP-IDF: 5.2.1, 5.1.3, 5.0.6, 4.4.7
• Upcomming release: 5.1.4

New books

• author: Omar Hiari
  • Simplified Embedded Rust: ESP Core Library Edition
  • Simplified Embedded Rust: ESP Standard Library Edition

Slint

• Oxidize workshop - Tuesday 28th May 2024

Events

• Oxidize - Berlin - 28th-30th May - https://oxidizeconf.com/
• DevCon 2024 - Call for speakers - https://devcon.espressif.com/
• Euro Rust - Vienna - 10th-11th Oct - https://eurorust.eu/

[SergioGasquez]

awesome-embedded-rust

• Update Espressif content rust-embedded/awesome-embedded-rust#450

book

• Add which series are Xtensa and Riscv book#160

esp-flasher-stub

• Prepare 0.3.0 release esp-flasher-stub#61

esp-hal

• Enable gpio::test_gpio_interrupt for Xtensa targets. esp-hal#1555

espflash

• Update stubs espflash#638

rust

• Add no_std Xtensa targets support rust-lang/rust#125141

wokwi-builders

• Fix esp builders wokwi/wokwi-builders#64

[georgik]

@bjoernQ @MabezDev Any update on DMA SPI support in new Bare Metal HAL?
Missing API is blocking update of graphical examples like https://github.com/georgik/esp32-conways-game-of-life-rs . AFAIK the only possible solution is to use older version of HAL before refactoring.

[JurajSadel]

esp-hal

1. added SPI Slave for S2: ESP32-S2: Add SPI Slave support esp-hal#1562
2. clean up after GPIO refactor: GPIO: Use Level enum instead of plain bool in constructors esp-hal#1574

[Vollbrecht]

embuild

• ⚡️ speed up submodule git clones embuild#86
• Impl custom tools parsing logic + export PATH creation embuild#85

esp-idf-sys

• fix esp-idf >= 5.3 esp-idf-sys#303
• 🗑️ cleanup deprecated idf 4.3 related code esp-idf-sys#305
• similar changes in esp-idf-hal/svc

esp-idf-hal

• multiple small fixes

esp-idf-svc

• contribution from AlixANNERAUD Add wrapper for SD/SDIO/SDMMC driver and vFS  esp-idf-svc#422
• multiple other small fixes provided by; jothan ,YouXam, torkleyy, Angelo13C, owenthewizard, DavidVentura, weiying-chen and more !!
• ivmarkov working on better BLE BLE/GATT bindings for Bluedroid esp-idf-svc#421

esp-idf-template

• Include cc fix by default now
• work upgrading it for new esp-idf releases

[georgik]

@Hahihula please drop an eye on embuild, some concepts might be also useful to your work with replacing Python dependency with Rust for the deployment of tooling. Especially on Windows this could save us from custom build of Python like this one - https://github.com/espressif/idf-python .

[Vollbrecht]

@Hahihula Feel free to ping me about it here or on matrix if you explore the space a bit. To make it a more manageable task we currently only reduced the export path complexity in embuild from previous versions. At that moment we still relight on the tools installer and a setup because we still need a working special python kconfig wrapper and the esp-idf-component manager.

Replacing the tools installer per se is not that complicated as i have a branch that does that completely, but in its current state its not worthwhile to integrate because the python dependency's for the esp-idf-component manager and kconfig still needs to be installed regardless.

So the goal would be to replace python kconfig wrapper with something rusty and than think about how the esp-idf-compnent manager can be handled. Keep in mind that both are currently heavily integrated into the cmake system.

[jessebraham]

SVD

• New SVDs for ESP32-C6/H2 with IEEE802154 registers included
  • https://github.com/espressif/svd/releases/tag/2024-05-09

ESP-PACS

• Add IEEE802154 registers for ESP32-C6 and ESP32-H2 esp-pacs#248

ESP-WIFI

• Generate bindings for IEEE802.15.4 radio on ESP32-C6/H2 esp-wifi-sys#467

ESP-IEEE802154

• Use esp-wifi-sys in place of blobs/binary module, use PAC instead of RAL esp-ieee802154#25

ESP-HAL

• Add additional HIL tests for UART esp-hal#1511
• [1/3] Timer abstraction: refactor systimer and timer modules into a common timer module esp-hal#1527
• Use esp-rs logo in docs and enable nightly feature in docs for esp-alloc esp-hal#1533
• Add a lint exception rule for unexpected_cfgs esp-hal#1539
• Refactor and clean up xtask package esp-hal#1540
• Update PACs and fix resulting errors, convert IEEE802154 from virtual to real peripheral esp-hal#1549
• Add the esp-ieee802154 package to the repository esp-hal#1554
• [2/3] Timer abstraction: add OneShotTimer/PeriodicTimer drivers, Timer trait esp-hal#1570
• Add the esp-println package to the repository esp-hal#1575
• Add the esp-backtrace package to the repository esp-hal#1583

[tom-borcin]

esp-rs changes

The esp-rs organization is undergoing changes to optimize repositories and Rust language support. The focus will shift from adding new devices to enhancing existing code bases and user experience, aiming to build a comprehensive Rust development stack. While continuing to support newer chips like ESP32-C6, development efforts will concentrate on the esp-hal repository. Other repositories will be maintained, archived if inactive, or merged for improved content management. This transition aims to minimize disruption and ensure accessible resources.

Feedback is welcomed through:

• Matrix channel: https://matrix.to/#/#esp-rs:matrix.org
• Biweekly community meetings. Next meeting can be found on: https://github.com/esp-rs/rust/discussions

You can read the full announcement here: Upcoming esp-rs changes