Tornado

2
Setup and Startup
Download Configuration
It is possible that the NetROM is not correctly configured for downloading code to
the target. Make sure you can download and run a simple piece of code (for
example, to blink an LED — this code should be something simpler than a
complete VxWorks image).
2
Initialization
If you can download code and execute it, the next possibility is that the board
initialization code is failing. In this case, it never reaches the point of trying to use
the NetROM for communication. The code in target/src/config/usrWdb.c makes a
call to wdbNetromPktDevInit( ). If the startup code does not get to this point, the
problem probably lies in the BSP. Contact the vendor that supplied the BSP for
further troubleshooting tips.
RAM Configuration
If the NetROM communication initialization code is being called but is not
working, the problem could be due to a mis-configuration of the NetROM. To test
this, modify the file wdbNetromPktDrv.c. Change the following line:
to:
int wdbNetromTest = 0;
int wdbNetromTest = 1;
NOTE: There are two versions of wdbNetromPktDrv.c. The one for the 400 series
is located in target/src/drv/wdb and the one for the 500 series is located in
target/src/drv/wdb/amc500. Be sure to edit the appropriate one.
When you rerun VxWorks with this modification, the wdbNetromPktDevInit( )
routine attempts to print a message to NetROM debug port. The initialization code
halts until you connect to the debug port (1235), which you can do by typing:
% telnet NetROM_IPaddress 1235
If the debug port successfully connects, the following message is displayed in the
telnet window:
WDB NetROM communication ready
43