Software Development Guide 1.X

Using the NAI Software Support Kit 1.x

You have the SSK 1.x package downloaded and want to build an application with it. This guide covers setting up your development environment and writing and building an application against the NAI SSK 1.x naibrd API.

NAI SSK 1.x is intended for use with boards such as: 75G5, 68G5, 64G5, 68ARM1, 64ARM1, 75INT2, 79G5.

This guide does not cover:

• Cabling, network reachability, terminal access, and transferring your built app onto the board — see Connecting to Boards.
• Launching an NAI sample application and answering its configuration menu — see Running Applications from the Target.
• The naibrd_* API calls that open a handle to your board in code — see Opening a Software Handle to Your Board.

Not sure if SSK 1.x is right for your hardware?

See Choosing the Right SSK — an interactive guide that recommends the correct SSK family and package based on your board, OS, and deployment style. For a breakdown of what’s inside the SSK 1.x package itself, see the SSK 1.x Package Guide.

If you have not already NAI recommends using the NAI Embedded Soft Panel to kickstart development. Via a GUI it allows users to quickly configure and operate NAI products. The API Logger tool within the NAI Embedded Soft Panel will allow you to kickstart writing your program as it will record the API calls made as you use the GUI to configure and operate your hardware.

If you do not yet have your hardware you can still use the NAI Embedded Soft Panel to kickstart your development via the Demo Panel.

If you do not yet know details about your hardware and have already started using the NAI Embedded Soft Panel you can skip to Starting Development. If you want help setting up the environment you can simply pick your preferred OS and follow the corresponding instructions before continuing to Starting Development. The code you write will be fully portable.

To download the NAI Software Support Kit click here.

Environment Setup

These sections will explain how to setup your environment to begin development for your chosen OS. If you do not know what OS you will use yet simply pick your preferred OS, all written .c files are fully portable.

PetaLinux 2014.2 Target

Environment Setup

Choose the instructions for your development host below. The .c files you write are fully portable across hosts.

Windows Host

Development Environment Setup

Host PC

The recommended development platform is a PC with minimum 2GB RAM and 30GB hard drive space, and with Windows 7 or later.

Cross-Compiler

The ARM Linux Cross-Compiler package is available on Xilinx’s website. Download the software as follows:

1. If you have not done so already, create a Xilinx account and make sure you are signed into it for the duration of the installation (you will need to be signed in to complete some parts of the installation).
2. Navigate to https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools/archive.html.
3. Locate release 2014.2 and download “Vivado 2014.2 Full Image for Windows with SDK”.

4. On the “Download Center” page that comes up, fill out all of the required fields and then press “Next”.

5. In the window that pops up, select “Save File” and then click “OK” to save the file to the “Downloads” directory on your PC.

6. Unzip the “Xilinx_Vivado_SDK_Win_2014.2_0612_1.tar.gz” file, which should now be found in the “Downloads” directory on your PC.
7. Run xsetup.exe from the unzipped file folder.

8. Click “Yes” when the User Account Control window pops up.

Note

The Vivado 2014.2 Installation menu will prompt you to install a newer version of Vivado SDK. DO NOT upgrade to the newer version of the SDK.

9. If a window pops up that says it is checking for the latest version, click “Ignore”. If a window labelled “A Newer Version Is Available” pops up, click “Continue”.

10. In the “Vivado 2014.2 Installer – Welcome” window, click “Next >”.

11. In the “Accept License Agreements” window that pops up, check all of the “I Agree” check boxes and then click “Next >”.

12. Select “Software Development Kit (Standalone)” edition to install. This package includes the Cross-Compiler and debugger for application development. Then click “Next >”.

13. In the 1^st and 2^nd window, click “Next >”. In the 3^rd window, click “Install”.

14. After the installation is complete, if you do not already have a license file for the SDK on your computer, select “Get Free Licenses – Vivado WebPACK, SDK, free IP and more”. Then, click “Connect Now”.

Note

You don’t need to purchase a license for the Software Development Kit (Standalone).

15. When you click “Connect Now”, you will be taken to the Xilinx website. If you are not signed in to your Xilinx account, sign in. If the Xilinx website asks you to fill out some personal information, fill it out. Then, you will be taken to the “Product Licensing” page. Select “Vivado Design Suite: HL WebPACK 2015 and Earlier License”, and then click “Generate Node-Locked License”.

16. Click “Next”.

17. Click “Next” again. The license file will now be emailed to the email account you specified when creating your Xilinx account. Copy the license file to your PC so that it can be detected when you run the SDK.

18. Open Xilinx. You will be prompted to choose a workspace location. This will be where all the projects you create will be placed. There is no certain place where the workspace needs to be made; in this case, the workspace, called “Workspace,” is made in the C drive.

19. Exit the “Welcome” tab that shows up by default.

Linux Host

Host PC

• The recommended development platform is a PC with minimum 2GB RAM and 30GB hard drive space, and with Linux CentOS 64-bit v6.5 installed.
• We have tested the application development environment with the above version of CentOS. Other versions of Linux may work as well but are not guaranteed.

CentOS

There are additional packages required to be installed after CentOS is installed on host PC. Type the following:

$ sudo yum install update

$ sudo yum groupinstall “Development Tools”

$ sudo yum install texi2html texinfo glibc-devel chrpath

$ sudo yum install glibc.i686 libgcc.i686 libstdc++.i686 glibc-devel.i686 ncurses-libs.i686 zlib.i686

Cross-Compiler

The current ARM target board is running on an XILINX® XC7Z015 SoC. The ARM Linux Cross-Compiler package is available on Xilinx’s website. Download the software as follows:

1. Navigate to: https://www.xilinx.com/support/download.htmlhttps://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools.htmlhttps://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/vivado-design-tools.html
2. Click on the “Embedded Development” tab.
3. Click on “Archive” under “Version”.
4. Select version “2017.2” under 2017. Under “Software Development Kit Standalone WebInstall Client”, download “SDK 2017.2 WebInstall for Linux 64”.
5. You will be taken to a sign in page. If you have an account, sign in, otherwise click “Create your account.”

6. Enter all required details and click “Create Account.”

7. You will be e-mailed an activation message to your entered email address. Follow its instructions to activate your Xilinx account.
8. Once your Xilinx account is created and activated, sign in. If necessary, go back to the Software Development download page and click “SDK 2017.2 WebInstall for Linux 64” once again.
9. On the “Download Center” page that comes up, fill out all of the required fields and then press “Next”. The file should begin downloading.

