• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 98 subscribers
  • Views 3435 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

RTOS: XGCONF cfgNew

user4239066
Prodigy 20 points

Tool/software: TI-RTOS

hi，

The  software i used is bios_6_33_06_50 and ndk_2_21_01_38. I want to config NDK  module using XGCONF . My application originally  is cofigured by writing C code that called CfgNew() to create a configuration database. when I config NDK  module using XGCONF, code is set up in file .cfg. And i cancel  the call of  CfgNew()  and Cfg*() in my application. But the function NC_NetStart( hCfg, NetworkOpen, NetworkClose, NetworkIPAddr )  needs a handle of hCfg, which now i cannot supply. I don't know how to fix this,please help me.

  • 0
    TI__Guru* 96960 points
    The NC_NetStart is generated also. Look in the debug\configPkg\package\cfg\<cfg_filename>_p<target>.c file. It's in there in the ti_ndk_config_Global_stackThread function.

    If you need the hCfg for something else, you can use the CfgGetDefault() API.

    Todd
  • 0 in reply to ToddMullanix
    Prodigy 20 points

    Thank you for your reply. I created a TCP server in function NetworkOpen()  like this  hTCPtask =TaskCreate(task_TCP_recvSvr,,,,); If i need not call  NC_NetStart() according what you have answered above, i‘m  not sure whether the NetworkOpen(), NetworkClose() and NetworkIPAddr() should be changed . Do they keep unchanged,as i did when i use cfg*() functions?   

    My application come from the client example in path C:\ti\mcsdk_2_01_02_06\examples\ndk\client。If i use XGCONF to config NDK ，i should tailor  StackTest()  function to cancel anything about NDK configuration and keep other part unchanged. Am i right?

  • 0 in reply to user4239066
    TI__Guru* 96960 points
    If you use the .cfg to config the NDK, you do NOT supply the stackThread. It is generated in the file I specified above.
    If you do NOT use the .cfg to config the NDK, you need to supply the stackThread.

    Todd