IBM
Contents Index Previous Next



Trouble-Shooting


What to Do if the SDL Editor Trace Does Not Work?

The SDL Target Tester gets the SDL Editor references from the generated file <systemname>.sym in the known form #SDTREF( ... ).

As it is possible to generate an SDL system and to test it on another platform it is possible that the paths contained in each #SDTREF() are not up to date if using the SDL Target Tester.

All the paths in <systemname>.sym must simply be updated.

What to Do if There Is a Warning of the Information/Message Decoder?

If the message decoder detects an error there will be a warning like the one shown in Example 631.

Example 631 : warning of the message decoder

**WARNING: There is an inconsitency in the information decoder.
This message will be suppressed form now on.
Message Class: 241,d
Message Tag  : 5,d
Number of data bytes received=6
Number od data bytes decoded =5

  ***Received buffer (32 octets):
  ***f1 05 aa 06 00 00 00 00 - 01 04 ab ee ee ee ee ee
  ***ee ee ee ee ee ee ee ee - ee ee ee ee ee ee ee ee

This warning must be interpreted as follows:

Note:

The kind of C basic type the xPID value is represented by, depends on the SDL system in use (single instance processes only or multiple instance processes). Please view the typedef of xPID in the file ml_typ.h.

The size of the C basic type depends on the microcontroller and compiler that is used.

By having a look to the C struct (xmk_T_CMD_TSTATE) which is represented by the 6 data octets received a value for xPID is found like 0x00000000 as an integer is given with the length 4 octets in this example.

Note:

The kind of C basic type the xmk_T_STATE value is represented by, depends on the SDL system in use, please view the flag XMK_USE_HUGE_TRANSITIONTABLES.

The size of the C basic type depends on the microcontroller and compiler in use.

Having a look to the fifth octet of the message data the value for xmk_T_STATE is 0x01, as the length of character is 1 and the alignment of character is 8. Please view Preparing the Host to Target Communication.

After all in this example there are 5 bytes (octets) decoded (4+1) and 6 received which leads to the inconsistency in the information decoder.

The user is asked to correct the settings in the file sdtmt.opt to support the SDL Target Tester's host site with the correct information about the target's memory layout.

Caution!

The Example 631 is an exception concerning the inconsistency in the information decoder.

The compiler used for this example only knows C structures with a size dividable by two which leads to a message data length of 6.

The value 0x04 in the example only represents a filler octet which does not need to be noticed.


http://www.ibm.com/rational
Contents Index Previous Next