10. Based upon the Firefox revision used, security errors may be encountered. If an error occurs, update the Firefox version installed by entering the following in the terminal, restarting the host PC, and retrying to install the SDK.

# sudo yum update firefox

11. Go to the location the SDK file is downloaded to. Use the terminal as follows to allow the file to be executed, or right click the file, go to properties, then permissions, and check the “Allow executing file as program” box.

# cd <Directory of downloaded SDK file>

# chmod 777_ Xilinx_SDK_2017.2_0616_1_Lin64.bin

12. Run Xilinx_SDK_2017.2_0616_1_Lin64.bin from the location it is downloaded to.

# ./Xilinx_SDK_2017.2_0616_1_Lin64.bin

Note

The Vivado 2017.2 Installation menu may prompt you to install a newer version of Vivado SDK. DO NOT upgrade to the newer version of the SDK.

13. Click on “Next.”

14. Enter your credentials to login and click Next.

15. Check all of the “I Agree” boxes and click Next.

16. Select “Xilinx Software Development Kit (XSDK)”.

Note

You don’t need to purchase a license for the Software Development Kit (Standalone).

17. Leave the defaults checked and click Next. DocNav can be unchecked if not needed or disk space needs to be conserved.

18. Choose your desired installation directory and click Next.

19. Make sure all options chosen are correct and click Install.

20. Once the installation is complete, click “OK.”

Link to original

Linux Target

Environment Setup

The Linux Library SSK can be used with Intel-based NAI boards (eg. 75INT2) or NAI boards that live in the PCI slot of a Linux-based PC (eg. 79C3, 79G5). In both cases, the NAI Linux SSK was tested with CentOS 6.5. Other Linux distributions and kernel versions may function, but support is not guaranteed.

The pre-installed OS on the 75INT2 has the following default credentials:

• username: nai
• password: 123456
• default root password: 123456.

Building and Loading NAI PCI driver

Run the following series of commands to build and load the NAI PCI driver on your Linux Host:

cd /home/nai/NAI_SSK/Drivers/PCI
$ make clean
$ make all
$ sudo chmod a+x nai_install.sh
$ sudo ./nai_install.sh load

Development Environment Setup

NAI Intel x86 boards are pre-installed with CentOS 64-bit v6.5 and GCC development tools and standard C libraries are pre-loaded in OS. To install these libraries on a non-NAI Linux host or reinstall onboard, run the following commands:

$ sudo yum groupinstall “Development Tools”
$ sudo yum install libstdc++-devel.i686
$ sudo yum install glibc-devel.i686

Now that your host is configured with the proper tools and NAI drivers, you can now choose your favorite IDE to develop C programs with and open the Software Support Kit.

Link to original

VxWorks 6.9 Target

Environment Setup

Configure the Board Library

Due to the portable nature of the NAI Software Support Kit some configuration is necessary to specify information about your target. If the information changes simply reconfigure the project, the code you have developed will be reuseable.

The NAI Board Software Support Kit (SSK) libraries need to be added to the VxWorks project and built for the SBC that they will be run on. There are three files that need to be modified before the project is built. Two of the files are located in the naibrd/include/advanced directory and one in the naibrd/src directory.

The file naibrd_config.h (located in naibrd\src) is used to determine how the NAI Board libraries will be configured. The files nai_pci_vxworks_adv.h and nai_vme_vxworks_adv.h (located in naibrd\include\advanced) determine how NAI Board will interface with the SBC hardware.

The following table shows which definitions need to be included or excluded for each of the NAI Single Board Computers currently available.

NAI 64PPC1 SBC Example of naibrd_config.h

/* Define if running on ARM Processor and a Xilinx FPGA (i.e. 64ARM1, 99ARM1, NIU1A) */
/* #define ARM_XILINX */
/* Define if running on PPC Processor and a Xilinx FPGA (i.e. 75PPC1, 64PPC1) */
#define PPC_XILINX
/* Define if running on Intel Processor and a Xilinx FPGA (i.e. 75INT2) */
/* #define INTEL_XILINX */
/* Define if running on PPC Processor and a Altera FPGA (i.e. legacy 75PPC1) */
/* #define PPC_ALTERA */
/* Define for Gen 5 processors */
#define NAI_GEN5_GENUSE_SIZE 0x4000u
#if defined(__VXWORKS__)
 #if defined(ARM_XILINX)
 #define GEN5_ARM
 #elif defined(INTEL_XILINX)
 #define GEN5_INTEL
 #elif defined(PPC_XILINX) || defined(PPC_ALTERA)
 #define GEN5_PPC
 #endif
#endif
#if defined(LINUX)
 #if defined(LINUX_ARM)
 #define GEN5_ARM
 #else
 #define GEN5_INTEL
 #endif
#endif
#if defined (WIN32) || defined(LINUX) || defined(__VXWORKS__) || defined(__INTEGRITY)
 /* Enables Ethernet communication support */
 #define NAI_USE_INTF_ETHER
#endif
#if defined (WIN32) || defined(LINUX) || defined(PROC_U2) || defined(__VXWORKS__) || defined(__INTEGRITY)
 /* Enables PCI/CPCI/PCI Express support */
 #define NAI_USE_INTF_PCI /* 75PPC1, 75INT2, 64PPC1 (on board has PCIe) */
 /* Enables VME support */
 #define NAI_USE_INTF_VME /* 64ARM1, 64PPC1 */
#endif

NAI 64PPC1 SBC Example of nai_pci_vxworks_adv.h

