Module shutting down when wifi is used
Posted: Sat Jul 20, 2019 8:56 am
I am using the following dev kit from geekworm which is based on WROVER.
http://www.raspberrypiwiki.com/index.ph ... R-i_DevKit
When I try simple examples from esp-idf, everything is working great.
I get problems when I try one of the Wifi examples, for example the "station" example here:
https://github.com/espressif/esp-idf/tr ... ed/station
The serial connection dies and it seems that the module is constantly restarting itself:
It is not an ordinary restart as usually the serial connection does not disconnect.
I have read that this could be caused by power issues during wifi manual callibration, but this is a devkit with voltage regulator and capacitor and I suppose that they designed it for wifi usage, otherwise it would be pointless to use ESP32.
http://www.raspberrypiwiki.com/index.ph ... R-i_DevKit
When I try simple examples from esp-idf, everything is working great.
I get problems when I try one of the Wifi examples, for example the "station" example here:
https://github.com/espressif/esp-idf/tr ... ed/station
The serial connection dies and it seems that the module is constantly restarting itself:
It is not an ordinary restart as usually the serial connection does not disconnect.
$ make monitor
Toolchain path: /home/artium/esp/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc
Toolchain version: crosstool-ng-1.22.0-80-g6c4433a
Compiler version: 5.2.0
Python requirements from /home/artium/esp/esp-idf/requirements.txt are satisfied.
MONITOR
--- idf_monitor on /dev/ttyUSB0 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Ju
�8 20L��Ғ�:57��Hrs�'�� (�]I=9_RESEU����:0x33BSPI_TMQ}1SH_Bϊ�j
c�˥�ͥ�: 0, *�]A鰕�5
ck�E���0x00,�E���0�0,d_���0x�,cs0E���0A0,hdE���0�0,wp_���0x�
m�V�"%=1 clo�-"���2
l�X����fff00L�len'SHloX���������len:6LM�H��+��0����0,leK���j
loX����008040blen:��j
Y����0x4008��SH�I (28) boot: ESP-IDF v3.2.2 2nd stage bootloader
I (28) boot: compile time 03:08:54
I (32) boot: Enabling RNG early entropy source...
I (33) boot: SPI Speed : 40MHz
I (37) boot: SPI Mode : DIO
I (41) boot: SPI Flash Size : 4MB
I (45) boot: Partition Table:
I (49) boot: ## Label Usage Type ST Offset Length
I (56) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (63) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (71) boot: 2 factory factory app 00 00 00010000 00100000
I (78) boot: End of partition table
I (83) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x13fc0 ( 81856) map
I (120) esp_image: segment 1: paddr=0x00023fe8 vaddr=0x3ffb0000 size=0x02e8c ( 11916) load
I (125) esp_image: segment 2: paddr=0x00026e7c vaddr=0x40080000 size=0x00400 ( 1024) load
0x40080000: _WindowOverflow4 at /home/artium/esp/esp-idf/components/freertos/xtensa_vectors.S:1779
I (127) esp_image: segment 3: paddr=0x00027284 vaddr=0x40080400 size=0x08d8c ( 36236) load
I (151) esp_image: segment 4: paddr=0x00030018 vaddr=0x400d0018 size=0x62364 (402276) map
0x400d0018: _stext at ??:?
I (292) esp_image: segment 5: paddr=0x00092384 vaddr=0x4008918c size=0x06e20 ( 28192) load
0x4008918c: xEventGroupWaitBits at /home/artium/esp/esp-idf/components/freertos/event_groups.c:338
I (314) boot: Loaded app from partition at offset 0x10000
I (314) boot: Disabling RNG early entropy source...
I (314) cpu_start: Pro cpu up.
I (318) cpu_start: Starting app cpu, entry point is 0x40080ffc
0x40080ffc: call_start_cpu1 at /home/artium/esp/esp-idf/components/esp32/cpu_start.c:246
I (0) cpu_start: App cpu up.
I (328) heap_init: Initializing. RAM available for dynamic allocation:
I (335) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (341) heap_init: At 3FFB8D78 len 00027288 (156 KiB): DRAM
I (347) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (354) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (360) heap_init: At 4008FFAC len 00010054 (64 KiB): IRAM
I (366) cpu_start: Pro cpu start user code
I (49) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (135) wifi station: ESP_WIFI_MODE_STA
I (135) wifi: wifi driver task: 3ffc09c8, prio:23, stack:3584, core=0
I (135) wifi: wifi firmware version: 693c7b6
I (135) wifi: config NVS flash: enabled
I (145) wifi: config nano formating: disabled
I (145) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (155) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (195) wifi: Init dynamic tx buffer num: 32
I (195) wifi: Init data frame dynamic rx buffer num: 32
I (195) wifi: Init management frame dynamic rx buffer num: 32
I (195) wifi: Init management short buffer num: 32
I (205) wifi: Init static rx buffer size: 1600
I (205) wifi: Init static rx buffer num: 10
I (215) wifi: Init dynamic rx buffer num: 32
Exception in thread Thread-2:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/threading.py", line 754, in run
self.__target(*self.__args, **self.__kwargs)
File "/home/artium/esp/esp-idf/tools/idf_monitor.py", line 130, in _run_outer
self.run()
File "/home/artium/esp/esp-idf/tools/idf_monitor.py", line 220, in run
data = self.serial.read(self.serial.in_waiting or 1)
File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 501, in read
'device reports readiness to read but returned no data '
SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
I have read that this could be caused by power issues during wifi manual callibration, but this is a devkit with voltage regulator and capacitor and I suppose that they designed it for wifi usage, otherwise it would be pointless to use ESP32.