ESP32 Forum

Hi all,

To address some questions about our plans for particular features and associated timelines, we post here the list of high-level features planned for ESP-IDF 1.0. Target release date for 1.0 is November 30. Each feature will appear in ESP-IDF master branch as soon as it is integrated, which may happen before the actual release date. Some features which are not on the list may be prioritized and some features on the list may be dropped, but this is roughly what we are aiming for. Note that the list below doesn't include bug fixes, which are too numerous to list.

Disclaimer: this feature list is for information purposes only. It is not a commitment to deliver the features. Espressif Systems shall not be held liable for any change in release plan or schedule. Order of items in the list does not indicate priority.

• Secure boot and flash encrypt support, including documents and host side tools
• Device abstraction layer for file descriptors
• Support for filesystems (SPIFFS or FAT — TBD)
• Newlib time syscalls support
• Partition read/write/erase API
• Use hardware bigint/SHA engine in mbedTLS
• Hardware random number generator API
• OTA library
• RF init and calibration data handling
• Openssl compatibility layer around mbedTLS
• New peripheral drivers: uart/timer 1&2/sigmadelta/pluse CNT/i2c/rmt/rtc gpio/epwm/adc/dac/touch/spi/motor pwm/i2s/uhci.
• Ethernet support
• mDNS library
• Clean up debugging output in libraries
• WPS support
• WPA2-Enterprise(TLS/PEAP) support
• Power saving (modem sleep)
• WiFi APIs clean up (function and type names, return values)
• BLE host
• Generic BLE profile for WiFi configuration
• We chat BLE profile for WiFi configuration
• Other common BLE profiles (battery, HID)
• BT host
• BT A2DP/AVRCP profiles
• BT HID profile
• Support WiFi/BT coexistence
• Optimize BT DRAM usage
• API documentation for ESP-IDF (except third party components)

So much feature! So win!

What about:

• CAN peripheral
  BLE dual role, scatternet
  ULP FSM
  IRAM optimization
  Task stack size optimization & tools
  SPI/SDIO slave firmware & Linux driver

Thanks!

Any plan about DMA and external RAM?

Would very much like to see SPIFFS but in fact give me flash APIs I can port it in one day.

FAT is good for SDCARD though.

CAN and ULP are not on the list for 1.0 at the moment, as are all the optimisations (beyond trivial ones).

Is far as i can tell, DMA is implemented on a case by case basis for each peripheral. There is a common part for all drivers, it should be part of the release as well.

For external SPI RAM (as in, "mapping it into address space" feature), please wait for the errata document and related announcements.

Regarding filesystems, yes, porting actual filesystems and integrating them with C library should be a trivial task as soon as two features (partition table APIs and virtual filesystem APIs) are merged. Both are implemented and are at the end of review-merge flow.

I2S interface is really important to my project, hope to see it soon in master branch!!!

Maybe a long-shot, but how about an optimized libsodium for Ed25519, or maybe even with hardware acceleration if that's possible? Probably not for 1.0 since it's less used, but it's becoming more popular.

Libsodium is certainly a possibility. I have a rough and dirty port of micro-ecc (which replaces modular multiplication with a hardware based one), which took two days to do. I can imagine that doing something similar with libsodium should not be difficult.

Well that would be sweet!

Also -don't mean hijack, I can't send PMs- I've been experimenting with using AVRNaCl (https://munacl.cryptojedi.org/atmega.shtml) on the ESP8266. With that code it takes 500ms to do a crypto_box_open() running @160MHz. So too long for frequent use. Would your micro-ecc port have any relevance to the 8266 (i.e. apart from the HW accelerators)?

Congrats on this project, I am really enjoying using it! I was just following up to see if you are still on track for Nov 30? I have a project that needs SPI and WiFi AP support. I was wondering how these things were progressing?

The components which have been postponed for the next release are: motor PWM driver, EPWM driver, UHCI (=UART DMA) driver.

I am not sure about mDNS, and BT classic profiles — some of these may also end up being postponed.

For the rest of points, we are on track for the next week's release.