/*******************************************************************************************/
/* This section must be defined for the particular SBC that the Library will be running on */
/*******************************************************************************************/
#define NAI_BSP_NAI64PPC1
/* Only ONE of these definitions should be define 
#define NAI_BSP_NAI75PPC1
#define NAI_BSP_NAI64PPC1
#define NAI_BSP_GE_SBC610
#define USER_BSP_PCI // Search for this value and add appropriate code for PCI/PCIe SBC being used
*/
#ifdef NAI_BSP_NAI75PPC1 /* NAI 75PPC1 SBC */
/*
* The NAI 75PPC1 only supports vxBus
* The NAI 75SBC4 does not have a rear connector
* PCI Interface but requires PCI be defined,
* so the NAI 75PPC1 setting are used.
*/
#define NAI_BSP_CPCI75PPC1
#define NAI_ENDIAN_SWAP /* PPC is Big Endian */
#define VXB_PCI_ENABLE /* VxBus PCI supported */
#define VXB_DEVICE_NAME "QorIQPciEx" /* VxBus Driver Name (from vxBusShow) */
#define NAI_SBC_DEVID 0x7584 /* Card PCI Device ID */
#endif
#ifdef NAI_BSP_NAI64PPC1 /* NAI 64PPC1 SBC */
/*
* The NAI 64PPC1 is a VME SBC but it uses PCIe
* for onboard access, so it requires PCI be defined.
*/
#define NAI_BSP_VME64PPC1
#define NAI_ENDIAN_SWAP /* PPC is Big Endian */
#define VXB_PCI_ENABLE /* VxBus PCI supported */
#define VXB_DEVICE_NAME "QorIQPciEx" /* VxBus Driver Name (from vxBusShow) */
#define NAI_SBC_DEVID 0x6484 /* Card PCI Device ID */
#endif
/*
* GE VPX SBC610 SBC
*/
#ifdef NAI_BSP_GE_SBC610
#define GE_BSP_SBC610
#define NAI_ENDIAN_SWAP
#define VXB_PCI_ENABLE
#define VXB_DEVICE_NAME "m85xxPci" /* VxBus Driver Name (from vxBusShow) */
#endif
/*
* USER PCI SBC
*/
#ifdef USER_BSP_PCI 
#define USER_BSP_PCI_SBC /* SBC type/name */
#define NAI_ENDIAN_SWAP /* PPC is Big Endian, Intel & ARM is Little Endian */
#define VXB_PCI_ENABLE /* VxBus PCI supported */
#define VXB_DEVICE_NAME "xxxxxPci" /* VxBus Driver Name (from vxBusShow) */
#endif

NAI 64PPC1 SBC Example of nai_vme_vxworks_adv.h

/*******************************************************************************************/
/* This section must be defined for the particular SBC that the Library will be running on */
/*******************************************************************************************/
#define NAI_BSP_NAI64PPC1
/* Only ONE of these definitions should be define
#define NAI_BSP_NAI64PPC1
#define NAI_BSP_NAI64ARM1
#define MOT_BSP_MV6100
#define USER_BSP_VME // Search for this value and add appropriate code for VME SBC being used
*/
#ifdef NAI_BSP_NAI64PPC1 /* NAI VME 64PPC1 SBC */
/*
* The NAI 64PPC1 uses PCIe for onboard
*/
#define NAI_BSP_VME64PPC1
#define NAI_ENDIAN_SWAP /* PPC is Big Endian */
#define VXB_VME_ENABLE /* VxBus VME supported */
#define NAI_SBC_DEVID 0x6484 /* Card Device ID */
#endif
/*
* NAI VME 64ARM1 SBC
*/
#ifdef NAI_BSP_NAI64ARM1 
#define NAI_BSP_VME64ARM1
// #define NAI_ENDIAN_SWAP /* ARM is Little Endian */
#define VXB_VME_ENABLE /* VxBus VME supported */
#define NAI_SBC_DEVID 0x6481 /* Card Device ID */
#endif
/*
* Motorola MV6100 SBC
*/
#ifdef MOT_BSP_MV6100 
#define MOT_BSP_VME_MV6100
#define NAI_ENDIAN_SWAP
// #define VXB_VME_ENABLE /* VxBus VME supported */
#endif
/*
* USER VME SBC
*/
#ifdef USER_BSP_VME 
#define USER_BSP_VME_SBC /* SBC type/name */
#define NAI_ENDIAN_SWAP /* PPC is Big Endian, Intel & ARM is Little Endian */
#define VXB_VME_ENABLE /* VxBus VME supported */
#endif

Non NAI Single Board Computer Software Modifications

PCI/CPCI/PCIe

If NAI Board is running on a non NAI SBC, there are a couple of files that will need to be modified for the libraries to work correctly. If the backplane interface is PCI, CPCI or PCIe, the files nai_pci_vxworks.h and nai_pci_vxworks.c will need to be modified.

At the top of the nai_pci_vxworks.h file the definition USER_BSP_PCI needs to be defined.

#define USER_BSP_PC1
/* Only ONE of these definitions should be define
#define NAI_BSP_NAI75PPC1
#define NAI_BSP_NAI64PPC1
#define NAI_BSP_GE_SBC610
#define USER_BSP_PCI // Search for this value and add appropriate code for PCI/PCIe SBC being used
*/

In the section where the USER_BSP_PCI definition are declared, the appropriate #defines will need to be included based on the SBC.

/*
* USER PCI SBC
*/
#ifdef USER_BSP_PCI 
#define USER_BSP_PCI_SBC /* SBC type/name */
#define NAI_ENDIAN_SWAP /* PPC is Big Endian, Intel & ARM are Little Endian */
#define VXB_PCI_ENABLE /* VxBus PCI supported */
#define VXB_DEVICE_NAME "xxxxxPci" /* VxBus Driver Name (from vxBusShow) */
#endif

#define USER_BSP_PCI_SBC This can be left as is or can be renamed to better reflect the SBC type that the library is running on. If it is changed, a global search and replaced should be performed.

#define NAI_ENDIAN_SWAP This should be defined if the library is running on a Big Endian processor such as a PPC. If the library is running on a Little Endian processor such as an ARM or Intel, this should not be defined

#define VXB_PCI_ENABLE This should be defined if the library is running on a processor that has a vxBus driver for PCI/PCIe. If not, this should not be defined.

#define VXB_DEVICE_NAME ” QorIQPciEx ” If a vxBus driver is available, this should be updated to the appropriate driver name. The driver name can be obtained by running the vxBusShow command from the shell. Search the output for the PCI drive name.

-> vxBusShow
Registered Bus Types:
 USB-EHCI_Bus @ 0x0903b340
 USB-Host_Bus @ 0x003c74c4
 USB-HUB_Bus @ 0x003c74a8
 MII_Bus @ 0x003bfa64
 PCI_Bus @ 0x003bf6d4
 PLB_Bus @ 0x003bf6f0
Registered Device Drivers:
 vxbUsbBulkClass at 0x0903b480 on bus USB-HUB_Bus, funcs @ 0x003c748c
 vxbUsbHubClass at 0x003d36c0 on bus USB-HUB_Bus, funcs @ 0x003c748c
 :
 :
 QorIQQman at 0x003bebfc on bus PLB_Bus, funcs @ 0x003bebd8
 QorIQPciEx at 0x003be7d8 on bus PLB_Bus, funcs @ 0x003be75c
 QorIQBman at 0x003beac0 on bus PLB_Bus, funcs @ 0x003beaa4
 QorIQLaw at 0x003beb98 on bus PLB_Bus, funcs @ 0x003beb5c
 openPicTimer at 0x003bedf8 on bus PLB_Bus, funcs @ 0x003bedd4
 plbCtlr at 0x003bf718 on bus PLB_Bus, funcs @ 0x003bf70c
