Hi Martin, Section 3.5.6 of the user guide explains how to interpret the report. As per the report, no memory is available for allocation. It looks like the memory manager init routine has not run yet. I am guessing what might be happening is that your statically created task that call fdOpenSession() is being called before the NDK task runs and is able to initialize the NDK stack. Can you try the following ? - Create a sempahore and update your network task to pend on it before calling fdOpenSession(). - Add a networkIPAddrHook function that posts this semaphore. This hook function is called once the stack is initialized so it should be safe to unblock your network task so it can call fdOpenSession() at this time. *.cfg: var Global = xdc.useModule('ti.ndk.config.Global'); Global.networkIPAddrHook = '&myIPAddrHook'; *.c: Void myIPAddrHook(IPN IPAddr, uint IfIdx, uint fAdd) { Semaphore_post(...); } Best, Ashish
↧