Table of Contents NMS Glossary Previous Page Next Page Version


Chapter 2

Communications Processor Console Utility: cpcon


2.1 Running cpcon

2.1 Running cpconTop of Page

Name

cpcon

Purpose

Monitors the flow of data to and from TX board communication processors.

Note: Before running cpcon, you may want to run a program (for example, ping) to test network transmissions between Fusion gateway systems.

Usage

cpcon option option


command

Valid options include:
Option

Function

-b boardnumb

TX board number (1-8). (default = 1)

-c channelnumb

Dual port RAM channel number. (default = 6)

Valid commands include:
Command

Use this command to display...

Information Displayed

help

The full command set or details for a specified command name.

Names of valid commands.

chan

Ownership of all dual port RAM channels (replaced by VPORTS command).

List of dual port RAM channels/ownership.

date

The current date
(as viewed by the communication processor).

Current date.

dpram

Information about the dual port RAM interface.

· DPR Context: Memory address of dual port RAM control structure.

· CP Number: Communications processor number assigned to this board.

· VS,VR,NS,NR: Sequence numbers used to maintain synchronization with the host processor.

· Errors: A set of error counters indicating communication problems.

· Current DPD: Address of dual port descriptor currently involved in transfer.

· TX Semaphore: State of semaphore used to ensure only 1 transmit in progress.

· Two Part: Status of transmit that was broken into 2 parts.

· Trans Queue: Number of transmits waiting to go to host (and peak number queued).

dump memory address

A hex/ASCII dump of the memory address specified (256 bytes display).

Address information.

if

All interfaces currently defined.

· Res#: Resource number that interface is associated with.

· HW: Hardware type for given interface:

DPR Dual port RAM
interface.

SCC Serial communications
controller.

ETH Ethernet controller.

QCH QUICC32 channel.

· Type: Type of usage:

SER Serial.

ETH Ethernet.

TDM Time division
multiplexed.

· Port: Physical port number associated with interface.

· Max Tx: Maximum number of pending transmit requests over interface.

kernel

Information from the main KERNEL control structure.

· Context: Memory address of KERNEL context block.

· Unused RGDs: Number of region descriptors currently available.

· current: Shows information about the current task.

· Memory: Shows the address range and total amount of memory on the system.

· msg: Shows message handing key and errors related to messages.

· tcb: Shows task control block key and TCB deallocation errors.

· tmr: Shows timer control key and timer queuing errors.

· levels: Shows how deep exceptions and critical code areas have nested.

· semaphore: Shows any saved SR (due to critical code) & state of DMA semaphore.

· sys info: Memory address of the SYSTEM INFORMATION block.

· idle peak: Counter used for determining CPU utilization.

· Timer Granularity: Indicates the tick interval used to advance timers.

l1dpr

All dual port RAM channel assignments.

· Ch: Dual port RAM channel number owned by task.

· Nam: Name of task that has attached to the given channel.

· Rx Succ: Number of packets successfully received from the host.

· Tx Succ: Number of packets successfully transmitted to the host.

· Tx Fail: Number of transmits to the host that failed.

· Tx Q-Err: Number of times a transmit request could not be added to the queue.

· Tx BadCP: Number of transmit requests to invalid destination communication processor.

· Rx Giant: Number of packets received from host that were larger than allowed.

· Rx Drop: Number of packets received by communication processor but dropped before given to task.

· PcQ: Number of packets currently queued to be transmitted to the host PC.

lfd

All open files (logical file descriptors).

· Name: Unique name identifying file.

· State: Either \pending\ (open has not completed) or \live\.

· Task: Name of the task that owns the file (i.e. issued the open).

· IAddr: Internal address associated with open.

· Server: Name of the task that serviced the open.

· IO Outst: Count of IO requests issued by owner and not yet responded to.

· CLOSING: Indicates whether a close was issued.

· CLOSED: Indicates whether the server responded to a close request.

Log

The KERNEL error log.

KERNEL error log.

mem

Total amount of memory in use and available.

Memory in use and available.

memreg

Assignments for all memory regions.

· Owner: Name of task owning the memory region (*KERNEL if no task).

· Name: Name of memory region (or address if not named).

· Start: Starting memory address of region.

· End: Address of last byte in memory region.

· Size: Total number of bytes in region.

· Access: Memory access flags.

modem

Modem signals for each physical port.

List physical ports/modem signals.

mvip

All current MVIP stream/timeslot assignments.

· Status/Map: Status of FMIC (\reset \enabled\disabled\) and frame B value.

· Clocking: Clock source for Master, Sec8K, and T1/E1.

· Current FMIC Map: Output destination where connection is directed (MVIP or LOCAL stream/timeslot).

· Source where connection originates (MVIP or LOCAL stream/timeslot).

· Stream: MVIP stream number (Output and Source).

· TS: MVIP timeslot number (Output and Source).

· Pat: Pattern being generated when in pattern mode.

· Mode: FMIC mode for connection (NORMAL, PATTERN, or REVERSE).

· Conn: Connection indication of one of following types:

<--> Full duplex.
Connects points
to each other.

<--- Connect points to
entry with
NULL connection.

---- Connect of NULL
when Mode =
PATTERN.

!!!! Connect of NULL
when Mode !=
PATTERN.

???? Connect points to
entry without
connect back.

pmem

The percentage of memory assigned to each task.

List of tasks with allocated memory percentages.

q32

Information about each 360 operating in QUICC32 mode.

· 360 #: Number identifying the 360 that is in QUICC32 mode (0 = MAIN).