Busses and Devices Present:
 PLB_Bus @ 0x003db1b0 with bridge @ 0x003bf758
 Device Instances:
 ppcIntCtlr unit 0 on PLB_Bus @ 0x003dc170 with busInfo 0x00000000
 epic unit 0 on PLB_Bus @ 0x003dc270 with busInfo 0x00000000
 :
 :
 QorIQLaw unit 0 on PLB_Bus @ 0x003dcc70 with busInfo 0x0
 QorIQBman unit 0 on PLB_Bus @ 0x003dcd70 with busInfo 0x00000000
 QorIQQman unit 0 on PLB_Bus @ 0x003dce70 with busInfo 0x00000000
 QorIQFman unit 0 on PLB_Bus @ 0x003dcf70 with busInfo 0x00000000
 QorIQPciEx unit 0 on PLB_Bus @ 0x003dd070 with busInfo 0x00000000
 vxbPlbUsbEhci unit 1 on PLB_Bus @ 0x003ebc70 with busInfo 0x003ef270

nai_pci_vxworks.c Modifications In the file nai_pci_vxworks.c, there are two functions that will need to the modified. The first function is:

STATUS naiPciVxInstallISR(int32_t cardIndex, nai_isr_t isr, void* param)

This will need to be modified to install and enable an Interrupt Service Routine on your SBC. This can sometimes be very BSP specific and you may need to contact your SBC Vendor for help. You can use the code supplied for the NAI SBC as a starting point.

The second function is:

STATUS naiPciVxUninstallISR(int32_t cardIndex, nai_isr_t isr)

This will need to be modified to uninstall and disable an Interrupt Service Routine on your SBC. This can sometimes be very BSP specific and you may need to contact your SBC Vendor for help. You can use the code supplied for the NAI SBC as a starting point.

VME

If the backplane interface is VME, the files nai_vme_vxworks_adv.h and nai_vme_vxworks.c will need to be modified. At the top of the nai_vme_vxworks_adv.h file the definition USER_BSP_VME needs to be defined.

#define USER_BSP_VME
/* Only ONE of these definitions should be define
#define NAI_BSP_NAI64PPC1
#define NAI_BSP_NAI64ARM1
#define MOT_BSP_MV6100
#define USER_BSP_VME // Search for this value and add appropriate code for VME SBC being used
*/

In the section where the USER_BSP_VME definition are declared, the appropriate #defines will need to be included based on the SBC.

/*
* USER VME SBC
*/
#ifdef USER_BSP_VME 
#define USER_BSP_VME_SBC /* SBC type/name */
#define NAI_ENDIAN_SWAP /* PPC is Big Endian, Intel & ARM are Little Endian */
#define VXB_VME_ENABLE /* VxBus VME supported */
#endif

#define USER_BSP_VME_SBC This can be left as is or can be renamed to better reflect the SBC type that the library is running on. If it is changed, a global search and replaced should be performed.

#define NAI_ENDIAN_SWAP This should be defined if the library is running on a Big Endian processor such as a PPC. If the library is running on a Little Endian processor such as an ARM or Intel, this should not be defined

#define VXB_VME_ENABLE This should be defined if the library is running on a processor that has a vxBus driver for VME. If not, this should not be defined.

nai_vme_vxworks.c Modifications

In the file nai_vme_vxworks.c, there are three functions that will need to the modified. The first function is:

STATUS naiVmeVxInstallISR(int32_t cardIndex, nai_isr_t isr, void* param)

This will need to be modified to install and enable an Interrupt Service Routine on your SBC. This can sometimes be very BSP specific and you may need to contact your SBC Vendor for help. You can use the code supplied for the NAI SBC as a starting point.

The second function is:

STATUS naiVmeVxUninstallISR(int32_t cardIndex, nai_isr_t isr)

This will need to be modified to uninstall and disable an Interrupt Service Routine on your SBC. This can sometimes be very BSP specific and you may need to contact your SBC Vendor for help. You can use the code supplied for the NAI SBC as a starting point.

The third function is:

nai_status_t naiVmeVxList(int32_t count, int32_t* numCardsFound, int32_t nSlot[], 
 int8_t sCardName[][16], uint32_t unVmeStartAddr[], uint32_t unVmeEndAddr[],
 uint32_t unVmeAddrMod[])

This function is used to identify all of the cards on the VME bus. By default the information is read from the table naiSlvWindows[NAI_VME_MAX_SLOT] located at the top of the file. This table will need to be updated to reflect your system configuration.

A typical system configuration might look like the following:

/*
 * This table is used for non NAI SBCs to describe the system configuration
 * Enter information for each board in the chassis
 */
nai_slv_window_t naiSlvWindows[NAI_VME_MAX_SLOT] = {
 /* Slot Num Slot Occupied Card name AM Begin VME addr End VME addr */
 { 1, TRUE, "MV6100", 0xD, 0x00000000, 0x00800000-1},
 { 2, TRUE, "64C3", 0xD, 0x08200000, 0x08300000-1},
 { 3, TRUE, "64ARM1", 0xD, 0x09000000, 0x09800000-1},
 { 4, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF},
 { 5, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF},
 { 6, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF},
 { 7, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF},
 { 8, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF},
 { 9, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF},
 { 10, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF},
 { 11, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF},
 { 12, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF},
 { 13, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF},
 { 14, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF},
 { 15, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF},
 { 16, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF},
 { 17, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF},
 { 18, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF},
 { 19, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF},
 { 20, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF},
 { 21, FALSE, "", 0xD, 0xFFFFFFFF, 0xFFFFFFFF}
};

Dual Port Ethernet Module

The EM1 Dual Port Ethernet Module is installed in module position 1 on the NAI PPC SBC card (i.e. 75PPC1). The Ethernet driver needs to be added to VxWorks for proper operation.

Adding EM1 Driver to the VxWorks Image

In Workbench, open the VxWorks Image Project for the processor, then open the Kernel Configuration tool.

Search for INCLUDE_GEI825XX_VXB_END

Include “INCLUDE_GEI825XX_VXB_END” in the configuration, and then rebuild the VxWork Image.

Load the new VxWorks Image on the processor. The two Ethernet port will now be available as gei0 and gei1.

Enabling the EM1 Ethernet Ports

To enable the Ethernet ports, the VxWorks commands ipAttach and ifconfig are used.

ipAttach (X,“gei”) X = device (0 or 1) ifconfig (“geiX AAA.AAA.AAA.AAA netmask MMM. MMM. MMM. MMM up”) X = device (0 or 1) AAA = IP Address MMM = subnet mask

