Closed ccli8 closed 5 years ago
Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-313
FYI @samchuarm
@VeijoPesonen
@ccli8 my recommendation would be that you should update ESP8266's firmware to version 1.7.0. With that firmware the driver doesn't allocate memory for TCP packets but uses application provided buffers directly instead. That would be the solution in case of TCP. For further details please read ARMmbed/mbed-os/master/components/wifi/esp8266-driver/README.md
@VeijoPesonen Thanks for your information. 1.7.0 AT requires 16Mb or above flash, but M487 IoT on-board ESP8266 module just has 8Mb flash. Currently, we cannot upgrade the on-board ESP8266 module to 1.7.0 AT. Besides, we fly-wire another 32Mb ESP8266 module which upgrades to 1.7.0 AT for PDMC tests. It is passed. Currently, we are struggling for the upgrade... @samchuarm
1.7.0 AT requires 16Mb or above flash, but M487 IoT on-board ESP8266 module just has 8Mb flash.
cc @SeppoTakalo
Please run full set on Mbed OS socket tests for this platform as instructed in Network Socket test plan.
If it passes the Mbed OS tests, then you should continue testing with Client.
From: https://www.espressif.com/en/products/hardware/esp8266ex/resources
ESP8266 AT Bin V1.7.0
Based on ESP8266_NonOS_SDK V3.0.0.
Limited by the size of the AT bin file, only `1024+1024 flash map` is supported by default.
We have test cases that proof the 1.6.2 and older to be not working properly, and therefore we cannot support those. For any commercial platform, the minimum requirement would be that lates ESP AT firmware is installed and CTS, RTS and Reset for the ESP8266 as well.
And as we cannot support this, we need to close this as "Won't fix"
Description
mbed-os 27e1bc30d Merge pull request #9073 from vervaekejonathan/master
simple-mbed-cloud-client 0a3221a (HEAD -> master, origin/master, origin/HEAD) Merge pull request #60 from ARMmbed/override-callbacks
mbed-cloud-client 62de4b8 (HEAD, tag: 2.0.1.1, origin/master, origin/HEAD) Merge pull request #20 from ARMmbed/release-2.0.1.1
NuMaker-mbed-SD-driver 9557d57 (HEAD -> master, origin/master, origin/HEAD) Fix user buffer is not SD DMA-compatible
Related issue or PR
8927
I am running PDMC tests on NUMAKER_PFM_M487. On M487+Ethernet, tests are passed. On M487+ESP8266, almost
simple-mbed-cloud-client-tests-basic*
tests are failed. Per my check, these tests are failed indownload_test()
function (simple-mbed-cloud-client/TESTS/COMMON/download_test.cpp
), which tries to download a large text file through HTTP. On M487+ESP8266, there are buffer overrun or packet dropped in these failed tests. As I know, ESP8266 driver can be seen with 3 level buffers:MBED_CONF_DRIVERS_UART_SERIAL_RXBUF_SIZE
(enlared from 256 to 1024) inmbed-os/drivers/UARTSerial.h(cpp)
MBED_CONF_ESP8266_SOCKET_BUFSIZE
(default to 8 KiB) inmbed-os/components/wifi/esp8266-driver
When M487+ESP8266 cannot consume received packets in time, these packets will be dropped when
MBED_CONF_ESP8266_SOCKET_BUFSIZE
limit is reached, or buffer overrun withMBED_CONF_DRIVERS_UART_SERIAL_RXBUF_SIZE
. The best solution to it seems to be support for UART flow control (CTS/RTS). But for targets like M487 which cannot consume packets in time and no UART flow control ready, is there another solution?M487+ARM+Ethernet
M487+ARM+ESP8266
Issue request type