Data Trace Timing Diagrams (8 Mdo / 2 Mseo Configuration) - STMicroelectronics SPC572L series Reference Manual

RM0400
66.13.4

Data Trace Timing Diagrams (8 MDO / 2 MSEO configuration)

MCKO
MSEO_B[1:0]
MDO[7:0]
MCKO
MSEO_B[1:0]
MDO[7:0]
66.14 Data Acquisition messaging
this section details the Data Acquisition mechanisms supported by the Nexus 3 module.
Data Acquisition Trace is implemented using Data Acquisition Trace Messages in
accordance with IEEE-ISTO 5001 definitions. The control mechanism to export the data is
different from the recommendations of the standard, however.
Data Acquisition Trace provides a convenient and flexible mechanism for the debugger to
observe the architectural state of the machine through software instrumentation.
66.14.1 Data Acquisition ID Tag field
The DQTAG Tag field (DQTAG) is an 8-bit value specifying control or attribute information
for the data included in the Data Acquisition message. DQTAG is sampled from
DEVENT
DQTAG is left to the discretion of the development tool to be used in whatever manner is
deemed appropriate for the application.
66.14.2 Data Acquisition Data field
The Data Acquisition Data field (DQDATA) is the data captured from the DDAM write
operation via mtspr operations. Leading zeros are omitted from the message.
Figure 1178. Data Trace — Data Write message
11 00
00000101
TCODE = 5
source processor = 0000
data size = 0010 (halfword)
relative address = 8'hA5
write data = 16'hBEEF
Figure 1179. Data Trace — Data Read w/ Sync message
11
00001110 00001000
TCODE = 14,
source processor = 0000
data size = 0001 (byte)
full access address = 32'h01468ACE
write data = 8'h5C
when a write to DDAM is performed via mtspr operations. The usage of the
DQTAG
DocID027809 Rev 4
00 01
00010100 000101010
00
01100111 01000101
e200z215An3 Nexus 3 Module
00
11101111 10111110
01
10100011 00000000
11
11
01011100
1965/2058
1982