0% found this document useful (0 votes)
62 views

Debug and Verification Tool

This document provides a description of the commands available from DVT for debugging and verifying the RBS 2000. It includes 3 sections: terminology, general information about DVT functionality and communication, and descriptions of debug and verification functions and corresponding commands. The debug and verification commands cover data storage, reading and writing data, handling flash memory, process handling, monitoring, and software logging.

Uploaded by

upkumara
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
62 views

Debug and Verification Tool

This document provides a description of the commands available from DVT for debugging and verifying the RBS 2000. It includes 3 sections: terminology, general information about DVT functionality and communication, and descriptions of debug and verification functions and corresponding commands. The debug and verification commands cover data storage, reading and writing data, handling flash memory, process handling, monitoring, and software logging.

Uploaded by

upkumara
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 46

DESCRIPTION 1(46)

Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

DVT COMMANDS

Abstract

This document gives a description of the commands


available from DVT for debug and verification of RBS 2000.

Application

This document is used as a command reference for users


and developers of the DVT.

Supplementary documents

Revision History

Complete list of revisions presented:

Date Rev Characteristics


1996−04−16 A First version based on
2/190 82−HRB 105 01 Uen, rev D.

Updates


LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 2
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

Table of Contents

1 Terminology 4

2 General 5

2.1 DVT functionality overview 5


2.2 DVT Communication description 6
2.3 Command syntax 7
2.4 Function keys 7

3 Debug and verification functions 8

3.1 Syntax of DVT Commands 8


3.2 Command descriptions 9
3.2.1 User Help 9
3.2.2 Data Storage 10
3.2.2.1 Command History 10
3.2.2.2 Command Output 10
3.2.2.3 Window Contents 11
3.2.2.4 Printer Options 11
3.2.2.5 Save current setup 11
3.2.2.6 Flush oldest output to file 11
3.2.2.7 Scroll output window horizontal 12
3.2.3 Data Read 13
3.2.4 Data Write 13
3.2.4.1 Enable data write 13
3.2.4.2 Write data to memory 13
3.2.5 Handle FLASH memory 15
3.2.5.1 Read flash 15
3.2.5.2 Enable flash write 15
3.2.5.3 Write flash 16
3.2.5.4 Clear flash 16
3.2.6 Process handling commands 18
3.2.6.1 Start execution of processes 18
3.2.6.2 Stop execution of processes 18
3.2.6.3 Read stack usage for processes 18
3.2.6.4 Measure processor time usage for processes 19
3.2.7 Monitor 20
3.2.7.1 Read monitor datalist 20
3.2.7.2 Define and enable monitoring of data 21
3.2.7.3 Disable monitoring 21
3.2.7.4 Read status of enabled monitors 22
3.2.8 Software Log 23
3.2.8.1 Define bus log condition 23
3.2.8.2 Define and enable event log 24
3.2.8.3 Define and enable signal log 25
3.2.8.4 Disable bus log condition 25
3.2.8.5 Disable event log 26
3.2.8.6 Disable signal log 26
3.2.8.7 Set log destination 27
3.2.8.8 Set debug level 27
LZF 032 41/1M RJ

3.2.8.9 Read status on enabled loggings 28


3.2.8.10 Freeze log 28
3.2.8.11 Resume log 29

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 3
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.8.12 Read log 29


3.2.8.13 Clear log 29
3.2.8.14 Reset log conditions 30
3.2.9 Reset hardware 31
3.2.10 Trig fault 31
3.2.11 Get PLS Software revision 32
3.2.12 Read and set time 32
3.2.13 Error handling 33
3.2.13.1 Get startcause description 33
3.2.13.2 Display OSE Error description 33
3.2.13.3 View OSE error list 33
3.2.14 Signal number translation 34
3.2.14.1 Enable signal number translation 34
3.2.14.2 Setup signal number translation 34
3.2.15 Setup Help for Transparent Commands 35
3.2.16 Command Scripts 36
3.2.16.1 Run a script file 36
3.2.16.2 Loops in Command Scripts 36
3.2.16.3 Wait for DVT link establishment 37
3.2.16.4 Wait for DVT link lost 37
3.2.16.5 Auto start of script 38
3.2.17 DVT Time 39
3.2.18 DVT Echo 39
3.2.19 DVT Beep 39
3.2.20 DVT Sleep 40
3.2.21 DVT Wakeup 40
3.2.22 View a text file 40
3.2.23 Show dvt directory 41
3.2.24 Set dvt directory 41
3.2.25 List dvt directory 41

4 DVT PC Menu Commands 43

5 References 46
LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 4
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

1 TERMINOLOGY

Abbreviations:

Systems and subsystems:

BSC Base Station Controller


BTS Base Transceiver Station (RBS 2000)
MS Mobile Station

BTS Subsystems:

EPS Environment platform subsystem


OMS Operation and maintenance subsystem
PLS Platform subsystem
RTS Radio transceiver subsystem
TFS Traffic functions subsystem

BTS Active Replaceable Units:

DXU Distribution switch


ECU0−1 Environment control unit
TRU0−11 Transceiver units

Miscellaneous:

DVT Debug & Verification Terminal


O&M Operation and Maintenance
RU Replaceable Unit
menu Indicates a menu choice in DVT
LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 5
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

2 GENERAL

2.1 DVT FUNCTIONALITY OVERVIEW

The DVT is separated in two parts (see figure 1):

− The user interface (DVT client) is a PC−Windows program where


commands are written and results are presented to the user.

− The DVT server, located in the RBS 2000, interprets and


handles commands written from the DVT client.

DVT
RBS
DVT client 2000
Serial link
PC DVT server

Figure 1, DVT overview

The user interface consists of four windows (see figure 2):

− A command window in which commands to the DVT server are


written and command answers from the DVT server presented.
Optionally a number of user defined shortcut command keys can
also be visible.

− A monitor window in which all monitor messages from the DVT


server are presented.

− A log window in which all logging messages from the DVT


server are presented.

− An information and help window.


LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 6
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

DVT <Rel>
File Edit Search View Options Help

DXU:PLS>

DVT Monitor DVT Log


File Edit Search File Edit Search

DVT Information & Help


File Edit Search Help

Figure 2, Example of DVT user interface windows

2.2 DVT COMMUNICATION DESCRIPTION

Two types of serial communication protocols exists:

