Version

Chapter 3

Communications Processor Task Loader Utility: cplot

3.1 Running cplot

3.2 cplot Error Codes

: 3.2.1 Errors While Initializing KERNEL
: 3.2.2 Errors While KERNEL is Executing
: 3.2.3 Errors While Prebooting
: 3.2.4 Errors While Processing Host File

3.1 Running cplot

Option	Use this option to...
`-a`	Start the named communications processor task. The communications processor task specified by the `-n` option is automatically started. If the `-a` option is specified along with the `-f` option, the communications processor task is started immediately after it is loaded. Default = `off`.
`-c` *cp#*	Specify the communications processor number (1-8). Default = 1.
`-f` *filename*	Specify the object file for `cplot` to load. This is a required option and the file must be an SDSI-type object file.
`-g` *functioncode*	Download TDM configuration file output (*functioncode)* from the `tdmcfg` utility.
`-k`	Specify the kernel load. Default = off.
`-n` *name*	Specify a communications processor task name. When used with the `-f` option, `cplot` requests a communications processor task to be created with the taskname *name*. The program object file is then loaded as the program for the new communications processor task. Required. Maximum 8 characters.
`-o` *options*	Specify the options to use when executing the communications processor task. The *options* is a longword. It is task specific and may use hexadecimal notation by prepending a `0x`. Default = 0.
`-p` *priority*	Specify the priority of the communications processor task. Valid priority levels are from 0-31. By default, the created communications processor task will have a priority of 30. 0 is the highest priority, 31 is the lowest priority.
`-q` *number*	Enable QUICC32 functionality: Option Operation `0` Disables QUICC32 (default) `1` Enables QUICC32 slave processors `2` Enables QUICC32 slave and main processors Can only be used if the 68360s on the TX board are QUICC32 parts and enabled.
`-s` *size*	Specify the stack size of the communications processor task. Valid stack sizes are from 4096 to 40960 bytes. By default, the communications processor task stack size will be 4096 bytes. Hexadecimal notation may be used by prepending a `0x`.
`-u`	Download special microcode options. Currently `SS7` is the only available microcode option. Default = none.

Procedure

To run cplot:

From the command line, navigate to the directory nms\tektx\soft\util.

Enter the following at the command line:

cplot option option

Example

A program which has been compiled into the object file tpx.lot can be loaded onto the communications processor. The name of the communications processor task is tpx, its priority is 31, its stack size is 4096 bytes. The task will start running immediately (due to the -a autostart option).
To load this task onto the communications processor, enter:
cplot -f tpx.lo -n tpx -p 31 -s 4096 -a
The output display looks similar to the following:
TXn000 Communication Processor Task Loader Utility V2.00
Copyright 2000 Natural MicroSystems, Inc.

3.2 cplot Error Codes

cplot returns four types of errors at four different times: Errors that occur while initializing the KERNEL Errors that occur while the KERNEL is executing Errors that occur while prebooting Errors that occur while processing the host file
The following sections list the errors returned while cplot is running.

3.2.1 Errors While Initializing KERNEL

Error Number

Description

`$21`

Configuring interrupt controller.

`$22`

Initializing KERNEL logger.

`$23`

Initializing exception table.

`$24`

Initializing memory management.

`$25`

Initializing library handling.

`$26`

Initializing KERNEL's GPLIB context.

`$27`

Initializing system information region.

`$28`

Initializing configured sub-processors.

`$29`

Installing microcode.

`$2A`

Initializing SS7 microcode handling.

`$2B`

Initializing T1/E1 handling.

`$2C`

Initializing DMA controller.

`$2D`

Activating named object handling.

`$2E`

Initializing timer management.

`$2F`

Initializing task dispatcher.

`$30`

Initializing dual port RAM services.

`$31`

Initializing serial communications.

`$32`

Initializing CEBus communications.

`$33`

Initializing mobile communications.

`$34`

Initializing Ethernet communications.

`$35`

Initializing time division multiplexing.

`$36`

Initializing QUICC32 handling.

`$37`

Initializing virtual port handling.

`$38`

Initializing IO system.

`$39`

Reading the EEPROM.

`$3A`

Verifying the EEPROM checksum.

`$3B`

Enabling flash memory access.

`$3C`

Determining hardware resources.

`$3D`

Setting write latches.

`$3E-$7F`

Reserved for future errors.

Error Number	Description
`$21`	Configuring interrupt controller.
`$22`	Initializing KERNEL logger.
`$23`	Initializing exception table.
`$24`	Initializing memory management.
`$25`	Initializing library handling.
`$26`	Initializing KERNEL's GPLIB context.
`$27`	Initializing system information region.
`$28`	Initializing configured sub-processors.
`$29`	Installing microcode.
`$2A`	Initializing SS7 microcode handling.
`$2B`	Initializing T1/E1 handling.
`$2C`	Initializing DMA controller.
`$2D`	Activating named object handling.
`$2E`	Initializing timer management.
`$2F`	Initializing task dispatcher.
`$30`	Initializing dual port RAM services.
`$31`	Initializing serial communications.
`$32`	Initializing CEBus communications.
`$33`	Initializing mobile communications.
`$34`	Initializing Ethernet communications.
`$35`	Initializing time division multiplexing.
`$36`	Initializing QUICC32 handling.
`$37`	Initializing virtual port handling.
`$38`	Initializing IO system.
`$39`	Reading the EEPROM.
`$3A`	Verifying the EEPROM checksum.
`$3B`	Enabling flash memory access.
`$3C`	Determining hardware resources.
`$3D`	Setting write latches.
`$3E-$7F`	Reserved for future errors.

3.2.2 Errors While KERNEL is Executing

Error Number

Description

`$80`

Uninitialized vectors.

