NSDSP Interface Library Objects

NSDSP Interface Library uses the following objects:

NSDSP List Object allows you to enumerate all the NSDSP programmers connected to the PC. When you have multiple NSDSP programmers, you can use this object to select the appropriate programmer.

NSDSP Object is created every time you establish a connection to a NSDSP programmer and represents the NSDSP programmer. You can use the NSDSP Object to configure various parameters, such as communication rates, programming methods etc. Once configured, the NSDSP Object can be used to start sessions for various purposes, for example to program or debug the target device, to communicate with target using UART or SPI etc.

Session Objects are created to perform specific tasks with NSDSP programmer. There are several types of Session Objects. For example you can create a programming session, or UART session, or debugging session. While a session is active, the NSDSP is put into one of active modes. When there are no active sessions, the NSDSP is in the idle mode.

The following sessions are available:

• UART
• SPI and pin control
• Programming
• Debugging

MCU Object represents a target device and provides some basic information about the target device. The MCU Object is also used to start programming and debugging sessions.

Hex Map Object represents a map of target's program memory. The Hex Map is usually read from a HEX file and then used for programming. The NSDSP Interface library contains functions to load, modify, merge, and store Hex Maps.

The details of object implementation are language specific. Currently, only C Interface is available

Threading

The library functions can be accessed from multiple threads. However, all functions using any particular object must be called from the same thread where the object was created.