− ASCII protocol, with plain character by character


transmission of data. serial communication port 1 or 2 with
baudrates from 4800−19200 baud is selectable from the DVT PC.

− PCS protocol, with layered frame protocol. Checksum control


and retransmission are handled on the frames. The first free
communication port (com1/com2) with 19200 or 9600 baud is
automatically selected on the DVT PC. This protocol is the
default at startup.

The DVT (PC) can handle both these types of communication, but
the DVT server (in BTS) can only handle one of those. The DVT
(PC) has to be restarted in order to change protocol. The
function to change protocol is reached from the DVT main window
under the File−menu:

menu; File − Restart Using [ASCII−link]


LZF 032 41/1M RJ

or
menu; File − Restart Using [PCS−link]

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 7
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

2.3 COMMAND SYNTAX

Command syntax is described in BNF (backus naur form). Short


description follows:

[ ] Optional
{ } Repeated option
| Selection
.. Interval
< > Meta commmand, defined elsewhere
" " or
nothing Typed as is

Each command is described as follows, example:

’Textual description of command’

Syntax: command_name <parameter1> <parameter2>

parameter1 − ’Textual description of a parameter’

parameter2 = ’Formalized description in BNF’

Example: >command_name parameter1 parameter2

’Description of the example’

Fault condition:
− ’Description of an action leading to an error’

2.4 FUNCTION KEYS

The user can define a number of function keys to get easy


access of often used commands. They are optionally displayed at
the bottom of the command window. Some keys are defined as
default at start.

The functions to setup new keys and show/hide keys


are reached from the menu ’options’ in the command window.

It is also possible to save/load new function key definitions


to/from a file.

The maximum number of simultaneously defined function keys are


limited to 40.
LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 8
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3 DEBUG AND VERIFICATION FUNCTIONS

3.1 SYNTAX OF DVT COMMANDS

commandline = [<destination>]<command>[;<commandline>]

destination = <act_ru>:<subsystem><commandgroup>">"

command = <action>{ <parameter>}

act_ru = dxu | ecu0 | ecu1 | tru0 .. tru11

subsystem = oms | pls | tfs | rts | eps

commandgroup = 1 .. 9

action = help | run | <destination> | <transparent_action>

transparent_action = <alphachar>{<alphachar>}

parameter = <alphachar> {<alphachar>}

alphachar = 0 .. 9 | a .. z | A .. Z

Note: The following combinations of act_ru and


subsystem/commandgroup are invalid:

dxu:eps
dxu:tfs
ecu*:tfs
ecu*:rts
tru*:eps

More than one command can be written on each line, using


semicolon as separators.

Direction of commands to the destination subsystem is


controlled by placing the destination in front of the command.
The destination consists of a ’active replaceable unit’
followed by the subsystem command group. Active RU and
subsystem information are separated by a ’:’.

The command group is a name (address) of a receiver for


commands in a subsystem. Each subsystem can install up to 9
(1−9) command groups (receivers), except for PLS which only
uses one.

Example:
LZF 032 41/1M RJ

DXU:PLS>dxu:oms1>start test1

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 9
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

The example temporarily directs the command ’start test1’ to


the subsystem TFS, command group 1 in active RU DXU.

Another way to control direction of commands is similar to how


the command line prompter acts in DOS or UNIX. Instead of
writing:

DXU:PLS>dxu:oms1>start test1

The user can write:

>DXU:PLS>dxu:oms1>

Then the prompter at command line changes from:

DXU:PLS>

To:

DXU:OMS1>

All commands will then be directed to active RU DXU in


subsystem TFS, command group 1, without specifying any
destination in front of the command.

3.2 COMMAND DESCRIPTIONS

The following syntax description of DVT commands does not


include subsystem specific commands. Only PLS and DVT internal
commands are described in this document. Commands for other
subsystems are instead described in separate documents for each
subsystem.

All numbers are in decimal integers if nothing else is stated.

All fault conditions leads to command abort and an error


message.

The user can cancel an active command by pressing the ESC−key


on the DVT client (PC). This is especially useful when reading
long data sequences (read log), which otherwise can take
several minutes to finish.

3.2.1 User Help

Help can be accessed from the help menu in the command window
or from the DVT prompt (PLS). Help text is provided from this
document. The user can setup a help file for each subsystems,
see ’Setup Help for Transparent Commands’.
LZF 032 41/1M RJ

If the command asked for cannot be found, then the help command
is redirected to the owning subsystem.

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 10
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

Syntax: help [<command>]

or

Syntax: menu; Help − <ss> Commands−<command>

or

Syntax: menu; Help − <ss> Descriptions−<descr>

menu; − command is reached from the DVT − menu.

<ss> = DVT | EPS | OMS | PLS | RTS | TFS

command − name of a specific command to get help on. Default


name is "help".

descr − Name of chapter for a command description.

Example: TRU1:TFS3>help

Give help on help command for subsystem TFS. If a TFS helpfile


is not installed or does not contain help about help, the help
request is sent further to command group 3 on the subsystem TFS
in active RU TRU.

Fault condition:
− The named command does not exist.

3.2.2 Data Storage

3.2.2.1 Command History

Command lines that has been executed is saved in buffer. This


’history’ of commands can be saved and used in command scripts.
The command input can be treated as follows:

Function Menu choice

Save History ’File’−‘Command Input’−’Save History As...’.


Read History ’File’−‘Command Input’−’Read History From...’.
Edit History ’File’−‘Command Input’−’Edit History File...’.
Print History ’File’−‘Command Input’−’Print’

3.2.2.2 Command Output

The Contents of the DVT Command Output part of a DVT window can
be treated as follows:
LZF 032 41/1M RJ

Function Menu choice

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 11
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

Save Output ’File’ − ‘Command Output’ − ’Save As...’


Edit Output ’File’ − ‘Command Output’ − ’Edit File...’
Print Output ’File’ − ‘Command Output’ − ’Print’

3.2.2.3 Window Contents

The Contents of the DVT Monitor, Log and Information & Help
Windows can be treated as follows:

Function Menu choice

Save Output ’File’ − ’Save As...’


Edit Output ’File’ − ’Edit File...’
Print Output ’File’ − ’Print’

3.2.2.4 Printer Options

Printer setup options:

Function Menu choice

Setup Printer ’File’ − ‘Printer Setup’ − ’Configure...’


