Search found 53 matches

by axellin
Wed Nov 28, 2018 8:45 am
Forum: General Discussion
Topic: TCP Spurious Retransmission when both BT and WIFI are enabled
Replies: 2
Views: 953

Re: TCP Spurious Retransmission when both BT and WIFI are enabled

Set SW coexistnce with wifi priority reduce the chance or TCP Spurious Retransmission, but it still can happen.
Comment out esp_ble_gap_start_scanning() then the TCP Spurious Retransmission never happen.
I do believe there are some issues with bt+wifi coexist...
by axellin
Wed Nov 28, 2018 6:22 am
Forum: General Discussion
Topic: Upgrade lwIP version?
Replies: 3
Views: 1244

Re: Upgrade lwIP version?

Thanks axellin, Hope we can upgrade the LWIP to latest version in IDF v4.0. Hi @liuzhifu, I'm still newbie in ESP-IDF. So it's not clear to me about the meaning of v4.0. Current git tree shows the version is v3.3-dev. Is v4.0 the version after v3.3 release? In the other words, when will v4.0 be ava...
by axellin
Wed Nov 28, 2018 6:15 am
Forum: General Discussion
Topic: TCP Spurious Retransmission when both BT and WIFI are enabled
Replies: 2
Views: 953

TCP Spurious Retransmission when both BT and WIFI are enabled

Hi, I test with master tree (v3.3-dev-270-g6f8e2b018). When BT and Wifi are both enabled, it's easy to observe "TCP Spurious Retransmission" issue. In my case, I only use BLE by calling esp_ble_gap_start_scanning(). The scan_interval=0x50 and scan_widow=0x30 in my setting. If I comment out the esp_b...
by axellin
Tue Nov 27, 2018 4:02 am
Forum: General Discussion
Topic: Upgrade lwIP version?
Replies: 3
Views: 1244

Upgrade lwIP version?

Hi,
Current ESP-IDF is using lwIP-v2.0.3.
However, the v2.0.x is no longer maintained by upstream.
There are many bug fixes in the latest stable relese lwip-v2.1.2.
( http://git.savannah.gnu.org/cgit/lwip.g ... ABLE-2_1_x )
Just wondering if any plan to upgrade the lwIP version?
by axellin
Tue Nov 27, 2018 3:20 am
Forum: General Discussion
Topic: Recommendations for MQTT Library with ESPIDF
Replies: 15
Views: 7088

Re: Recommendations for MQTT Library with ESPIDF

Hi @axellin, The outbox for MQTT needs to be implemented to re-send the failed packet. Currently esp-mqtt directly writes data to the socket without reading from the outbox. Then, there are no semaphore needed to protect the outbox (read/write from difference threads). I think the next release, the...
by axellin
Mon Nov 26, 2018 6:46 am
Forum: General Discussion
Topic: wifi: rx ampdu: duplicated addba request, potential compitability bug
Replies: 2
Views: 955

wifi: rx ampdu: duplicated addba request, potential compitability bug

Testing with master tree, sometimes I got below output:
W (220437) wifi: rx ampdu: duplicated addba request, potential compitability bug
W (220438) wifi: discard, ba not setup

The device looks still working but I'm not sure if this is harmless.
by axellin
Mon Nov 26, 2018 5:19 am
Forum: General Discussion
Topic: Recommendations for MQTT Library with ESPIDF
Replies: 15
Views: 7088

Re: Recommendations for MQTT Library with ESPIDF

Since this post was originally made last year, the esp-mqtt library has been integrated into ESP-IDF. Is the esp-mqtt library thread safe? I don't find locking mechanism in the esp-mqtt library code. So I'm wondering if it is ok to call esp_mqtt_client_publish() in another task? The example code ca...
by axellin
Thu Nov 22, 2018 3:46 am
Forum: General Discussion
Topic: esp-mqtt: mqtt protocol version should be run-time configurable
Replies: 0
Views: 499

esp-mqtt: mqtt protocol version should be run-time configurable

Hi, Current implementation uses CONFIG_MQTT_PROTOCOL_311 setting to decide mqtt protocol version. However, as a mqtt client, it needs to support different versions because we don't know which version is used (or supported) by the broker. Would you consider to make it run-time configurable rather tha...
by axellin
Tue Nov 20, 2018 1:57 am
Forum: General Discussion
Topic: simple_ota_example: Firmware Upgrades Failed
Replies: 1
Views: 1121

Re: simple_ota_example: Firmware Upgrades Failed

Resolved the issue by using ip address instead of hostname as CN. (I tested with connecting a local server with ip address)