`$81`

Bus error.

`$82`

Address error.

`$83`

Illegal instruction.

`$84`

Zero divide.

`$85`

Priviledge violation.

`$86`

Function call error.

`$87`

Breakpoint.

`$88`

Trace.

`$89`

No such task.

`$8A`

Task is currently executing.

`$8B`

Already exists.

`$8C`

Invalid parameter.

`$8D`

Serial DMA bus error.

`$8E`

Internal DMA bus error.

`$8F`

Checksum disparity.

`$90-$9F`

Reserved for future errors.

Error Number	Description
`$80`	Uninitialized vectors.
`$81`	Bus error.
`$82`	Address error.
`$83`	Illegal instruction.
`$84`	Zero divide.
`$85`	Priviledge violation.
`$86`	Function call error.
`$87`	Breakpoint.
`$88`	Trace.
`$89`	No such task.
`$8A`	Task is currently executing.
`$8B`	Already exists.
`$8C`	Invalid parameter.
`$8D`	Serial DMA bus error.
`$8E`	Internal DMA bus error.
`$8F`	Checksum disparity.
`$90-$9F`	Reserved for future errors.

3.2.3 Errors While Prebooting

Error Number

Description

`$A1`

Setting clock synthesizer.

`$A2`

Setting system protection.

`$A3`

Clearing internal DPRAM.

`$A4`

Setting timing parameters.

`$A5`

Setting chip selects.

`$A6`

Initializing refresh controller.

`$A7`

Sizing DRAM banks.

`$A8`

Verifying DRAM bank configuration.

`$A9`

Setting final DRAM mapping.

`$AA`

Resetting refresh and page size.

`$AB`

Testing DRAM.

`$AC`

Completing preboot.

`$AD`

Operation timed out.

`$AE`

Invalid selection index.

`$AF`

Invalid internal address.

`$B0`

Remapping chip selects.

`$B1`

Starting preboot.

`$B2`

Ending preboot.

`$B3`

Verifying KERNEL checksum in dual port RAM.

`$B4`

Initializing SUB 360(s).

`$B5`

Verifying KERNEL checksum in DRAM.

`$B6-$BF`

Reserved for future errors.

Error Number	Description
`$A1`	Setting clock synthesizer.
`$A2`	Setting system protection.
`$A3`	Clearing internal DPRAM.
`$A4`	Setting timing parameters.
`$A5`	Setting chip selects.
`$A6`	Initializing refresh controller.
`$A7`	Sizing DRAM banks.
`$A8`	Verifying DRAM bank configuration.
`$A9`	Setting final DRAM mapping.
`$AA`	Resetting refresh and page size.
`$AB`	Testing DRAM.
`$AC`	Completing preboot.
`$AD`	Operation timed out.
`$AE`	Invalid selection index.
`$AF`	Invalid internal address.
`$B0`	Remapping chip selects.
`$B1`	Starting preboot.
`$B2`	Ending preboot.
`$B3`	Verifying KERNEL checksum in dual port RAM.
`$B4`	Initializing SUB 360(s).
`$B5`	Verifying KERNEL checksum in DRAM.
`$B6-$BF`	Reserved for future errors.

3.2.4 Errors While Processing Host File

Error Number

Description

`$C0`

Unable to open file.

`$C1`

Unable to bootstrap KERNEL.

`$C2`

Truncated file.

`$C3`

Invalid file.

`$C4`

Failed transfer of code block.

`$C5`

Error starting KERNEL.

`$C6`

Task already exists.

`$C7`

Unable to create task.

`$C8`

Invalid version of `.lot` file.

`$C9`

Insufficient memory on host.

`$CA`

Error getting memory on communications processor.

`$CB`

Error while closing file.

`$CC`

Error setting task program counter.

`$CD`

Error performing TDM configuration.

`$CE`

Unknown KERNEL function requested.

`$CF`

Unable to access DPR driver.

`$D0`

Unable to obtain loader channel.

`$D1`

Unknown type of communications processor reported.

`$D2`

Invalid task name specified.

`$D3`

Error starting task.

`$D4`

Error destroying task.

`$D5`

Number of fragments exceeds maximum.

`$D6`

Bad fragment header in load file.

`$D7`

Anomaly detected in dual port RAM.

`$D8`

Diagnostic message.

`$D9-$EF`

Reserved for future errors.

Error Number	Description
`$C0`	Unable to open file.
`$C1`	Unable to bootstrap KERNEL.
`$C2`	Truncated file.
`$C3`	Invalid file.
`$C4`	Failed transfer of code block.
`$C5`	Error starting KERNEL.
`$C6`	Task already exists.
`$C7`	Unable to create task.
`$C8`	Invalid version of `.lot` file.
`$C9`	Insufficient memory on host.
`$CA`	Error getting memory on communications processor.
`$CB`	Error while closing file.
`$CC`	Error setting task program counter.
`$CD`	Error performing TDM configuration.
`$CE`	Unknown KERNEL function requested.
`$CF`	Unable to access DPR driver.
`$D0`	Unable to obtain loader channel.
`$D1`	Unknown type of communications processor reported.
`$D2`	Invalid task name specified.
`$D3`	Error starting task.
`$D4`	Error destroying task.
`$D5`	Number of fragments exceeds maximum.
`$D6`	Bad fragment header in load file.
`$D7`	Anomaly detected in dual port RAM.
`$D8`	Diagnostic message.
`$D9-$EF`	Reserved for future errors.

Version

Want to send us feedback on our documentation? Email: Tech_Pubs@nmss.com

Chapter 3

Communications Processor Task Loader Utility: cplot

3.1 Running cplot

Name

Purpose

Usage

Procedure

Example

3.2 cplot Error Codes