Setup Printer ’File’ − ‘Printer Setup’ − ’Fonts...’
Setup Printer ’File’ − ‘Printer Setup’ − ’Margins...’

3.2.2.5 Save current setup

Current setup is saved for future use via the "Save Setup"
menu command in the DVT main window.

Syntax: menu; File − Save Setup − On Exit


or
menu; File − Save Setup − Now!

menu; − command is reached from the DVT − menu.

Fault conditions:

3.2.2.6 Flush oldest output to file

In every DVT subwindow, it is possible to flush the oldest


output to a file instead of deleting it from the output window.
This is useful before an operation that will generate a lot
(more than 20 kByte) of data as output.

From the file menu the user chooses "Flush Oldest Output To..."
command. The user is then asked for the name of a file in which
LZF 032 41/1M RJ

to store the information. All output in the current subwindow


will then also be stored into the file. Next time the user

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 12
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

chooses this command, the output currently visible is also


copied to the file and it is closed. Now it is possible to
examine output data via the "Edit file..." command.

Syntax: menu; File − Flush Oldest Output To...

menu; − command is reached from the DVT − subwindow menu.

Fault conditions:
If the disk becomes full while this command is in progress, the
operation will be ended.

3.2.2.7 Scroll output window horizontal

In every DVT subwindow, it is possible to scroll the output


horizontal. From the file menu the user selects "Horizontal
scroll" and then positions the scrollbar as he/she wishes.

Syntax: menu; File − Horizontal scroll

menu; − command is reached from the DVT − subwindow menu.


LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 13
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.3 Data Read

A command to read a number of data octettes beginning at a


specific memory address.

Syntax: read <address> <octettes>

address = memory start address in hexadecimal.

octettes = the number of octet blocks to be read from memory, in


decimal.

Example: DXU:PLS>read 40000000 10

Reads 10 octettes of data, beginning at address ’40000000’.

Fault condition:
− Memory address out of memory map.

3.2.4 Data Write

3.2.4.1 Enable data write

A command to initialize data write to memory. After initiation


of data write it stays enabled until the DVT is disconnected.
This command cannot be used inside a scriptfile.

Syntax: write enable

Example: DXU:PLS>write enable


DXU:PLS>write 3FFF0000 FFFF

An enable followed by a data write.

Fault condition:
− Trying to use the command in a scriptfile.

3.2.4.2 Write data to memory

A command to write data to a specific memory address. The


command must be preceded by an enabling of the function (data
write enable). The command should be handled with care due to
unpredictable results.

Syntax: write <address> <hexdata>

address − memory address in hexadecimal (4 bytes).

hexdata − A block of data in hexadecimal. The block can be 1, 2


LZF 032 41/1M RJ

or 4 bytes long. If the data does not comply to one


of the block sizes, it is expanded to the next
greater block size or shrunken to maximum 4 bytes.

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 14
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

Example: DXU:PLS>write enable


DXU:PLS>write 3FFF0000 FFFF

Writes the data ’FFFF’ (2 bytes) to the address ’3FFF0000’.

Fault conditions:
− Memory address out of memory map.
− Memory write not enabled.
LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 15
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.5 Handle FLASH memory

To be aware of when handling Flash memory:

− The Flash memory in the DXU/TRU is divided into segments of


256 kbytes. The flash memory in the ECU is divided into
segments of 128 kbytes.

− Bits written to ’zeros’ can not be changed to ’ones’,


except by erasing the whole segment.

3.2.5.1 Read flash

Reads blocks of data from the FLASH.

Syntax: flash read <address> <blocks> <format>

address − memory start read address.

blocks − Number of data blocks in bytes to read.

format = full | word0 | word1 | byte0 | byte1 | byte2 | byte3

full − Reads the whole data bus (32/16 bits databus)


word0 − Reads the lower halfword (32 bits databus)
word1 − Reads the upper halfword (32 bits databus)
byte0 − Reads first byte, bits 0−7 (32/16 bits databus)
byte1 − Reads second byte, bits 8−15 (32/16 bits databus)
byte2 − Reads third byte, bits 16−23 (32 bits databus)
byte3 − Reads fourth byte, bits 24−31 (32 bits databus)

Example: DXU:PLS>flash read 01000000 16 full

Reads 16 bytes as whole words (32 bits), starting at hex


address 01000000, from the DXU.

Fault conditions:
− Memory address out of memory map.

3.2.5.2 Enable flash write

Enables the command ’flash write ..’ and ’flash clear ..’. The
command stays enabled until the hardware is restarted.

Syntax: flash write enable

Example: DXU:PLS>flash write enable

Fault conditions:

LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 16
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.5.3 Write flash

Writes blocks of data to the FLASH. Writing to flash can only


changes indiviual bits from 1 to 0. This command is protected
from accidental misuse by the command ’flash write enable’,
which first must be executed.

Syntax: flash write <address> <hexdata> <format>

address − memory start write address.

hexdata − Data to write to FLASH, in hexadecimal. The data in


the flash will not be the same as written unless the
flash segment has previously been cleared.

format = full | word0 | word1 | byte0 | byte1 | byte2 | byte3

full − Writes the whole data bus (32/16 bits databus)


word0 − Writes the lower halfword (32 bits databus)
word1 − Writes to the upper halfword (32 bits databus)
byte0 − Writes to first byte, bits 0−7 (32/16 bits databus)
byte1 − Writes to second byte, bits 8−15 (32/16 bits databus)
byte2 − Writes to third byte, bits 16−23 (32 bits databus)
byte3 − Writes to fourth byte, bits 24−31 (32 bits databus)

Example: DXU:PLS>flash write 01000000 bbbbbbbb full

Writes the hex data bbbb to the flash address 01000000 as whole
words (32 bits). The data at address 01000000 will only be
bbbbbbbb if it previosly was ffffffff, i.e erased.

Fault conditions:
− Memory address out of memory map.
− Flash write not enabled.

3.2.5.4 Clear flash

Erases blocks of memory in the FLASH, all data values in the


flash will be FF hexadecimal.

Syntax: flash clear <address> <blocks> <format>

address − memory start address, the address will be rounded


down to the start of the block that contains the
specified address.

blocks − Number of data blocks to clear, blocks are 256 kbytes


on TRU and DXU, 128 kbytes on ECU.

format = full | word0 | word1 | byte0 | byte1 | byte2 | byte3


