Quantcast
Channel: Forums - Recent Threads
Viewing all articles
Browse latest Browse all 262198

NDK & NSP Installation Issue

$
0
0

Dear TI:

I do not think that the installation of  my NDP and NDK packages installed correctly. 

I am running SYS/BIOS 6.35 and CodeComposer 5.4.

When I look in CodeComposer in Available Products I see:

                        

 I right clicked on Repositories and selected “Check Path”.  The following Screen came up.

 Both of the Yellow Yield signs state the same thing… “This Repository contains only packages that are not accessible”.   I thought that to be a bit “off”.

 

On Page 12 of spru523h.pdf - TI Network Developer's Kit (NDK) v2.21 - it states:

 The file extensions for pre-built libraries provided with the NDK are as follows:

.a64P For C64x+ targets (COFF format, little endian).

.a64Pe For C64x+ targets (COFF format, big endian).

.a674 For C674x targets (COFF format, little endian).

.ae9 For ARM9 targets (ELF format, little endian)

.ae66 For C66x targets (ELF format, little endian).

.ae66e For C66x targets (ELF format, big endian).

.ae674 For C674x targets (ELF format, little endian).

.aea8f For Cortex-A8 targets (ELF format, little endian, does not use hardware-based floating point support, for legacy application support)

.aea8fnv For Cortex-A8 targets (ELF format, little endian, uses hardware-based vector floating point support, recommended over .aea8f)

.aem3 For Cortex-M3 targets (ELF format, little endian)

 

I am working with a Stellaris lm3s6965 board, so I started hunting down the library for “.aem3”.

 The documentation (Section 1.3.3 Library Directory Structure) states that the “Pre-built linkable libraries and source code are provided for each of the libraries that make up the NDK in the <NDK_INSTALL_DIR>\packages\ti\ndk directory tree”.

 

As I search the directories for the .aem3 extension, I find no files.

 

I skipped to Section 1.5.1 Directories in packages\ti\ndk

The <NDK_INSTALL_DIR>\packages\ti\ndk directory contains the following subdirectories. For each library, both source files and pre-build libraries are provided.

 

Directory Description

benchmarks Contains spreadsheets with throughput and CPU load statistics from benchmark testing on the TCI6482 board.

config Used internally. Contains packages for all the modules configured by XGCONF and used by application code.

docs Contains Doxygen documentation for NDK internals (for advanced users only).

hal Contains NDK driver libraries and source code. See Section 1.3.7.

inc NDK include file directory. See Section 1.5.2.

miniPrintf Contains small code size printf libraries and source code. See Section 1.3.6.

netctrl Contains libraries and source code for network startup and shutdown, including special versions for various subsets of network functionality. See Section 1.3.8

nettools Contains libraries and source code for network tools, such as DHCP, DNS, and HTTP. See Section 1.4.3.

os Contains libraries and source code for the OS Adaptation Layer. See Section 1.3.6.

package Used internally.

productview Used internally by XGCONF.

rov Used internally by the ROV debugging tool in CCS.

stack Contains libraries and source code for the network stack. See Section 1.3.4.

tools Contains libraries and source code for several network tools. See Section 1.5.3.

winapps Contains client test applications for Windows® and Linux command-prompt use. Both source code and executables are provided. See Section 1.5.4.

 

My directories seem to match up.

 

Finally, I went to Section 1.6.1….

 

1.6.1 Adding NDK Support to an Existing Application

If you have an existing application that has SYS/BIOS and XDCtools support, but does not have the NDK

enabled, follow these steps to enable the NDK and NSP:

1. Right-click on the CCS project in the Project Explorer view. Choose Build Options from the context menu.

2. Select the General category in the Properties dialog.

3. Go to the RTSC tab.

4. Check the boxes next to the most recently installed versions of the NDK and NDK Network Support Package products.

5. Click OK(The following is what I see)

 

 

6. Reopen the *.cfg file in the project with XGCONF. The NDK and NSP should now be listed in the Available Products view.

7. Select the NDK > Global item in the Available Products view. You will see the Welcome sheet for NDK configuration. This sheet provides an overview of the NDK, configuration information, and documentation for the NDK.

8. Click the System Overview button in the Welcome sheet to see a handy diagram of the NDK modules you can configure.

 

Regarding #6 and #7….  I am not seeing these.   I have “Available Products” listed at the top.  The only reference I see to NDK and NSP are in “All Repositories”.

 And Finally….  Sorry for the long email….

 Either the Install went bad and I should re-install these.  If so, how do I uninstall?

-or-

I inadvertently installed the “updates” to these packages without the “base” package.  I did not see documentation for this.

-or-

I need to rebuild this and I just did not understand that I needed to do that.

-or-

Other….  In which case, I can not even offer a guess.

 

Any help would be greatly appreciated.

 

Thank you.

 

Rick

 


Viewing all articles
Browse latest Browse all 262198

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>