*
*Home|Chinese|Japanese*About ARM|Forums|Events|News|Employment|Contact Us|Investors*
dotted rule
*ARM - the architecture for the digital worldARM - the architecture for the digital world
search
*
*
***
*MARKETS:PRODUCTS & SOLUTIONS:CONNECTED COMMUNITY:TECHNICAL SUPPORT:DOCUMENTATION*
*
technical support
*
*
****
*.Technical Support
*
*
*>>Home Page*
*
*.Obtaining Support*
*
*.FAQs*
*
**Development Tool FAQs*
**IP FAQs*
**Embedded Software FAQs*
**Artisan Physical IP FAQs (Login Required)*
*
*.Downloads*
*
*.Documentation*
*
*.Training*
*
*.Where To Buy*
*
*.Keil MCU Tools*
*
*.What's New*
*
*.ARM Newsgroups*
*
*.Active Assist On-site Services*
*
*
*
technical support FAQsask ARM*
*

Technical Support Search
*     (Advanced Search)
  FAQs   Documentation   Downloads   Forums

*

 
downarrowHow does the ARM11 JTAG synchronisation logic work?
Applies to: JTAG Debug Issues, RealView ICE (RVI)

For general information about the JTAG synchronisation logic and debugging with adaptive clocking, please see the following FAQ entries:

Whereas in most ARM cores DBGTDO changes when DGBTCKEN is high, in ARM11 DBGTDO changes one cycle after DBGTCKEN is high. For this reason the ARM11 JTAG synchronisation logic is different from other cores.

The best scenario to debug the ARM11 would be to have a TCK high period equal to 3 core clock periods, and a TCK low period equal to 4 core clock periods, which sets a maximum TCK frequency less than one seventh of the core clock frequency.

With a 50% duty cycle the maximum TCK frequency is one eigth of the core clock frequency.






back to top

*
**
*4 dots*Other ARM Websites
*
shadow *LEGAL STATEMENTshadow