LZF 032 41/1M RJ

full − Clears the whole data bus (32/16 bits databus)


word0 − Clears the lower halfword (32 bits databus)
word1 − Clears the upper halfword (32 bits databus)

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 17
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

byte0 − Clears first byte, bits 0−7 (32/16 bits databus)


byte1 − Clears second byte, bits 8−15 (32/16 bits databus)
byte2 − Clears third byte, bits 16−23 (32 bits databus)
byte3 − Clears fourth byte, bits 24−31 (32 bits databus)

Example: DXU:PLS>flash clear 01000000 1 full

Clears, i.e. sets to FF, 256 kbytes (1 block) as whole words


(32 bits), starting at hex address 01000000, in the DXU memory.

Example: DXU:PLS>flash clear 01001234 1 byte0

Clears, i.e. sets to FF, each lowbyte in a 256 kbyte segment (1


block), starting at hex address 01000000, in the DXU memory.
Note that the start address is rounded down the start of the
block.

Example: ECU:PLS>flash clear 0122222 2 full

Clears, i.e. sets to FF, a 256 kbyte segment (2 128 kB blocks),


starting at hex address 120000, in the ECU memory. Note that
the start address is rounded down the start of the block.

Fault conditions:
− Memory address out of memory map.
− Flash write not enabled.
LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 18
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.6 Process handling commands

3.2.6.1 Start execution of processes

A command to start an earlier stopped process or groups of


processes. See ’stop process’

Syntax: process start <proc_name>

proc_name − Name of process to start. Groups of processes can


be selected using wildcards (*) at the end.

Example: process start SOME_NAME

Fault conditions:
− Process not found.

3.2.6.2 Stop execution of processes

A command to stop execution of a processor groups of processes.

Syntax: process stop <proc_name>

proc_name − Name of process to stop. Groups of processes can


be selected using wildcards (*).

Example: process stop SOME_NAME

Fault conditions:
− Process not found.

3.2.6.3 Read stack usage for processes

A command to read stack usage for a process or groups of


processes. The result will be sent to the log memory area with
the following data:

sz − Total stack size in bytes


rsp − Used register stack in bytes
msp − Used memory stack in bytes
so − Number of signals owned
sq − Number of signals in queue

Syntax: process stack <proc_name>

proc_name − Name of process to read stack for. Groups of


processes can be selected using wildcards (*) at
the end.
LZF 032 41/1M RJ

Example: process stack SOME_NAME

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 19
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

Fault conditions:
− Process not found.

3.2.6.4 Measure processor time usage for processes

A command to show processor time usage (in %) for a process or


groups of processes. The result is calculated based on time
usage since the last execution of this command. The result will
be sent to the log memory area with the following data:

OSE + IDLE: Procent of time spent executing OSE or in idle


state.

TOTAL (<proc_name>): Total procent of time executing


process(es).

For each process

<proc_name>: Procent of time executing defined process. If the


process is an interrupt process, the following
data is also presented: (A, B, C) where:
A = Min number of cycles spent in interrupt
process.
B = Max number of cycles spent in interrupt
process.
C = Avarage number of cycles spent in interrupt
process.

Syntax: process time <proc_name>

proc_name − Name of process to show time usage for. Groups of


processes can be selected using wildcards (*) at
the end.

Example: process time SOME_NAME

Fault conditions:
− Process not found.
LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 20
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.7 Monitor

The monitoring function reads and displays selectable data at


given intervals or events. The following monitor commands
exists:

− Request a list of possible data to monitor.

− Select data and set up monitor conditions.

− Disable monitoring.

− List status on the previously enabled monitors.

Identities of monitorable data uses a syntax similar to a


’directory’ structure in DOS or UNIX. For example a data can
have the identity: "pls/dvt/data1", which is a data named
"data1" in subsystem PLS software block DVT.

When a monitor is activated it is read in two different ways,


depending on how it is implemented:

− The monitor value is read at every read incident, set by the


read interval (see Define and enable monitoring of data). If
the value has not changed since the last read, it is ignored.

− The owner of the monitor decides when to read a monitor


value, and then puts it in a buffer which is read at defined
intervals (see Define and enable monitoring of data). The
whole buffer is read at every read incident.

3.2.7.1 Read monitor datalist

This command retrieves a list of identities on the previously


installed monitorable data. The command can be used for
searching of a specific identity name, which can be used when
defining a monitor (below).

Syntax: monitor list <data>

data = <monitor_identity>

monitor_identity − name of data or groups of data, supports the


use of wildcards.

Example: DXU:PLS>monitor list tfs

tfs/data1
tfs/data2
..
LZF 032 41/1M RJ

The example lists identities of all data in subsystem TFS


possible to monitor.

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 21
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

Fault condition:

3.2.7.2 Define and enable monitoring of data

Defines and enables monitoring of data, using its identity.


Optionally the monitor display rate and destination of the
monitored data can be set. Default setting is slow display rate
and window as monitor data destination. At most 10 monitorings
can be active simultaneously.

Syntax: monitor enable <data> [<interval>] [<destination>]

data = <monitor_identity>
interval = fast | slow | once
destination = file | log | window

monitor_identity − the name of data parameter(s) to monitor


(retrieved by the ’monitor list’ command).

file − directs monitored data to a default monitor file in the


DVT. If the file already exist, new data is appended to
the old.

log − directs monitored data to the software log area in RBS


2000.

window − directs monitored data to the monitor window


(default).

fast − monitor display interval 1s.

slow − monitor display interval 5s (default).

once − reads the monitor value once, does not start a continues
monitoring.

Example: DXU:PLS>monitor enable tfs/data1 log

Selects to monitor the data "data1" in subsystem TFS at


standard slow interval (5s) and directs it to the SW log.

Fault condition:
− Selecting non existing monitor data.

3.2.7.3 Disable monitoring

Disables a previously defined monitoring. It is possible to


select groups of monitor data using wildcards in the identity.
LZF 032 41/1M RJ

Syntax: monitor disable <data>

data = <monitor_identity>

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 22
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

monitor_identity − the name of data parameter(s) to disable


monitoring for. It is possible to use
wildcards.

Example: DXU:PLS>monitor disable tfs/data1

Disables monitoring of the data "tfs/data1".

Fault condition:
− Selecting non existing monitor data.

3.2.7.4 Read status of enabled monitors

