program correlation message questions

[algrobman]

Hi,

Our design emits this message as first one when tracing is enabled.
Appears that this message can be encoded as 3 or 2 bytes:

% ~/bin/nexrv -dump try.bin

0x84 100001_00: TCODE[6]=33 (MSG #0) - ProgTraceCorrelation

0x00 000000_00: EVCODE[4]=0x0 CDF[2]=0x0

0x03 000000_11: ICNT[6]=0x0

 

0x84 100001_00: TCODE[6]=33 (MSG #1) - ProgTraceCorrelation

0x03 000000_11: EVCODE[4]=0x0 CDF[2]=0x0 ICNT[0]=0x0

 

Stat: 5 bytes, 0 idles, 2 messages, 0 error messages, 2.50 bytes/messa

what encoding is legal?

Background :
3 byte one has 2nd byte generated "manually" as EVCODE and CDF occupy 6 bits and thus fits into 2nd byte of the message.
2 byte version is generated by the reference tool, which processes all message packets the same way - removes zero MSB bytes from each packet.

Second question is:
if timestamping is enabled, what value should be emitted for this first message ? full value? Delta? Delta from what? No Timestamp packet?