See E2E post: https://e2e.ti.com/support/processors/f/791/t/834640#pi320966=3

NDK_recvfrom() will return an error if MSG_DONTWAIT is passed and no data is ready. SockRecv() is ultimately called in this path and that will exit with an error without filling in the sockaddr struct if MSG_DONTWAIT is used and no data is ready for the socket. 

SlNetIfNDK_recvFrom() checks the sockaddr struck BEFORE checking the return code of NDK_recvfrom(), and will thus cause an assert to be fired. 

SlNetIfNDK_recvFrom() should check the return value first, and return with an error if there is an issue.