• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 873 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.

NDK: Configuring IP address during runtime with XGCONF

Ralf Goebel
Genius 3715 points

Hi,

is it possible to setup the IP address during runtime without using the legacy API?
The IP address configuration is stored on a memory card in my application.

And another question I already asked in a different forum:
Is there an easy way to activate the semaphore library of the kernel gate functions llenter() and llexit()?
The priority based library is used by default (os.ae66 instead of os_sem.ae66). I couldn't find a setting in the RTSC configuration.

Thanks,

Ralf

  • 0
    TI__Mastermind 26780 points

    Ralf,

    For the first question: The answer is no, you need to use the legacy API.  There is some discussion about this on this thread: http://e2e.ti.com/support/embedded/bios/f/355/p/221215/779079.aspx#779079

    For the second question from a different forum: Can you describe more what you are asking?  What are llenter(), llexit(), os.ae66, etc.?

    Thanks,
    Scott

  • 0 in reply to ScottG
    Genius 3715 points

    Hi Scott,

    You can find the information about my second question in the NDK Users Guide spru523h.pdf on page 73: "Choosing the llEnter()/llExit() Exclusion Method"

    The os.ae66 library automatically gets linked in the application for my C66 hardware when configuring the NDK with XGCONF.

    Thanks,

    Ralf

  • 0 in reply to Ralf Goebel
    TI__Mastermind 45025 points

    Ralf,

    This is a bug.  I've filed a bug report to track it and ensure it gets fixed:

    SDOCM00097076 - need config param to link osal semaphore libraries

    In the meantime, you should be able to work around this issue.  I was trying to find a way to link in the os_sem.ae66 library ahead of the os.ae66 one coming in from the ti.ndk.config package, but I couldn't do it; it seems the generated "linker.cmd" file (which has -l"os.ae66") always comes in first.

    So I think you should work around this problem by editing the file ti/ndk/config/package.xs.

    You can change this line:

            "os/lib/os" + libSuffix,

    To be:

            "os/lib/os_sem" + libSuffix,

    Save the file then clean and rebuild your app.  You can check that it is linking in the os_sem lib file by looking in the generated linker.cmd (e.g. under your project in Debug/configPkg/linker.cmd).  I see this in mine:

        -l"C:\ti\ndk_2_22_00_5x\packages\ti\ndk\os\lib\os_sem.ae66"

    Steve

  • 0 in reply to Steven Connell
    Genius 3715 points

    Hi Steve,

    is there any progress on this bug? I couldn't find anything in the release notes of more recent NDK versions.

    Thanks,
    Ralf

  • 0 in reply to Ralf Goebel
    TI__Mastermind 45025 points

    Hi Ralf,

    Thanks for checking in.  We have an NDK release due out in the next couple of weeks and this bug will be fixed in that.

    Steve