Page 2 of 7

Re: Document Requests

Posted: Sun Mar 26, 2017 2:43 pm
by bkgoodman
RTC watchdog is COMPLETELY undocumented. Seeing how it is the only mechanism to do an main system reset, the is very important to me. I saw a reference to some registers used

Re: Document Requests

Posted: Mon Mar 27, 2017 1:37 am
by ESP_Sprite
The RTC documentation in general is still a work-in-progress... if it's any help, the RTC watchdog, apart from the reset stages (which iirc do a SoC reset instead of a CPU reset), is exactly the same as the timer group watchdogs. Also, if you want to reset the chip, does the ROM function software_reset() not do what you want?

Re: Document Requests

Posted: Mon Mar 27, 2017 12:07 pm
by bkgoodman
I *really* need to the RTC watchdog - because I need my circuit to be able to perform a full-system-reset in the event of something bad happening. (It is being designed for installation in a 7/24 lights-out [remote] environment. I have already seen cases where some of the libraries - like Secure WiFi can crash on some edge cases. I need the chip to hard-reset itself out of such scenarios).

Re: Document Requests

Posted: Wed Mar 29, 2017 12:11 pm
by novalight
I would also appreciate a thorough documentation of TASK- and RTC-Watchdog. Our use case is the same as bkgoodman. Some of our products are used in really remote areas were user reset is not an option or would cause a technician to drive several hundreds of kilometers to do a manual reset.
Since we also have seen lockups after crashes (even with the option to "reboot on exception" set in sdkconfig) this pretty much ruins these product.
Of course we could still add a "hardware watchdog" by means of circuitry but that would add a really unpleasant layer of complexity to our products.

So I would request the WDT docs and also an example/best practice/guide or whatever on how to prevent lockups in software.

Re: Document Requests

Posted: Wed Mar 29, 2017 1:03 pm
by bkgoodman
Yep - Exactly what Novalight said ;-)

Re: Document Requests

Posted: Fri Jun 16, 2017 1:15 am
by rudi ;-)
Hi

there was a Wrover Guide Request in the past from me
now found and spottet in the wild :
first release 2017 05 is here
SP_Wrover_User_Guide_s.png
SP_Wrover_User_Guide_s.png (32.82 KiB) Viewed 9870 times
with SSC Command Reference

not sure when it comes to the resource of espressif document side
in the meantime you can take this
ESP-WROVER_User_Guide.pdf
User Guide PDF Version
English
(268.7 KiB) Downloaded 2394 times
best wishes
rudi ;-)

Re: Document Requests

Posted: Fri Jun 16, 2017 5:53 am
by aknkotts7256
Hello,

Just saw this thread. I'd like to request the pinout for the Geekcreit/DOIT esp32 VROOM-32 devkit V1, a "clean" version. doit.am posts no data for their product. The supplied pdf schematic makes it too difficult for quick pin reference when coding.

Thank you for the help,

Alex

Re: Document Requests

Posted: Wed Jul 12, 2017 6:16 pm
by raemond
I am looking for the certification guide (ESP32_Certification_and_Test_Guide__EN.pdf). I have seen it referenced in the forums but can't find it anywhere.

Re: Document Requests

Posted: Wed Jul 12, 2017 7:43 pm
by loboris

Re: Document Requests

Posted: Sun Jul 16, 2017 7:00 pm
by robbym
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.