Rust ESP32 Community Meeting 2024-02-01

[SergioGasquez]

Please add topics and links to this discussion.

The meeting is scheduled for 2nd February 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.75.0.0 - latest release with LLVM 17 and GCC 13 - https://github.com/esp-rs/rust-build/releases/tag/v1.75.0.0
• 1.76.0.0 - scheduled official release with LLVM 17 and GCC 13 - around 15th Februart 2024

ESP-IDF Releases

• Available releases of ESP-IDF: 5.2-beta2, 5.1.2, 5.0.5, 4.4.6, 4.3.7

Discontinued HW

• ESP32-S3-BOX, ESP32-S3-BOX-Lite - replaced by ESP32-S3-BOX-3
• ESP32-C3-LcdKit - alternative kits are available

Experiments

• ESP SPI Display Interface DMA
  • separation of original SPI DMA from @bjoernQ example to new crate
  • published as crate esp-display-interface-spi-dma
• ESP-BSP-RS - release 0.2.0 - update to new SPI Display interface with DMA
• ESP32 Buddy RS
  • added Wi-Fi NTP clock based on esp-clock-nostd
  • all examples updated to latest hal and esp-wifi 0.3.0
  • make sure to include feature dhcpv4 with esp-wifi 03.0., otherwise app might compile, but won't process the DHCP response in runtime
• ESP32 Language Lab - comparison between technologies
  • CI automated build and data gathering from meassurements from Wokwi simulation

Updates to Embedded HAL 1.0.0

• ESP32 LilyGo T5 ePaper
• ESP32-S3-BOX Convay's game of life
• RustZX-ESP32

Developer's tooling

• RustRover has support to Run examples directly from README, works well with Rust on ESP32
  • import of environment configuration is possible by calling open -na "RustRover 2023.3 EAP" from CLI (e.g. source of ESP-IDF or other env. variables)

[jessebraham]

ESP-PACS

• ESP32-P4: Patch the HP_SYS peripheral esp-pacs#184
• Patch the RTC_CNTL and RTC_IO peripherals of the ESP32-S2/S3's ULP cores esp-pacs#185
• Add updated SVD for ESP32-P4, remove old patches esp-pacs#187

ESP-HAL

• Do not invert ADC readings when using ESP32 esp-hal#1093
• Update to latest smart-leds-trait and smart-leds packages esp-hal#1094
• New package releases esp-hal#1098
  • https://crates.io/crates/esp-riscv-rt/0.6.1
  • https://crates.io/crates/esp-hal-common/0.15.0
  • https://crates.io/crates/esp-hal-smartled/0.8.0
  • https://crates.io/crates/esp32-hal/0.18.0
  • https://crates.io/crates/esp32c2-hal/0.13.0
  • https://crates.io/crates/esp32c3-hal/0.15.0
  • https://crates.io/crates/esp32c6-hal/0.8.0
  • https://crates.io/crates/esp32h2-hal/0.6.0
  • https://crates.io/crates/esp32s2-hal/0.15.0
  • https://crates.io/crates/esp32s3-hal/0.15.0
• Begin next release cycle esp-hal#1099
• Refactor the analog module esp-hal#1100
• Add initial support for the ESP32-P4 esp-hal#1101
• Use the document-features crate instead of manually writing package feature docs esp-hal#1107
• Update documentation/comments in soc::peripherals modules esp-hal#1108
• Combine the esp-ulp-riscv-hal and esp32c6-lp-hal packages esp-hal#1115
• Refactor DMA to make API more consistent across devices esp-hal#1125
• Unify: rename the esp-hal-common package to esp-hal [0/?] esp-hal#1131
• Rename the ADC constructor to new, make it infallible esp-hal#1133

MISCELLANEOUS

• Upstreamed patches and published new SVD for ESP32-P4

[SergioGasquez]

book

• Update probe-rs support book#139
• Add matrix room links book#141

esp-flasher-stub

• Add dprint flag in xtask and document pins esp-flasher-stub#47

esp-hal

• Update lp cores crates esp-hal#1119
• Reviewed a few PRs

esp-println

• Update README with latest esp-backtrace changes esp-println#81

espflash

• Unify configuration methods espflash#551
• Support different crystal frequencies bootloader espflash#553
• Add read-flash support espflash#558
• Add a changelog check in CI espflash#560
• Add before and after reset arguments espflash#561
• Windows: Set RTS before DTR to avoid issues espflash#562
• Fix lib compilation espflash#565
• Reviewed a few PRs
• HIL is still WIP
  • See Set up automated testing on hardware espflash#439 (comment)
• Once the open PRs get reviewed and merged, we will probably release 3.0.0-rc1

