Transcript
1 BootROM/Tester V3.30b Release Notes 1.1
Affected switches: NH2012, NH2012R, NH2012RFO, NH2015, NH2048
1.2
Changes
1.2.1 External Loopback 1.2.1.1 “loopback 2” now puts the tester in external loopback mode In this mode, external loopback connectors MUST be attached to the device on ALL ports for the self-test to complete properly. To run the tester in external loopback mode, type: dbg> lo 2 dbg> te Note: “lo 2” will NOT work with the NH2048
1.2.1.2 Fiber PHY (100BaseFX/Gigabit/ATM) Simply loop a single fiber of appropriate type from a ports TX to it’s own RX connector.
1.2.1.3 RJ45 PHY (10/100BaseFX) Get a RJ45 jack and loop pins 1 to 3 and 2 to 6.
1.2.2 Support for i960 family of modules (ATM, FDDI, etc.) 1.2.2.1 Added “inmp” family of commands The INMP protocol is the method by which the on-board MSII family CPU (the AMD 29k-based) management module) communicates with the module CPU (the ATM/FDDI i960-based module). There are two possible INMP paths for each port – a dedicated serial line and an in-band path via the switch backplane. All inter-CPU communication takes place over this channel; both the bootrom/debugger and the Snagent software depend heavily on INMP.
Usage: “inmp [-i[i]] [-p port] [-c count] [cmd […]]” “-i”: use the “hybrid” inmp interface (i.e. serial port tx, in-band rx) “-ii”: use the “inband” inmp interface (i.e. in-band tx AND rx). Note that due to a bus arbitration bug, the FIRST in-band message to or from each module may be lost. “-p port”: which port to send the inmp command to. For example, on the 2012, port 9 is the first module, and port 11 is the second. If no [-p port] is specified, the default is the port that was last accessed.
“-c count”: number of times to repeat the command. Useful only with the “ping” command to test the communications channel (see “ping”, below). cmd is one of the following: (if cmd is not specified, the default is “ping”) “fetch” copy the contents of flash into module memory. “run” execute the program in module memory “fr” equivalent to both fetch and run. “core
[arguments]” raw core command – reserved for debugging. “exec [arguments]” raw exec command – reserverd for debugging. “get ” raw get param command – reserved for debugging “erase” erase the module’s flash “swap [0|1]” when in loopback mode, whether to swap a frame’s DA and SA – reserved for debugging “lo” raw loopback command – reserved for debugging. Use “pmode” or “loopback” command instead. “reset” reset the board. Necessary if the board is to be used with the in-band INMP channel (see below) Note: after the board is reset, the board is NOT sent a fetch/run command. This means that “inmp fr” must be sent if external loopback mode is needed after an “inmp reset”. In addition, the “loopback 2” command should be re-typed following the fetch/run. I.e. dbg> inmp -p 9 reset dbg> inmp -p 11 reset dbg> inmp -p 9 fr dbg> inmp -p 11 fr dbg> loopback 2 dbg> tester “ls” list the contents of the module’s flash file. “sitx.rbf” is needed for the in-band channel (i.e. neither the self test nor in-band INMP will work w/o it). “app” is needed for fetch/run to succeed. “ping” send an empty request to the module. Used to test the INMP channel (see also the [-c count] option). If no command is specified, “ping” is the default. E.g. “inmp -ii -p 11 -c 100” will send 100 in-band pings to port 11.
1.2.2.2 “tftp” command modified The tftp command now allows fast, in-band downloads to the modules.
Usage: “tftp [-i[i]] [-f] server_ip filename [port] “-i”: use the “hybrid” inmp interface (i.e. serial port tx, in-band rx) “-ii”: use the “inband” inmp interface (i.e. in-band tx AND rx) “-f”: if [port] is specified, write the code into the module’s flash. By default, if [port] is specified the code will only be downloaded to the module’s memory, and not written to the flash for permanent storage. “server_ip”: tftp server IP in dot notation (xxx.xxx.xxx.xxx) “filename”: filename to fetch from server_ip. “port”: port number to send file to. If not specified, the default is the on-board mgmt flash, and the -f argument has no effect. Note that the “ip” command MUST be used before using tftp.
1.2.3 Preliminary support for NH2048 family As of yet, the NH2048 is not supported in the “lo 2” mode. Full external tester functionality is also still in progress.
1.2.4 Execute FETCH/RUN on all modules in interactive mode Downloading into modules using interactive debugger and INMP is a bit different now. Since fetch/run is executed when the debugger enters interactive mode, the modules stop responding to the in-band INMP channel. Either the out-of-band channel must be used for downloading (which is <1kbyte/sec) or the “inmp reset” command (see above) should be used to reboot the module into its boot status, allowing tftp –ii to be used, assuming the SI altera is already loaded. Since the module firmware is normally downloaded initially when the board has NO SI firmware, the in-band is not used. In this case, the following commands should be executed: dbg> ip 192.168.1.xxx (local-ip) dbg> tftp -f 192.168.1.xxx atm.rev 9 (where xxx is the tftp server ip) dbg> tftp -f 192.168.1.xxx atm.rev 11 Should the SI firmware be loaded and present, the firmware can be upgraded over the in-band interface as follows: dbg> inmp -p 9 reset dbg> inmp -p 11 reset dbg> inmp -ii -p 9 (may have to be done a few times) dbg> inmp -ii -p 11 (may have to be done a few times) dbg> ip 192.168.1.xxx (local-ip) dbg> tftp -ii -f 192.168.1.xxx atm.rev 9 (where xxx is the tftp server ip) dbg> tftp -ii -f 192.168.1.xxx atm.rev 11
1.2.5 “stats” command fixed in debug mode rollover bug originally introduced in 3.10f release
1.2.6 additional debugging in send_and_test and loopback routines added length encoding in packet for redundant verification
1.2.7 fixed bug in loopback test if a port fails, the loopback test continues testing the rest of the ports, instead of aborting the test.
