| Electronic Components Datasheet Search |
|
UM0434 Datasheet(PDF) 307 Page - STMicroelectronics |
|
|
|||||||||||||||||||||||||||||
UM0434 Datasheet(HTML) 307 Page - STMicroelectronics |
|
307 / 390 page ![]() Debug support UM0434 308/391 instruction and returns to the debug state (again indicated by the OSR). The debug session remains in force until the final Go+Exit command is executed, at which time the CPU returns to its previous state (unless a new debug request is pending). A scan into the CPUSCR is required before executing each Go+Exit or Go+NoExit command. 11.5.2 JTAG/OnCE signals The JTAG/OnCE interface is used to transfer OnCE instructions and data to the OnCE control block. Depending on the resource being accessed, the CPU may need to be placed in debug mode. For resources outside the CPU block and contained in the OnCE block, the processor is not disturbed and may continue execution. If a processor resource is required, an internal debug request ( dbg_dbgrq) may be asserted to the CPU by the OnCE controller, and causes the CPU to finish the instruction being executed, save the instruction pipeline information, enter debug mode, and wait for further commands. Asserting dbg_dbgrq causes the chip to exit the low-power mode enabled by setting MSR[WE]. Table 196 details the primary JTAG/OnCE interface signals. A full description of JTAG signals is provided in Chapter 9.3.2: JTAG ID signals.” 11.5.3 OnCE internal interface signals The following sections describe the OnCE interface signals to other internal blocks associated with the OnCE controller. Table 197 shows the OnCE internal interface signals. Table 196. JTAG/OnCE primary interface signals Signal name I/O Description j_trst_b I JTAG test reset j_tclk I JTAG test clock j_tms I JTAG test mode select j_tdi I JTAG test data input j_tdo O Test data out to master controller or pad j_tdo_en O Enables TDO output buffer. Set when the TAP controller is in the Shift-DR or Shift-IR state. Table 197. OnCE internal interface signals Signal name I/O Description CPU Debug Request ( dbg_dbgrq) O The db g_dbgrq signal is set by the OnCE control logic to request the CPU to enter the debug state. It may be set for a number of different conditions, and causes the CPU to finish the current instruction being executed, save the instruction pipeline information, enter debug mode, and wait for further commands. CPU Debug Acknowledge ( cpu_dbgack) I The cpu_dbgack signal is set by the CPU upon entering the debug state. This signal is used as part of the handshake mechanism between the OnCE control logic and the rest of the CPU. The CPU core may enter debug mode through either a software or hardware event. |
|
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 |