ESP32 WROOM Mesh problem

nigno21
Posts: 5
Joined: Sat Aug 04, 2018 1:26 am

ESP32 WROOM Mesh problem

Postby nigno21 » Sat Aug 04, 2018 1:48 am

Hi to all,
I'm following the official esp-idf examples for create a mesh network.
I'm using the internal_communication example, in which I have configured the following parameters with

Code: Select all

make menuconfig
(10) channel
(PocketCube-8F1A) Router SSID
(myrouterpassword) Router password
Mesh AP Authentication Mode (WIFI_AUTH_OPEN) --->
(MAP_PASSWD) Mesh AP Password
(6) Mesh AP Connections
(6) Mesh Max Layer
(50) Mesh Routing Table Size
(PARENT_SSID) Parent SSID

When I start the application on my two nodes, the connection of the root node with AP won't create...
Here the logs:

Code: Select all

root@anto-Studio-XPS-1340:~/esp/3.1/esp-idf/examples/mesh/internal_communication# make flash monitor
Flashing binaries to serial port /dev/ttyUSB0 (app at offset 0x10000 )...
esptool.py v2.5.0
Serial port /dev/ttyUSB0
Connecting........__
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core
MAC: 30:ae:a4:15:30:b8
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 4MB
Flash params set to 0x0220
Compressed 21184 bytes to 12565...
Wrote 21184 bytes (12565 compressed) at 0x00001000 in 1.1 seconds (effective 152.8 kbit/s)...
Hash of data verified.
Compressed 702960 bytes to 428593...
Wrote 702960 bytes (428593 compressed) at 0x00010000 in 37.8 seconds (effective 148.8 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 103...
Wrote 3072 bytes (103 compressed) at 0x00008000 in 0.0 seconds (effective 1654.3 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
MONITOR
--- idf_monitor on /dev/ttyUSB0 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_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:5852
load:0x40078000,len:9076
load:0x40080400,len:6148
entry 0x40080748
I (28) boot: ESP-IDF v3.2-dev-362-g1c7a8b3b 2nd stage bootloader
I (28) boot: compile time 03:18:42
I (29) boot: Enabling RNG early entropy source...
I (34) boot: SPI Speed      : 40MHz
I (38) boot: SPI Mode       : DIO
I (42) boot: SPI Flash Size : 4MB
I (47) boot: Partition Table:
I (50) boot: ## Label            Usage          Type ST Offset   Length
I (57) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (65) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (72) boot:  2 factory          factory app      00 00 00010000 00100000
I (80) boot: End of partition table
I (84) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x1a84c (108620) map
I (131) esp_image: segment 1: paddr=0x0002a874 vaddr=0x3ffb0000 size=0x035c0 ( 13760) load
I (137) esp_image: segment 2: paddr=0x0002de3c vaddr=0x3ffb35c0 size=0x00000 (     0) load
I (138) esp_image: segment 3: paddr=0x0002de44 vaddr=0x40080000 size=0x00400 (  1024) load
0x40080000: _iram_start at /home/anto/esp/esp-idf/components/freertos/xtensa_vectors.S:1685

I (147) esp_image: segment 4: paddr=0x0002e24c vaddr=0x40080400 size=0x01dc4 (  7620) load
I (159) esp_image: segment 5: paddr=0x00030018 vaddr=0x400d0018 size=0x7d5b0 (513456) map
0x400d0018: _stext at ??:?

I (344) esp_image: segment 6: paddr=0x000ad5d0 vaddr=0x400821c4 size=0x0e3e0 ( 58336) load
0x400821c4: _xt_panic at /home/anto/esp/esp-idf/components/freertos/xtensa_vectors.S:354

I (369) esp_image: segment 7: paddr=0x000bb9b8 vaddr=0x400c0000 size=0x00000 (     0) load
I (369) esp_image: segment 8: paddr=0x000bb9c0 vaddr=0x50000000 size=0x00000 (     0) load
I (385) boot: Loaded app from partition at offset 0x10000
I (385) boot: Disabling RNG early entropy source...
I (387) cpu_start: Pro cpu up.
I (391) cpu_start: Starting app cpu, entry point is 0x40081018
0x40081018: call_start_cpu1 at /home/anto/esp/esp-idf/components/esp32/cpu_start.c:225

I (0) cpu_start: App cpu up.
I (401) heap_init: Initializing. RAM available for dynamic allocation:
I (408) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (414) heap_init: At 3FFBAA40 len 000255C0 (149 KiB): DRAM
I (420) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (427) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (433) heap_init: At 400905A4 len 0000FA5C (62 KiB): IRAM
I (439) cpu_start: Pro cpu start user code
I (122) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (266) wifi: wifi driver task: 3ffc2194, prio:23, stack:3584, core=0
I (266) wifi: wifi firmware version: e4d8ac5
I (266) wifi: config NVS flash: enabled
I (266) wifi: config nano formating: disabled
I (276) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (286) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (316) wifi: Init dynamic tx buffer num: 32
I (316) wifi: Init data frame dynamic rx buffer num: 32
I (316) wifi: Init management frame dynamic rx buffer num: 32
I (316) wifi: Init static rx buffer size: 1600
I (316) wifi: Init static rx buffer num: 10
I (326) wifi: Init dynamic rx buffer num: 32
I (386) phy: phy_version: 3910, c0c45a3, May 21 2018, 18:07:06, 0, 0
I (396) wifi: mode : sta (30:ae:a4:15:30:b8) + softAP (30:ae:a4:15:30:b9)
I (396) mesh: <nvs>error in read layer, err:0x1102
I (396) mesh: <nvs>error in read assoc, err:0x1102
I (1386) wifi: Set ps type: 0

I (1396) mesh_main: <MESH_EVENT_STARTED>ID:77:77:77:77:77:77
I (1396) mesh_main: mesh starts successfully, heap:185232, root not fixed

I (1756) mesh: [SCAN][ch:10]AP:1, otherID:0, MAP:0, idle:0, candidate:0, root:0, topMAP:0[c:0,i:0]
I (1756) mesh: [FAIL][1]root:0, fail:1, normal:0, <pre-root>backoff:0

I (2116) mesh: [SCAN][ch:10]AP:1, otherID:0, MAP:0, idle:0, candidate:0, root:0, topMAP:0[c:0,i:0]
I (2116) mesh: [FAIL][2]root:0, fail:2, normal:0, <pre-root>backoff:0

I (2486) mesh: [SCAN][ch:10]AP:1, otherID:0, MAP:0, idle:0, candidate:0, root:0, topMAP:0[c:0,i:0]
I (2486) mesh: [FAIL][3]root:0, fail:3, normal:0, <pre-root>backoff:0

I (2846) mesh: [SCAN][ch:10]AP:2, otherID:0, MAP:0, idle:0, candidate:0, root:0, topMAP:0[c:0,i:0]
I (2846) mesh: [FAIL][4]root:0, fail:4, normal:0, <pre-root>backoff:0

I (3216) mesh: [SCAN][ch:10]AP:2, otherID:0, MAP:0, idle:0, candidate:0, root:0, topMAP:0[c:0,i:0]
I (3216) mesh: [FAIL][5]root:0, fail:5, normal:0, <pre-root>backoff:0

I (3576) mesh: [SCAN][ch:10]AP:1, otherID:0, MAP:0, idle:0, candidate:0, root:0, topMAP:0[c:0,i:0]
I (3576) mesh: [FAIL][6]root:0, fail:6, normal:0, <pre-root>backoff:0

Someone can help me please ???

Thanks in advance.

nigno21
Posts: 5
Joined: Sat Aug 04, 2018 1:26 am

Re: ESP32 WROOM Mesh problem

Postby nigno21 » Sat Aug 04, 2018 1:02 pm

Somebody can help me please?
Anyone have been make a fully stable mesh network?

Thanks in advance

Who is online

Users browsing this forum: No registered users and 26 guests