Lists the status on all the previously defined and enabled


monitors.

Syntax: monitor status

Example: DXU:PLS>monitor status

tfs/data1

The example lists the identity of the previously defined and


enabled monitor.

Fault condition:

LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 23
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.8 Software Log

The software log collects data from selectable sources at


defined events. Each logged data is stamped with time and date,
before they are stored as ’log entrys’ in a cyclic memory area
in RBS 2000. The log entrys can also optionally be sent to the
Log Window or Log File in the DVT.

Three types of logging exist:

Bus log − is trigged when defined data is sent on the bus for a
process.

Event log − is trigged at defined events for a process.

Signal log − is trigged when a defined signal is sent from a


subsystem.

The following operations are available for each type of log:

− Enabling or disabling.

− Setting the destination of logged messages.

− Listing the status of all previously enabled loggings.

− Freezing the input to the memory log area immediately or at a


specified log message.

− Resuming the input to the memory log area.

− Reading the memory log area in the BTS and storing the
content in a file on DVT.

− Clearing the memory log area in the BTS.

3.2.8.1 Define bus log condition

Define bus data to trig log on. The content on the bus will be
logged when the defined data expression appears on the bus,
from or to a process. Wildcards can be used to select groups of
source processes. Use the command ’log enable event ..’ to
select between the events ’bus_send’ and ’bus_receive’ in order
to enable logging for a process.

Syntax: log enable busfilter <bus_data> <source_proc>

bus_data = <data_expr>{ <data_operator> <data_expr>}


data_expr = "["<byte_no>[:<bit_no>]"]"=<byte_value>
data_operator = AND|OR
byte_no = 0 .. 32767
LZF 032 41/1M RJ

bit_no = 0 .. 7
byte_value = 0 .. 255

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 24
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

The syntax of a trig condition consists of a byte number,


optionally with a bit number, and a value. This can be combined
to other conditions with the operators ’AND’ and ’OR’. For
example the expression "[2:1]=0 AND [4]=255" means to trig when
byte 2, bit 1 is equal to 0 and byte 4 is equal to 255. The
trig condition must be surrounded with " " when more than one
data expression is used.

source_proc − Name of process to log on. Groups of processes


can be selected using wildcards.

Example: DXU:PLS>log enable busfilter "[4]=255" P*

The example defines a trig condition on the bus when byte


number 4 is equal to 255 for all processes in subsystem PLS.

Fault conditions:
− Syntax error in the data expression causes an error.
− Selecting an non existing source_proc causes an error.

3.2.8.2 Define and enable event log

Select events to log on, for a source process. Groups of source


processes can be selected using wildcards in the parameter.

The log condition can also be set to be resident under


restarts. The resident log conditions can only be cleared by a
new power up.

Syntax: log enable event <event> <source_proc> [resident]

event = require | check | ensure | error | fall_through | enter


| leave | traceh | tracem | tracel | state_change |
bus_send | bus_receive | trace_fault | trace_dist |
user_1 .. user_8

source_proc − name of process to log on. Possible to use


wildcards.

Example: DXU:PLS>log enable event tracel P*

The example logs the tracel event for all processes in


subsystem PLS.

Fault condition:
− Selecting an non existing event or source_proc causes an
rejection and error message.
LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 25
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.8.3 Define and enable signal log

The software log selects signals or interval of signals to log


on, sent from a subsystem or all subsystems.

The log condition can also be set to be resident under


restarts. The resident log conditions can only be cleared by a
new power up.

This command should be handled carefully when logging many


signals simultaneously. If the signals are of high frequency and
if the user also monitors the log i.e. ’log dest window’, the
serial communication between the DVT server and client will be
overflowed.

Syntax: log enable signal <signal_sel> <subsys> [resident]

signal_sel = sig_no[−sig_no]

sig_no − signal number.

subsys = pls | oms | tfs | rts | eps | all

Example: DXU:PLS>log enable signal 256−260 all

The example logs signal numbers 256−260 in all subsystems.

Fault condition:
− Selecting an non existing subsystem causes an error.

3.2.8.4 Disable bus log condition

Disables all the previously defined bus conditions (software


log) for a process. Groups of source processes can be selected
using wildcards in the source_proc parameter.

Syntax: log disable busfilter <source_proc>

source_proc − name of process to disable log for. Wildcards can


be used.

Example: DXU:PLS>log disable busfilter P*

The example disables bus log for all processes in subsystem


PLS.

Fault condition:
− Selecting an non existing source_proc causes an rejection and
error message.
LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 26
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.8.5 Disable event log

Disables log for events. Groups of source processes and events


can be selected using wildcards in the parameters.

Syntax: log disable event <event> <source_proc>

event = require | check | ensure | error | fall_through | enter


| leave | traceh | tracem | tracel | state_change |
bus_send | bus_receive | trace_fault | trace_dist |
user_1 .. user_8

The event parameter can also include wildcards to select groups


of events.

source_proc − name of process or groups of processes to disable


log for. Wildcards can be used.

Example: DXU:PLS>log disable event tracel P*

The example disables log on the tracel event for all processes
in subsystem PLS.

Fault condition:
− Selecting an non existing event or source_proc causes an
rejection and error message.

3.2.8.6 Disable signal log

Disables log for signals. Groups of source processes can be


selected using wildcards in the parameter.

Syntax: log disable signal <signal_sel> <subsys>

signal_sel = sig_no[−sig_no]

sig_no − signal number to disable log for

subsys = pls | oms | tfs | rts | eps | all

Example: DXU:PLS>log disable signal 256−260 p*

The example disables log on signal numbers 256−260 for all


processes in subsystem PLS.

Fault condition:
− Selecting an non existing signal number causes an rejection
and error message.
LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 27
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.8.7 Set log destination

Set an optional destination for the log messages. Each new log
message can be displayed or stored in the DVT as they appear.
The command ’log read’ is disabled while this function is
enabled. Execute the command ’log dest off’ to be able to use
the command ’log read’ again.

This command can not be executed if the log is frozen.

Syntax: log dest <dest>

dest = file | window | off

file − logged messages is directed to a default log file in the


DVT. If the file already exist, new data is appended to
the old.

window − logged messages is directed to the ’log window’ in the


DVT.

Example: DXU:PLS>log dest window

The example sets the destination to the Log Window in the DVT.
Each new log message that is logged in the BTS will also be
printed on the DVT.

