NetBurner provides
Not all of the NetBurner example programs have networking enabled. If you downloaded an application to your NetBurner device that does not have networking enabled, it will not be recognized by IPSetup. To determine if this is the reason why your NetBurner device no longer works:
Please refer to both the "Cook Book" section and "MTTTY" (in "The NetBurner Development Tools" section) in your NetBurner User's Manual for more information. From Windows: Start --> Programs --> Netburner NNDK --> NNDK Users Manual.
A trap indicates that your application has caused an illegal operation. The monitor responds by halting and restarting your application. A typical trap message printed over the serial port looks like this:
Trap occuredAt this point, you will need to figure out what line of code in your application is causing this. See the SmartTrap utility for help in doing this. SmartTrap usage is discussed in the NetBurner tools manual, located in \nburn\docs\NetBurnerPcTools.
To find out what version of the NNDK tool set you are using - navigate to your Nburn directory, and open up (e.g. in notepad) the release_tag file.
You have two options when you want to change the resolution of the ticks.
Be default, a tick is 50ms in length. This is defined by the constant TICKS_PER_SECOND. The default for this constant is 20. You can safely increase this constant to 200, which will yield a tick length of 500 us.
If this is not fast enough for your application, you may want to use a timer to generate a faster interupt.
The XXX_APP.s19 file is stored as ascii hex, a very inefficent way to store the file; on the actual device it is stored as binary. When you build an application, the last lines of output you will see:
Block starts at 2000000The second number is the number that you need to worry about. In the case I've just shown, the app file was 251K, but only 83.1K were actually needed in the flash.
TaskScan is a network debugging tool that is used to view all of the tasks (and their status) in your application. Note: If you create a new application using NetBurner's Application Wizard, you must manually add the TaskScan functionality.
To use TaskScan you must add #include
There are no performance hits if you include TaskScan in your application unless you call it. TaskScan can be executed from Windows: Start --> Programs --> Netburner NNDK --> TaskScan.
When the TaskScan application is executed, a "TaskScan" window will appear. In order to use the TaskScan application, you must know the IP address of your NetBurner device, and you must select your application's .elf file. The .elf file is located in the same directory as your application.
When you are finished, click the Scan button in the "TaskScan" window.
There are 64 uC/OS tasks - task 1 has the highest priority and task 63 the lowest. There are seven task priorities that are predefined in constants.h (located in the \Nburn\include directory). They are:
#define MAIN_PRIO (50)SmartTrap is an optional debugging tool to help you find out (troubleshoot) where your application trapped. Please refer to your NetBurner Tools User's Manual \Nburn\docs\NetBurnerPcTools\NetBurnerTools.pdf for information about SmartTrap application.
When the monitor boots, the code in the monitor program does a checksum calculation on the application currently in your NetBurner device.
There are two ways to accomplish this:
From NBEclipse:Procedure:
For additional information, please refer to Section 4.3 (Getting Started) Using MTTTY in DocumentationOverview.pdf located by default in C:\Nburn\docs. Instructions can also be found in your Hard Copy Quick Start Guide (i.e RS-232 Downloads).
Pinout information can be found in your platform help documentation, located in \Nburn\docs\platform. Refer to the section labeled "Signal and Connecter Information"
All of the signals on our modules are brought out directly onto the pins from the processor, so there really isn't a need for the schematic.
Since we provide all the source, we provide a schematic only with a license agreement to protect our IP. For additional information, please refer to the Hardware Specifications section in your Hardware User's Manual. From Windows: Start --> Programs --> Netburner NNDK --> Platform Hardware. If you have specific questions about the pins, please submit another support request, and we will answer them.
The most reliable USB to Serial Aaapter we have found so far is Cables Unlimited USB 2.0 to DB9M Serial Adapter. Here is a link to this adapter at Tiger Direct: Cables Unlimited USB to Serial
NetBurner Module Current Draw (mA) Running the Factory Demo
Mod5234-100IR - 210 no network , 310-with networkConnect your host computer to your NetBurner device using MTTTY (From Windows: Start --> Programs --> Netburner NNDK --> Mttty Serial Terminal) and boot to the monitor. You will see the nb> prompt.
Go into the Setup menu (type the word setup at the nb> prompt and press the Enter key), and turn on quiet boot (option Q). This will disable the boot message that is normally printed out when the system is booting. Note: It is still possible to press an (uppercase) A to enter the setup prompt during boot.
If you wish to completly disable stdo, you should comment out the iprintf statements in the ip.cpp file. These statments are located around line 630.
There are two ways to do this:
If networking is enabled in your application:
If you do not have networking enabled, you can use MTTTY to change the wait time of your NetBurner device:
WARNING: If you do not have networking enabled in your application and you set the wait time to 0, you will be unable to change the wait time.
The most common issue that causes this is that you are running Java 1.4. You should upgrade to the latest Java JDK, and this problem will resolve itself.
NBEclipse can be a memory intensive application, depending much on the size of your application. At a minimum, you should have 512 MB of ram in your machine. If you have less then this, the best solution for you is to upgrade the amount of RAM in your machine.
One way that you can reduce the memory footprint on these large projects would be to disable the indexer. To do this, right click on project and go to properties. Under C/C++ Indexer, select No Indexer. Now, restart NBEclipse and see if that improves your memory situation.
Another solution to try is to increase the memory available to NBEclipse. Create a windows shortcut to NBEClipse.exe (right click, create shortcut). On the shortcut, right click and go to properties. Change the target from
C:\Nburn\NBEclipse\NBEclipse.exeRun NBEclipse with the shortcut, and you should have more memory available. If you still get a failure, try 1024M.