User guide

5: Freeway Boot and Operation
DC 900-1333Q 153
-------------------------------------------------------------------------------
@@@@@ Actual Data offset 291 Size = 83
000000: 00 00 00 00 00 00 00 00 00 0c 00 14 00 02 00 01 ................
000016: 00 32 00 00 00 04 00 00 2c 10 c1 be 6c a1 1c 08 .2......,...l...
000032: 14 ea 1d 08 20 00 00 00 00 00 06 00 00 00 00 00 .... ...........
000048: 00 17 08 05 40 00 06 00 00 00 00 00 88 13 00 00 ....@...........
000064: 00 00 00 00 04 00 00 00 00 00 00 00 a5 68 b5 0d .............h..
000080: bd 25 a4 .%.
@@@@@ Decoding begins
<====(READ 83 bytes)Conn 2: Mon Aug 26 00:10:19.272333333 2013
Freeway header info: length = 44
Packet Type(2) = FW_DATA Command(1) = FW_ICP_WRITE
Status(0) = OK Client ID = 0 Freeway ID = 4
ICP header info:
OldClientID = 0 OldServerID = 0
Data length = 23 Cmd(2053) = DLI_ICP_CMD_WRITE
Status(0) = DLI_ICP_ERR_NO_ERR
Parms: [0] = 1536 [1] = 0 [2] = 0
Protocol header info: ( little-endian client )
Cmd(5000) = DLI_PROT_SEND_NORM_DATA
Modifier = 0 Link = 0
Cir = 0 Sess = 4 Seq = 0
Parms: [0] = 0 [1] = 0
DATA : a5 68 b5 0d bd 25 a4 .h...%.
-------------------------------------------------------------------------------
The arrows at the start of the packet decoding indicate which direction the packet was
going. A packet that shows “<====(READ xx bytes)” is from the client to the Freeway.
A packet that shows “====>(WRITE xx bytes)” is from the Freeway to the client.
When you are finished tracing, go back to the interactive menu and in the Trace Func-
tions menu select:
"3) Turn MSGMUX Trace Off"
If you leave tracing on, it will continue to trace new events into the circular buffer while
overwriting the oldest events. Then if another item of interest occurs, you can go back
to the Trace Functions menu and select "4) Process Trace Data" again to produce a trace
file containing the latest events. MSGMUX tracing is set to “off ” by default after a Free-
way boot.