Fault condition:
− Log is frozen.

3.2.8.8 Set debug level

Sets for how many levels of procedures the events ’enter’ and
’leave’ will be logged for a process. The default at start is
one.

Syntax: log level <lev_no> <source_proc>

level_no − number representing the new debug level.

source_proc − name of the process to change the debug level


for. Wildcards at the end can be used.

Example: DXU:PLS>log level 3 PLS*

Sets the debug level 3 for all PLS processes.

Fault condition:
− Selecting a non existing process name.
LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 28
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.8.9 Read status on enabled loggings

Display a list on all the previously enabled loggings.

Syntax: log status

Example: DXU:PLS>log status

bus enable "[4]=255" P*


event enable tracel P*
signal enable 256−260 all
signal disable 259−260 all

The example lists the previously enabled and disabled loggings.

Fault condition:

3.2.8.10 Freeze log

Freezes the input to the log memory area immediately or at a


defined ’freeze message’. Each logged message will be searched
to find a match on the ’freeze message’. If a match is found ,
then the log input will be stopped according to a defined
’storage method’. If no ’freeze message’ and ’storage method’
is defined, an unconditional freeze of the log input will take
place. If no storage method is specified, it is set to default
’instant’.

This command can not be executed while monitoring of the log is


activated.

Syntax: log freeze ["<message>" [<storage_method>]]

message − ascii ’freeze message’ to search for in logged


messages.

storage_method = instant | half | full

instant − The log will be frozen instantly, i.e log before


trig.

half − Half of the log will be written and then frozen, i.e
half of the log is before trig and half after.

full − The log will be filled and then frozen, i.e log after
trig.

Example: DXU:PLS>log freeze "signal receive timeout"

Freezes input to log area when a log message includes the


LZF 032 41/1M RJ

string "signal receive timeout".

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 29
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

Fault condition:
− Log is being monitored.

3.2.8.11 Resume log

Resumes the input to the log memory area after a freeze command
has been executed. This command also disables freeze commands
not yet trigged according to a ’freeze message’.

Syntax: log resume

Example: DXU:PLS>log resume

Resumes to log messages to the log memory area.

Fault condition:

3.2.8.12 Read log

Reads the log area and transfers it to the DVT log−window or


log−file. The default destination is to the log−window.
Optionally the user can specify how old log entries he wants to
read. Default is the entire content of the log.

Syntax: log read [<time>] [<dest>]

time = 0..32767
dest = file | window

The parameter <time> specifies how far back in time (seconds),


counted from present system time, log entrys will begin to be
read.

Example: DXU:PLS>log read 60

Reads log entries with timestamps newer than 60 seconds.

3.2.8.13 Clear log

Clears the log memory area in BTS.

Syntax: log clear

Example: DXU:PLS>log clear


LZF 032 41/1M RJ

Fault condition:

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 30
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.8.14 Reset log conditions

Resets log conditions for a log type as they were at startup.

Syntax: log reset <log_type>

log_type = bus | event | signal

Example: DXU:PLS>log reset event

Resets event log conditions to default for all processes in the


DXU.

Fault conditions:

LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 31
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.9 Reset hardware

Restart the hardware and set a startcause.

Syntax: hardware reset <startcause>

startcause − See reference /IWD HWU_ADM/ for a description of


each startcause number.

Example: DXU:PLS>hardware reset 0

Fault conditions:

3.2.10 Trig fault

Triggers a fault for a supervised entity.

Syntax: trig fault <fault_number>

fault_number = 0 .. 10

where the numbers corresponds to the following supervised


entitys:

0 − LB_A_HDLC_ERR, Number of errored incoming HDLC frames on


local bus A.
1 − LB_A_TX_DATA, Physical transmission of data on local bus A.
2 − NV_MEM, checksum of non volatile memory.
3 − SW_ERR, the application software.

The following are only valid in the DXU:

4 − DXUD_G703_A_LOF_OOF, signal and frame alignment on PCM−A.


5 − DXUD_G703_A_CSES, PCM−A bit error ratio counted on
submultiframes.
6 − DXUD_G703_A_LOS, PCM−A bit error ratio counted on frame
alignment signals in TS0.
7 − DXUD_G703_A_AIS, PCM−A is scanned for a continuos stream
of 1’s.
8 − DXUD_G703_A_RAI, Remote alarm indication bit on PCM−A.
9 − DXUD_G703_HDLC_ABORT, Number of aborted incoming HDLC
frames.
10 − DXUD_G703_HDLC_ERR, Number of errored incoming HDLC
frames.

See reference /DESC SUP_ENT/ for a complete description on the


fault selections.

Example: DXU:PLS>trig fault 3


LZF 032 41/1M RJ

The command triggers a software error for the DXU.

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 32
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

Fault conditions:

3.2.11 Get PLS Software revision

Print the name/revision of the installed software.

Syntax: rev

Example: DXU:PLS>rev

Fault conditions:

3.2.12 Read and set time

A command to read and set the clock in the BTS. The single
command ’time’ prints the previous date and time in the command
window on the DVT. It can optionally also be directed to the
monitor/log window. The clock can be set by a hand or
synchronized with the DVT PC clock (dvttime).

Syntax: time [<dest> | set <date_time>]

dest = monitor | log

date_time = yy−mm−dd hh:mm:ss | dvttime

dvttime − DVT PC date and time.

y − year
m − month
d − day
h − hour
m − minute
s − second

Example: DXU:PLS>time

BTS time is: 94−09−20 13:15:08

Fault condition:
− Wrong date/time values.
LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 33
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.13 Error handling

3.2.13.1 Get startcause description

Displays a description of the latest reason for (re)start of


the hardware (startcause). If the startcause was a software
error a description for that is also displayed.

Syntax: startcause get

Example: DXU:PLS>startcause get

The example displays a textual description of the startcause.

Fault conditions:

3.2.13.2 Display OSE Error description

Displays a description of an OSE error given the hex code of


the error.

Syntax: dvt oseerr <error_code>

error_code − 6 digit hex code.

Example: DXU:PLS>dvt oseerr 2d0032

The example displays a textual description of the OSE error


number.

Fault conditions:

3.2.13.3 View OSE error list

A DVT command available from main DVT window help menu. It


displays a list on all defined OSE errors.

Syntax: menu; Help − View OSE Error List