-> ipAttach (0,"gei")
value = 0 = 0x0
-> ifconfig ("gei0 192.168.2.16 netmask 255.255.255.0 up")
value = 0 = 0x0
-> ipAttach (1,"gei")
value = 0 = 0x0
-> ifconfig ("gei1 10.0.8.123 netmask 255.0.0.0 up")
value = 0 = 0x0
-> ifconfig
lo0 Link type:Local loopback Queue:none
 inet 127.0.0.1 mask 255.255.255.255
 inet6 unicast fe80::1%lo0 prefixlen 64 automatic
 inet6 unicast ::1 prefixlen 128
 UP RUNNING LOOPBACK MULTICAST NOARP ALLMULTI
 MTU:1500 metric:1 VR:0 ifindex:1
 RX packets:3 mcast:3 errors:0 dropped:0
 TX packets:3 mcast:3 errors:0
 collisions:0 unsupported proto:0
 RX bytes:168 TX bytes:168

dtsec3 Link type:Ethernet HWaddr 00:16:c6:fe:dd:20 Queue:none
 inet 192.168.1.116 mask 255.255.255.0 broadcast 192.168.1.255
 inet6 unicast fe80::216:c6ff:fefe:dd20%dtsec3 prefixlen 64 automatic
 UP RUNNING SIMPLEX BROADCAST MULTICAST
 MTU:1500 metric:1 VR:0 ifindex:2
 RX packets:423 mcast:0 errors:0 dropped:0
 TX packets:149 mcast:8 errors:0
 collisions:0 unsupported proto:0
 RX bytes:28k TX bytes:9090

gei0 Link type:Ethernet HWaddr 00:a0:c9:00:00:02 Queue:none
 capabilities: TXCSUM TX6CSUM
 inet 192.168.2.16 mask 255.255.255.0 broadcast 192.168.2.255
 inet6 unicast fe80::2a0:c9ff:fe00:2%gei0 prefixlen 64 automatic
 UP RUNNING SIMPLEX BROADCAST MULTICAST
 MTU:1500 metric:1 VR:0 ifindex:3
 RX packets:294 mcast:0 errors:0 dropped:0
 TX packets:103 mcast:8 errors:0
 collisions:0 unsupported proto:0
 RX bytes:20k TX bytes:6330

gei1 Link type:Ethernet HWaddr 00:a0:c9:00:00:03 Queue:none
 capabilities: TXCSUM TX6CSUM
 inet 10.0.8.123 mask 255.0.0.0 broadcast 10.255.255.255
 inet6 unicast fe80::2a0:c9ff:fe00:3%gei1 prefixlen 64 tentative automatic
 UP SIMPLEX BROADCAST MULTICAST
 MTU:1500 metric:1 VR:0 ifindex:4
 RX packets:0 mcast:0 errors:0 dropped:0
 TX packets:0 mcast:0 errors:0
 collisions:0 unsupported proto:0
 RX bytes:0 TX bytes:0
value = 0 = 0x0

Link to original

Windows Target

Environment Setup

The NAI Windows Library Software Support Kit is originally built and tested in Visual Studio 2010. However, the SSK is also compatible with the SDK and toolset versions in Visual Studio 2012 and Visual Studio 2022.

Link to original

Starting Development

NAI recommends starting with the NAI Embedded Soft Panel (ESP) to kickstart development. Its GUI lets you quickly configure and operate NAI products, and its API Logger tool generates the corresponding API calls as you exercise the hardware — a useful jumping-off point for your own code.

When you are ready to write code, the SSK ships a selection of sample applications you can build, run, and use as templates. The full collection is available in the Sample Applications tab. For board-level functionality across module families, NAI also provides standalone guides on interrupts, watchdog timers, NAI ethernet protocols, BIT, multicore applications, and backplane reset.

For the SSK 1.x library API reference, see Software Support Kit 1.x Library API Documentation.

Running NAI sample applications

When you launch an NAI sample application on the target, it presents a configuration menu that asks where the application is running and how it should reach the modules. See Running Applications from the Target for the full walkthrough — organized by application location and connection type.

Connecting to the System

For the cabling, network reachability, terminal access, file transfer, and NAI Ethernet Listener prerequisites needed to get the board ready to communicate with your application, see Connecting to Boards — it covers the cross-compile flow used by SSK 1.x targets (PetaLinux 2014.2 host, Linux host with PCI driver, VxWorks 6.9, Windows host) and includes the HDMI/MIL adapter board details, standard serial terminal settings, detailed minicom setup, and the EEPROM IP-setting walkthrough. On older boards the EEPROM utility is named mbeeprom_util (legacy); on newer boards it is naiMBEEPROMUtil — both work the same way.

Building and Running a Project

Linux

Building and Running a Project

PACKAGE LAYOUT

The NAI Linux SSK includes the following folders:

Resource	Description
App/Linux_x86	Contains pre-built 32-bit x86 Linux executable ELF files
AppSrc	Contains the source for module-specific NAI sample applications
Documentation	Contains NAI’s API library, API function mappings, and reference documents
Drivers	Contains I2C and PCI drivers for using NAI boards in Linux
Include	Contains the header files(.h) needed by the applications to call functions in the NAI library (.so) file
Libraries/naibrd	Contains the source code and GNU Makefile to build NAI SSK Linux share library (.so) and static library (.a)

Building NAI SSK Library

NAI provides the source code of hte NAI SSKLibrary, and you can also rebuild the library on the NAI Intel board.

1. Enter the following commands to build the NAI SSK Library:

Note

To build the SSK for a 64-bit host, change the references to x86_32 to x86_64 in all make commands.

$ cd <directory of NAI SSK on host PC>/Libraries/naibrd
$ make clean NAI_TARGET_BOARD_TYPE=x86_32
$ make all NAI_TARGET_BOARD_TYPE=x86_32

2. Enter the following commands to install the NAI SSK share library:

$ sudo make uninstall NAI_TARGET_BOARD_TYPE=x86_32
$ sudo make install NAI_TARGET_BOARD_TYPE=x86_32

Building naiapp_common Library

naiapp_common is a library included in the AppSrc folder of the NAI SSK package that is used by the sample applications. It must be built and installed like the naibrd library in order for the sample applications to run.

3. Enter the following commands to build the naiapp_common library:

$ cd <directory of NAI SSK on host PC>/AppSrc/naiapp_common
$ make clean NAI_TARGET_BOARD_TYPE=x86_32
$ make all NAI_TARGET_BOARD_TYPE=x86_32

4. Enter the following commands to install the naiapp_common share library:

