	U.S. Robotics Channelized T1-386 SDL Application 4.3.2 - READ.ME
	Copyright (C) 1998 3COM, Inc. - All Rights Reserved


	* ABOUT THE FILES ON THIS DISK


        Files                   Function
        -----                   ---------

        PCSDL.EXE              PC SDL PROGRAM

        CT040302.NAC           Chan.T1-386 OPERATING CODE

        CT010001.SDL           Chan.T1-386 SDL PROGRAM LOADED INTO RAM


	* SDL from TCM

	For TCS downloading copy these files to /usrsuite/sdl/ directory
	so that TCM can download these files on command.


        * RUNNING CH-T1 386 SDL


        Copy these files on to your directory on the hard drive.
        Be sure that the RS-232 cable that was
        provided with your purchase is plugged in to the back of the T1
        NIC card.  Make sure you also use the null modem adapter that
        was included with your purchase.  You will need this adapter to plug
        in to the COM port on your PC.

        In order to perform SDL, you should check the DIP switch settings
        on the T1-386 Card. DIP switch 3 enables/disables hardware flow 
        control. To perform SDL, hardware flow control must be enabled. 
        DIP switch 3 must be in the OFF, or down, position. This is the 
        factory setting.

        In addition, your PC COM port baud rate, data bits, and parity
        must match those of the T1-386 Card. If you are unsure of the 
        current baud rate of the T1-386 Card, do the following.

        1) The factory default is 9600 baud. To verify that the T1-386
           Card is set to 9600 baud, connect a PC or dumb terminal to the 
           User Interface Port on the back of the T1 NIC. Set your PC 
           communication package to 9600 baud, and press Enter or Return
           a few times. You should see the T1-386 Main Menu screen 
           scroll by. If you see this, you are ready to begin SDL. If not, 
           try the next option and set the PC baud rate accordingly.


        2) Check the DIP switch settings on the T1-386 Card (do this 
           quickly if you are on a live T1 trunk).

           SW1      SW2      Baud
           ---      ---      ----

           OFF      OFF      9600

           OFF      ON       19200

           ON       OFF      38400

           ON       ON       reserved


                  pcsdl  -p[1] -r[38400] -vNA4.3.2 -vSD1.0.1 -nSDct -nNAct 
                    |      |        |        |          |       |      | 
                    |      |        |        |          |       |      |
        EXECUTABLE---      |        |        |          |       |      |
        COM PORT (1-[n])----        |        |          |       |      |
        PC BAUD RATE-----------------        |          |       |      |
        SW NAC CODE REV-----------------------          |       |      |
        SDL VER #----------------------------------------       |      |
        SDL TYPE-------------------------------------------------      | 
        NAC TYPE-------------------------------------------------------- 
       

        At the DOS prompt, type:


        c:pcsdl  -p1 -r38400 -vNA4.3.2 -vSD1.0.1 -nSDct -nNAct 


        When SDL begins, the RN/FL LED on the T1-386 Card will begin flashing
        green.  Your PC screen should have the following messages scrolling
        while SDL is running:

        Verifying Initialization Program File. . .100 %\
        Verifying Operation Program File. . .100 %\
        Establishing Communication...
        Downloading Initialization Program. . .100 %\
        Initiating Software Download. . .
        Downloading Operation Program. . .100 %\
        Erasing Flash ROM. . .
        Programming Flash ROM. . .
        Checking Download Program CRC. . .
        Software Download Successful!

	c>


        * SDL SUCCESSFUL AND COMPLETE


        When SDL is complete, the RN/FL LED will continue to flash for about
        five seconds, and then go back to a solid green. SDL is complete
        at this point. If you now go back to your T1-386 Main Menu screen,
        you will see that the "Operation Code Linked Date" will have the
        current SDL date. The "Boot Code Linked Date" would only change if
        the ROMS were replaced.

        If there are problems or questions about SDL, please check
        Appendix A in your T1-386 Card manual. If these problems or questions 
        remain unanswered, please call our Technical Support Department.


   * ERROR MESSAGES
 

   All of the following errors are considered fatal and will cause
   the PC software to abort.  If one of these errors is detected, the 
   operator must restart the PC software download.


   Bad Address in Downloadable Data

   The NAC SDL software detects an invalid address while parsing
   through the Intel records.  These Intel records are down-
   loaded in RAM and are used for flash ROM programming.


	Bad CRC on Downloadable Code in ROM

	The CRC of the software programmed in ROM is corrupted.


	Bad CRC in Program Loaded in RAM

	The CRC of the program just loaded in the NACs RAM is
	corrupted.


	Bad File Number

	The file system in the SDL program detects a bad file number
	when trying to close the file.  This normally indicates either a
	programming error or program corruption.


	Bad Message Buffer

	The communication buffer is too small or invalid due to
	program corruption.


	Bad Message CRC

	The CRC associated with each message is bad, possibly due to
	noise on the transmission line.


	Bad Message Length

	The SDL program detects an invalid message length at the data
	link layer.  The message length is either larger or smaller than
	the length required by the protocol.  This error normally indi-
	cates message corruption due to noise on the transmission line.


	Bad Start of Text Characters

	The data link layer of the PC SDL program detected an invalid
	start-of-text characters sequence.


	Command Line Error

	The PC SDL program detected unknown command line
	arguments.


	Communication Error

	The PC SDL program detected unknown communication
	errors.


	File CRC Error

	During file verification, prior to SDL, a bad CRC was found on
	the program file.  This indicates file corruption.


	File Error

	The PC SDL program detected unknown information in the file
	header of the program to be downloaded.


	File I/O Error

	The PC SDL program detected unknown file I/O errors.


	Indicator Unknown

	The PC SDL program detected an unrecognized indicator in
	the MB message returned from the NAC software.


	Insufficient Number of Arguments

	The number of arguments in the command line is less than the
	number of required arguments.  The required arguments are -p (COM port),
	-r (serial port rate), -vsd (.SDL file version), -vna 
        (.NAC file version), -nsd (.SDL file type) and -nna (.NAC file type). 


	Insufficient Work Space to Download Program

	The work space returned from the loader is too small to accom-
	modate software download for the initialization or NAC
	operation program.


	Invalid Access Code

	The file system software of the SDL program denies access to
	the file due to an invalid access code.  This error probably indi-
	cates a program corruption in the SDL program.


	Invalid Argument

	The file system software does not recognize the arguments
	passed from the application software.  This normally indicates
	program corruption.


	Invalid Baud Rate

	The valid baud rates are 9600, 19200, and 38400 bps.


	Invalid Card Type

	The valid card types are CT for a T1-386 Card, ST for a Single T1 Card,
	QM for a Quad Modem, TR for a Token Ring Card, T1 for a Dual T1 Card,
	DP for T1-PRI card, and NM for a Network Management Card.

	Invalid Code Returned from Flash ROM Erase

	An error was detected while erasing flash ROM.


	Invalid Code Returned from Flash ROM Program

	An error was detected while programming flash ROM.


	Invalid COM Port

	The valid COM Ports are 1, 2, 3, and 4.


	Invalid COM Port Handler

	The communication driver software detected an invalid com-
	munication port handler.  This normally indicates program
	corruption.


	Invalid Control Word

	The SDL application layer does not recognize the control word
	returned from the NAC.


	Invalid Device/Manufacturing ID in Flash

	There was a problem reading the ID in flash ROM due either to
	a wrong or bad chip.


	Invalid Directory Path

	The directory path specified in the command line does not
	comply with DOS naming conventions.


	Invalid Flash ROM ID for This Card

	The NAC SDL program does not recognize the flash ROM ID
	sent from the PC SDL program.


	Invalid File Type

	The PC SDL program detected an invalid file marker in the file
	to be downloaded.


	Invalid Intel Record Found

	This error occurs when the NAC SDL software detects unrecog-
	nized Intel record types while parsing through the Intel
	records in RAM for flash ROM programming.


	Invalid Software Version

	The software version specified in the command line has an
	invalid syntax.  The valid syntax is xxx.xxx.xxx , where xxx is a
	decimal number 0-255.


	Missing Required Argument

	There is a sufficient number of arguments, but some required
	arguments are missing.  The required arguments are -p (COM port),
	-r (serial port rate), -vsd (.SDL version number), -vna (.NAC version
	number), -nsd (.SDL file type), and -nna (.NAC file type).


	No Response from NAC within the Time-out Period

	The PC sent a message to the NAC three times and failed to
	receive a response.


	No Such File or Directory

	Cannot find the program to be downloaded in the specified or
	default directory.


	Permission Denied

	The SDL program tries to open a file, but the file system
	software denies access to the file.


	Problem Erasing Flash ROM

	The PC software's request to erase flash ROM was
	unsuccessful.


	Programming Flash ROM Error

	An error was detected during flash ROM programming.


	Software Download Error

	Unknown error occurs during software download.


	Too Many Open Files

	The number of open files exceeded the number of open files
	allowed by the file system software.


	Unknown Error Returned from NAC

	The PC SDL program does not recognize the error code
	returned from the NAC.


	Unknown Information Received from NAC

	The CRC is good, but the application layer detected unrecog-
	nized information, for example, control word indicators in the
	message.


	VPP Programming Voltage Low

	The voltage is too low for flash ROM programming.


	Work Space Buffer Overflow

	There is no more space left in the NACs buffer for the PC to
	download its data.  Since the PC software knows the RAM
	buffer size and can determine when the buffer is filled, this
	should not happen unless the software is corrupted.


	Wrong Card Type

	The card type specified in the command line does not match
	the one in the file header of the software to be downloaded.


	Wrong Card Type for Software Download

	The card ID returned from the NAC does not match the
	software type to be downloaded.  This normally indicates that
	an operator may be trying to download software to the wrong
	card, or the card ID stored in EEPROM is corrupted.


	Wrong File Type

	There is an invalid file type in the program to be downloaded.


	Wrong Software Type

	There is an invalid software type in the program to be
	downloaded.


	Wrong Software Version

	The software version specified in the command line does not
	match the one in the file header of the software to be
	downloaded.

	Note:
	The internal clock is NOT a recommended clock source. It is provided
	purely for testing purposes. Inorder to use this set the timing
	sources on one card as "0 0 1" and issue "reset to highest priority
	timing source command" from the User Interface Menus. On the card-
	status menu it will  show as "Internal(Master)".Then on the second
	card set the timing source as " 1 2 0" from the user interface menu.
	The TCM doesn't support "Internal(Master)" so use the user interface 
	menu. 
	