menu; − command is reached from the DVT subwindow menu.

Fault conditions:

LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 34
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.14 Signal number translation

3.2.14.1 Enable signal number translation

Enables translation of logged signal numbers to the defined


textual name of each signal number. Before this function can be
enabled an ascii textfile with one signal definition for each
line, has to be defined. See ’Setup signal number translation’.

Syntax: menu; Options − Translate Signal Numbers

Fault conditions:

3.2.14.2 Setup signal number translation

Setup a signal number translation file, including the number


and name of each signal. Each line in the file should consists
of the number, one tab character and the name of the signal
(number<TAB>name). The signal name can be max 48 characters
long.

Syntax: menu; Options − Signal Number Translation Setup...

Fault conditions:

LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 35
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.15 Setup Help for Transparent Commands

Each subsystem can set up a new or updated helpfile for their


commands. It is also possible to take an old helpfile and use
it as a new helpfile (Import from...).

Syntax: menu; Help − Help Setup − DVT | <ss>... | Import from...

menu; − command is reached from the DVT − menu.

<ss> = EPS|OMS|PLS|RTS|TFS

The user is prompted for the name and location of the specific
subsystem helpfile.

The help file must be an EXCO−file with layout as this


description. The first chapter looked for is "Revision
History".

Chapters with no lines excluding the subchapters, are ignored.

The following EXCO control sequences are also ignored:


− Hidden text (% −)
− Bold
− Double

Fault conditions:
− Help file does not exist.
− The "Revision History" chapter is not found. Help is not
installed.
LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 36
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.16 Command Scripts

A command script is a simple text file with one command on each


line, or many commands separated by semicolon. Lines preceded
with the word "rem" will not be executed. It is allowed for a
script to call another script. The scriptfile can contain loops
with or without loopindex. This is a local DVT PC command.

3.2.16.1 Run a script file

Run a specified script file. If no path to the file is


specfied, it will be searched for in the previous dvt
directory, i.e in the last used directory. The directory path
’dvt$\’ can be used for short of the dvt home directory path.

Syntax: run <scriptfile>

Or running a script file from the menu:

menu; File − Script − Run...

Editing a script file from the menu:

menu; Help − Script − Edit...

scriptfile − can be any DOS file, i.e. max 8 character long


with a 3 character extension. Max number of lines in the
scriptfile is 32767. Max number of nested loopfiles is 90 (or
depending on system setup in config.sys "files= nn").

Example: >run dvt$\test1.scr

Fault conditions:
− Script file does not exist.
− Script includes an unknown command. Execution of the script
is interrupted.

3.2.16.2 Loops in Command Scripts

To simplify the use of Command Scripts, the user can insert


loop control statements in a script.

Syntax: LOOP_TO [<loopvar>"="]<loopmax>


<command 1>
.
.
<command n>
LOOP_END

loopvar − The name of the loopindex variable.


LZF 032 41/1M RJ

loopmax − Value 1 − 32767

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 37
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

command − Any DVT−command. Wherever <loopindex> is inserted, it


is replaced with current loop value.

n − Number of commands inside a loop, max 30.

loopindex = "%"<loopvar>

Example: LOOP_TO i=5


monitor enable mypar%i
LOOP_END

This is equivalent to a Script layout

monitor enable mypar1


monitor enable mypar2
monitor enable mypar3
monitor enable mypar4
monitor enable mypar5

Fault condition:
− If number of commands inside a loop exceeds the maximum as
specified above.

3.2.16.3 Wait for DVT link establishment

Inhibit execution of a DVT script file until the link to the


DVT server is established. The command can be cancelled by
pressing the Escape key.

Syntax: wait_linkest

Example: DXU:PLS>wait_linkest

Fault conditions:

3.2.16.4 Wait for DVT link lost

Inhibit execution of a DVT script file until the link to the


DVT server is lost. The command can be cancelled by pressing
the Escape key.

Syntax: wait_linklost

Example: DXU:PLS>wait_linklost

Fault conditions:

LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 38
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.16.5 Auto start of script

As an option the DVT can automatically start executing a script


file at startup. The script file should be named
’autoexec.scr’.

Syntax: menu; Options − Auto Start Script


LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 39
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

3.2.17 DVT Time

Set and read the time on the DVT (PC).

Syntax: dvt time [<dest> | set <date_time>]

dest = monitor | log

date_time = yy−mm−dd hh:mm:ss

y − year
m − month
d − day
h − hour
m − minute
s − second

Example: DXU:PLS>dvt time

DVT time is: 94−09−20 13:15:08

Fault condition:
− Wrong date/time values.

3.2.18 DVT Echo

Echoes text messages into specified window or (default) to the


DVT main window. The command can also be used to set echoing of
script commands on or off.

Syntax: dvt echo <text> [<dest>]


or
Syntax: dvt echo on|off

text − ASCII text message.

dest = mon | log

Example: DXU:PLS>dvt echo hello world

Prints the text ’hello world’ to the DVT main window.

Fault condition:

3.2.19 DVT Beep

Beeps a number of times (default 1) via the PC speaker.

Syntax: dvt beep [<n>]


LZF 032 41/1M RJ

n − Number of beeps.

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 40
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

Example: DXU:PLS>dvt beep

Beeps one time.

Fault condition:

3.2.20 DVT Sleep

Sleep specified amount of time.

Syntax: dvt sleep <time>

time = [[hh:]mm:]ss

hh, mm, ss − Time in hours, minutes and seconds.

Example: DXU:PLS>dvt sleep 10

Stops execution for 10 seconds.

Fault condition:
− Error in time specification.

3.2.21 DVT Wakeup

Sleep until a specified time.

Syntax: dvt wakeup <time>

time = [[hh:]mm:]ss

hh, mm, ss − Time in hours, minutes and seconds.

Example: DXU:PLS>dvt wakeup 10:12:00

Resumes execution at time 10:12:00.

Fault condition:
− Error in time specification.

3.2.22 View a text file

Type a text file in a selected window on the DVT. Default is


the command window.

Syntax: dvt type [dvt$|<path>\]<filename> [<output window>]

dvt$ − Path to DVT home directory.


LZF 032 41/1M RJ

path = Directory path to a file in DOS format. If not given,


the last used path will be used.

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 41
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

output window = cmd | log | mon | info

Example: DXU:PLS>dvt type aladdin.txt