$ sudo make uninstall NAI_TARGET_BOARD_TYPE=x86_32
$ sudo make install NAI_TARGET_BOARD_TYPE=x86_32

Building NAI Sample Applications

NAI provides source code of the sample applications in the NAI SSK package, and you can rebuild the sample application on the NAI Intel board or Linux host.

5. Enter the following commands to build the NAI SSK sample applications:

$ cd <directory of NAI SSK on host PC>/AppSrc
$ make clean NAI_TARGET_BOARD_TYPE=x86_32
$ make all NAI_TARGET_BOARD_TYPE=x86_32

The compiled .elf files of all sample applications are now available to be run from the /App directory of the package.

Link to original

PetaLinux 2014.2

Building and Running a Project

Building the “Hello World” Application

Create simple HelloWorld.c file on the Host PC as follows:

1. Navigate to File→New→Project→C/C++.

2. Select “C Project” and click “Next >”.

3. Select “Xilinx ARM Linux Executable” under “Project type:” and make sure “Xilinx ARM GNU/Linux Toolchain” is selected under “Toolchains:”. Also, set “Project name:” to “HelloWorld”. Then, click “Next >”.

4. You will be asked to select project configurations. Selecting Debug means debugging and symbolic information is included. Selecting Release means the compiler will optimize the executable and strip it of debugging information. By default, both Debug and Release configurations are selected. You can leave the defaults and select .

5. Add the HelloWorld src file by right clicking on the HelloWorld project in the project explorer and then selecting New→File. This will cause the “New File” window to come up.

6. Make sure that HelloWorld is selected as the parent folder. Then, enter HelloWorld.c as the File Name and click the “Finish” button.

7. Type some code to execute in the HelloWorld.c file. Then, save the project and build it by clicking the hammer icon.

Running “Hello World” on the Target Board

An executable .elf file may be run from the board using either a Serial Console (Tera Term) or the Xilinx SDK.

8. Copy the HelloWorld.elf executable file from your PC to the /home/root directory of the target board.

