# Organization Overview - esp-rs **January, 2023** This a collection of repositories from within the `esp-rs` organization that I feel are the main points of interest. I've included any ongoing projects as much as possible. A repository be omitted from this list does _not_ mean that it is not important or useful, only that it requires much less development effort than other projects. ### HARDWARE SUPPORT - https://github.com/esp-rs/embedded-svc #### `std` - https://github.com/esp-rs/esp-idf-hal - https://github.com/esp-rs/esp-idf-sys - https://github.com/esp-rs/esp-idf-svc **Current Projects:** - Add support for new devices - Slim-down: only pay for what you use: i.e. if I only use e.g. the ESP IDF HAL drivers and don't use STD (posix, LwIP networking, event loop), I should get a much smaller firmware size. Not sure that's the case right now? ESP IDF is kind of going in that direction recently, I think - Mix and match `esp-*` (the `no_std` ecosystem) with `esp-idf-*` (the std ecosystem); possible? hurdles? what is the gap? - Using esp-hal for ULP/LP programming? - Async story: - Upstream the ESP IDF async support for the `smol-rs` crate ecosystem and for `socket2` (networking) - Async story for the ESP IDF HAL drivers (spi, i2c, uart, etc.) - Make sure `embassy works` on top of the std stack - ESP-IDF - More support for ESP IDF components that live out-of-tree (outside the ESP IDF repo) - Unclear: any outstanding build issues? Stuff that we want to improve in esp-idf-sys - Improve documentation for all packages #### `no_std` - https://github.com/esp-rs/esp-pacs - https://github.com/esp-rs/esp-hal - https://github.com/esp-rs/esp-wifi **Current Projects:** - Add async support to `esp-hal` (`no_std`) - GitHub Project: https://github.com/orgs/esp-rs/projects/3 - Low-power/deep-sleep and ULP support in `esp-hal` - `esp-wifi` - Continue adding chip support - improve quality and usability of library - add AP support - add async support - add esp-now support - Implement IEEE802.15.4 suppport - ESP32-C6 support - ESP32-H2 support - Refactor GPIO to firstly address [#115](https://github.com/esp-rs/esp-hal/issues/115) and secondly to fully hide the implementation details (@mabez) has some ideas on this. - Track and refine which reexports we need from esp-hal-common, in the chip hals. Relevant issue: [#339](https://github.com/esp-rs/esp-hal/issues/339) - More of a compiler issue, but being able to link all our projects with LLD would be very nice. Will free us from the GCC toolchain. ### TOOLING - https://github.com/esp-rs/espflash - https://github.com/esp-rs/espup - https://github.com/esp-rs/esp-template **Current Projects:** - Release new major versions, `cargo-espflash@2.0.0` and `espflash@2.0.0` - Milestone: https://github.com/esp-rs/espflash/milestone/1 - This is currently in the release candidate stage, with `2.0.0-rc.3` being the most recent version - Other than fixing a few small bugs I think this is quite close to being complete - Stabilize and generally improve `espup`. ([What is the future of espup?](https://github.com/esp-rs/espup/discussions/154#discussioncomment-4767616)) - Add a feature to allow installing standalone components like ESP-IDF Windows drivers - Add support for new devices - `esp-template`: Support new chips and [refactor](https://github.com/esp-rs/esp-template/issues/45) ### DOCUMENTATION - https://github.com/esp-rs/book **Current Projects:** - Overhaul the book; better organization, add additional and more clear information - Tracking issue: https://github.com/esp-rs/book/issues/59