RTOS/TDA2E: Start NDK task from application instead of creating using config

Hi Prasad,

Unfortunately what you want isn't directly supported.

Prasad Jondhale said:

I tried using different hook functions(net open hook, ip address hook) but that doesnt serve my purpose.

Have you tried pending on a semaphore in one of the early NDK hook functions (i.e Global.stackBeginHook)?  This would allow you to block within the NDK task thread.  You could then post the semaphore once your board config is complete, allowing the stack to carry on at that point.

-----

If the above does not work for you, one idea I have is to use the following setting to get what you want:

Global.stackThreadUser = '&myStackThread';  // i.e. gives you control of the definition of the stack thread function

You could define the stack thead that's created automatically from the NDK code to either block or just exit the fist time around.  For example:

boardConfigDone = 0;
myTaskThread()
{
    if (boardConfigDone == 1) {
        // board config complete.  Start the stack:
        // <insert content of NDK stack thread here>
    }
    // else just let the task exit ... create it later once board config done
}

So you could do something like:

1. Global.stackThreadUser = '&myStackThread';

2. define stack thread user as above (or make it block on a semaphore)

3. NDK will start up and run myTaskThread() as the main stack thread and just exit (or block).

4. let your board config complete

5. once complete, set boardConfigDone = 1 (or post the semaphore)

6. create the task thread yourself with appropriate stack size and fxn myTaskThread(), etc.

7. Now when the Task thread runs, it will run the NDK stack code b/c the if statement will be true this time.

Note that if you decide to use the stackThreadUser option, you must create the NDK heartbeat clock yourself.  From the documentation on stackThreadUser:

    /*!
     *  Allows user to define their own implementation of the NDK stack thread
     *
     *  If set, the user is responsible for defining the NDK stack
     *  thread, which has no return value and has two parameters of type UArg.
     *
     *  For example (C code):
     *
     *      Void MYMODULE_stackThreadUser(UArg arg0, UArg arg1);
     *
     *  And in the configuration file:
     *
     *      Global.stackThreadUser = '&MYMODULE_stackThreadUser';
     *
     *  The user is also responsible for creating the SYS/BIOS Clock
     *  instance for the NDK 100ms heartbeat, calling appropriate NC_* APIs,
     *  and adding the appropriate C run time configuration code that matches
     *  the settings of the BIOS config file in the function. (e.g. if
     *  configuring the Ip module, the stack thread must call NC_SystemOpen(),
     *  'ti_ndk_config_ip_init(hCfg)', etc.).
     */
    config ndkHookFxn stackThreadUser = null;

Steve