.. In the Xilinx SDK, in the “Remote Systems” tab in the “Remote System Explorer” perspective, right-click “root” (/Sftp Files/Root///home/root) and click “Export From Project…”

9. In the “Remote file system” window, in the left box, navigate to and select HelloWorld/Debug (but do not check either the “HelloWorld” or “Debug” folders, as this will copy over the entire folder). In the box on the right, select and check the check box next to “HelloWorld.elf”. Then, click “Finish”.

9. Run HelloWorld.elf using either the Serial Console or the Xilinx SDK.

Running “Hello World” Via the Serial Console (Tera Term used in this example)

10. Navigate to the /home/root directory of the target board using the serial console (Tera Term).

11. While in this directory, type chmod 777 HelloWorld.elf to change the permission mode of HelloWorld.elf to executable.
12. Stay in the /home/root directory and type ./HelloWorld.elf to run the program via the serial console.

Running “Hello World” via the Xilinx SDK

12. In the Xilinx SDK, with “HelloWorld” selected in the Project Explorer, go to Run→Run Configurations…

13. In the “Run Configurations” window, double-click “Target Communication Framework”. This will create a new TCF run configuration for the HelloWorld project, called “HelloWorld Debug” by default.

14. With the “HelloWorld Debug” configuration selected, under the “Target” tab, uncheck the check box labelled “Use local host as the target”. Then, in the “Available Targets:” list view, select the row saying “TCF Agent” in the “Name” column and lists the target board’s IP Address in the “Host” column. Then, verify that it says “TCP::” in the “Target ID:” text box. In this case, the IP Address is 192.168.1.16, and the port is 1534.

15. Click the “Apply” button.

16. Navigate to the “Application” tab.

17. Fill in the text boxes highlighted in the picture. For the “Project Name:” text box, you can click the “Browse…” button and select “HelloWorld” from the list of projects. Then, in the “Application” group box, next to the “Local File Path:” text box, you can click the “Search…” button and select “HelloWorld.elf” from the pop up menu. Then, type “/home/root/HelloWorld.elf” into the “Remote File Path:” field.

18. Click “Apply” to save all the changes you just made, and then click “Run” to run “HelloWorld” using the “HelloWorld Debug” run configuration.

Debugging “Hello World” via the Xilinx SDK

The process of Debugging a program via the Xilinx SDK is very similar to the process of Running a program via the Xilinx SDK.

19. If it has not been done already, copy the HelloWorld.elf executable file from your PC to the /home/root directory of the target board. This can be done via the Xilinx SDK. See step 1 of Running “Hello World” on the Target Board for more details.
20. If you have not done so already, create a run configuration for the HelloWorld project (see Running “Hello World” via the Xilinx SDK).

Note

The run configuration you just made for the HelloWorld project can also be used as a debug configuration.

21. Navigate to Run→Debug Configurations…

22. In the “Debug Configurations” window, under “Target Communication Framework”, select “HelloWorld Debug” (the run configuration we created). The configuration properties you set up in Running “Hello World” via the Xilinx SDK should still be there.

23. Click “Debug” to start debugging the HelloWorld project.

Building naibrd_SSK_Linux_ARM_Rev1.63 Library

NAI provides a pre-built library and source code. You can also rebuild the library on your Host PC.

Note

Cross-Compiler and PATH must be configured on Host PC. Refer to Step 18 of the Cross-Compiler subsection of Environment Setup for details.

Note

The latest version of Linux Library for ARM Processor SSK can be found at: http://www.naii.com/Downloads.

24. Copy NAI SSK Library and Sample Application package to Host PC.
25. Build NAI SSK Library on Host PC to generate a (libnaibrd.so) file as follows:

.. Import \Libraries\naibrd as a project.

26. Click File→Import…

27. On the Import pop-up page, select the option “Existing Code as Makefile Project” under “C/C++” and then click the “Next >” button.

28. Click “Browse…” and navigate to \Libraries\naibrd. Once you navigate to this folder and click OK, the text box labelled “Project Name” will fill itself out with the name of the naibrd folder (which is “naibrd”).
29. Select “Xilinx ARM GNU/Linux Toolchain” under “Toolchain for Indexer Settings”, and then click “Finish”.

30. With naibrd Project selected in the Project Explorer, select Project→Properties→C/C++ Build→Environment, and click the “Add…” button.

31. Enter a new environment variable with Name = NAI_TARGET_BOARD_TYPE and Value = arm, and click “OK” button.

32. Click Apply Button

30. To Clean and Build the naibrd project, right-click on “naibrd” in the Project Explorer and click “Clean Project”. Then, with “naibrd” selected in the Project Explorer, either click the hammer icon at the top of the page or right-click on “naibrd” in the Project Explorer and click “Build Project”.

31. Copy NAI library (libnaibrd.so) from /Libraries/naibrd to /Lib/Linux_ARM.

Copy from here

Copy to here

[!note]

NAI sample application MakeFile will link with the library (.so) file in /Lib/Linux_ARM folder. Ensure the latest library file is in that folder.

32. Build NAI SSK Library on Host PC to generate a (libnaiapp_common.so) file as follows:

.. Import \AppSrc\naiapp_common as a project.

33. Click File→Import…

34. On the Import pop-up page, select the option “Existing Code as Makefile Project” under “C/C++” and then click the “Next >” button.

35. Click “Browse…” and navigate to \AppSrc\ naiapp_common. Once you navigate to this folder and click OK, the text box labelled “Project Name” will fill itself out with the name of the naiapp_common folder (which is “naiapp_common”).
36. Select “Xilinx ARM GNU/Linux Toolchain” under “Toolchain for Indexer Settings”, and then click “Finish”.

37. With naiapp_common Project selected in the Project Explorer, select Project→Properties→C/C++ Build→Environment, and click the “Add…” button.

38. Enter a new environment variable with Name = NAI_TARGET_BOARD_TYPE and Value = arm, and click “OK” button.

39. Click Apply Button

37. To Clean and Build the naiapp_common project, right-click on “naiapp_common” in the Project Explorer and click “Clean Project”. Then, with “naiapp_common” selected in the Project Explorer, either click the hammer icon at the top of the page or right-click on “naiapp_common” in the Project Explorer and click “Build Project”.

38. Copy NAI library (libnaiapp_common.so) from /AppSrc/naiapp_common to /Lib/Linux_ARM.

Copy from here

Copy to here

Building an NAI Sample Application

NAI provides prebuilt sample applications and source code. You can also rebuild the sample applications on your host PC.

Note

Cross-Compiler and PATH must be configured on Host PC. Refer to Step 18 of the Cross-Compiler subsection of Environment Setup for details.

Prerequisite: Pre-built naibrd_SSK_Linux_ARM_Rev1.63 Library including the following:

• \Lib\Linux_ARM
• \include

39. Copy naibrd_SSK_Linux_ARM_Rev1.63 Library and Sample Application package to Host PC.
40. Import \AppSrc into the Xilinx SDK.

.. Click File→Import…

41. On the Import pop-up page, select the option “Existing Code as Makefile Project” under “C/C++” and then click the “Next >” button.

42. Click “Browse…” and navigate to \AppSrc. Once you navigate to this folder and click OK, the text box labelled “Project Name” will fill itself out with the name of the AppSrc folder (which is “AppSrc”).
43. Select “Xilinx ARM GNU/Linux Toolchain” under “Toolchain for Indexer Settings”, and then click “Finish”.

41. With AppSrc Project selected in the Project Explorer, select Project→Properties→C/C++ Build→Environment, and click the “Add…” button.

42. Enter a new environment variable with Name = NAI_TARGET_BOARD_TYPE and Value = arm, and then click “OK”.

43. Hit “Apply” button

44. To Clean and Build the “AppSrc” project, right-click on “AppSrc” in the Project Explorer and click “Clean Project”. Then, with the “AppSrc” project selected in the Project Explorer, either click the hammer icon at the top of the page or right-click on “AppSrc” in the Project Explorer and click “Build Project”.

Running NAI Sample Application on Target Board

45. Copy naibrd_SSK_Linux_ARM_Rev1.63 to host pc if you have not done so already.
46. Upload the NAI Library (libnaibrd.so) to /usr/lib on the target board from Host PC.

Note

You can do this in the Xilinx SDK. The libnaibrd.so file should be in \Lib\Linux_ARM, and also in \Libraries\naibrd.

47. Go to the “Remote Systems” tab in the “Remote System Explorer” perspective, right-click “lib” (/Sftp Files/Root///usr/lib), and click “Export From Project…”.

48. In the “Remote file system” tab, select the “naibrd” folder (but do not check it). Then, within that folder, select “libnaibrd.so” and check the check box next to it. Then, click “Finish”.

47. Upload the NAI Common Library (libnaiapp_common.so) to /usr/lib on the target board from Host PC.

Note

You can do this in the Xilinx SDK. The libnaiapp_common.so file should be in \Lib\Linux_ARM, and also in \AppSrc\naiapp_common.

48. Go to the “Remote Systems” tab in the “Remote System Explorer” perspective, right-click “lib” (/Sftp Files/Root///usr/lib), and click “Export From Project…”.

49. In the “Remote file system” tab, select the “naiapp_common” folder (but do not check it). Then, within that folder, select “libnaiapp_common.so” and check the check box next to it. Then, click “Finish”.

48. Choose an executable ELF from \AppSrc and upload it to /home/root/ on the target board.

49. In the “Remote Systems” tab, right-click “root” (/Sftp Files/Root///home/root) and click “Export From Project…”

50. In the “Remote file system” window, select “AppSrc” in the left box (but do not check it), and then select and check the check box next to the project you want to run from the board (in this case, “TTL_BasicOps”). Then, click “Finish”.

49. Run the sample application executable ELF file using either the Serial Console or the Xilinx SDK.

Running NAI Sample Application on Target Board Using Serial Console (Tera Term)

50. Navigate to /home/root/ on the Linux shell terminal. (See picture below Step 3)

# cd /home/root/

51. Give Execute permission to application: (See picture below Step 3)

# chmod 777 (e.g. chmod 777 TTL_BasicOps)

52. Execute program from Linux shell terminal (See picture)

# ./ (e.g. # ./TTL_BasicOps )

Running NAI Sample Application on Target Board Using Xilinx SDK

53. We must create a Run Configuration for the sample program we just copied to the board. With the AppSrc project selected in the Project Explorer, go to Run→Run Configurations…

54. In the “Run Configurations” window, double-click “Target Communication Framework”. This will create a new Run Configuration for the AppSrc project, called “AppSrc Default” by default.

55. With the “AppSrc Default” configuration selected, under the “Target” tab, uncheck the check box labelled “Use local host as the target”. Then, in the “Available Targets:” list view, select the selection that says “TCF Agent” in the “Name” column and lists the target board’s IP Address in the “Host” column. Then, verify that it says “TCP::” in the “Target ID:” text box. In this case, the IP Address is 192.168.1.16, and the port is 1534.

56. Click the “Apply” button.

57. Navigate to the “Application” tab.

58. Fill in the text boxes highlighted in the picture. For the “Project Name:” text box, you can click the “Browse…” button and select “AppSrc” from the list of projects. Then, in the “Application” group box, next to the “Local File Path:” text box, you can click the “Search…” button and select the sample application you want to run from the pop up menu (in this case, TTL_BasicOps). Then, type “/home/root/” into the “Remote File Path:” field.

59. In the Serial Console (Tera Term), navigate to the /home/root directory of the target board and type “chmod 777 <name of sample application in /home/root to run>” (ex. chmod 777 TTL_BasicOps) to give the sample application permission to run.

60. Click “Apply” to save all the changes you just made, and then click “Run” to run the program on the target board using the SDK.

Debugging NAI Sample Application on Target Board Using Xilinx SDK

The process of Debugging a program via the Xilinx SDK is very similar to the process of Running a program via the Xilinx SDK.

61. If it has not been done already, copy the naibrd library and naiapp library .so files (libnaibrd.so & libnaiapp_common.so) from your PC to the /usr/lib directory of the target board. This can be done via the Xilinx SDK. See step 2 of “Running NAI Sample Application on Target Board” for more details.
62. If it has not been done already, copy the sample program executable ELF file you want to run on the board from your PC to the /home/root directory of the target board. This can be done via the Xilinx SDK. See step 3 of “Running NAI Sample Application on Target Board” for more details.
63. If you have not done so already, create a run configuration for the sample application you want to run on the board, and use the serial console to get permission to run the sample application executable file you copied from your PC to the /home/root directory of the target board (see ”Running NAI Sample Application on Target Board Using Xilinx SDK”).

Note

The run configuration you just made for the HelloWorld project can also be used as a debug configuration.

64. With “AppSrc” selected in the Project Explorer, navigate to Run→Debug Configurations…

65. In the “Debug Configurations” window, under “Target Communication Framework”, select “AppSrc Default” (the run configuration we created). The configuration properties you set for “AppSrc Default” in “Running NAI Sample Application on Target Board Using Xilinx SDK” should still be there.

66. Click “Debug” to start debugging the sample application.

Link to original

Windows

Building and Running a Project

The NAI Windows SSK contains a Visual Studio Solution file in the \AppSrc directory named naibrd_AppSrc.sln. Open this file in Visual Studio, and the project window will be occupied by all NAI sample applications and libraries. Right-click on an application folder of your choice and select Build. The sample is now ready to be run by targeting your NAI board over ethernet.

Link to original

VxWorks 6.9

Building and Running a Project

Creating a Project in Workbench

• This sample project is being built for a NAI 64PPC1 SBC, it will also work for other NAI PPC based SBCs. To build the project for an ARM processor SBC such as the NAI 64ARM1, some of the build parameters will be different and they will be noted where applicable.

1. Once Workbench has started, create a new project by selecting the menu option “File”, “New”, “Project”. In the New Project window, expand the VxWorks6.x line by clicking the arrow (►) and select “VxWorks Downloadable Kernel Module Project”. Click the Next button.

2. Enter a name for the project, for this sample we will use NAI_Board_Sample_Project.

3. Click the “Next” button until you get to the “Build Specs” window. Click “Deselect All”, then scroll down the list of available build specs and select “PPC32diab” (“ARMARCH7diab” for an ARM processor) for single core. To build for SMP select “PPC32diab_SMP” (“ARMARCH7diab_SMP” for an ARM processor). Click “Finish”.

• The project will now appear in the Project Explorer window of Workbench.

Importing NAI Board SSK Files into a Project

4. To import the SSK files into the project, right click on the NAI_Board_Sample_Program entry in the Project Explorer window, and then select “Import”. In the Import Window, select “General”, “File System”, then click “Next”.

5. Navigate to NAI Board SSK directory (CDROM). From the base directory, select the naibrd and AppSrc sub directories. This will include the Library and sample programs in the project. Click the “Finish” button.

• The NAI Board library and Sample Source files are now included in the project.

6. You will need to configure the NAI Board Library for the Single Board Computer that it will be running on. To do this, refer to Configure the Board Library in Environment Setup.

Building a Project

7. To build the project, select on the menu, “Project”, “Build Project”. The first time the project is built, the include paths will need to be generated. Workbench will automatically add the paths for you, click the “Generate Includes…” button.

8. When the “Analyses Include directives” windows appears, click “Next”

9. When the “Resolve include directives” window appears, click “Resolve All”.

10. If the “Resolve Ambiguous Include Directives” appears, click “OK”.

11. The include paths will be added to the project.

12. Click the “Next” button.

13. Verify that the “PPC32diab” (“ARMARCH7diab” for an ARM processor) build spec is selected and click “Finish”. The project is now ready to be built. From the menu select “Project”, Build Project”, the project will be built and a NAI_Board_SampleProject.out file will be created.

Creating a Target Remote Server

• A target server connection is needed to download and debug your application program.

14. From the menu select “Target”, “New Connection. Highlight “Wind River VxWorks 6.x Target Server Connection”, and then click Next.

15. Enter the IP address of the SBC and the location of the VxWorks Image that was downloaded to the SBC.

16. Click the next button until you get to the Connection Summary window. Enter a Connection name for your target server and click finished.

17. Your new Target Server connection will appear in the Remote System tab in your Workbench project. Highlight the server, right click and select “Connect”

Downloading Application to the Single Board Computer (SBC)

• The Sample application file can now be downloaded and run on the processor.

18. From the Menu select “Run”,”Download”,”Download”,”VxWorks Kernal Task”

19. Select “NAI_Board_Sample_Sample_Project.out”, the appropriate target processor, and click “Download”. You can now run any of the provided sample applications from the Shell.

Link to original

Next Steps: Sample Application Guides

Now that the SSK is built and you can run the sample applications on your hardware, the Sample Applications section of this site is where development begins in earnest. The Using NAI SSK 1.x Sample Applications overview walks you through the board connection menu and introduces the guide categories.

Each individual sample application guide is designed to be more than a demo walkthrough — it is a practical reference for writing your own code. The guides break down every API call sequence step by step, with annotated code snippets that you can lift directly into your own application. They cover configuration, data transfer, interrupt setup, communication protocols, and diagnostics for each module type, along with troubleshooting tables for common errors. The complete source file is included with every guide so you can see how the individual snippets fit together in a working application.

When you are ready to move from running samples interactively to deploying your own application, the guides also explain how to replace the sample’s interactive board connection menu with hard-coded connection logic suited to your specific hardware configuration. The Opening a Software Handle to Your Board guide provides the full set of board access API calls and configuration options for automating this process.