Tool/software:
I am calling slRecvFrom (in blocking state) from task and delete the task.
Then I restart the network processor.The i create the socket again.
But sl_RecvFrom is returning error -9.
What is the meaning of this and how can i fix this?
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
I am calling slRecvFrom (in blocking state) from task and delete the task.
Then I restart the network processor.The i create the socket again.
But sl_RecvFrom is returning error -9.
What is the meaning of this and how can i fix this?
I am using a Timeout for sl_stop(200).But the problem is the new socket is getting created successfully and send function is also working.When Recv gets first packet it goes in -8 error loop or its stuck somewhere in recv.
Is there anything else i am missing here.
I am using Freertos.
sounds like you get -8 every time regardless of restarting the NWP.
does it happen on the first time you open a socket? after opening socket for the first time, you should be able to send/recv without any issue.
what Servicepack version are you using?
Hi,
I tested locally using the network_terminal and I am able to use the UDP recvfrom API with no issues.
please share your code or alternatevly try to program the network_terminal example and retest.
Also, would be good to get an NWP log to see what is going on under the hood.
There are plenty of posts where we explain how to fetch logs.
Just as a recap, you should add the following to your code to mux the line:
#include <ti/devices/cc32xx/driverlib/rom_map.h>
#define PIN_62 0x0000003D
#define PIN_MODE_1 0x00000001
Then inside mainThread() after SPI_Init(), add:
/* NWP log */
MAP_PinTypeUART(PIN_62, PIN_MODE_1);
Rest of the procedure is as described in chapter 20.1 under https://www.ti.com/lit/ug/swru455m/swru455m.pdf?ts=1638204986283&ref_url=https%253A%252F%252Fwww.google.com%252F
please note that it is very important to capture the binary stream in 921600bps and in binary mode.
Shlomi
you can follow the SDK for these questions.
Shlomi