MicroPython on ESP-WROOM-32

[Pithon]

Hi all,

How do I install MicroPython on the ESP-WROOM-32 module using Windows?

Thanks.

[Roberthh]

You can do so using esptool.py v2.0, which is for instance here: https://github.com/espressif/esptool/tr ... 524b688ade
If you have a bar ESp32Wrrom, you have to connect an usb/serial adapter to rx/tx of UART0 and pull GPIO0 low for bootloading.
Development board may have the usb/serial already installed.
A precompiled imange can be found on the micropython download page http://micropython.org/download/
In case you want to install the esp-idf, of which esptool is a part of, look here: http://esp-idf.readthedocs.io/en/latest ... et-esp-idf
If you want to build the micropython binaries yourself, it might be easier to install a Linux VM as the development environment.

[wr300000]

done

[wr300000]

I'm using NodeMCU-32s (ESP WROOM-32), running esptool v2.0beta2, erased completed and flashed completed on esp32-20180523-v1.9.4-85-gdf9b7e8f.bin file. Everything is fine with positive screen response during flashing I didn't see any error during erasing and flashing MicroPython on my NodeMCU-32s.
Once I open PUTTY to communicate with my NodeMCU so It's looping by below texts. Could you suggest me on this error ? What should I do next ?

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:QIO, clock div:2
load:0x3fff0018,len:4
load:0x0aa0a20a,len:679547529
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:QIO, clock div:2
load:0x3fff0018,len:4
load:0x0aa0a20a,len:679547529
ets Jun 8 2016 00:22:57

[Roberthh]

Did you flash the binary at address 0x1000 ? So the command for flashing is something like:

python esptool. py --chip esp32 --port <portname> --baud 460800 write_flash -z --flash_mode dio --flash_freq 40m 0x1000 filename

[wr300000]

I've reflashed my NodeMCU-32s without holding IO0 sw, changed to latest esptool v2.3.1, changed to latest bin file so the result is good but still see some error message before getting Python prompt , please see below list. Could you kindly suggest more ?
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:4524
load:0x40078000,len:0
load:0x40078000,len:12720
entry 0x4007ad38
I (378) cpu_start: Pro cpu up.
I (378) cpu_start: Single core mode
I (378) heap_init: Initializing. RAM available for dynamic allocation:
I (382) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (388) heap_init: At 3FFC55E8 len 0001AA18 (106 KiB): DRAM
I (394) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (400) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (407) heap_init: At 40090794 len 0000F86C (62 KiB): IRAM
I (413) cpu_start: Pro cpu start user code
I (207) cpu_start: Starting scheduler on PRO CPU.
OSError: [Errno 2] ENOENT <-------- " WHAT DOES IT MEAN ? "
MicroPython v1.9.4-85-gdf9b7e8f on 2018-05-23; ESP32 module with ESP32
Type "help()" for more information.
>>>

[devnull]

OSError: [Errno 2] ENOENT <-------- " WHAT DOES IT MEAN ? "

When uPy starts up, it first runs boot.py and then main.py

If one of these files is missing your will get this 'warning' rather than error, so it's normal.

You can always create a dummy main.py file with just 'pass' and the warning will go away:

/main.py

Code: Select all

pass

[wr300000]

Thank you all, it's working...have a great day.

[Len]

I have been getting a bunch of repeating garbage on my PuTTy when I tried to connect to the ESP32. The addition of "--flash_freq 40m 0x1000" to the command line for esptool as suggested above fixed the problem. Thanks.

I know the 0x1000 is the offset into flash, but what is the 40m?

[Roberthh]

see the documentation of the esptool.py:

Flash Frequency (--flash_freq, -ff)

Clock frequency for SPI flash interactions. Valid values are keep, 40m, 26m, 20m, 80m (MHz). The default is keep, which keeps whatever value is already in the image file. This parameter can also be specified using the environment variable ESPTOOL_FF.

The flash chip connected to most chips works with 40MHz clock speeds, but you can try lower values if the device won't boot. The highest 80MHz flash clock speed will give best performance, but may cause crashing if the flash or board designis not capable of this speed.