espup

• Update dependencies espup#413
• Bump MSRV espup#414
• Add CHANGELOG check action espup#415

no_std-training

• Update defmt project with esp-backtrace changes no_std-training#36

this-week-in-rust

• Add Rust on Espressif chips last quarter recap rust-lang/this-week-in-rust#5090

wokwi-builders

• Update base images for esp-rs builders wokwi/wokwi-builders#60

[bjoernQ]

probe-rs

• support a hart/core other than 0
  • RISC-V: Support hart != 0 probe-rs/probe-rs#2080

esp-ieee802154

• usual update of esp-hal etc.
  • Update esp-hal esp-ieee802154#19

esp-wifi

• starting with next release we will have release notes based on CHANGELOG.md
  • Add change log esp-wifi-sys#421
• release
  • https://crates.io/crates/esp-wifi-sys/0.3.0
  • https://crates.io/crates/esp-wifi/0.3.0

esp-pacs

• prepare P4's GPIO implementation
  • Align ESP32-P4's GPIO and IO_MUX esp-pacs#186

esp-hal

• review of Add LCD_CAM I8080 Driver esp-hal#1086
• initial GPIO support for ESP32-P4
  • ESP32-P4: Initial GPIO support esp-hal#1109
• initial support for interrupts on ESP32-P4
  • Initial support for CLIC esp-hal#1112
• efuse support for ESP32-P4
  • ESP32-P4: Enable efuse esp-hal#1114
• explore runtime interrupt binding
  • Runtime interrupt handler binding esp-hal#1121
• CI
  • check that all examples are checked in CI
    • Check examples are checked in CI esp-hal#1128
    • not gonna merge it but we will probably implement something similar after the HAL unification

esp-openthread

• update dependencies
  • Update dependencies esp-openthread#5

esp-backtrace

• cleanup
  • don't select any features in esp-println anymore
  • fix error when using it without the colors feature
  • Feature clean-up esp-backtrace#48
• improve the backtrace
  • Improve backtrace esp-backtrace#49

esp-template

• minor fix
  • Minor fixes esp-template#142

espflash

• fix SHA256 comparison failed
  • Re-calculate the bootloader's SHA256 espflash#567

[JurajSadel]

esp-hal

• finished and merged lp-uart: C6: Basic LP_UART driver esp-hal#1113
• rebased/updated lp-i2c, still in-progress

[ivmarkov]

esp-idf-svc/hal/sys

New releases last week! A few highlights:

• Require Rust 1.75
  • No longer need nightly Rust features (aside from -Z build-std)
  • Can be built with Rust stable too, but need a terribly looking __CARGO_TEST_CHANNEL_OVERRIDE_DO_NOT_USE_THIS env var set
• MQTT & event loop APIs simplified further
• Lots of new examples!

embedded-svc

Lost weight. Following traits (did anybody know about them??) no longer there:

• Ping, EventBus+Postbox, SysTime, Timer
• 99% of the "utilities" removed, including the asyncify adaptors which are now merged into esp-idf-svc directly

What is remaining?

• ??? Some IPv4 structures which are not in core::net
• Wifi trait + structures
• ??? Eth trait (do we need this??? it is basically just start/stop/is_up)
• OTA trait + structures
• HTTP client & server traits and structures
• MQTT client traits and structures
• WS send/receive traits and structures
• ??? "Storage" trait - this is really just key-value in disguise, perhaps we don't need this???

Topic for discussion: the future of embedded-svc

• Option A: Retire completely. It was not a smashing success anyway!
• Option B: Continue it somehow, but then:
  • Split into micro-crates yes/no? What would that give us?
  • What traits are useful and should remain there?
  • Remove heapless from the APIs? Might result in less ergonomic traits

=============

Side project: edge-net split into micro-crates and also released!

I think the project is getting in shape.Case in point: the HTTP client/server in there as well as the Websockets support are already more flexible, and useful (IMO of course!) than the ESP IDF ones, especially in async context.

We might need new traits contributed to embedded-nal-async though.

Time for espidf_time32?

Background: Currently when compiling for ESP IDF 5+, user needs RUSTFLAGS="--cfg espidf_time64

• ESP IDF 5 getting more popular than ESP IDF 4
• => For compiling on ESP IDF 5, user should no longer need to set a --cfg (IMO)
• => For compiling on ESP IDF 4, having a cfg is tolerable as it is falling out of popularity (I think)

Not requiring any --cfg for ESP IDF 5 is future-proofing our case for some day moving the *-espidf targets to Tier 2, which would mean that STD and libc will be built for the *-espidf targets upstream.