Page 1 of 1

Problems with the udp_client example

Posted: Mon Nov 26, 2018 2:12 pm
by trinacu
I might just not understand what I am doing, but I am trying to run the udp_client from examples/protocols/sockets.
The esp32 connects to the wifi successfully and sends one message, but encounters problems after that - sometimes I can read the message on the receiving end while other times I get the packet but it appears to be empty. It keeps saying "wifi: discard, ba not setup". If i send a packet from my PC to the esp it stops reporting that but nothing seems to change - it doesn't receive the data so it seems as the "Received ..." ESP)LOGI doesn't appear on the idf-monitor.

Below is the output from idf-monitor:

Code: Select all

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:6164
load:0x40078000,len:10168
load:0x40080400,len:6552
entry 0x40080764
I (29) boot: ESP-IDF v3.3-dev-236-gfa59b1b-dirty 2nd stage bootloader
I (29) boot: compile time 13:49:53
I (30) boot: Enabling RNG early entropy source...
I (35) boot: SPI Speed      : 40MHz
I (39) boot: SPI Mode       : DIO
I (43) boot: SPI Flash Size : 4MB
I (47) boot: Partition Table:
I (51) boot: ## Label            Usage          Type ST Offset   Length
I (58) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (66) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (73) boot:  2 factory          factory app      00 00 00010000 00100000
I (81) boot: End of partition table
I (85) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x14f8c ( 85900) map
I (124) esp_image: segment 1: paddr=0x00024fb4 vaddr=0x3ff80000 size=0x00000 (     0) load
I (124) esp_image: segment 2: paddr=0x00024fbc vaddr=0x3ff80000 size=0x00000 (     0) load
I (131) esp_image: segment 3: paddr=0x00024fc4 vaddr=0x3ffb0000 size=0x030d8 ( 12504) load
I (145) esp_image: segment 4: paddr=0x000280a4 vaddr=0x3ffb30d8 size=0x00000 (     0) load
I (149) esp_image: segment 5: paddr=0x000280ac vaddr=0x40080000 size=0x00400 (  1024) load
0x40080000: _WindowOverflow4 at /home/aleks/esp/esp-idf/components/freertos/xtensa_vectors.S:1685

I (158) esp_image: segment 6: paddr=0x000284b4 vaddr=0x40080400 size=0x07b5c ( 31580) load
I (180) esp_image: segment 7: paddr=0x00030018 vaddr=0x400d0018 size=0x6372c (407340) map
0x400d0018: _stext at ??:?

I (323) esp_image: segment 8: paddr=0x0009374c vaddr=0x40087f5c size=0x09584 ( 38276) load
0x40087f5c: rcUpdateTxDoneAmpdu2 at ??:?

I (339) esp_image: segment 9: paddr=0x0009ccd8 vaddr=0x400c0000 size=0x00000 (     0) load
I (339) esp_image: segment 10: paddr=0x0009cce0 vaddr=0x50000000 size=0x00000 (     0) load
I (346) esp_image: segment 11: paddr=0x0009cce8 vaddr=0x50000000 size=0x00000 (     0) load
I (365) boot: Loaded app from partition at offset 0x10000
I (365) boot: Disabling RNG early entropy source...
I (366) cpu_start: Pro cpu up.
I (370) cpu_start: Starting app cpu, entry point is 0x400811d8
0x400811d8: call_start_cpu1 at /home/aleks/esp/esp-idf/components/esp32/cpu_start.c:246

I (0) cpu_start: App cpu up.
I (380) heap_init: Initializing. RAM available for dynamic allocation:
I (387) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (393) heap_init: At 3FFB9088 len 00026F78 (155 KiB): DRAM
I (399) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (406) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (412) heap_init: At 400914E0 len 0000EB20 (58 KiB): IRAM
I (418) cpu_start: Pro cpu start user code
I (101) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (184) wifi: wifi driver task: 3ffc0c64, prio:23, stack:3584, core=0
I (184) wifi: wifi firmware version: abbd416
I (184) wifi: config NVS flash: enabled
I (184) wifi: config nano formating: disabled
I (184) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (194) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (234) wifi: Init dynamic tx buffer num: 32
I (234) wifi: Init data frame dynamic rx buffer num: 32
I (234) wifi: Init management frame dynamic rx buffer num: 32
I (234) wifi: Init static rx buffer size: 1600
I (234) wifi: Init static rx buffer num: 10
I (244) wifi: Init dynamic rx buffer num: 32
I (244) example: Setting WiFi configuration SSID [ssid]...
I (324) phy: phy_version: 4000, b6198fa, Sep  3 2018, 15:11:06, 0, 0
I (324) wifi: mode : sta (30:ae:a4:26:99:a0)
I (324) example: Waiting for AP connection...
I (324) example: SYSTEM_EVENT_STA_START
I (444) wifi: n:2 0, o:1 0, ap:255 255, sta:2 0, prof:1
I (1424) wifi: state: init -> auth (b0)
W (1434) wifi: discard, ba not setup
W (1434) wifi: discard, ba not setup
I (1434) wifi: state: auth -> assoc (0)
I (1434) wifi: state: assoc -> run (10)
I (1674) wifi: connected with [ssid], channel 2
I (1674) wifi: pm start, type: 1

W (2184) wifi: discard, ba not setup
I (2684) event: sta ip: 192.168.0.105, mask: 255.255.255.0, gw: 192.168.0.1
W (2684) wifi: discard, ba not setup
I (2684) example: SYSTEM_EVENT_STA_GOT_IP
W (2884) wifi: discard, ba not setup
I (3184) example: SYSTEM_EVENT_STA_GOT_IP6
W (3184) wifi: discard, ba not setup
I (3184) example: IPv6: FE80::32AE:A4FF:FE26:99A0
I (3184) example: Connected to AP
I (3194) example: Socket created
I (3194) example: Message sent
W (4184) wifi: discard, ba not setup
W (5184) wifi: discard, ba not setup
W (6984) wifi: discard, ba not setup
W (6994) wifi: discard, ba not setup


Re: Problems with the udp_client example

Posted: Thu Nov 29, 2018 11:14 am
by trinacu
I have been able to get the messages across, but the "wifi: discard, ba not setup" still shows up sometimes.