Fault conditions:
− Non existing file name.

3.2.23 Show dvt directory

Show the currently active dvt directory. This is the directory


where specified files are searched for and files are saved to,
if no path is specified.

Syntax: dvt directory show


or short
Syntax: dvt dospwd

Example: DXU:PLS>dvt dospwd

a:\LOG

Fault conditions:

3.2.24 Set dvt directory

Set the currently active dvt directory. This is the directory


where specified files are searched for and files are saved to,
if no path is specified.

Syntax: dvt directory change <dirspec>


or short
Syntax: dvt doscd <dirspec>

dirspec − DOS directory specification.

Example: DXU:PLS>dvt doscd a:\

Fault conditions:
− Setting an undefined directory path.

3.2.25 List dvt directory

List files in the currently active dvt directory . This is the


directory where specified files are searched for and files are
saved to, if no path is specified.

Syntax: dvt directory list <filespec>


or short
LZF 032 41/1M RJ

Syntax: dvt dosdir <filespec>

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 42
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

filespec − DOS file specification which can include ’*’ and


’?’.

Example: DXU:PLS>dvt dosdir test*.log

TEST1.LOG
TEST2.LOG

Fault conditions:

LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 43
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

4 DVT PC MENU COMMANDS

An overview of accessible DVT menu commands in each window with


a short description.

Command window:

File
Save Setup
On Exit − Enables/Disables saving of the setup on
exit from the DVT application.
Now! − Saves setup immediately.
Printer Setup
Configure... − Configure printer.
Fonts... − Setup fonts for printer output.
Margins... − Setup margins for printer output.
Command Input
Save History As... − Save command history to a
file.
Read History From... − Read command history from a
file.
Edit History File... − Edit a command history file.
Print − Print current command history.
Command Output
Save As... − Save command output to a file.
Edit File... − Edit a command output file.
Print − Print the current command output.
Script
Edit... − Edit a script file.
Run... − Run a script file.
Restart Using [ASCII/PCS−link] − Restarts the DVT using the
ASCII or PCS link protocol.
Exit − Exits the DVT application.

Edit
Cut − Cuts marked text to buffer.
Copy − Copys marked text to buffer.
Paste − Pastes text from buffer.
Delete − Deletes marked text.
Select All − Marks all text.
Delete All − Deletes all text.

Search
Find... − Find a specified text string in window.
Find Next − Find next occurence of text string.

View
DVT Monitor Output − View Monitor output window.
DVT Log Output − View Log output window.
DVT Information & Help − View Information & Help window.
LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 44
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

Options
Auto Start Script − Enables/Disables automatic execution of
the script autoexec.scr at startup.
Translate Signal Numbers − Enables/Disables translation of
signal numbers to signal names
in the log.
Show Function Keys − Show/Hide the function keys at
the bottom of the command window.
Signal Number Translation Setup... − Setup the signal
translation file for
signal numbers to
signal names.
Function Keys Setup... − Add or edit shortcut function keys.
Com Port Setup (ASCII link)
COM1 − Use com1.
COM2 − Use com2.
4800 Baud − Set baud rate to 4800.
9600 Baud − Set baud rate to 9600.
19200 Baud − Set baudrate to 19200.
Disable unused COM port pins
− Enables/Disables some unused com
port pins which in some cases might
otherwise disturb the
communication.

Help
DVT Descriptions... − See a description on the DVT
function.
DVT/EPS/OMS/PLS/RTS/TFS Commands...
− See a installed command description
for a subsystem.
Help Setup
Import From... − Import an old subsystem
command description.
DVT − Install a new command description for
the DVT.
EPS − Install a command description for EPS.
OMS − Install a command description for OMS.
PLS − Install a command description for PLS.
RTS − Install a command description for RTS.
TFS − Install a command description for TFS.
View OSE Error List − See a document that lists all
OSE errors.
View Readme − See a readme file with information
about the files contained together with
the DVT.
About − About the DVT.
LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 45
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

Monitor and Log window:

File
Edit File... − Edit a Monitor/Log output file.
Save As... − Save Monitor/Log output to a file.
Print − Print Monitor/Log output.
Flush Oldest Output To... − Save flushed Monitor/Log output
to a file.
Horizontal Scroll − Enables/Disables horizontal scroll in
window.
Exit − Exit window.

Edit
Cut − Cuts marked text to buffer.
Copy − Copys marked text to buffer.
Paste − Pastes text from buffer.
Delete − Deletes marked text.
Select All − Marks all text.
Delete All − Deletes all text.

Search
Find... − Find a specified text string in window.
Find Next − Find next occurence of text string.

Information & Help window:

File
Edit File... − Edit a Monitor/Log output file.
Save As... − Save Monitor/Log output to a file.
Print − Print Monitor/Log output.
Flush Oldest Output To... − Save flushed Monitor/Log output
to a file.
Horizontal Scroll − Enables/Disables horizontal scroll in
window.
Exit − Exit window.

Edit
Cut − Cuts marked text to buffer.
Copy − Copys marked text to buffer.
Paste − Pastes text from buffer.
Delete − Deletes marked text.
Select All − Marks all text.
Delete All − Deletes all text.

Search
Find... − Find a specified text string in window.
Find Next − Find next occurence of text string.

Help
DVT/EPS/OMS/PLS/RTS/TFS Commands...
− See a installed command description
LZF 032 41/1M RJ

for a subsystem.

(crh201102;d66)d2_19082.tec;2 d2_19082.tec
DESCRIPTION 46
Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) Nr - No.

ERA/LR/FP Peter Hertzman 2/190 82−CRH 201 102 Uen


Dokumentansvarig/Godkänd - Document responsible/Approved Kontr - Checked Datum - Date Rev Tillhör/Referens - File/Reference

ERA/LR/FP ERALKR 1996−04−16 A

5 REFERENCES

/DESC SUP_ENT/ Description, Supervised entities in PLS


2/1551−CRH 201 102

/IWD DEBUG/ Application Layer, Debug Services


11/155 19−CRH 201 102

/IWD PC/ Application Layer, PC Support


14/155 19−CRH 201 102

/HEAD MONITOR/ Format Description, Debug support,


Monitors 27/155 19−CRH 201 102
LZF 032 41/1M RJ

(crh201102;d66)d2_19082.tec;2 d2_19082.tec

You might also like