It seems WF200 firmware does not like SL_WFX_SEND_FRAME_REQ_ID messages with zero-length payload. It is also explicitly written in the documentation of sl_wfx_send_frame_req_body_t. But the loop in sl_wfx_tx_process() can produce such messages, triggering the firmware exception.
When using ThreadX + NetXDuo + WF200 this can be triggered by:
ping -6 -s 1450 fdfe::1000:b63a:31ff:fed3:2cd2
This patch prevents the crash by skipping zero-length-payload tx frames.
It seems WF200 firmware does not like
SL_WFX_SEND_FRAME_REQ_ID
messages with zero-length payload. It is also explicitly written in the documentation ofsl_wfx_send_frame_req_body_t
. But the loop insl_wfx_tx_process()
can produce such messages, triggering the firmware exception.When using ThreadX + NetXDuo + WF200 this can be triggered by:
ping -6 -s 1450 fdfe::1000:b63a:31ff:fed3:2cd2
This patch prevents the crash by skipping zero-length-payload tx frames.