Document Requests

ESP_Angus
Posts: 953
Joined: Sun May 08, 2016 4:11 am

Re: Document Requests

Postby ESP_Angus » Mon Jul 17, 2017 12:16 am

robbym wrote:If I want to port the esptool.py to another language, is there a document somewhere specifying the protocol used to communicate with the ROM bootloader? Or do I have to infer it from the python source? I will do the latter if the former isn't available, but having documentation would speed up the process.


At the moment this is the case (infer it from the Python source.)

There is an out of date Wiki page here: https://github.com/espressif/esptool/wi ... l-Protocol but it predates esptool.py being an Espressif project, and doesn't cover ESP32 at all. I have been meaning to find time to update it, but haven't had time yet.

SteveOfTheStow
Posts: 3
Joined: Fri Jun 16, 2017 1:07 pm

Re: Document Requests

Postby SteveOfTheStow » Fri Feb 09, 2018 10:08 am

Is there any written protocol specification for developing an ESP-TOUCH client? The documentation here https://www.espressif.com/en/products/software/esp-touch/resources talks a bit about how it works at a very high level, and the API for the ESP32 and ESP8266, but there's nothing really describing the protocol a client has to send the SSID and password with. Would be nice to have that documented as opposed to reverse engineering it from the sample app.

ESP_Lvxinyue
Posts: 13
Joined: Fri Dec 25, 2015 6:13 am

Re: Document Requests

Postby ESP_Lvxinyue » Tue Feb 27, 2018 7:04 am

SteveOfTheStow wrote:Is there any written protocol specification for developing an ESP-TOUCH client? The documentation here https://www.espressif.com/en/products/software/esp-touch/resources talks a bit about how it works at a very high level, and the API for the ESP32 and ESP8266, but there's nothing really describing the protocol a client has to send the SSID and password with. Would be nice to have that documented as opposed to reverse engineering it from the sample app.


Hi, thanks for using the ESP-TOUCH technology. The protocol specification is not public.

User avatar
ninjaneer
Posts: 5
Joined: Mon Apr 02, 2018 5:15 pm

Re: Document Requests

Postby ninjaneer » Fri Apr 06, 2018 5:41 pm

ESP8266_SDKSSL_User_Manual_EN_v1.4.pdf as referenced at:

https://github.com/espressif/esp-idf/blob/master/examples/protocols/openssl_server/README.md

...is missing. I gave up and used mbedTLS directly based on their docs and examples.

michprev
Posts: 27
Joined: Fri Aug 04, 2017 8:57 pm

Re: Document Requests

Postby michprev » Sun Apr 15, 2018 5:20 pm

Documentation of functions implemented in ROM would be also nice.

Technical reference manual also does not correspond with ESP-IDF (many registers / register bits are missing).
E. g.:
  • DPORT_APP_CACHE_CTRL1_REG is missing (it is according to ESP-IDF very important to work around a hardware bug
  • how to set pad hold feature of GPIO32 / GPIO33 ?
  • how to set RTC function to RTC_GPIO / RTC_I2C ?
  • in RTCIO_RTC_GPIO_OUT_REG it is possible to set output value of some pins that are input only, that is kind of misleading
As I would like to implement a custom SDK I believe that there is more I am about to discover

EDIT
  • addresses of RTC registers are in sections 30.4 and 30.5 increased by 1 instead of 4
  • setting CPU frequency is not well documented (RTC8M and RTC_CLK need to be calibrated, how to do that? when changing CPU frequency there is needed to set DBIAS voltage - how to set it correctly?)
  • SPI flash options in SPI registers are not documented (e. g. SPI_FLASH_READ, SPI_FLASH_WREN in SPI_CMD_REG register)
  • as I have read here https://github.com/espressif/esp-idf/issues/1346#issuecomment-368740348 it is very unclear how to correctly setup SPI timing; I am missing info about SPI mode - DMA incompatibility

Who is online

Users browsing this forum: No registered users and 2 guests