| Electronic Components Datasheet Search |
|
UM0434 Datasheet(PDF) 354 Page - STMicroelectronics |
|
|
|||||||||||||||||||||||||||||
UM0434 Datasheet(HTML) 354 Page - STMicroelectronics |
|
354 / 390 page ![]() UM0434 Nexus3 module 355/391 If only a program trace message attempts to enter the queue while it is being emptied, the error message incorporates the program trace only error encoding, 00001. If both OTM and program trace messages attempt to enter the queue, the error message incorporates the OTM and program trace error encoding 00111. If a watchpoint also attempts to be queued while the FIFO is being emptied, the error message incorporates error encoding 01000. Note: DC1[OVC] can be set to delay the CPU in order to alleviate, but not eliminate, potential overrun situations. Error information is messaged out in the format shown in Table 253: Program trace synchronization messages A program trace direct/indirect branch with synchronization message is messaged using the auxiliary port, provided program trace is enabled, for the following conditions (see Table 256): ● Initial program trace message upon the first direct/indirect branch after exit from system reset or whenever program trace is enabled ● Upon direct/indirect branch after returning from a CPU low-power state ● Upon direct/indirect branch after returning from debug mode ● Upon direct/indirect branch after occurrence of queue overrun, which can be caused by any trace message ● Upon direct/indirect branch after the periodic program trace counter has expired, indicating 255 without-synchronization program trace messages have occurred since the last with-synchronization message occurred ● Upon direct/indirect branch after assertion of the event-in ( nex_evti_b) signal, if the EIC bits within the DC1 register have enabled this feature ● Upon direct/indirect branch after the sequential instruction counter has expired, indicating 255 instructions have occurred between branches ● Upon direct/indirect branch after a BTM message was lost due to an attempted access to a secure memory location (for SOCs with security) ● Upon direct/indirect branch after a BTM message was lost due to a collision entering the FIFO between the BTM message and either a watchpoint message or an ownership trace message If the Nexus3 module is enabled at reset, a nex_evti_b assertion initiates a program trace direct/indirect branch with synchronization message if program trace is enabled upon the first direct/indirect branch. The format for program trace direct/indirect branch with synchronization messages is shown in Table 254: Table 253. Error message format (5 bits) (4 bits) (6 bits) Error Code(1) 1. Must be one of 00001, 00111, or 01000. Source Process TCODE (001000) Fixed length = 15 bits |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |