esp-rs/awesome-esp-rust + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/book + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/embedded-svc + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/embuild + repo issues and pull requests +
+ +Add support for PlatformIO `platform = native` #97 + [delan] + + +
this patch makes cargo-pio compatible with platform = native by making the changes in #96: + +mcu, pio_platform_dir,...
`platform = native` support? #96 + [delan] + + +
we have a project that can be built for both embedded and host platforms, using a second platformio env set to...
`embuild` shouldn't require `git` or `.git` to exist in order to build the project #81 + [svelterust] + + +
When trying following in NixOS, it fails because this crate expects .git to exist for $ESP_IDF:...
Support building with non-git repositories #95 + [denbeigh2000] + + +
This is a repackaging of the work originally done in #80 and #82. +This allows embuild to build non-git source...
esp-rs/esp-flash-loader + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/esp-flasher-stub + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/esp-generate + repo issues and pull requests +
+ +Error: Could not execute process `espflash flash --monitor ..` No such file or directory #63 + [3210jr] + + +
For a fresh new project, created with esp-generate --chip esp32s3 hello-esp. +Building with cargo build has no...
+Verify every dependency is required #65 + [mart-e] + + +
If not, the generated code will not work +Fixes #64
alloc is required for wifi? #64 + [mart-e] + + +
Steps to reproduce: +$ esp-generate --chip esp32 -o wifi myproject +$ cd myproject +$ cargo check +… + Compiling...
+esp-rs/esp-hal-community + repo issues and pull requests +
+ +smartled: updates for changes in the RMT driver #13 + [liebman] + + +
Updates for the changes in the RMT driver.
esp-rs/esp-hal + repo issues and pull requests +
+ +Resolve `C-METADATA` violations #2627 + [SergioGasquez] + + 1.0-blocker + +
See Cargo.toml includes all common metadata (C-METADATA), esp-hal is currently...
+[RFC] The value of `new_typed` vs always type erasing drivers #2572 + [MabezDev] + + RFC + 1.0-blocker + +
For our drivers we have the option of opting into the new_typed method to create a driver without type erasure, i.e...
+esp-hal: otg_fs: drop obsolete late cnak quirk #2621 + [kaspar030] + + +
Thank you for your contribution! +We appreciate the time and effort you've put into this pull request. +To help us...
+Add new function `esp_hal::try_init` #2618 + [speelbarrow] + + +
Thank you for your contribution! +We appreciate the time and effort you've put into this pull request. +To help us...
Don't require importing macro for esp-config #2630 + [bugadani] + + +
Fixes this: +error: cannot find macro `esp_config_int_parse` in this scope + -->...
Allow docs to show unstable features #2498 + [MabezDev] + + documentation + beta-blocker + +
We could simply do this with cfg(feature = "unstable"), but I think we can do better by using...
Unstable documentation proof of concept #2628 + [bugadani] + + documentation + skip-changelog + +
Closes #2498
RX/TX pin assignment in UART driver is done in the constructor instead of builder functions #2632 + [jessebraham] + + peripheral:uart + 1.0-blocker + +
Missing `Drop` implementation(s) for UART driver #2633 + [jessebraham] + + peripheral:uart + 1.0-blocker + +
`embassy_embedded_hal::SetConfig` needs to be gated with the unstable feature in UART driver #2635 + [jessebraham] + + peripheral:uart + 1.0-blocker + +
UART driver should follow naming conventions in order to be consistent across drivers #2636 + [jessebraham] + + peripheral:uart + 1.0-blocker + +
Some methods use <action>_tx eg (flush_tx), others (tx_fifo_count) +Some methods dont have undescore between TX/RX...
Add RS485 support to UART driver #2638 + [jessebraham] + + peripheral:uart + 1.0-blocker + +
Add IrDA support to UART driver #2639 + [jessebraham] + + peripheral:uart + 1.0-blocker + +
UART driver does not support autobaud functionality #2641 + [jessebraham] + + peripheral:uart + 1.0-blocker + +
UART driver does not support DMA mode #2642 + [jessebraham] + + peripheral:uart + 1.0-blocker + +
Not all UART hardware interrupts are supported/handled #2643 + [jessebraham] + + peripheral:uart + 1.0-blocker + +
UART driver does not support configuring SW/HW flow control #2644 + [jessebraham] + + peripheral:uart + 1.0-blocker + +
Test embassy-exector changes #2626 + [bugadani] + + +
Testing embassy-rs/embassy#3579 on HIL.
SDM is not supported yet #2646 + [bjoernQ] + + peripheral:gpio + 1.0-blocker + +
GPIO filter is not supported yet #2647 + [bjoernQ] + + peripheral:gpio + 1.0-blocker + +
Glitch filter is not supported yet #2648 + [bjoernQ] + + peripheral:gpio + 1.0-blocker + +
Direct CPU GPIO access is not supported yet #2649 + [bjoernQ] + + peripheral:gpio + 1.0-blocker + +
Using multiple GPIO interrupts is supported yet (e.g. 4 on P4) #2650 + [bjoernQ] + + peripheral:gpio + 1.0-blocker + +
Hysteresis Config is not supported yet (e.g. for P4) #2651 + [bjoernQ] + + peripheral:gpio + 1.0-blocker + +
It's possible to safely create pins "from thin air" #2653 + [bjoernQ] + + peripheral:gpio + 1.0-blocker + +
Problem: it's possible to safely create pins "from thin air" - e.g. let p1 = esp_hal::gpio::GpioPin::<9>; let p2 =...
PeripheralInput and PeripheralOutput are not sealed #2655 + [bjoernQ] + + peripheral:gpio + 1.0-blocker + +
PeripheralInput and PeripheralOutput are not sealed - however no one can currently build something useable with that
Address GPIO FIXME's #2656 + [bjoernQ] + + peripheral:gpio + 1.0-blocker + +
esp-hal/esp-hal/src/gpio/mod.rs + + + Line 898 + in + 7095576 + + + + + + + ...
Double check usage of unwrap / panic #2657 + [bjoernQ] + + peripheral:gpio + 1.0-blocker + +
There are two unwraps - one can never fail the other could (set_interrupt_priority) + + +There are a few explicit...
Overwritten default GPIO handler: currently no way to use async #2659 + [bjoernQ] + + peripheral:gpio + 1.0-blocker + +
See #2492 (comment)
Evaluate the `Peripheral` and `Peripheral` ref module #2661 + [MabezDev] + + api + 1.0-blocker + +
For various issues, documentation and soundness issue, for example are we affected by embassy-rs/embassy#2919
Possible interrupt footgun on multicore systems #1525 + [MabezDev] + + beta-blocker + +
Now that the interrupt is handled internally by the peripheral driver, the interrupt is configured for the core the...
Update to smoltcp 0.12.0 #2662 + [bjoernQ] + + package:esp-wifi + +
We unfortunately need (very few) code changes but it's not too much. +The blocking network stack used by the examples...
Mark unstable APIs #2499 + [MabezDev] + + api + beta-blocker + +
We need to mark APIs we're not stabilizing as such. These are all APIs except...
In init_output the condition to include the call to `disable_usb_pads` should be `#[cfg(usb_device)]` #2654 + [bjoernQ] + + peripheral:gpio + 1.0-blocker + +
Track async GPIOs in memory #2625 + [bugadani] + + +
Fixes #561 - even though that issue was closed without resolution. +Drive-by fixes #2654
+ + + + + Dominaezzz: Could this race against the user calling listen() on the other core?
+ + + ++ + + + + Dominaezzz: I think deadlock is possible with this code
+ +GPIO: Implement common traits #2664 + [playfulFence] + + peripheral:gpio + 1.0-blocker + +
From esp-hal API Guidelines: + +Where the guidelines suggest implementing Debug, defmt::Format should also be...
GPIO: `C-FAILURE` violation #2665 + [playfulFence] + + peripheral:gpio + 1.0-blocker + +
From Rust APU Guidelines: +C-FAILURE: Function docs include error, panic, and safety considerations. +We're somewhat...
I2C: `C-FAILURE` violation #2666 + [playfulFence] + + peripheral:i2c + 1.0-blocker + +
From Rust APU Guidelines: +C-FAILURE: Function docs include error, panic, and safety considerations. +We're good in...
Derive Builder Lite pattern for HAL configuration, update examples/tests #2645 + [jessebraham] + + +
ESP32-S2: UART Stop bit can be 3 bits long #2640 + [jessebraham] + + peripheral:uart + chip:esp32s2 + 1.0-blocker + +
+Stabilizing `CpuClock` #2663 + [MabezDev] + + RFC + 1.0-blocker + +
As part of #2499 +We're discussing how to stabilize the minimum amount. Or whether this should be stabilized at...
+Remove Dma[Rx|Tx]Buffer::length #2587 + [Dominaezzz] + + +
Thank you for your contribution! +We appreciate the time and effort you've put into this pull request. +To help us...
+UART: Enum variants should use `UpperCamelCase`. This is not true for `StopBits`. #2637 + [jessebraham] + + peripheral:uart + 1.0-blocker + +
Use upper camel case for UART's `StopBits` variants #2669 + [jessebraham] + + +
Closes #2637
UART driver's `set_rx_fifo_full_threshold` should use `cfg_if!` instead of multiple `#[cfg]`s #2634 + [jessebraham] + + peripheral:uart + 1.0-blocker + +
Use `cfg_if` in favour of multiple `cfg`s in `set_rx_fifo_full_threshold` function #2670 + [jessebraham] + + skip-changelog + +
Closes #2634
Stable driver analysis: I2C master #2493 + [MabezDev] + + peripheral:i2c + api + beta-blocker + +
As part of #2491, which has more details on driver analysis. +esp-hal API-GUIDELINE omissions + +The asynchronous...
+Add xtask subcommand to determine version change required based on `CHANGELOG.md` #2579 + [jessebraham] + + +
Example output (hardcoded to previous release to generate this, just as an example): +esp-alloc: minor +esp-backtrace:...
Stable driver analysis: UART #2495 + [MabezDev] + + peripheral:uart + api + beta-blocker + +
As part of #2491, which has more details on driver analysis. +esp-hal API-GUIDELINE omissions + + #2632 + #2633 + #2634 +...
+Mark some dependencies as unstable #2668 + [bugadani] + + skip-changelog + +
Even though the TWAI and USB serial drivers are unstable, marking the trait impls separately has some future...
+Hide most of the unstable peripherals #2667 + [bugadani] + + skip-changelog + +
There are a few annoying details, like how #[macro_export] refuses to work (workaround), and satellite crates, as...
SPI Master additional features #2503 + [Dominaezzz] + + peripheral:spi + +
The SPI Master is currently not exposing some hardware features. +I'm listing them here to begin with rather than...
+[RFC] Do we need a prelude? #2660 + [MabezDev] + + RFC + beta-blocker + +
It's shrunk considerably in the last year or two, maybe we can get away without having one at all?
Explore how private dependencies with `links = ` affect esp-hal #2589 + [MabezDev] + + RFC + 1.0-blocker + +
I'm slightly concerned that when we release 1.0 some of our deps may in inadvertently break esp-hal builds by...
+`embassy_embedded_hal::SetConfig` impl needs to be marked unstable #2675 + [bugadani] + + +
[RFC] Should config options affect the public API? #2509 + [MabezDev] + + RFC + package:esp-config + 1.0-blocker + +
Continuing the discussion from #2422 (comment) +We need to answer this question and then write the appropriate...
+RFC: Provide consistent APIs for configuring clock sources for peripheral drivers #1668 + [jessebraham] + + RFC + 1.0-blocker + +
From this project's inception we've just been hard-coding the clock source for peripheral drivers (usually just...
+Stable driver analysis tracking issue #2491 + [MabezDev] + + api + beta-blocker + +
Of the four drivers we're choosing to stabilize initially, we need to analyse them and determine a number of...
+Fix into_async/blocking on typed Spi #2674 + [bugadani] + + +
Closes #2673
Create non-trivial example applications which encapsulate all required dependencies and configuration #2596 + [jessebraham] + + examples + 1.0-blocker + +
This has been discussed internally, but I would like to open an issue to track progress on this and give a bit more...
+ + + + bjoernQ: Maybe when combined with good documentation the examples might replace...
+ +parl_io uses `InputConnection` instead of `PeripheralInput` #2658 + [bjoernQ] + + peripheral:gpio + 1.0-blocker + +
see #2492 (comment) +If a driver requires pins, those pins must be configured using +fn with_signal_name(self, pin:...
API-GUIDELINES tweaks #2677 + [bugadani] + + +
HIL(QOL): Use global timeout instead of timeout macros #2489 + [JurajSadel] + + skip-changelog + +
Reading / writing multiple GPIO pins in one go #2652 + [bjoernQ] + + peripheral:gpio + 1.0-blocker + +
Can be done with a separate driver that is initialized with multiple GPIO pins?
Stable driver analysis: GPIO #2492 + [MabezDev] + + peripheral:gpio + api + beta-blocker + +
As part of #2491, which has more details on driver analysis. +esp-hal API-GUIDELINE omissions + +Revisit: Private...
+ + + + bjoernQ: The API guidelines say: + + + + esp-hal/documentation/API-GUIDELINES.md + + + ...
+ ++ + + + bjoernQ: Modules we probably don't want to stabilize yet + +ETM +LP_IO +RTC_IO
+ +`RESERVED_INTERRUPTS` to be `INTERRUPT_TO_PRIORITY` #2676 + [playfulFence] + + skip-changelog + +
closes #2671
Incorrect RESERVED_INTERRUPTS list for PLIC? #2671 + [wisp3rwind] + + bug + +
I'm just browsing the code to understand interrupt handling in esp-hal better, and the following line looks off to...
+BLE and Wifi examples not working on ESP32S3. #1626 + [hydra] + + package:esp-wifi + chip:esp32s3 + +
Hi, +I'm testing the examples on board here, and none of the wifi or bluetooth examples that I tried work. +I was...
+ + + + tommasoclini: The ap example still doesn't work, is this going to be fixed?
+ ++ + + + tommasoclini: Rust analyzer is throwing erros of the kind: +[{ + "resource":...
+ +esp-backtrace: Add `coredump` feature #2672 + [bjoernQ] + + +
Thank you for your contribution! +We appreciate the time and effort you've put into this pull request. +To help us...
+ + + + MabezDev: We shouldn't do this unless we really have to, it pulls in core::fmt machinery
+ + + ++ + + + bugadani: unstable esp-hal already pulls in embedded-io
+ +Add priority-limited locks #2684 + [bugadani] + + skip-changelog + +
However, when it does, we can use it in embassy-executor to lock certain resources without affecting higher priority...
+DHCP support added to wifi embassy access point example #2683 + [tommasoclini] + + skip-changelog + +
Submission Checklist 📝 + + I have updated existing examples or added new ones (if applicable). + I have used cargo...
ESP32 SPI: Dummy phase is not handled correctly if there is no data phase #2240 + [bugadani] + + bug + peripheral:spi + chip:esp32 + 1.0-blocker + +
After #2231 the emulated address phase ignores dummy bits, which then get inserted to before the address is sent...
Can we avoid panicking in init_spi_data_mode? #2685 + [bugadani] + + peripheral:spi + 1.0-blocker + +
`#[non_exaustive]` missing on `esp_hal::spi::Error` #2680 + [bugadani] + + peripheral:spi + 1.0-blocker + +
The title was the original issue, but it was solved since. The following sub-point has not yet been resolved: + +DMA...
`#[non_exaustive]` missing on Half duplex enums `Command`, `Address` #2679 + [bugadani] + + peripheral:spi + 1.0-blocker + +
`Debug`/`Format` missing on the drivers `Spi` #2678 + [bugadani] + + peripheral:spi + 1.0-blocker + +
RFC: Mark `enum`'s and `Config` structs as `#[non_exaustive]` unless proven to be feature complete #2500 + [MabezDev] + + RFC + api + beta-blocker + +
Whilst this is technically already part of the API-guidlines, I've seen some pushback in doing this we lose the...
+Auto-implement Debug, PartialEq and defmt::Format for peripherals #2682 + [bugadani] + + +
Thank you for your contribution! +We appreciate the time and effort you've put into this pull request. +To help us...
Mention that config structs should derive `procmacros::BuilderLite` in the API guidelines #2686 + [jessebraham] + + +
Closes #2500
+SPI: one of the half-duplex modes is not supported #2687 + [bugadani] + + peripheral:spi + 1.0-blocker + +
I can't actually tell whether the half-duplex mode we support is 3 or 4-wire single-bit. Our data modes are defined...
+esp_wifi_set_country() called late #2689 + [liclac] + + bug + status:needs-attention + +
Bug description +If you construct a configuration which is not world-safe (allowed in the default country code of...
Stable driver analysis: SPI master #2494 + [MabezDev] + + peripheral:spi + api + beta-blocker + +
As part of #2491, which has more details on driver analysis. +Note: we are not stabilizing DMA support right...
+ + + + bugadani: With a GPIO, as they already do when using ExclusiveDevice.
+ +SPI and related changes #2681 + [bugadani] + + skip-changelog + +
Closes #2678 +Closes #2679 +Closes #2680 +Closes #2685
+Prevent creating GpioPin #2688 + [bugadani] + + +
Closes #2653
[DMA 8/8] Burst configuration #2543 + [bugadani] + + +
Thank you for your contribution! +We appreciate the time and effort you've put into this pull request. +To help us...
+ + + + + bjoernQ: maybe it's just me but internal and external are not very descriptive
+ + + ++ + + + bugadani: Not accidentally, those changes didn't work (yet)
+ ++ + + + Dominaezzz: Will those be coming in a subsequent PR or in this one?
+ ++ + + + bugadani: I don't intend to change this PR unless some issue comes up.
+ +esp-rs/esp-idf-hal + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/esp-idf-part + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/esp-idf-svc + repo issues and pull requests +
+ +gatekeep mdns ipv6 behind feature flag #523 + [indexds] + + +
Hello, +This is a very ugly hack so you most likely do not want to merge this as is, i'm open to working on any...
+ + + + ivmarkov: As per above, and everywhere below, #[cfg(esp_idf_lwip_ipv6)]
+ +Resolve log ambiguity #518 + [nullstalgia] + + +
Howdy. I've been using a lot from esp-rs's work recently, and I've been really impressed! The traits from...
Shouldn't EspNetifDriver be `pub` ? #524 + [Luctins] + + +
Shouldn't this line be pub mod ...? + + + + esp-idf-svc/src/netif.rs + + + Line 960 + in + ...
+ + + + ivmarkov: Oh. And you need features = ["experimental"] on the esp-idf-svc dependency.
+ ++ + + + ivmarkov: Closing - still - let me know if you have troubles.
+ +esp-rs/esp-idf-sys + repo issues and pull requests +
+ +esp32 wifi crash (brownout issue) #352 + [indexds] + + +
Hello, +I've been struggling for the past few hours with this. Running a simple wifi snippet as shown below results...
build cargo_driver: update embuild to support non-git `IDF_PATH` #353 + [denbeigh2000] + + +
Updates the version of embuild, and the way it gets invoked, so that we can make use of the changes in...
+ + + + + denbeigh2000: will update and un-draft following the merge of esp-rs/embuild#95
+ +Fails to build on Nix #184 + [svelterust] + + enhancement + +
I have everything setup except for the esp-idf which this crate should handle. However, when attempting to build, I...
+ + + + ChocolateLoverRaj: What issue is blocking you? Asking because the Nix devShell I have at...
+ +esp-rs/esp-idf-template + repo issues and pull requests +
+ +Python - dependencies conflict with esp-idf-kconfig #249 + [FssAy] + + +
Bug description + +I am getting a python error referring to a dependency conflict on building the template. +To...
error: Toolchain esp in path_project\rust-toolchain.toml is custom and not installed #250 + [zhenchuanpeng] + + +
2024-12-04T02:44:30.1924937+08:00 ERROR FetchWorkspaceError: rust-analyzer failed to load workspace: Failed to load...
esp-rs/esp-mbedtls + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/esp-openthread + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/esp-pacs + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/esp-rs.github.io + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/esp-rust-board + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/esp-web-flash-server + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/esp-wifi-sys + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/esp-wireless-drivers-3rdparty + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/espflash + repo issues and pull requests +
+ +Return of direct-boot #706 + [JohnnyZig] + + +
I like your tool, it is fast, simple, does the job and has UART monitor with reset. +But I am using it to flash bare...
esp-rs/espup + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/no_std-training + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/repo-activity-digest + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/rfc2217-rs + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/rust-build + repo issues and pull requests +
+ +LoadLibraryExW failes on libclang.dll #282 + [FssAy] + + +
When trying to run cargo build on Windows 10 after performing every step from the book I am getting an error: +Unable...
+ + + + FssAy: Fixed by downgrading to a lower espup version. +esp-rs/espup#440
+ +esp-rs/rust + repo issues and pull requests +
+ +Support for position independent code (PIC) #247 + [benhansen-io] + + +
I would like to use espressif/elf_loader to load an elf file with Rust code on the esp32s3 (xtensa) however elf...
+esp-rs/std-training + repo issues and pull requests +
+ +Nothing happening
+ +esp-rs/xtensa-toolchain + repo issues and pull requests +
+ +Failed to detect version of Xtensa Rust, reinstalling it #29 + [rowanfr] + + +
Whenever I try to use the default action from the ESP no-std template with act I keep running into the repeated...
+
+ + + + ivmarkov: I am myself a big fan of avoiding the MCU-flash+run step when developing firmware, so yeah - why...
+ +-
+
+
+ ++ + + + ivmarkov: I'm not sure this (pub) method is for now used by anything else but the pio builder, but - with...
+ +-
+
+
+ ++ + + + delan: ahh sorry, i didn’t see it was part of the public api. done in dea89a1 :)
+ ++ + + + ivmarkov: Thanks!
+ +