· context: Memory address of context block controlling QUICC32.

· IMPBASE: Base address of QUICC32 360 chip.

· Level 1: Level 1 driver context block assigned to each QUICC32 channel.

· ctrlbase: Control base address for SCC3 and SCC4 (channels split between).

· prbase: Parameter ram base address (SCC3 and SCC4).

· stats: Statistics indicating total number of interrupts and error counts.

Ques

The list of priority queues (tasks waiting to execute).

Priority queue list.

res

All resources currently defined.

List of defined resources.

scc

Information for each serial communications controller.

· Type: Type of serial communications controller (SCC) usage:

SCC Physical SCC port
(POD port).

ETH Physical ethernet
port.

MVIP MVIP bus
connection.

· Chl #: Channel number associated with serial communications controller.

· SCC # : Physical serial communications controller number of processor indicated by IMPBase.

· IMPBase: Memory address of base of serial communications controller processor.

· CTLBase: Control base address for serial communications controller.

· PRamBase: Parameter RAM base address for serial communications controller.

· Tx/Rx: Average (last 10 secs) transmit and receive packet counts.

t1cfg

The T1/E1 configuration.

· Framing: Type of framing (T1 or E1) in use:

D4 D4 (193S) Framing
(T1).

ESF Extended
Superframe
Format(T1).

CCS Common Channel
Signaling (E1).

CAS Channel
Associated
Signaling (E1).

CCS/CRC CCS with CRC4
(E1).

CAS/CRC CAS with CRC4
(E1).

· Encoding: Type of encoding (T1 or E1) in use:

NONE No encoding.

AMI AMI encoding
with no
zero suppression.

B7ZS Bit 7 Stuffing
(T1).

B8ZS Bipolar Eight Zero
Substitution (T1).

HDB3 High Density
Bipolar
Order 3 (E1).

· Build Out: Measure of build out (T1 in feet / E1 ohm desc).

· Robbed Bit: (T1 only) either blank (not active) or \Robbed Bit\.

· Loop Master: Either blank (not master) or \Loop Master\.

t1stat

T1/E1 statistics information.

T1/E1 statistics.

tasks

All tasks created on the TX board.

· Name: Name of the given task (leading \$\ indicates KERNEL task.

· Prior: Priority of task (1 = highest priority; 31 = lowest).

· Read: Indicates whether task is ready to be executed.

· State: Shows the current state of task. Valid states include:

Created Task has been
created but
never executed.

Stalled KERNEL detected
invalid instruction.

Waiting Task is asleep,
waiting for work.

Blocked Higher priority
task currently
blocking.

Running Task is executing.

Holding Invalid KERNEL
service was
requested.

time

The current time (as viewed by the communication processor).

Current time.

timers

All timers that exist on the system.

· Owner: Name of task that created the timer.

· Address: Address of timer control block.

· Period: Number of milliseconds between timer ticks.

· Init: Initial number of milliseconds waited.

· Value: Number of milliseconds remaining before timer fires.

· User Key: Key provided by the application.

· User Pkt: Timer control packet provided by user.

· Status: Current status of timer (running or stopped).

· Timer Granularity: Indicates the tick interval used to advance timers.

tmem

All memory regions assigned to the specified task.

· Owner: Name of task ($kernel if no task specified).

· Name: Name of memory region (or address if not named).

· Start: Starting memory address of region.

· End: Address of last byte in memory region.

· Size: Total number of bytes in region.

· Access: Memory access flag.

util

The current and average system utilization.

Current/average system utilization.

vol

All volumes - mounted tasks (I/O accessible).

· Name: Name of the mounted volume.

· Devtype: Device type used on the mount (indicates alarm number range).

· Task: Name of the task that has been mounted as \Name\.

Note: Mount Pending indicates that the mount has not been completed.

vport vp#

Detailed information for the virtual port number specified.

· Vport: Virtual port number.

· Owner: Task that has attached to virtual port.

· AtchKey: Task-supplied key associated with attach.

· Addr1..4: Receive addresses associated with port (up to 4, all F's = ALL).

· Rx Frm: Maximum receive frame size.

· State: Current state of the virtual port:

FREE No task has been
attached
to virtual port.

DISABLED Task attached, but
virtual port not
enabled.

IDLE Virtual port
enabled, but
not transmitting.

FULL Transmitting all
allowed for
transmit window.

DISABLING Bringing down
an enabled virtual
port.

· Free/Pend: Number of transmit requests available (free) and in progress (pend).

· Tx/Rx Stats: Counts of frames/bytes transmitted and received.

· Fail Stats: Counts of Tx and Rx failures with last error code reported.

· HW Port: Hardware type and physical port number.

· Lvl1 Key: Level 1 driver key (and protocol indication).

· Type-Specif: HW type-specific additional description of virtual port.

vports

All virtual ports currently defined.

List of defined virtual ports.

Procedure

To run cpcon:

  1. Open a command line window.

    
    
  2. Navigate to the directory nms\tektx\soft\util.

    
    
  3. At the prompt, enter the following:

    
    cpcon [-b boardnumb -c channelnumb]
  4. At the prompt, enter one of the cpcon commands.

    
    cpcon displays the requested information.

Description

In Fusion systems, cpcon can be used as a diagnostic tool to track the flow of data between a TX board communication processors and an NMS board DSPs.

Use cpcon to verify that:



Table of Contents NMS Glossary Previous Page Next Page Version


Want to send us feedback on our documentation? Email: Tech_Pubs@nmss.com
Copyright © 2000, Natural MicroSystems, Inc. All rights reserved.