• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 79 subscribers
  • Views 234 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.

MSP432E401Y: Rebuilt a library within the NDK. HowTo ?

ngrkus
Expert 1020 points
Part Number: MSP432E401Y

Hi,

I made some NDK changes due to a customers feature requirement. The changes are limited to the slnetif subdirectory within the ndk folder. At link time the library is included:

-l"ti/ndk/slnetif/lib/slnetifndk_msp432e4.aem4f"

I would like to rebuild this library only. I am using the following setup:

- CCS Version: 9.2.0.00013 on Windows 10

- simplelink_msp432e4_sdk_3_20_00_10 with the ndk_3_61_00_09

- The XDC Tools installed xdctools_3_51_03_28_core

- I am using FreeRTOS and the TI-Compiler

I tried to read through ( processors.wiki.ti.com/index.php/Rebuilding_The_NDK_Core_Using_Gmake ) However I do struggle to build this library "slnetifndk_msp432e4.aem4f" with debug enabled. Is there some more info about building libraries within the NDK?

br

Markus

  • 0
    TI__Guru* 96960 points

    Hi,

    Can you see if this updated page answers you question: https://e2e.ti.com/support/processors/f/791/p/822409/3042423#3042423

    If it does help, can you include you full build output (please attach as a file instead of copy/pasting into the thread).

    Todd

    The processors.wiki link you include should be re-routing to the above link soon.

  • 0 in reply to ToddMullanix
    Expert 1020 points

    Hi Todd,

    after reading the document and the web several times I did the following (I explain in detail. Maybe I miss something and you will note it):

    1.) I made a copy of the whole SDK (20k files or so). Don't know if that is needed. However I wanted to be on the safe side. I call this copied directory "simplelink_msp432e4_sdk_3_20_00_10_rebuild".

    2.) Within the SDK directory (the copied one! simplelink_msp432e4_sdk_3_20_00_10_rebuild) I did modify the file 'imports.mak' according to my settings. I did delete everything that I don't intend to use. For example I do work with the TI compiler. I have no need to build for the gnu compiler as well. The file 'imports.mak' is self explanatory. Just read what's on top of the file.

    3.) Then I switched to  the directory called ndk which is in ./source/ti/ndk three levels below the copied SDK installdir. Finally I did open cmd.exe (I am on W10) as an administrator (may work at the user level as well) and within the ndk rund gmake clean and then gmake. There is a makefile. That's why I suppose it is okay to call gmake with no other option.

    Now it takes some time (5 minutes or so) until all the lib files are recreated. My initial intension was to only build the slnetif library within slnetif. However I could not figure out how to do this since I have no experience with this XDC toolchain and the slnetif specific makefile is being created based on a package.bld file or so. Anyway I will try to run it. I still don't know what I have to do in order to create a debug version of the library.

    br

    Markus

  • 0 in reply to ngrkus
    TI__Guru* 96960 points

    Markus,

    You can find rebuild insttuctions in the SL SDK's NDK User Guide also. It talks about rebuilding in debug mode: http://dev.ti.com/tirex/explore/node?node=ABfxdRTcqyaL.ESg2JhTBg__J4.hfJy__LATEST

    Look in section 1.2 (at least in the 3.30 release it is 1.2).

    Todd

**Attention** This is a public forum