Documentation for ESP32 Port

[MisterWho]

Hi everyone!

I am rather new to micropython and having difficulties using micropython. I found the official documentation http://docs.micropython.org/en/latest/
Some weeks ago it was possible to change between the boards (PyBoard, WiPy,...). Now it is impossible to change between the boards, because the option disappeared. Reading through forums and discussions on GitHub I am missing a lot of documentation or the ducumentation from the above link is incorrect. For example:
- calss UART: You can find it unter "Libraries specific to the pyboard". But it also works under ESP32.
- class ADC: Neither a reference about the ESP32 nor that the written doc is only for the wipy. I noticed it, because the link there points to a wipy pinout table. No hint about the ESP32 spefic adc configuration with ADC.ATTN_6DB

I can find detailed information abou the ESP32 and his adc here: https://github.com/loboris/MicroPython_ ... o/wiki/adc

But if I try to initialise the adc as suggested there it gives me errors as the micropython version is somehow different.

Don't get me wrong! I like micropython but I am having difficulties in using it.

Or do I miss a documentation somewhere else?

Best regards
Joachim

[jickster]

Documentation is not a high priority.


Sent from my iPhone using Tapatalk Pro

[jickster]

If you can read C code, look at it.


Sent from my iPhone using Tapatalk Pro

[kevinkk525]

Well in that case I guess you should just use the loboris fork of micropython for esp32 as that port at least has some good documentation for most of the important differences in the esp32

[fdufnews]

There is no documentation for ESP32. Usually the ESP8266 one do the trick.
You only have access to documentation for the pyboard because you are in the "latest" release.
Select "1.9.4", you will then be able to choose between different boards.

[jedie]

It seems that LoBo fork is the best choice for ESP32 boards, ins't it?

What's the reason it's not being pull back to mainline microPython?

[jickster]

It seems that LoBo fork is the best choice for ESP32 boards, ins't it?

What's the reason it's not being pull back to mainline microPython?

Not enough developers. There’s very necessary open issues from 2 years ago that are still in discussion stage.


Sent from my iPhone using Tapatalk Pro

[Roberthh]

I do not think that it's the best port. In my view, it is just another port. It contains things like ftp and telnet, which could as well be in the base version, like you find in in the CC3200 implementation or in the PyCom branch. Other stuff is overfeatured beyond a minimal base.
But is is an impressive amount of work being done, and the documentation is very good.

[wr300000]

Is there any kind ETA for using ADC function on ESP32? I'm using both with PSRAM and w/o PSRAM boards. Still can not be initialized ADC pin 35. (using pin 35 to avoid conflict of Wifi connection and hall sensor and also Lolin D32 pro V2 had wired pin 35 on battery voltage measure internally)

MicroPython v1.9.4-757-g39eef2708 on 2018-12-17; ESP32 module with ESP32 (WROVER chip)
Type "help()" for more information.
>>> now()
Thr 20 DEC 2018 - 14 : 44 Bangkok Thailand
>>> import machine
>>> a=machine.ADC(35)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: expecting a pin

MicroPython v1.9.4-674-g27ca9ab8b on 2018-10-27; ESP32 module with ESP32 (WROOM-32 chip)
Type "help()" for more information.
>>> now()
Thr 20 DEC 2018 - 14 : 47 Bangkok Thailand
>>> import machine
>>> a=machine.ADC(35)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: expecting a pin

[mattyt]

>>> import machine
>>> a=machine.ADC(35)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: expecting a pin

I know that sometimes the error messages aren't fantastic but, in this case it's spot-on:

Code: Select all

MicroPython v1.9.4-725-gd690c2e14 on 2018-12-09; ESP32 module with ESP32
Type "help()" for more information.
>>>
>>> import machine
>>> a = machine.ADC(35)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ValueError: expecting a pin
>>> a = machine.ADC(machine.Pin(35))
>>> a.read()
14

Now, whether ADC should also accept an int to infer a Pin is open for debate - but at least that should get you going.