Last updated: 8 Oct 2007

1. First Steps
   • Initialize NetBurner Ethernet
   • Load the Factory Demo Program
   • Make a Folder for Your Applications
2. Using IDEs
   • Using DevCPP
   • Using NBEclipse
3. Troubleshooting
   • Correcting an IP address conflict
   • Recovering from a crashing program on the netburner board

Initialize NetBurner Ethernet

1. Verify hardware setup
   1. Serial cable 1 is connected to topmost serial port on PC
   2. Serial cable 1 connects to jack J7 on the board
   3. Red ethernet cable is connected to the hub/switch

      For the black and purple colored hubs: DO NOT CONNECT any cable into port 5 (second from the right if looking at the back ports). It will make the network not work or work intermittently.

      The silver and black network equipment are switches, which don't have that problem, so any open port is okay to use.

   4. Red ethernet cable is connected to the board.
   5. Power adapter is plugged into the electrical socket.
   6. Power adapter connector is plugged into the board.

      A small red LED will light up near the connection, and the segmented LED display will also be on.

      If unplugging the power, do if from the electrical socket end. The connector near the LED might be hot enough to burn your fingers.

2. Launch the MTTY Serial Terminal Program from the Desktop\ECS Lab\Netburner NNDK folder.

   Click on OK if the firewall asks you to unblock or allow access for MTTY.

   The communication parameters should be set to:

     COM1, 115200, None, 8, 1

   COM1 relates to serial port 1 of the PC.

3. Click Connect

   A prompt will appear.

4. Press the small blue button labeled Reset (near the blue dipswitch module) on the NetBurner board

   This will appear:

   Waiting 2 sec to start; 'A' to abort

   Enter a capital A within two seconds:

     A

   A prompt will appear:

   nb>

5. Press reset again if you took too long to respond.
6. Enter:

     help

   to list the help menu.

7. Enter:

     setup

   and check or enter IP parameters, where:

     IP Address = 10.1.x.1
       (x is the number of your NetBurner station -- click on Show Netburner IPs)
     IP Mask = 255.255.255.0
     IP Gateway = IP Address of your host is displayed on the Desktop
                 (or open DOS window enter IPCONFIG)

8. Save the new IP information, and exit

Load the Factory Demo Program

1. Enter

     FLA

   This will appear:

   Begin Down Load now ...

2. Choose from the menu at the top of Multi-threaded TTY (MTTY):

     Transfer
     Send File (text)
     C:\Nburn\MOD5282\original\Mod 5282FactoryDemo_APP.S19

   The file will transfer, and the application will run. Don't abort the application.

3. Create the network routing
   • Open the ECS Lab folder
   • Double click Show Netburner IPs

     Due to a minor undiagnosed bug, it may take two tries to see the information.

     The DOS window will show the Netburner IP address to use and the PC host's IP address for the gateway.

4. From the Factory Demo Application:
   • find your host IP address

         ipconfig

   • ping your host from the board using the IP address above:

     FOR EXAMPLE -- your IP address will be different

         ping 128.208.244.240

   • ping your NetBurner to ensure the Ethernet connection is working; e.g.:

         ping 10.1.25.1

Make a Folder for Your Applications

NetBurner's default folder for projects is C:\Nburn\examples. Since you don't have write privileges to folders on the C: drive:

1. Create a folder called examples on your H: drive.
2. Open a DOS window and type the command:

     C:\Nburn\setenv

3. Redirect project defaults from C:\Nburn\examples to H:\examples

Using DevCPP

DevCPP is the old integrated development environment (IDE) for the Netburner boards.

There is an icon on in the ECS Lab desktop folder's Netburner NNDK subfolder that you can double-click on to start devcpp.

Note that it automatically calls C:\nburn\setenv.bat BEFORE starting devcpp, so whatever you have set up for NBROOT will be what is used for your home folder. Please use a subfolder on your H:\ drive.

Using NBEclipse

NBEclipse is the new integrated development environment (IDE) for the Netburner boards.

There is an icon on in the ECS Lab desktop folder's NBEclipse subfolder that you can double-click on to start NBEclipse.

Note that it automatically calls C:\nburn\setenv.bat BEFORE starting NBEclipse, and it sets up H:\nburn_eclipse as both your Eclipse workspace and for NBROOT. We chose a different workspace than the one the Eclipse icon uses to avoid problems between the two different versions of Eclipse.

A PDF file of instructions on using NBEclipse can also be found in the NBEclipse subfolder.

Note that if you exit NBEclipse and then try to immediately start it again, it will say it is locked. The lock will clear in 30-60 seconds, so try again a little later.

Troubleshooting

The most common issues with netburners in a lab environment are:

• reconfigured hardware setup
• incorrect ip addresses being set
• recovering from a crashing application

1. Reconfigured hardware setup

   Please read about verifying the hardware setup.

2. Correcting an IP address conflict:

   Note: This needs to be done from the mtty program (the MTTY Serial Terminal Program from the Desktop\ECS Lab\Netburner NNDK folder)

   1. Press "Reset" on the netburner board
   2. Enter a capital A:

          A

      to get the nb> prompt.

   3. Enter the configuration menu by entering setup at the nb> prompt
   4. Enter the menu option that shows the ip address.
   5. Enter the correct ip address and press enter
   6. Enter captial S:

          S

      to save the settings.

   7. Reboot the board and check the correct settings have taken effect.
3. Recovering from a crashing program on the netburner board:

   Note: This needs to be done from the mtty program (the MTTY Serial Terminal Program from the Desktop\ECS Lab\Netburner NNDK folder)

   1. Press "Reset" on the netburner board
   2. Enter a capital A:

          A

      to get the nb> prompt.

   3. At the nb> prompt type:

          reset

      and enter capital A:

          A

      to get back to the nb> prompt.

      Note: Doing this extra reset step clears any traps and memory issues that have occurred. If you skip or miss this step you will find that the following steps have no effect. You need to make sure that the crashing program didn't start after you typed reset. If that happened, just press the reset button and try again.

   4. Enter:

          FLA

      to prepare the system for an application upload

   5. Enter the transfer window

      Press F5 or select Transfer/Send file from the pull down menu.

   6. Send a program that you know works

      The factory demo program works best, but any program that runs properly should work.

   7. Once the program has transferred, let the system reboot and check that the new program starts as expected.
   8. If you get the crash again, repeat from step a. again and check that step b. was done.

Change Log