Problem running 'internal communication' sample

magnomp
Posts: 5
Joined: Tue Sep 11, 2018 7:57 pm

Problem running 'internal communication' sample

Postby magnomp » Tue Sep 11, 2018 8:09 pm

I flashed my esp32 dev board with 'internal communication' sample, but i'm not exactly sure if it's working properly

This is what I get from monitor:

Code: Select all

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:5728
ho 0 tail 12 room 4
load:0x40078000,len:9020
load:0x40080000,len:6064
0x40080000: _iram_start at C:/msys32/home/Magno/esp/esp-idf/components/freertos/xtensa_vectors.S:1685

entry 0x40080330
0x40080330: _KernelExceptionVector at ??:?

I (30) boot: ESP-IDF v3.1 2nd stage bootloader
I (30) boot: compile time 16:46:39
I (30) 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=0x1b264 (111204) map
I (132) esp_image: segment 1: paddr=0x0002b28c vaddr=0x3ffb0000 size=0x035ec ( 13804) load
I (138) esp_image: segment 2: paddr=0x0002e880 vaddr=0x3ffb35ec size=0x00000 (     0) load
I (139) esp_image: segment 3: paddr=0x0002e888 vaddr=0x40080000 size=0x00400 (  1024) load
0x40080000: _iram_start at C:/msys32/home/Magno/esp/esp-idf/components/freertos/xtensa_vectors.S:1685

I (148) esp_image: segment 4: paddr=0x0002ec90 vaddr=0x40080400 size=0x01380 (  4992) load
I (159) esp_image: segment 5: paddr=0x00030018 vaddr=0x400d0018 size=0x7ee20 (51970x400d0018: _stext at ??:?

I (347) esp_image: segment 6: paddr=0x000aee40 vaddr=0x400817800x40081780: esp_timer_stop at C:/msys32/home/Magno/esp/esp-idf/components/esp32/esp_timer.c:412

 size=0x0ed10 ( 60688) load
I (373) esp_image: segment 7: paddr=0x000bdb58 vaddr=0x400c0000 size=0x00000 (     0) load
I (373) esp_image: segment 8: paddr=0x000bdb60 vaddr=0x50000000 size=0x00000 (     0) load
I (389) boot: Loaded app from partition at offset 0x10000
I (389) boot: Disabling RNG early entropy source...
I (391) cpu_start: Pro cpu up.
I (395) cpu_start: Starting app cpu, entry point is 0x40080fd4
0x40080fd4: call_start_cpu1 at C:/msys32/home/Magno/esp/esp-idf/components/esp32/cpu_start.c:225

I (0) cpu_start: App cpu up.
I (405) heap_init: Initializing. RAM available for dynamic allocation:
I (412) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (418) heap_init: At 3FFBAB30 len 000254D0 (149 KiB): DRAM
I (424) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (431) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (437) heap_init: At 40090490 len 0000FB70 (62 KiB): IRAM
I (443) cpu_start: Pro cpu start user code
I (126) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (172) wifi: wifi driver task: 3ffc2220, prio:23, stack:3584, core=0
I (172) wifi: wifi firmware version: 54ef8ed
I (172) wifi: config NVS flash: enabled
I (172) wifi: config nano formating: disabled
I (182) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (192) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (212) wifi: Init dynamic tx buffer num: 32
I (212) wifi: Init data frame dynamic rx buffer num: 32
I (212) wifi: Init management frame dynamic rx buffer num: 32
I (212) wifi: Init static rx buffer size: 1600
I (222) wifi: Init static rx buffer num: 10
I (222) wifi: Init dynamic rx buffer num: 32
I (292) phy: phy_version: 3960, 5211945, Jul 18 2018, 10:40:07, 0, 0
I (292) wifi: mode : sta (30:ae:a4:90:15:30) + softAP (30:ae:a4:90:15:31)
W (302) wifi: [beacon]interval:100ms
I (1292) wifi: Set ps type: 0

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

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

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

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

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

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

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

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

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

(.....)

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

I (37902) mesh: <MESH_NWK_PARENT_SELECTION>no parent found, scan times:120, heap:188256
I (37912) mesh_main: <MESH_EVENT_NO_PARENT_FOUND>scan times:120
I (37922) mesh: <MESH_NWK_PARENT_SELECTION>scan_from_yield:0, connected_layer:0
I (37932) mesh: [no parent found]looking for a new parent, [L:0]try layer:0
I (38232) mesh: [SCAN][ch:1]AP:1, otherID:0, MAP:0, idle:0, candidate:0, root:0, topMAP:0[c:0,i:0]
I (38232) mesh: [FAIL][121]root:0, fail:121, normal:0, <pre-root>backoff:0

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

(....)

(I skipped aparently redundant lines for brevity)

Is that normal? What is this sample expected to do? Is there any sample that shows me how to send messages to/from my desktop?

ESP_Dazz
Posts: 38
Joined: Fri Jun 02, 2017 6:50 am

Re: Problem running 'internal communication' sample

Postby ESP_Dazz » Wed Sep 12, 2018 10:59 am

The internal communication example is supposed to demonstrate how a mesh network is built using multiple nodes. Once the mesh network is built, the root node will send a data packet to every other node in the mesh network. See Mesh API Reference and Mesh Guide

What is the goal of your application? Are you attempting connect a single device to your desktop or actually build a multi device mesh network? If the former, the Wi-Fi examples are probably more relevant.

magnomp
Posts: 5
Joined: Tue Sep 11, 2018 7:57 pm

Re: Problem running 'internal communication' sample

Postby magnomp » Wed Sep 12, 2018 11:08 am

OK, I found another thread related to this issue which mentions it could be the wifi channel, so I checked on my router that it is using channel 6 and configured my esp32 acordingly ant it seems to work now.

Is there a way to automate this? I mean, I don't have to worry about wifi channel for my laptop to connect, cant esp32 behave the same way?

What is the goal of your application? Are you attempting connect a single device to your desktop or actually build a multi device mesh network? If the former, the Wi-Fi examples are probably more relevant.

Ok, my goal is to actually build a multi node mesh network. For now I'm playing with just one device to get familiarized with the technology

ESP_yudong
Posts: 29
Joined: Wed May 16, 2018 12:31 pm

Re: Problem running 'internal communication' sample

Postby ESP_yudong » Fri Sep 28, 2018 12:00 pm

Looks like you've solved this.
ESP-MESH network is established on a fixed channel (1-14) now, so the channel is mandatory.
Is there a way to automate this? I mean, I don't have to worry about wifi channel for my laptop to connect, cant esp32 behave the same way?

https://docs.espressif.com/projects/esp-idf/en/latest/api-reference/mesh/esp_mesh.html#_CPPv219esp_mesh_set_configPK10mesh_cfg_t

Who is online

Users browsing this forum: No registered users and 3 guests