CORELIS
CAS-1000-I2C/E
I2C Bus Analyzer, Exerciser, Programmer, and Tester
1
™
User’s Manual
Corelis, Inc.
13100 Alondra Blvd. Cerritos, CA 90703
Telephone: 562.926.6727 • Fax: (562) 404-6196
Preface
Copyright © 2006-2017, Corelis Inc.
PRINTING HISTORY
Edition 1, February 2006
Edition 2, March 2006
Edition 3, May 2006
Edition 4, June 2006
Edition 5, November 2006
Edition 6, October 2007
Edition 7, July 2008
Edition 8, January 2009
Edition 9, January 2010
Edition 10, February 2011
Edition 11, October 2012
Edition 12, October 2013
Edition 13, October 2016
Edition 14, July 2017
GENERAL NOTICE
Information contained in this document is subject to change without notice. CORELIS shall not be liable
for errors contained herein for incidental or consequential damages in connection with the furnishing,
performance, or use of material contained in this manual.
This document contains proprietary information that is protected by copyright. All rights reserved. No part
of this document may be reproduced or translated to other languages without the prior written consent of
CORELIS. This manual is a CORELIS proprietary document and may not be transferred to another party
without the prior written permission of CORELIS.
CORELIS assumes no responsibility for the use of or reliability of its software on equipment that is not
furnished by CORELIS.
ENVIRONMENTAL NOTICE
This product must be disposed of in accordance with the WEEE directive.
TRADEMARK NOTICE
2
I
C Bus is a registered trademark of Philips Electronics N.V.
Pentium and SMBus are registered trademarks of Intel Corporation.
Windows is a registered trademark of Microsoft Corporation.
Other products and services named in this book are trademarks or registered trademarks of their
respective companies. All trademarks and registered trademarks in this book are the property of their
respective holders.
Preface
i
PRODUCT WARRANTY AND SOFTWARE MAINTENANCE
For product warranty and software maintenance information, see the PRODUCT WARRANTY AND
SOFTWARE MAINTENANCE POLICY statement included with your product shipment.
EXCLUSIVE REMEDIES
THE REMEDIES CONTAINED HEREIN ARE THE CUSTOMER'S SOLE AND EXCLUSIVE REMEDIES.
CORELIS SHALL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR
CONSEQUENTIAL DAMAGES, WHETHER BASED ON CONTRACT, TORT, OR ANY OTHER LEGAL
THEORY.
Product maintenance agreements and other customer assistance agreements are available for Corelis
products. For assistance, contact your nearest Corelis Sales and Service Office.
RETURN POLICY
No items returned to CORELIS for warranty, service, or any other reason shall be accepted unless first
authorized by CORELIS, either direct or through its authorized sales representatives. All returned items
must be shipped pre-paid and clearly display a Return Merchandise Authorization (RMA) number on the
shipping carton. Freight collect items will NOT be accepted.
Customers or authorized sales representatives must first contact CORELIS with notice of request for
return of merchandise. RMAs can only originate from CORELIS. If authorization is granted, an RMA
number will be forwarded to the customer either directly or through its authorized sales representative.
CONTACT INFORMATION
The latest news, tips and updates on the Corelis bus analyzer hardware and software products can be
found in the Corelis user forums. The forums are provided as a free service to our existing customers but
an individual user name and password is required. To request an account, please visit
forums.corelis.com/register.php
For sales inquiries, please contact sales@corelis.com.
For any support related questions, please enter a support request at www.corelis.com/support or email
support@corelis.com
For more information about other products and services that Corelis offers, please visit www.corelis.com
.
ii
Table of Contents
Chapter 1 Product Overview ...................................................................................... 1
Introduction to I2C and SMBus.............................................................................................................. 1
Introduction to the CAS-1000-I2C™......................................................................................................2
Software Toolset ..................................................................................................................................... 3
Hardware Features ................................................................................................................................. 4
Host Computer Requirements............................................................................................................... 6
Chapter 2 Installation.................................................................................................. 7
Installing the I2C Exerciser Application Software...............................................................................8
CAS-1000-I2C/E Hardware Installation ............................................................................................... 17
Chapter 3 Getting Started......................................................................................... 23
Overview ................................................................................................................................................ 23
Tutorial – Using Demo Mode ...............................................................................................................23
Tutorial – Using Live Mode ..................................................................................................................74
Chapter 4 Connecting to a Target............................................................................ 91
Connecting the I2C Signals.................................................................................................................. 91
Interface Setup ...................................................................................................................................... 93
Chapter 5 Bus Traffic Monitor................................................................................ 103
Trace Listing .......................................................................................................................................104
Timing Field.........................................................................................................................................107
Monitor Configurations ......................................................................................................................110
Monitor Preferences ...........................................................................................................................117
Monitor Trigger ...................................................................................................................................121
Monitor Window Reference ............................................................................................................... 134
Chapter 6 Interactive Debugger............................................................................. 150
Send Data ............................................................................................................................................ 151
Receive Data .......................................................................................................................................153
Debugger Script.................................................................................................................................. 155
Error Injection .....................................................................................................................................158
Debugger Options ..............................................................................................................................160
Debugger Window Reference............................................................................................................ 162
iii
Chapter 7 Serial EEPROM Programmer ................................................................ 166
Programmer Operations .................................................................................................................... 167
Programmer Options .......................................................................................................................... 171
Programmer Window Reference .......................................................................................................172
Chapter 8 Configuration and Preferences ............................................................ 176
Configuration Manager ......................................................................................................................176
Preferences Dialog .............................................................................................................................193
Using Project Files .............................................................................................................................198
Calibration ...........................................................................................................................................200
Chapter 9 Third Party Application Interface ......................................................... 203
Overview .............................................................................................................................................. 203
Dynamic Link Library (DLL)...............................................................................................................204
General Calling Sequence .................................................................................................................205
Function Reference ............................................................................................................................206
Chapter 10 I2C Device Emulator............................................................................. 249
Emulation Manager Window..............................................................................................................251
Emulated Master Window ..................................................................................................................257
Emulated Slave Window ....................................................................................................................267
Emulated Slave Clock Stretching .....................................................................................................272
Chapter 11 Script-Driven Bus Tester..................................................................... 275
Test Window Reference .....................................................................................................................276
Chapter 12 Parameters Scope ............................................................................... 289
Parameter Measurements ..................................................................................................................290
Waveform Display...............................................................................................................................295
Parameters Scope Window Reference.............................................................................................297
Chapter 13 Scripting Language ............................................................................. 299
Overview .............................................................................................................................................. 299
The Essential Syntax Elements......................................................................................................... 300
Example Script .................................................................................................................................... 306
Built-in Functions: Summary ............................................................................................................308
Built-In Functions: Detailed Descriptions ........................................................................................312
iv
Syntax Summary (Advanced Users Only)........................................................................................402
Built-In Script Editor ........................................................................................................................... 406
Chapter 14 Glitch Pattern Injection ....................................................................... 415
Overview .............................................................................................................................................. 415
Using the Glitch Pattern Editor ......................................................................................................... 416
Adding Glitch Patterns to Master and Slave Emulation .................................................................421
Appendix A CAS-1000-I2C Hardware Reference ................................................. 427
Hardware Specifications ....................................................................................................................427
Electrical Specifications ....................................................................................................................428
v
List of Figures
Figure 1. I2C Bus Topology ..........................................................................................................................1
Figure 2. Illustration of the CAS-1000-I2C ...................................................................................................2
Figure 3. I2C Exerciser Installation Wizard ..................................................................................................8
Figure 4. Windows Run Dialog .....................................................................................................................9
Figure 5. License Agreement Screen...........................................................................................................9
Figure 6. Customer Registration Screen.................................................................................................... 10
Figure 7. Destination Folder Screen ..........................................................................................................11
Figure 8. Select Program Folder Screen....................................................................................................12
Figure 9. Completing the Installation Wizard Screen .................................................................................13
Figure 10. Windows 7 Security Warning Pop-up Window .........................................................................14
Figure 11. Windows XP Logo Test Warning Pop-up Window.................................................................... 14
Figure 12. Software Installation Button on the Windows XP Task Bar ...................................................... 15
Figure 13. Installation Completed Screen..................................................................................................16
Figure 14. Found New Hardware Wizard - Welcome Screen (Windows XP) ............................................ 17
Figure 15. Found New Hardware Wizard - Install Options (Windows XP)................................................. 18
Figure 16. Windows XP Logo Test Warning Pop-up Window.................................................................... 19
Figure 17. Found New Hardware Wizard – Installation Complete (Windows XP) ..................................... 20
Figure 18. Windows Device Manager (Windows XP) ................................................................................21
Figure 19. Initial I2C Exerciser Warning Message when CAS-1000-I2C is Not Initially Connected .......... 24
Figure 20. Tools Menu Demo Mode Selection........................................................................................... 25
Figure 21. Status Bar Indicating Demo Mode ............................................................................................25
Figure 22. Begin Monitor Data Collection ..................................................................................................26
Figure 23. Demo Mode Reminder Pop-up Window ...................................................................................26
Figure 24. Run Status Tab .........................................................................................................................27
Figure 25. Monitor Window Centered on Trigger Line ...............................................................................28
Figure 26. Monitor Window Right-Click Pop-up Menu ...............................................................................29
Figure 27. Monitor Window Trace List Positioned on Trigger Line ............................................................ 30
Figure 28. Monitor Window Right-Click Pop-up Menu Selecting Trigger Settings.....................................31
Figure 29. Configuration Manager Trigger Setup Screen ..........................................................................32
Figure 30. Monitor Window Trace List Column Headings.......................................................................... 33
Figure 31. I2C Exerciser Status Bar...........................................................................................................33
Figure 32. Go to Start Tool Bar Button....................................................................................................... 34
Figure 33. Monitor Window Trace List Showing Symbolic Address and Data Entries...............................35
Figure 34. Configuration Manager Symbols Definition Screen ..................................................................36
Figure 35. Symbol Definition Dialog........................................................................................................... 37
Figure 36. Configuration Manager Symbols Definition Screen with DAC Symbol..................................... 38
Figure 37. Monitor Window Trace List Showing New DAC Symbolic Address Entries ............................. 39
Figure 38. Monitor Window Trace List Data Byte Column Right-Click Pop-up Menu................................40
Figure 39. Monitor Window Trace List Data Column with Symbols Disabled............................................41
Figure 40. Monitor Window Trace List Data Byte Column Right-Click Pop-up Menu................................42
Figure 41. Monitor Window Trace List Data Column with Data Bytes in Binary Format............................ 42
Figure 42. Monitor Window Trace List Data Byte Column Right-Click Pop-up Menu................................43
Figure 43. Monitor Window Trace List in Compact Mode ..........................................................................44
Figure 44. Monitor Window Trace List in Compact Mode with Data Bytes Pop-up Window .....................45
Figure 45. Monitor Window Trace List I/O 2 Right-Click Pop-up Menu .....................................................46
Figure 46. Dragging Monitor Window Trace List I/O 1 Column Heading...................................................46
Figure 47. Monitor Window Trace List with Rearranged I/O Columns.......................................................47
Figure 48. Trace Layout Dialog .................................................................................................................. 48
vi
Figure 49. Monitor Window Timing Display................................................................................................49
Figure 50. Monitor Window Trace List Positioned on Cursor A Line .........................................................50
Figure 51. Monitor Window Trace List Positioned on Cursor B Line .........................................................51
Figure 52. Monitor Window Timing Display Showing Edges Zoomed in at Line 100 ................................52
Figure 53. Monitor Window Timing Display Measuring the Time Between Cursors A & B ....................... 53
Figure 54. Go to Start Tool Bar Button....................................................................................................... 54
Figure 55. Find Tool Bar Button .................................................................................................................55
Figure 56. Find Dialog ................................................................................................................................55
Figure 57. Find a Data Value of 2E ............................................................................................................57
Figure 58. Monitor Window Trace List Showing Find 2E Data Result ....................................................... 58
Figure 59. Find a Data Value of 72 ............................................................................................................ 59
Figure 60. Clear Tagged Rows Prompt......................................................................................................59
Figure 61. Matched Transactions Prompt ..................................................................................................60
Figure 62. Monitor Window Trace List Showing Find 72 Data Result ....................................................... 60
Figure 63. Go to Tagged Row Tool Bar Button.......................................................................................... 61
Figure 64. Monitor Window Trace List Showing the Second Find 72 Data Result ....................................61
Figure 65. Monitor Colors Preferences Screen.......................................................................................... 62
Figure 66. Monitor Colors Preferences Screen Changing Cursor A Background Color ............................ 63
Figure 67. Monitor Window with Updated Cursor A Colors .......................................................................64
Figure 68. Monitor Window with Updated Cursor A Colors .......................................................................65
Figure 69. Monitor Window with Alternating Row Colors ...........................................................................66
Figure 70. Monitor Window Trace List with the Trigger Line Centered......................................................67
Figure 71. Monitor Options Preferences Screen........................................................................................68
Figure 72. Monitor Window Trace List with Trigger at Line Zero Numbering ............................................69
Figure 73. Monitor Window Trace List with Trigger is Time Zero Timestamps.......................................... 70
Figure 74. Monitor Window Trace List with Relative Timestamps .............................................................71
Figure 75. Monitor Window Trace List Showing Addresses in FE mode...................................................72
Figure 76. Monitor Window Trace List Showing Addresses in 7F mode ...................................................73
Figure 77. Tools Menu Deselect Demo Mode............................................................................................74
Figure 78. Status Bar Indicating Live Data Mode ......................................................................................74
Figure 79. Analyzer Supplied Mode Prompt ..............................................................................................75
Figure 80. Debugger Window ....................................................................................................................76
Figure 81. Byte Sent From the Debugger ..................................................................................................77
Figure 82. Receive Three Bytes in the Debugger ......................................................................................78
Figure 83. Capture of Debugger Send .......................................................................................................79
Figure 84. Tutorial Script Loaded Into Debugger .......................................................................................80
Figure 85. Capture of Debugger Script ......................................................................................................81
Figure 86. Set Discrete I/O Modes.............................................................................................................82
Figure 87. Debugger Discrete I/O Script ....................................................................................................83
Figure 88. Monitor Debugger Discrete I/O Manipulation............................................................................ 83
Figure 89. Debugger Close ........................................................................................................................84
Figure 90. SMBus Raw Data......................................................................................................................85
Figure 91. SMBus Pane Before Associating Decoder File ........................................................................86
Figure 92. SMBus Decoder File Dialog with TC74 Information .................................................................87
Figure 93. Switch to SMBus Mode............................................................................................................. 88
Figure 94. SMBus Decoded Data ..............................................................................................................88
Figure 95. Decoded SMBus Message ToolTip ..........................................................................................89
Figure 96. SMBus Data Window ................................................................................................................89
Figure 97. RJ45 Connector Pin Numbering ...............................................................................................92
Figure 98. Configuration Manager .............................................................................................................94
Figure 99. Analyzer Supplied Voltage Prompt ...........................................................................................95
Figure 100. Configuration Manager Analyzer Supplied .............................................................................96
Figure 101. Configuration Manager Settings Pane ....................................................................................98
Figure 102. Bus Electrical Features ...........................................................................................................99
Figure 103. Bus Drive and Monitoring Features ......................................................................................100
vii
Figure 104. Input/Output Signals .............................................................................................................101
Figure 105. Monitor Buffer Options ..........................................................................................................102
Figure 106. Monitor Window .................................................................................................................... 103
Figure 107. Monitor Trace Listing ............................................................................................................104
Figure 108. Monitor Timing Field .............................................................................................................107
Figure 109. Timing Field Popup Menu .....................................................................................................109
Figure 110. Filters Pane ........................................................................................................................... 111
Figure 111. Filter Definition Dialog (similar to Edit).................................................................................. 112
Figure 112. Symbols Pane ....................................................................................................................... 113
Figure 113. Symbol Definition Dialog....................................................................................................... 114
Figure 114. SMBus Pane .........................................................................................................................115
Figure 115. SMBus Decoder File Dialog.................................................................................................. 116
Figure 116. Monitor Colors Pane .............................................................................................................117
Figure 117. Monitor Options Pane ........................................................................................................... 119
Figure 118. Formats Pane........................................................................................................................120
Figure 119. Trigger Tab on Monitor Tools Dialog ....................................................................................121
Figure 120. Trigger on Single Event ........................................................................................................125
Figure 121. Trigger on Repeated Single Event........................................................................................ 126
Figure 122. Trigger on Sequence of Multiple Events ...............................................................................127
Figure 123. Trigger on Consecutive Sequence of Events .......................................................................128
Figure 124. Trigger Dialog........................................................................................................................129
Figure 125. Context Popup Menu on Trigger Definition Tree .................................................................. 130
Figure 126. Create New Trigger Dialog ...................................................................................................131
Figure 127. Active Trigger Operation Status............................................................................................ 133
Figure 128. I2C Exerciser Monitor Window Layout.................................................................................. 134
Figure 129. Monitor File Menu ................................................................................................................. 135
Figure 130. Monitor Trace Menu.............................................................................................................. 136
Figure 131. Trace | Execute Submenu .................................................................................................... 137
Figure 132. Run Status Tab on Monitor Tools Window ...........................................................................138
Figure 133. Trace | Go To Submenu ....................................................................................................... 139
Figure 134. Trace | View Submenu..........................................................................................................140
Figure 135. Monitor Find Dialog – Regular ..............................................................................................141
Figure 136. Monitor Find Dialog – Compact ............................................................................................141
Figure 137. Trace Layout Dialog.............................................................................................................. 143
Figure 138. Tools Menu ........................................................................................................................... 144
Figure 139. Monitor Window Menu ..........................................................................................................146
Figure 140. Monitor Help Menu ................................................................................................................146
Figure 141. Monitor Tool Bar....................................................................................................................147
Figure 142. Debugger Window ................................................................................................................150
Figure 143. Debugger Send Controls ......................................................................................................151
Figure 144. Debugger Receive Controls.................................................................................................. 153
Figure 145. Debugger Options Pane .......................................................................................................160
Figure 146. I2C Exerciser Debugger Window Layout ..............................................................................162
Figure 147. Debugger File Menu .............................................................................................................163
Figure 148. Debugger Tool Bar ................................................................................................................164
Figure 149. Programmer Window ............................................................................................................167
Figure 150. Programmer Read Window................................................................................................... 169
Figure 151. Programming Progress Window ...........................................................................................170
Figure 152. Verifying Progress Window................................................................................................... 170
Figure 153. Erasing Progress Window.....................................................................................................170
Figure 154. Programmer Options Pane ................................................................................................... 171
Figure 155. I2C Exerciser Programmer Window......................................................................................172
Figure 156. Programmer File Menu ......................................................................................................... 173
Figure 157. Programmer Tool Bar ...........................................................................................................174
Figure 158. Configuration Manager Dialog Panes (Settings selected)....................................................177
viii
Figure 159. Filters Pane ........................................................................................................................... 179
Figure 160. Filter Definition Dialog (similar to Edit).................................................................................. 180
Figure 161. Symbols Pane ....................................................................................................................... 181
Figure 162. Symbol Definition Dialog....................................................................................................... 182
Figure 163. SMBus Pane .........................................................................................................................183
Figure 164. SMBus Decoder File Dialog.................................................................................................. 184
Figure 165. Settings Pane ........................................................................................................................185
Figure 166. Files Pane .............................................................................................................................189
Figure 167. Target Slaves Pane ..............................................................................................................190
Figure 168. Timing Skew Pane ................................................................................................................192
Figure 169. Monitor Colors Pane .............................................................................................................193
Figure 170. Monitor Options Pane ........................................................................................................... 194
Figure 171. Debugger Options Pane .......................................................................................................195
Figure 172. Programmer Options Pane ................................................................................................... 196
Figure 173. Formats Pane........................................................................................................................197
Figure 174. Title Bar for a New Project ....................................................................................................198
Figure 175. Title Bar for a Saved Project .................................................................................................199
Figure 176. File Menu MRU Project List ..................................................................................................199
Figure 177. Calibration Prompt ................................................................................................................200
Figure 178. Calibration Warning ..............................................................................................................200
Figure 179. Calibration Status..................................................................................................................201
Figure 180. Calibration Complete ............................................................................................................201
Figure 181. Emulation Manager Window .................................................................................................251
Figure 182. Emulator Manager Window...................................................................................................252
Figure 183. Add Emulated Device Dialog ................................................................................................ 254
Figure 184. Emulator Execute Menu........................................................................................................255
Figure 185. Emulator Tool Bar .................................................................................................................256
Figure 186. Emulated Master Window .....................................................................................................257
Figure 187. Emulated Master Source Popup Menu .................................................................................259
Figure 188. Emulated Master File Menu ..................................................................................................261
Figure 189. Emulated Master Edit Menu..................................................................................................262
Figure 190. Emulated Master Execute Menu........................................................................................... 263
Figure 191. Emulated Master Breakpoint Menu.......................................................................................264
Figure 192. Emulated Master Tool Bar ....................................................................................................265
Figure 193. Emulated Slave Window .......................................................................................................267
Figure 194. Emulated Slave File Menu ....................................................................................................268
Figure 195. Emulated Slave Edit Menu....................................................................................................269
Figure 196. Emulated Slave Tool Bar ......................................................................................................270
Figure 197. Configuring Emulated Slave Device .....................................................................................273
Figure 198. Clock Stretched on ACK Bit ..................................................................................................273
Figure 199. Test Window .........................................................................................................................276
Figure 200. Test Window .........................................................................................................................277
Figure 201. Test Source Popup Menu .....................................................................................................280
Figure 202. Test File Menu ...................................................................................................................... 282
Figure 203. Test Edit Menu ...................................................................................................................... 283
Figure 204. Test Execute Menu ...............................................................................................................284
Figure 205. Test Breakpoint Menu........................................................................................................... 284
Figure 206. TestTool Bar..........................................................................................................................286
Figure 207. Parameters Scope Window ..................................................................................................289
Figure 208. Parameters Scope Measurement Controls...........................................................................290
Figure 209. Parameter Specification File Example ..................................................................................294
Figure 210. Parameters Scope Waveform Controls ................................................................................295
Figure 211. Editor Window....................................................................................................................... 407
Figure 212. Editor Popup Menu ............................................................................................................... 408
Figure 213. I2C Exerciser Editor Window Layout ....................................................................................409
ix
Figure 214. Editor File Menu .................................................................................................................... 410
Figure 215. Editor Edit Menu ...................................................................................................................411
Figure 216. Editor Tool Bar ......................................................................................................................413
Figure 217. Glitch Pattern Editor Window ................................................................................................416
Figure 218. Glitch Injection Trigger Conditions ........................................................................................417
Figure 219. Default Glitch Pattern Setting................................................................................................418
Figure 220. SDA Low Glitch Injected by Data / SDA / Rising-edge Triggering Condition .......................418
Figure 221. SDA Low Glitch Waveform ...................................................................................................419
Figure 222. Glitch Pattern Editor File Menu .............................................................................................420
x
List of Tables
Table 1. Optional Interface Cables ...............................................................................................................7
Table 2. Flying Leads Serial Bus Connector Pin Assignments .................................................................. 91
Table 3. 4-Pin Crimp Cable Pin Assignments ............................................................................................92
Table 4. Summary of available Trigger Components ...............................................................................122
Table 5. Monitor Window Layout ..............................................................................................................134
Table 6. Monitor Tool Bar Functions ........................................................................................................148
Table 7. Debugger Script Keywords......................................................................................................... 156
Table 8. Debugger Error Injection Keywords............................................................................................159
Table 9. Debugger Window Layout ..........................................................................................................162
Table 10. Debugger Tool Bar Functions................................................................................................... 164
Table 11. Programmer Function Descriptions ..........................................................................................168
Table 12. Programmer Read Contents Window Function Descriptions ...................................................169
Table 13. Programmer Window Areas .....................................................................................................172
Table 14. Programmer Tool Bar Functions ..............................................................................................174
Table 15. Configuration Manager Panes..................................................................................................178
Table 16. DLL Components......................................................................................................................204
Table 17. I2C DLL Functions .................................................................................................................... 207
Table 18. List of I
Table 19. Emulation Manager Areas ........................................................................................................251
Table 20. Emulator Tool Bar Functions ....................................................................................................256
Table 21. Emulated Master Tool Bar Functions ....................................................................................... 266
Table 22. Emulated Slave Tool Bar Functions ......................................................................................... 271
Table 23.Test Window Areas....................................................................................................................276
Table 24. Test Tool Bar Functions ...........................................................................................................287
Table 25. Built-In Scripting Functions....................................................................................................... 311
Table 26. Editor Window Areas ................................................................................................................409
Table 27. Editor Tool Bar Icon Descriptions .............................................................................................414
2
C Bus Measurement Parameters ................................................................................219
xi
Introduction
What this User’s Manual Covers
This User’s Manual was designed to make using your CAS-1000-I2C™ analyzer and its software easier
and more efficient. The manual contains easy to navigate tutorials and reference information that are
presented in a logical progression.
The following briefly summarizes each chapter:
Chapter 1: Product Overview
This chapter provides you with an introduction to the I2C bus and SMBus as well as a description of the
CAS-1000-I2C analyzer and software application features.
Chapter 2: Installation
In this chapter you will learn how to install the I2C Exerciser software and the CAS-1000-I2C hardware.
Chapter 3: Getting Started
This chapter introduces you to the basic usage of the CAS-1000-I2C for monitoring and generating bus
traffic, writing debug scripts, and working with EEPROM devices. Although it is possible to explore the
capabilities of the CAS-1000-I2C on your own, working through this chapter will provide you with an
immediate feel for its ease of use and core functionality.
Chapter 4: Connecting to a Target
This chapter provides you with instructions on how to hook up the CAS-1000-I2C to a target board and
describes the initial software settings that you should be aware of to have the CAS-1000-I2C working
properly.
Chapter 5: Bus Traffic Monitor
This chapter describes the features of the Monitor window which is used to collect and analyze traffic
from the target I
2
C bus.
Chapter 6: Interactive Debugger
This chapter describes the features of the Debugger which is used to manually generate traffic and
interact with the target I
2
C bus.
Chapter 7: Serial EEPROM Programmer
This chapter describes the features of the Programmer which is used to read and write the content of
EEPROM memory devices on the target I
2
C bus.
Introduction
xiii
Chapter 8: Configuration and Preferences
This chapter describes all of the various project options and settings that can be found in the
Configuration Manager and Preferences dialogs.
Chapter 9: Third Party Application Interface
This chapter provides a reference on all of the function calls available for use in third party software
applications that control the CAS-1000-I2C analyzer through the provided dynamic link library (DLL).
Chapter 10: I2C Device Emulator
This chapter describes the features of the Emulator which is used to emulate master and slave devices
on the target I
2
C bus.
Chapter 11: Script-Driven Bus Tester
This chapter describes the features of the Test tool which is used to execute test scripts that perform a
sequence of measurements and tests of the target I
2
C bus.
Chapter 12: Parameters Scope
This chapter describes the features of the Parameters Scope which is used to measure the electrical and
timing characteristics of the target I
2
C bus.
Chapter 13: Scripting Language
This chapter provides a reference on the usage and syntax elements of the I2C Exerciser’s scripting
language which is used in automated bus testing and device emulation.
Chapter 14: Glitch Pattern Injection
This chapter describes the features of the Glitch Pattern Injection which is used to inject glitches into the
target I
2
C bus.
Appendix A: CAS-1000-I2C Hardware Reference
This appendix presents a table comparing the features in different versions of Corelis bus analyzers as
well as the physical and electrical specifications for the CAS-1000-I2C hardware.
xiv
Introduction
Chapter 1
Product Overview
CAS-1000-I2C/E™ Bus Analyzer and I2C Exerciser product overview
2
Introduction to I
The I2C bus was developed by Philips for basic communication between devices. It has since evolved,
increasing in performance and finding many new applications including data transfer and system-level
command-and-control.
As shown in Figure 1, the physical I
ground. The two active signals on the bus consist of a serial data line (SDA) and a serial clock line (SCL),
each requiring a system voltage reference through a pull-up resistor. Every device connected to the bus
is software addressable by a unique address and masters can operate as master-transmitters or as
master-receivers. The I
arbitration to avoid data corruption if two or more masters simultaneously initiate data transfer. Serial, 8bit oriented bidirectional data transfers can be made at up to 100 Kbit/s in the Standard mode or up to
400 Kbit/s in the Fast mode.
C and SMBus
2
C bus consists of two bidirectional open-drain signals and a common
2
C bus supports a multi-master bus methodology including collision detection and
Figure 1. I2C Bus Topology
The System Management Bus, or SMBus, was defined by Intel® Corporation in 1995 and is based on the
2
C bus architecture. It is used in personal computers and servers for low-speed system management
I
communications.
SMBus is a two-wire interface through which simple system and power management related chips can
communicate with the rest of the system. A system using SMBus as a control bus for these system and
power management related tasks pass messages to and from devices by addressed transfers, enabling
moderate transfer rates using minimal board resources. With System Management Bus, for example, a
Product Overview
1
device can provide manufacturer information, tell the system what its model/part number is, save its state
for a suspend event, report different types of errors, accept control parameters, and return its status. The
SMBus may share the same host device and physical bus with standard I
2
C components. Intel originally
conceived the SMBus as the communication bus to accommodate Smart Batteries and other system and
power management components.
Introduction to the CAS-1000-I2C™
The Corelis CAS-1000-I2C is an I2C-bus/SMBus analyzer, exerciser, programmer, and tester. This
advanced instrument is used to:
Monitor and log I
Generate traffic to exercise the bus and communicate with its slave components
Program and read in-system EEPROMs
Emulate I
2
only)
Measure and test bus performance and characteristics (/E version only)
Because of its rich feature set and ease-of-use, the CAS-1000-I2C can be used in a variety of
applications, such as product development, troubleshooting, validation, system integration, production,
and field testing.
The CAS-1000-I2C pod, shown in Figure 2, connects to the PC via a high-speed USB 2.0 port and can
operate either with the provided I2C Exerciser software application, or using the included API of C/C++
library function calls from third party software applications such as National Instruments’ LabWindows/CVI
and LabVIEW, or custom user-developed software.
2
C bus traffic in real-time
C master and slave devices that are not yet physically connected to the bus (/E version
The CAS-1000-I2C/E also includes a JTAG controller that, when used with the optional Corelis
ScanExpress software, can perform boundary-scan interconnect testing and in-system programming of
flash memories and CPLDs. This JTAG testing capability is complementary to the I
2
C bus testing features
of the CAS-1000-I2C/E and greatly enhances target visibility control and testing access.
Figure 2. Illustration of the CAS-1000-I2C
2
Product Overview
Software Toolset
Monitor
Using the Monitor tool, the CAS-1000-I2C listens and records all I
2
C bus traffic while displaying it as
both state and timing information. Transactions can be examined and stored to files and later
retrieved for review. Monitor features include message filtering, symbolic translation of numeric
values, and event triggering. The CAS-1000-I2C continually verifies compliance to the bus protocol
and flags errors when it detects a protocol violation. Concurrent with the bus transaction state listings,
a timing display for both the SCL and SDA signals is depicted showing the edge transition history.
Debugger
Using the Debugger tool, the CAS-1000-I2C can be utilized to send and receive individual messages
on the I
2
C bus. Looping is supported for repeating I/O patterns to facilitate external signal
observation. Storing and restoring files allows saving of received data for post-analysis and reuse of
previously sent message scripts. A callable API library distributed as a Windows DLL further enables
access to the I
2
C bus from 3rd-party applications outside of the I2C Exerciser GUI.
Programmer
Using the Programmer tool, the CAS-1000-I2C can be utilized to perform high speed programming of
2
I
C-compatible serial EEPROM memory devices, with a user interface similar to the Corelis
ScanExpress Programmer boundary-scan in-system programming product. Devices can be
programmed in-system and at maximum programming speed, which is typically within several
seconds depending on the memory size. The Programmer provides options to Erase, Program,
Verify, and Read target EEPROM memory. The content of the EEPROM memory device can be
saved to a file in a supported file format including Motorola S-Record, Intel Hex, and a hex-text file
format.
Emulator
Using the Emulator tool, the CAS-1000-I2C/E can be configured to emulate a master or slave device
on the target I
2
C bus. The behavior of the emulated device is controlled using a sophisticated
scripting language that has a simplified C-language syntax. When emulating a slave, blocks of data
are defined that will be used in responding to any master transactions. When emulating a master, the
functionality of the Debugger tool is taken to the next level, adding conditional branching and
schedule control that enables a comprehensive bus and target exercising sequence, ranging from
simple target initialization to complex behavioral stimulation, stressing, and evaluation.
Test
Using the Test tool, the scripting features available in the Emulator tool are enhanced with the ability
to measure and compare target I
2
C bus electrical and timing parameters as well as the faculty to
manipulate the GUI elements of the Test window. Scripts run with the Test tool manipulate and
evaluate the behavior of the target bus and make a “go” or “no-go” decision on whether performance
is within a desired specification, reporting back the status and results via the Test window controls.
Parameters Scope
Using the Parameters Scope tool, the CAS-1000-I2C/E can be utilized to quickly measure and return
the basic electrical and timing parameters of the target I
2
C bus without setting up the advanced
scripting functions of the Test tool. It can gather master-specific and slave-specific parameters, such
as signal timing characteristics, and also system-wide parameters, such as bus voltage, pull-up
resistance, and capacitance. Each measurement is compared to maximum and minimum values
loaded from a specification file and the resulting pass or fail status is shown with the measurement.
The Parameters Scope provides the additional ability to display a graph of captured signal edge
transition data and a trigger can be set to capture a particular I
2
C bus signal’s rising or falling edge.
Product Overview
3
Hardware Features
The main hardware features of the CAS-1000-I2C/E are described in the following sections.
I2C Speed Support
The CAS-1000-I2C operates using the Standard/Fast-mode/Fast-mode Plus protocol over its entire
performance range for both monitoring and driving the bus (up to 5 MHz as a master, 1.9 MHz as a
slave). The High-speed mode (Hs-mode) is supported for monitoring only. Additionally, an accelerated
rising slope control feature is included to facilitate the driving of higher capacitance targets at high clock
rates.
USB Port Host Interface
The CAS-1000-I2C uses a high-speed USB 2.0 interface for easy connection to a PC. The host PC
supplies operating power to the unit and the hot-plug feature of the USB standard is fully supported. You
simply plug the CAS-1000-I2C into a PC USB 2.0 socket and it will be automatically detected, configured,
and then ready to go.
A USB 2.0 port on the host computer is required for optimal performance. The CAS-1000-I2C does not
support USB 1.1 ports.
Software Programmable Voltage Levels and Pull-Up Resistors
The I2C bus reference voltage can be programmed as target-driven (Target Supplied mode) through its
own pull-ups or as driven from the CAS-1000-I2C (Analyzer Supplied mode) through instrument pull-ups.
When the CAS-1000-I2C is programmed to source this reference level (for both SCL and SDA signals),
the voltage can be set in 100 mV steps from 0.8V to 5.0V. In this case, the target pull-ups should be
removed to prevent contention with the analyzer.
In addition, for the Analyzer Supplied mode reference voltage, you can select one of a set of pull-up
resistors with the same value for both bus signals. The resistor values can be set from about 250 to 50K
ohms in varying increments.
The TTL output signal level of the set of discrete I/O and trigger lines is programmable from 1.25V to 3.3V
in steps of 50 mV.
Furthermore, sensed bus signal high and low threshold levels can each be adjusted, supporting the bus
hysteresis requirement. Default software-determined values are provided automatically with user override
capability.
4
Product Overview
Programmable Clock Rate
The CAS-1000-I2C clock rate is software programmable when it drives the bus. It supports
Standard-mode, Fast-mode, and Fast-mode Plus transfers up to 5 Mbits/sec and many intermediate
rates. The target bus conditions, especially pull-up values and parasitic capacitance, can limit the upper
rate of operation. The ability of the analyzer to track the signals is also affected by receive threshold
voltage settings. The user should be aware of the analog behavior of the bus signals, especially slow risetimes, and their relationship to transitions at higher clock rates.
This clock rate setting does not apply to target master clocks which are not driven but are only monitored
by the CAS-1000-I2C. In such cases, the rate is automatically tracked up to 5 MHz.
When the CAS-1000-I2C drives the bus, it also automatically synchronizes the clock signal in compliance
with the I
2
C specification’s multi-master requirements.
Discrete I/O Signals
Two programmable general purpose lines can be operated under PC host software control and are
available to stimulate the target system or sense target conditions in coordination with its testing. Each
line is programmable as an input, a TTL output, or an open-drain output. The voltage level of these
signals is programmable independent of I
displayed in the trace listing while collecting bus traffic and they can contribute to trigger conditions.
Each one of the two discrete lines can source 12 mA and can be used as a limited programmable power
source to a target when configured as a TTL output.
2
C bus levels. The state of these signals is monitored and
Power Requirements
The CAS-1000-I2C receives the standard power available from the host USB port.
Built-in Self-Test
The CAS-1000-I2C has a built-in self-test capability. Logic is provided to loop back bus signals from the
target connector. This enables a basic go/no-go confidence testing of its operation. It is launched from the
Tools menu and requires that there be no external target attached.
Calibration
Since the electrical characteristics of each individual CAS-1000-I2C and host USB bus can be slightly
different, the CAS-1000-I2C includes a calibration feature to optimize output when using it to supply pullup voltage to a target bus. Calibration also adjusts the output voltage of the two discrete I/O signals.
JTAG Testing and In-System Programming
The CAS-1000-I2C includes an IEEE-1149.1 JTAG Test Access Port (TAP). This port can be used to
perform boundary-scan testing and in-system programming of flash, EEPROMs and CPLDs on the target
system. The optional Corelis ScanExpress software is needed to enable the boundary-scan testing and
in-system programming feature. This feature is mutually exclusive to the I
be put into the TAP mode.
Product Overview
2
C functionality and requires it to
5
Host Computer Requirements
I2C Exerciser is a 32-bit Microsoft Windows®-based application which controls the CAS-1000-I2C. The
PC on which it will be installed should meet the following minimum requirements:
One available USB 2.0 Port
Windows® XP (SP2), Windows® Vista, Windows® 7, or Windows® 8
3.2 GHz Pentium® 4 Processor (or equivalent)
1 GB of RAM
600 MB of Free Hard Disk Space (2 GB or more for continuous logging of trace data)
CD-ROM Drive
6
Product Overview
Chapter 2
Installation
Installing the I2C Exerciser software and the CAS-1000-I2C hardware
Prior to installation, please verify that the following I2C Exerciser software and CAS-1000-I2C hardware
materials are present and free from visible damage or defects. If anything appears to be missing or
damaged, please contact Corelis immediately.
The CAS-1000-I2C product consists of the following components:
- CAS-1000-I2C Hardware
- 6’ USB 2.0 Cable
- 12” I
- Corelis I2C Bus Analyzer, Exerciser, Programmer, and Tester CD-ROM containing the I2C
Your application may require additional optional interface cables. Table 1 lists the optional target interface
cables available from Corelis.
2
C Target Interface Cable consisting of flying leads with test clips (Part# 15438-2)
Exerciser application, support software and example target test files
Cable Description Corelis Part Number
24” I2C Target Interface Flying Leads with Test Clips 15438-3
6” I2C Target Interface 4-pin Crimp Connector 15431-1
12” I2C Target Interface 4-pin Crimp Connector 15431-2
24” I2C Target Interface 4-pin Crimp Connector 15431-3
Table 1. Optional Interface Cables
Installation
7
Installing the I2C Exerciser Application Software
You must first install the I2C Exerciser application software, and then connect the CAS-1000-I2C
controller. The application software contains the driver for the CAS-1000-I2C.
The CAS-1000-I2C controller is a hot-pluggable USB device. However, you should not plug in or unplug
the CAS-1000-I2C while the I2C Exerciser application is running. The CAS-1000-I2C CD-ROM contains
the installation program. Windows will automatically recognize and configure the CAS-1000-I2C the first
time it is detected in your system. Administrator rights are required to install the software on Windows XP.
If the I2C Exerciser is already installed on your system, skip this chapter and proceed to chapters 3
and 4.
To install the software:
Close any Windows applications that are currently running.
Disable any memory resident virus checking software. The software may interfere with the installation
process.
Insert the Corelis I2C Exerciser CD-ROM into your CD drive. The installation program should start
automatically and display the Welcome to the Installation Wizard screen as shown in Figure 3.
Figure 3. I2C Exerciser Installation Wizard
8
Installation
If the installation program does not automatically begin, go to the Windows Start Menu and select Start,
then Run. The Run dialog box will appear as shown in Figure 4.
Type “[D]:\setup.exe” where [D] is the CD-ROM drive letter.
Click on the OK button to run the installation program.
Figure 4. Windows Run Dialog
Click on the Next button. The License Agreement screen shown in Figure 5 will be displayed.
Installation
Figure 5. License Agreement Screen
9
Review the entire agreement, and if you agree, select I accept the terms of the license agreement, and
then click on the Next button. The Customer Registration screen shown in Figure 6 will then be
displayed.
Figure 6. Customer Registration Screen
Type in or change the Full Name and Organization as needed, then click on the Next button. The
Destination Folder screen shown in Figure 7 will be displayed.
10
Installation
Accept the default installation folder, or customize your installation by selecting the Change button.
It is strongly recommended that the application be installed in the default folder.
Figure 7. Destination Folder Screen
Click on the Next button, and the Select Program Folder screen shown in Figure 8 will be displayed.
Installation
11
Select Anyone who uses this computer or Only for me.
By default, the installer will place a shortcut icon for the I2C Exerciser on your desktop. If you do not wish
this shortcut to be created, uncheck the checkbox on this screen.
Figure 8. Select Program Folder Screen
Click on the Next button, and the Completing the Installation Wizard screen shown in Figure 9 will be
displayed.
12
Installation
To change any installation parameters, click on the Back button. Otherwise, click on the Next button and
the installation process will begin.
Figure 9. Completing the Installation Wizard Screen
The installer copies the program files to the specified folder and support files to the Windows system
folders. In addition, the installer creates a Windows Start Menu group named I2C Exerciser.
Installation
13
If you are running Windows 7 or Vista, the software installation may be interrupted by the operating
system by displaying warning pop-up windows as shown in Figure 10. If this occurs, click on the Install
this driver software anyway button to safely ignore the warnings and proceed with the installation.
Figure 10. Windows 7 Security Warning Pop-up Window
If you are running Windows XP, the software installation may be interrupted by the operating system by
displaying warning pop-up windows as shown in Figure 11. If this occurs, click on the Continue Anyway
button to safely ignore the warnings and proceed with the installation.
14
Figure 11. Windows XP Logo Test Warning Pop-up Window
Installation
The warning pop up windows may be hidden behind the installation window. If this happens, the
installation progress bar will stop updating and the installation may appear to be hung. Bring the
warning pop up windows to the foreground by clicking on the Software Installation button on the
Windows task bar as shown in Figure 12. Then click on the Continue Anyway button to safely ignore
the warnings and proceed with the installation.
Installation
Figure 12. Software Installation Button on the Windows XP Task Bar
15
The Installation Completed screen shown in Figure 13 will appear to indicate that the installation is
complete. Click on the Finish button to exit from the installation program.
16
Figure 13. Installation Completed Screen
Installation
CAS-1000-I2C/E Hardware Installation
The CAS-1000-I2C controller is a hot-plug USB device. You must first install the I2C Exerciser software
before installing the CAS-1000-I2C controller. Drivers for the CAS-1000-I2C controller are installed with
the I2C Exerciser software and not installing the software and drivers first may result in improper unit
configuration and operation.
Installation Steps
1. You should have already installed the I2C Exerciser at this point. If not, please do so before
continuing with hardware installation.
2. Connect a USB 2.0 compatible cable from the CAS-1000-I2C USB 2.0 connector to any available
USB 2.0 connector on your PC.
3. If you are running Windows XP, the Found New Hardware Wizard dialog box should automatically
appear as shown in Figure 14.
Figure 14. Found New Hardware Wizard - Welcome Screen (Windows XP)
4. Click on No, not this time and click on the Next button.
Installation
17
5. The dialog shown in Figure 15 will pop up. Click on Install the software automatically
(Recommended) and click on the Next button.
Figure 15. Found New Hardware Wizard - Install Options (Windows XP)
18
Installation
6. The Hardware Wizard will attempt to locate the driver that was installed with the I2C Exerciser
software. Under Windows XP, a warning dialog box will pop up as shown in Figure 16. You can safely
ignore the warning and continue the installation process by pressing the Continue Anyway button.
Figure 16. Windows XP Logo Test Warning Pop-up Window
Installation
19
7. After the necessary files are copied to the system, the dialog box shown in Figure 17 will appear
indicating that the driver has been successfully installed.
Figure 17. Found New Hardware Wizard – Installation Complete (Windows XP)
20
Installation
8. Click on the Finish button to close the Hardware Wizard dialog box.
9. Another Found New Hardware Wizard should appear again. Repeat steps 3 to 8.
10. The installation of the driver is now complete and Windows will proceed to detect and configure the
CAS-1000-I2C Verify that the CAS-1000-I2C was correctly detected by checking for its entry in the
Windows Device Manager. To open the Device Manager, right-click on the My Computer icon on
the desktop and then select Properties from the pop-up menu. Click on the Hardware tab and then
click on the Device Manager button. An entry named Corelis CAS-1000-I2C - 04A1 should be listed
in the Universal Serial Bus controllers section as shown in Figure 18.
Figure 18. Windows Device Manager (Windows XP)
11. Plug the RJ45 connector end of the target cable into the CAS-1000-I2C socket labeled Serial Bus
and the other end of the cable can be connected to the target I
2
C bus signals. The target cables and
pinouts are detailed in the Connecting to a Target chapter.
Congratulations! You have now successfully installed the CAS-1000-I2C and drivers on your computer
and it is ready to be used. We recommend that you preserve the original packing material for future
shipment or storage of the CAS-1000-I2C.
Installation
21
22
Installation
Chapter 3
Getting Started
I2C Exerciser operation overview and tutorial
Overview
This chapter will quickly introduce you to the basic usage of the Corelis I2C Exerciser tool for viewing bus
traffic via the CAS-1000-I2C. Although it is possible to explore the capabilities of this system on your own,
working through this chapter is intended to give an immediate feel and appreciation for its ease of use
and core functionality. After you have become familiar with the program, you can go back and explore the
rich variety of additional options, tools, and methods available by browsing through the menu system,
reading the remainder of this manual, or going through the on-line help.
The material in this chapter is divided into two parts. Most of what you will do while working through the
chapter will involve using the demo mode feature of I2C Exerciser with the Monitor window to look at
various bus tracing capabilities. The second part of the chapter will briefly take you through using the live
mode of I2C Exerciser in order to familiarize you with the Debugger window that is not available in the
demo mode.
Calibration Note
If you are going through these tutorials for the first time with a new installation of I2C Exerciser and you
have a CAS-1000-I2C connected, then you may be prompted to calibrate the CAS-1000-I2C. The
calibration feature fine-tunes the electrical outputs of the CAS-1000-I2C for use when it is providing the
voltage source for an attached target bus.
Feel free to skip the process during these tutorials by clicking on the No button if prompted to perform
calibration. However, if you wish to get the calibration out of the way, you may allow it to proceed by
following the on-screen instructions—it should only take a minute or two and need only be completed
once per the computer being connected to. For details on the calibration feature, refer to the Calibration
section in the Configuration and Preferences chapter.
Tutorial – Using Demo Mode
The steps in the following tutorial will guide you through basic CAS-1000-I2C usage once you have
successfully installed the software and, optionally, the hardware. This will not require a live target or even
an attached CAS-1000-I2C controller.
The demo mode feature of I2C Exerciser allows the user to quickly observe and become familiar with the
basic bus tracing features. This mode creates simulated traffic for display in the Monitor window, imitating
a connection to virtual targets on an I
understanding the information provided in the Monitor window, including both the trace list and timing
display. You will learn how to collect I
through the data, and utilize various options and features.
Getting Started
2
C bus. The steps outlined in the demo tutorial focus mainly on
2
C bus traffic, view it in the trace list and timing display, navigate
23
Step 1 – Start I2C Exerciser
Start the I2C Exerciser application by opening the Windows Start menu, clicking on Programs (or All
Programs), then clicking on the I2C Exerciser program group, and finally clicking on the I2C Exerciser
entry. A splash screen will be displayed for a few seconds, and then the main I2C Exerciser window will
appear with the Monitor window active. By default, the program will try to detect if the CAS-1000-I2C is
connected and will enter Live Data mode if the controller is found. If the CAS-1000-I2C is not attached to
the host PC, you will get the warning message shown in Figure 19 indicating that the controller was not
detected and the program will automatically start in Demo Mode. If the warning appears, click on the OK
button to close it.
Figure 19. Initial I2C Exerciser Warning Message when CAS-1000-I2C is Not Initially Connected
24
Getting Started
Step 2 – Enable Demo mode
Click on the Tools menu and verify that the Demo Mode menu item has a check mark next to it as shown
below in Figure 20. This indicates that the program is in Demo Mode. If the CAS-1000-I2C was connected
to the PC when you started I2C Exerciser, you will have to select this menu item to force the program into
Demo Mode. You can also verify that the program is in Demo Mode by observing the programs status bar
in the lower right corner of the main window as shown in Figure 21. The leftmost indicator will either
contain the bold red text DEMO or the plain text LIVE.
Getting Started
Figure 20. Tools Menu Demo Mode Selection
Figure 21. Status Bar Indicating Demo Mode
25
Step 3 – Begin the Monitor Window Simulated Bus Activity
Click on the Run Single tool bar button (represented by a green arrow) as shown in Figure 22 to begin
Monitor data collection of the simulated bus activity.
Figure 22. Begin Monitor Data Collection
When the program is in Demo Mode and a Run command is invoked, an informational pop-up window as
shown in Figure 23 will appear to remind you that the program is currently in Demo Mode. Click on the
OK button to proceed.
Figure 23. Demo Mode Reminder Pop-up Window
26
Getting Started
When traffic collection begins, the Run Status tab on the Monitor Tools window will be displayed to
show progress information as the trace buffer fills with simulated traffic. You may move or resize this
window at any time to obtain a better view of the trace list lines and timing display as shown in Figure 24.
Step-by-step color-highlighted progress milestones are provided in the Run Status tab. This tab also
displays the number of bus transactions collected so far and a progress bar indicating what percentage of
the trace buffer has been filled. After the buffer is filled, the Run Status tab will indicate Data collected
successfully and the Close will be enabled, allowing the user to close the window.
Getting Started
Figure 24. Run Status Tab
27
Step 4 – Close the Monitor Tools Window
Click on the Monitor Tools window close button and the window will close allowing a full view of the
Monitor window which shows a portion of the trace buffer content. If a user-specified trigger is
encountered while acquiring bus traffic, the trace list will automatically be centered on the transaction that
satisfied the trigger condition. The Demo Mode data has a matching trigger condition on line 45 as can be
seen in Figure 25.
28
Figure 25. Monitor Window Centered on Trigger Line
Getting Started
Step 5 – View the Trace Data
The Monitor window allows the user to examine the captured data in the trace buffer. A vertical scroll bar
is available on the right edge of the screen for standard positioning of the lines in addition to use of the
page-up and page-down keys. Scrolling the display up will show older entries with lower line numbers.
Scrolling the display down will show newer entries with higher line numbers. The oldest entry will be on
line one and the newest entry will be on the last line in the trace list. Each bus message is displayed as
multiple lines in the trace listing and consists of a master address read/write cycle, followed by one or
more data write (SDA line driven by a master toward a slave) or data read (SDA driven by a slave
towards a master) cycles.
Right-clicking anywhere in the Monitor window trace list will display the pop-up menu shown in Figure 26.
This menu provides easy access to navigation, command, and configuration functions. All of these
commands can also be accessed via either tool bar buttons or the regular menu system.
Getting Started
Figure 26. Monitor Window Right-Click Pop-up Menu
29
While scrolling around the trace list data, you will notice that some lines are highlighted with special
background colors and the Marker column may contain various indications such as Trigger, Cursor A,
Cursor B, or Tagged. These markers are used to indicate special transactions of interest and will be
described in more detail later. There are navigation tool bar buttons as well as menu equivalents to
immediately jump to any of these special types of lines or to quickly jump directly to the beginning or end
of the trace buffer.
Single-clicking on a trace list line will highlight that selected line. This highlighting helps to identify all of
the transaction information across the columns of the trace listing. The Find tool can also populate their
required transaction fields automatically by using the data from the currently selected line.
Lines in the trace listing can be arbitrarily flagged as lines of interest. Such lines are denoted by blue text
as well as the Tagged indicator in the Marker column. This flag is set or unset by double-clicking on the
trace list line. The Find tool, discussed later in this tutorial, can also use this tagging mechanism to
identify transactions throughout the trace buffer that satisfied certain specified criteria. Double-click on
any untagged line and observe its text color change and Marker column change to Tagged. Double-click
on the same line again and it will return to untagged status.
Right-click in the trace list area of the Monitor window and select the Go to Trigger pop-up menu entry as
shown in Figure 26. This will cause the trace list and timing display to reposition to the Trigger line as
shown in Figure 27. The Trigger line can be seen on line 45 in the trace list which is identified by a red
background and it is also indicated at the top of the timing display by a red flag (with the symbol “T”). I
2
bus transaction characteristics that constitute a Trigger are configured by the user prior to starting data
collection. The CAS-1000-I2C searches for the user-specified set of conditions while collecting trace data
in order to mark the Trigger line and place it in a specific position in the buffer.
C
30
Figure 27. Monitor Window Trace List Positioned on Trigger Line
Getting Started
To access the Trigger setup screen, right-click in the trace list area and select the Trigger… entry from
the pop-up menu as shown in Figure 28. The Trigger dialog will appear as shown in Figure 29.
Figure 28. Monitor Window Right-Click Pop-up Menu Selecting Trigger Settings
The Trigger dialog allows the user to specify particular address, data value, and other miscellaneous
event criteria which correspond to the bus transaction of interest.
Getting Started
31
In Demo mode, the trigger condition is fixed internally and this screen is non-functional. Click on the
Close button to close this dialog.
32
Figure 29. Configuration Manager Trigger Setup Screen
Getting Started
Transaction Line Columns
The Monitor window trace list column headings are shown in Figure 30. A description of each column is
provided below.
Figure 30. Monitor Window Trace List Column Headings
Line – Displays a sequential unique number for each bus transaction.
Marker – Identifies special lines such as the Trigger, Cursor A, Cursor B, or Tagged.
Type – Identifies the transaction as either an Address or Data cycle.
Location – Indicates the device involved in the current transaction as being either a target device on the
bus or the CAS-1000-I2C analyzer. For address transactions, “Analyzer” means the analyzer is the
master (debugger or emulated master), while “Target” means a UUT master is driving. For data
transactions (write toward the slave, read from the slave), “Analyzer” means the analyzer is an emulated
slave, while “Target” means a live UUT slave is involved. This localizes the source of address cycles and
the source/destination of data cycles as residing in the Analyzer or the Target.
Addr – Displays the bus address of the related message. This column can be displayed in hexadecimal,
decimal, or binary format. The display format is shown in parenthesis in the column heading.
AddrType – Identifies the address type as the protocol defined 7-bit, 10-bit, or Hs-mode. Note that for
7-bit addresses displayed in hex format, I2C Exerciser can present a given address value in one of two
formats based on the users preference. In 7F format mode, addresses are displayed with the seven
address bits shown as right-justified in the hex byte value with the MSB always being zero. In FE format
mode, the addresses are displayed with the seven address bits shown as left-justified in the hex byte
value with the LSB always being zero. For example, given a binary address of 0011010, the hex
representation in 7F format would be 1A, while in FE format it would be 34. Both of these formats are
encountered in the I
The currently active mode is reflected in the lower corner of the I2C Exerciser status bar (AddrFormat FE
or AddrFormat 7F) as shown in Figure 31. The AddrFormat can be configured on the Formats tab of
the Preferences dialog.
2
C world, and the I2C Exerciser application is flexible enough to use either format.
Getting Started
Figure 31. I2C Exerciser Status Bar
33
R/W – Displays the read/write direction of data flow relative to the master (R = read from a slave, W =
write toward a slave).
NAK – Blank for normal ACK responses, or will indicate NAK when the cycle is not acknowledged.
Error – Blank for normal bus protocol transactions, or will indicate Error if the CAS-1000-I2C detected a
protocol violation. If an error was detected, the user can click on the Error text and a pop-up window will
appear describing the cause of error. Observe line 85 which is an example of such an entry.
KHz – Displays the best estimate of the average clock rate for the transaction in units of Kilohertz.
I/O 1 – Displays the current state of discrete I/O line 1 (regardless of whether the discrete is configured as
an input or output).
I/O 2 – Displays the current state of discrete I/O line 2 (regardless of whether the discrete is configured as
an input or output).
Data Byte – Displays the byte value conveyed by this transaction to or from a slave device. This column
can be displayed in hexadecimal, decimal, or binary format. The current display format is shown in
parenthesis in the column heading.
Time – Displays the timestamp assigned to the beginning time of each transaction. Supported time
display units are nanoseconds, microseconds, milliseconds, and seconds. The current time unit format is
shown in parenthesis in the column heading.
The Monitor window tool bar shown in Figure 32 provides buttons for quickly repositioning the trace list
display to various points of interest. You can quickly jump to the trigger, to the next tagged row, to the
beginning or end of the buffer, or to Cursor A or Cursor B. You can also quickly jump to these positions in
the trace list using the right-click menu previously illustrated.
Click on the Go to Start tool bar button as shown in Figure 32 to bring the trace list view to the first
entries in the trace listing. This will also cause the first line in the trace list to be highlighted as shown in
Figure 33.
Figure 32. Go to Start Tool Bar Button
Observe that some address columns contain symbolic values such as PLL and ADC, and some data
columns contain symbolic values such as FAULT, WARNING, and CHANSEL. The user can define
symbols for both address and data to enhance device-specific readability.
34
Getting Started
Figure 33. Monitor Window Trace List Showing Symbolic Address and Data Entries
Getting Started
35
Using the method previously described, right-click in the trace list area of the Monitor window and select
the Symbols… pop-up menu entry. This will cause the Configuration Manager Symbols definition
screen to be displayed as shown in Figure 34. This screen allows the user to add new symbol definition
rules, and to edit or remove existing symbol definition rules.
36
Figure 34. Configuration Manager Symbols Definition Screen
Getting Started
Click on the Add button and the Symbol Definition dialog shown in Figure 35 will appear. In the Symbol
field, type DAC which is an acronym for Digital-to-Analog Converter. In the Addr field, type 18. This will
cause the string DAC to be displayed in the address column for any trace list entries with a 7-bit hex
address of 18. Click on the OK button to accept the new symbol definition rule.
Figure 35. Symbol Definition Dialog
Getting Started
37
The Configuration Manager Symbols screen will now contain the newly added DAC entry as shown in
Figure 36. Click on the Close button to close the Configuration Manager Symbols screen.
38
Figure 36. Configuration Manager Symbols Definition Screen with DAC Symbol
Getting Started
With the trace list still showing the beginning of the Demo data, you will now see that lines 17 through 34
are now all displaying the symbol DAC in the address column instead of the raw address value of 18.
Lines 46 through 50, lines 78 through 82, and lines 94 through 98 are similarly affected. The trace list
display with the new symbol entry is shown in Figure 37.
Figure 37. Monitor Window Trace List Showing New DAC Symbolic Address Entries
Getting Started
39
Right-clicking on the column headings of either the Addr or Data Byte column allows the user to toggle
the symbolic translation on and off. Additionally, the pop-up menu allows selection of the numeric display
format to either hexadecimal, binary, or decimal. These settings work independently for the Addr and
Data Byte columns. Right-click on the Data Byte column heading and select the Disable Symbols menu
entry as shown in Figure 38. Observe that symbols are no longer being displayed in the Data Byte
column as shown in Figure 39.
Figure 38. Monitor Window Trace List Data Byte Column Right-Click Pop-up Menu
40
Getting Started
Figure 39. Monitor Window Trace List Data Column with Symbols Disabled
Getting Started
41
Right-click on the Data Byte column heading and select the Binary format menu entry as shown in
Figure 40. Observe that the Data Byte column is now displaying values in binary format as shown in
Figure 41.
Figure 40. Monitor Window Trace List Data Byte Column Right-Click Pop-up Menu
42
Figure 41. Monitor Window Trace List Data Column with Data Bytes in Binary Format
Getting Started
Using the method just described, re-enable symbol translation and change the display format back to
hexadecimal.
The Data Byte column heading pop-up menu also allows the toggling of Compact Mode. This special
mode displays all of the data bytes for each message on a single line in the trace list. Enable Compact
Mode by right-clicking on the Data Byte column and select the Compact Mode entry as shown in Figure
42.
Figure 42. Monitor Window Trace List Data Byte Column Right-Click Pop-up Menu
Getting Started
43
The trace list data will be reformatted as shown in Figure 43. Some messages may contain more data
bytes than will fit on the screen. When the display is in Compact Mode, clicking on any data transaction in
the Data Byte column will cause a pop-up Data Bytes window to appear making it possible to view and
scroll through all data in the selected message. Click on line 18 in the Data Byte column and the pop-up
window shown in Figure 44 will appear allowing you to see all of the data bytes in that message which are
not all visible in the Data Byte column. This pop-up window will remain open until you close it and will
continue to update if you click in the Data Byte column for any other data transaction.
44
Figure 43. Monitor Window Trace List in Compact Mode
Getting Started
Figure 44. Monitor Window Trace List in Compact Mode with Data Bytes Pop-up Window
When you have finished viewing the trace list in Compact Mode, close the Data Bytes pop-up window.
Then select the Normal Mode selection from the Data Bytes column heading menu to put the trace list
display back into Normal mode.
Getting Started
45
You can right-click on any column heading and select Hide Column to remove the selected column from
the trace list display. This may be useful when the user is not interested in some of the data columns and
hiding them can reduce screen clutter. Additionally, you can drag and drop column headings to change
the order that the columns are displayed in. Right-click on the I/O 2 column heading and select Hide
Column as shown in Figure 45. Click on the I/O 1 column heading and while holding the mouse button
down, drag the column to just after the Time column heading as shown in Figure 46 and then release the
mouse button.
Figure 45. Monitor Window Trace List I/O 2 Right-Click Pop-up Menu
46
Figure 46. Dragging Monitor Window Trace List I/O 1 Column Heading
Getting Started
After hiding the I/O 2 column and repositioning the I/O 1 column, the Monitor window should now look like
Figure 47.
Getting Started
Figure 47. Monitor Window Trace List with Rearranged I/O Columns
47
If you wish to unhide one or more previously hidden columns or wish to restore the column layout to its
default state, right-click on any column heading and select the Trace Layout menu. The Trace Layout
dialog will appear as shown in Figure 48 showing each column and whether or not it is visible. Click on
the Default Column Layout button to restore the default column settings and then click on the Close
button.
48
Figure 48. Trace Layout Dialog
Getting Started
Timing Display
The lower portion of the Monitor window contains a graphical representation of the I2C bus signal
transitions depicted as a timing diagram similar to a logic analyzer. A picture of the timing display is
shown in Figure 49. It displays the actual state and edge times of the signals as they transitioned on the
bus while conveying transactions.
Figure 49. Monitor Window Timing Display
The bus clock line (SCL) is shown at the bottom of the timing display with the bus data line (SDA)
positioned just above it. This allows the value of the data line to be easily determined as the clock line
rises and falls.
The Bit row displays one of the following letters over each recognized sequence of bus transitions to
indicate what has occurred.
S – A Start/Restart bit occurred indicating a new message is beginning
P – A Stop bit occurred indicating the end of a message
R – Master indication that this message is performing a read operation
W – Master indication that this message is performing a write operation
0 – A value of 0 is being conveyed in either an address or data transaction
1 – A value of 1 is being conveyed in either an address or data transaction
A – The current address or data transaction is being acknowledged (ACK)
N – The current address or data transaction is being not-acknowledged (NAK)
The Field row provides a higher level decoding of bus transition groupings and identifies either an
address transaction, a data transaction, or when the bus has transitioned to an idle state.
The vertical orange dotted-line in the center of the timing display will identify the first timing edge that
corresponds to either the currently highlighted line in the trace list or to the entry at the top of the trace
list. This setting can be configured on the Monitor Options tab of the Tools | Preferences menu entry.
The default setting is to have the timing display track the currently highlighted trace line. Click on different
trace list transactions and observe how the timing display updates to show the newly selected
transactions.
You can navigate in the timing display area itself by jumping forward or backward between lines via the
provided arrow buttons or enter the desired trace line number in the edit field and press return. The
Monitor trace list will track the timing display according to the currently active display locking preference.
You can also use the horizontal scroll bar underneath the timing display to position the display without
affecting the position of the trace listing.
Getting Started
49
Notice the colored flags that are displayed just above the top Field row of the timing display. These flags
indicate the locations of the Trigger marker and the Cursor markers. A cursor is a special marker that can
be positioned in the timing display at various points of interest to allow time measurements between any
two points. There are two cursors available: Cursor A is identified by its green background and Cursor B
is identified by its magenta background by default. These colors can be configured on the Monitor
Colors tab of the Tools | Preferences menu entry.
If the cursors are not in the currently visible range of timing information, the Field row will contain a small
green (Cursor A) or magenta (Cursor B) triangle on either the extreme left or right side of the row to
indicate the cursor is located before or after the visible range of timing information. You can click on these
markers and drag them left or right to move the corresponding cursor into the visible range of timing
information. When in the visible range, the cursors are represented by small colored boxes with a vertical
line that extends below them through the timing display. Similarly, a trigger is represented by a red
vertical line and a small red box just above the Field row when in the visible range and represented by a
red triangle above the Field row when out of the visible range.
Right-click in the trace list area of the Monitor window and select the Go to Cursor A pop-up menu entry.
This will cause the trace list and timing display to reposition to the Cursor A line as shown in Figure 50.
The Cursor A line can be seen on line 16 in the trace list. Both the trace list line and vertical marker in
the timing display for Cursor A are colored green to help distinguish them from other display elements.
50
Figure 50. Monitor Window Trace List Positioned on Cursor A Line
Getting Started
Now right-click in the trace list area of the Monitor window and select the Go to Cursor B pop-up menu
entry. This will cause the trace list and timing display to reposition to the Cursor B line as shown in Figure
51. The Cursor B line can be seen on line 100 in the trace list. Both the trace list line and vertical marker
in the timing display are colored magenta to help distinguish them from other display elements. Note that
the timing display’s Line field is displaying 100 and that the magenta colored vertical marker for Cursor B
is positioned on the first edge of this data word.
Figure 51. Monitor Window Trace List Positioned on Cursor B Line
The zoom function focuses around the center of the display. Clicking on either the - or + zoom buttons in
the Scale area will change the time scale and cause the display to zoom out or zoom in allowing you to
see less detail but more edges or more detail but fewer edges. You can also right-click anywhere in the
timing display and select Zoom-in or Zoom-out from the pop-up menu to change the zoom level. If you
zoom out far enough in the timing display, you can see all of the timing edges in the entire trace buffer.
The Auto-Fit option when checked will automatically adjust the time scale so that one full transaction is
visible on the right side of the center orange marker line.
With the timing display still showing the timing edges beginning at line 100 as shown in Figure 51, click on
the + zoom button in the scale area. The timing display will zoom in as shown in Figure 52.
Getting Started
51
Notice that the time scale has been reduced from 50µs/div to 20µs/div and that the edges appear much
larger now revealing more detail.
Figure 52. Monitor Window Timing Display Showing Edges Zoomed in at Line 100
52
Getting Started
The Interval A to B field always displays the calculated time difference between the position of Cursor A
and Cursor B. Reposition Cursor A by clicking on the small green triangle on the left side of the Field row
and, while holding the mouse button, down drag it over the last edge of the previous transaction as shown
in Figure 53. Notice that while you are dragging the Cursor, a tool tip follows the cursor and constantly
updates to show you the current absolute time of the current cursor position and the difference in time
between Cursors A and B. Once Cursor A is positioned over the last edge of the previous transaction,
release the mouse button to place Cursor A there. The Interval A to B field now displays the difference in
time between Cursor A and Cursor B which in this case is measuring the gap in time between the end of
the transaction on trace line 99 and the start of the transaction on trace line 100.
Figure 53. Monitor Window Timing Display Measuring the Time Between Cursors A & B
Getting Started
53
Step 6 – Find Operations
Push the Go to Start tool bar button as shown in Figure 54 to bring the trace list view to the first entries in
the trace listing. This will also cause the first line in the trace list to be highlighted. The Find function will
now search for entries starting with the first entry all the way to the end of the trace buffer contents.
Figure 54. Go to Start Tool Bar Button
54
Getting Started
Click on the Find tool bar button as shown in Figure 55 below. It will bring up the Find dialog shown in
Figure 56.
Figure 55. Find Tool Bar Button
Getting Started
Figure 56. Find Dialog
55
The Less button compacts this dialog to display only the four buttons on top to minimize any obscuring of
the Monitor window. This is useful when you have configured the search parameters and want to repeat
the same search query many times. While compacted, this button changes to More enabling the user to
force the dialog back to its expanded format. The Tag All button launches a search throughout the trace
buffer for the specified search criteria and will tag all lines which match. After this type of search is
completed, you can use the Go to Tagged Row tool bar button on the Monitor window to easily locate
and step through all of these lines. The Find Next button simply moves the Monitor trace list to the next
found line matching the search criteria. This action can be repeated to locate all matching lines, but
without tagging them. If the end of the buffer if reached, the search will wrap and continue at the start of
the trace buffer.
The various fields are intuitive for defining search criteria and allow searching over a wide range of
conditions from very specific to entire classes of trace lines. The mask feature allows enabling/disabling
individual bits when looking for a single-byte data pattern. The Byte Position indicates which data byte in
a message is to be considered. The Width field may not be modified and is locked at one byte for search
data values.
When the user clicks on the Load From Selected Monitor Trace Line button, the characteristics of the
currently selected line in the trace buffer are used to populate the Find dialog. The user can then tweak
any needed changes to the search criteria fields. This facilitates searching for the same or similar lines
throughout the trace buffer with a minimal amount of manual data entry. Each field’s pull-down will supply
common selections, previously entered values, or defined symbols, as appropriate. Otherwise, type in the
desired values.
56
Getting Started
Go to the start of the trace list using the Go to Start tool bar button as previously shown. Then in the Find
window, enter the value 2E into the Data Byte Value field as shown in Figure 57.
Getting Started
Figure 57. Find a Data Value of 2E
57
Click on the Find Next button and the trace listing will go to the only line containing this data value which
is on line 13 as shown in Figure 58.
58
Figure 58. Monitor Window Trace List Showing Find 2E Data Result
Getting Started
Go to the start of the trace list using the Go to Start tool bar button as previously shown. Change the
Data Byte Value field to 72 as shown in Figure 59. Click on the Tag All button and you will be prompted
to clear all existing tags in the trace listing as shown in Figure 60. Click on the Yes button and the search
will commence.
Getting Started
Figure 59. Find a Data Value of 72
Figure 60. Clear Tagged Rows Prompt
59
When the search is complete, the pop-up window in Figure 61 will appear to notify you how many trace
lines matched the search criteria. Click on the OK button and the trace list will display the first tagged line
as shown in Figure 62. Lines 22 and 80 will be tagged since they contain the data value 72.
Figure 61. Matched Transactions Prompt
60
Figure 62. Monitor Window Trace List Showing Find 72 Data Result
Getting Started
You can click on the Go to Tagged Row tool bar button, shown in Figure 63, to move to the second
search result as shown in Figure 64. Repeatedly clicking on the Go to Tagged Row tool bar button will
cause the trace list to alternate between the two tagged lines.
Figure 63. Go to Tagged Row Tool Bar Button
Figure 64. Monitor Window Trace List Showing the Second Find 72 Data Result
Getting Started
61
Step 7 – Changing Preferences
There are a number of user configurable preferences available from the Tools | Preferences menu entry.
Right-click in the trace list and select Go to Cursor B from the pop-up menu. Select the
Tools | Preferences menu entry and the Preferences dialog will appear. By default, this screen will be
displaying the options on the Monitor Colors tab. Move the Preferences screen to the right side of the
Monitor window as shown in Figure 65.
The Monitor Colors tab affects the various coloring elements of the Monitor window. These settings
allow the user to change the text and background colors of the trigger and cursor markers, the color of the
SDA line, SCL line, and beginning marker lines in the timing display, and the normal trace list line coloring
scheme. Changing any of these settings while the affected element is visible on the screen will result in
the immediate update of the color change in the Monitor window.
62
Figure 65. Monitor Colors Preferences Screen
Getting Started
Since Cursor A is visible in the trace list, we will change its background color to observe how these color
configuration items work. Click on the Cursor A Background control and select the color Blue from the
pop-up color picker as shown in Figure 66. Using the same method, click on the Cursor A Text control
and select the color White from the pop-up color picker.
Figure 66. Monitor Colors Preferences Screen Changing Cursor A Background Color
Getting Started
63
After making these color changes, observe that the Cursor A line in the Monitor window trace list has
immediately been painted with the newly selected colors as shown in Figure 67. All of the other items on
the Monitor Colors tab can be similarly changed.
64
Figure 67. Monitor Window with Updated Cursor A Colors
Getting Started
The Color Scheme controls how trace line groupings are displayed. The options are no color, alternating
color per line, or alternating color per message (address transaction and all conveyed data to/from that
address). The default setting is Alternate color per message, but the user may prefer a different setting.
Click on the Color Scheme control and select the Alternate color per row entry as shown in Figure 68.
Getting Started
Figure 68. Monitor Window with Updated Cursor A Colors
65
After changing the Color Scheme, observe the resulting effect as shown in Figure 69. Click on the
Use Defaults button to reset all of the options on the Monitor Colors tab back to their default settings.
Click on the Close button to close the Preferences screen.
66
Figure 69. Monitor Window with Alternating Row Colors
Getting Started
Right-click in the trace list and select Go to | Trigger from the pop-up menu. Use the vertical scroll bar on
the right side of the trace list to position the line containing the trigger into the middle of the window as
shown in Figure 70.
Getting Started
Figure 70. Monitor Window Trace List with the Trigger Line Centered
67
Select the Tools | Preferences menu entry and the Preferences screen will appear. Click on the
Monitor Options tab and move the Preferences screen to the middle of the Monitor window as shown in
Figure 71.
68
Figure 71. Monitor Options Preferences Screen
Getting Started
The Monitor Options tab allows configuration of other Monitor window display options. The Line
Column option affects how the Line column in the trace list is displayed. When set to Starting from 1,
the trace list rows will start at number one and increment sequentially. This is the default setting. When
set to Trigger is line 0, the line containing the trigger will be zero, lines before the trigger will be negative,
and lines after the trigger will be positive. Click on the Trigger is line 0 option, and observe how the Line
number column changes around the Trigger line as shown in Figure 72.
Figure 72. Monitor Window Trace List with Trigger at Line Zero Numbering
Getting Started
69
The Timestamp Start option operates in a similar fashion. When set to Starting from 0, timestamps will
increment sequentially starting from the first trace list entry. This is the default setting. When set to
Trigger is time 0, the line entry containing the trigger will have a timestamp of zero with lines before the
trigger having a negative timestamp and lines after having a positive timestamp. Click on the Trigger is
time 0 option, and observe how the Time column changes around the Trigger line as shown in Figure 73.
70
Figure 73. Monitor Window Trace List with Trigger is Time Zero Timestamps
Getting Started
The Timestamp Display option affects how timestamps are calculated and displayed. When set to
Absolute, the timestamp displayed for each entry is the absolute time relative to the start of bus traffic
acquisition. This is the default setting. When set to Relative, the timestamp displayed for each entry is the
elapsed time since the last transaction was recorded. Click on the Relative option, and observe how the
Time column changes around the Trigger line as shown in Figure 74.
Figure 74. Monitor Window Trace List with Relative Timestamps
There are several other miscellaneous options on this tab which will not be explored in this tutorial but are
described in the Configuration and Preferences chapter. Click on the Use Default button to return the
Monitor Options settings back to their default settings.
Getting Started
71
Click on the Preferences screen Formats tab and position the screen to the right of the Monitor window
as shown in Figure 75. The Formats tab controls how addresses in 7-bit mode will be displayed when
shown in hex format. In FE mode, the LSB will always be zero and the 7-bits of address will be
left-justified within the byte. This is the default setting. In 7F mode, the MSB will always be zero and the
7-bits of address will be right-justified within the byte. Both of these formats are encountered in the I2C
world, and the tool is flexible enough to use either format throughout.
72
Figure 75. Monitor Window Trace List Showing Addresses in FE mode
Getting Started
Click on the 7F mode option and observe how the Addr column changes as shown in Figure 76. The
addresses are effectively divided by two since the seven address bits are now displayed in a right-justified
format within the byte. Click on the FE mode selection to return this setting to its default state. Click on
the Close button to close the Preferences screen.
Getting Started
Figure 76. Monitor Window Trace List Showing Addresses in 7F mode
73
Tutorial – Using Live Mode
By now you should have a firm grasp on the use of the I2C Exerciser’s Monitor window and basic bus
tracing features. The following portion of this tutorial will provide you with an understanding of the use of
the Debugger window which provides a facility for interactive communication with devices on the I
This window is not available for use in the demo mode and to fully employ its features requires
connection of the CAS-1000-I2C to an actual target. However, in working through the rest of this chapter,
you will use only the CAS-1000-I2C controller with no target attached which is sufficient to enable you to
become familiar with how the debugger component of the I2C Exerciser functions.
If it is not already connected, you will need to connect the CAS-1000-I2C controller by attaching the
provided USB cable between the USB port on the back of the CAS-1000-I2C and an available USB 2.0
port on the host computer. Refer to the Installation chapter for detailed installation instructions. No target
should be connected to the CAS-1000-I2C controller during this portion of the tutorial.
Step 1 – Enable Live mode
As mentioned in the first part of this chapter, I2C Exerciser checks upon starting to see if the CAS-1000I2C is attached and automatically enters Live Data Mode if it is or Demo Mode if it is not. Click on the
Tools menu to see if there is a check mark next to the Demo Mode menu item and, if so, you will have to
click on this menu item to remove the check mark and switch the program into Live Data Mode as shown
below in Figure 77. You can also verify that the program is in Live Data mode by observing the program’s
status bar in the lower right corner of the main window as shown in Figure 78. The leftmost indicator
should contain the text LIVE.
2
C bus.
74
Figure 77. Tools Menu Deselect Demo Mode
Figure 78. Status Bar Indicating Live Data Mode
Getting Started
When the I2C Exerciser is first used to interact with the bus in Live Mode (as you will do in the next step),
it checks the electrical characteristics of the target bus to determine if there may be a possible conflict
with the electrical settings of the current project. Because you have no target connected during this
tutorial, you can expect to see the warning message shown in Figure 79 below.
Figure 79. Analyzer Supplied Mode Prompt
If you see this message, click on the Yes button to open the Configuration Manager with the I2C
Exerciser’s recommended electrical settings. Then simply click on the Close button at the bottom of the
Configuration Manager window to accept the recommended defaults. You can then continue with the
tutorial.
Getting Started
75
Step 2 – Send and Receive with Debugger
Click on the Debugger icon in the shortcut bar on the far left side of the main window to open the
Debugger window. Alternatively, you could select the Debugger entry from the Tools menu. The
Debugger window will appear as shown in Figure 80 below.
2
The left area of the Debugger window is for sending data to slave devices on the I
area for receiving data back from slave devices. You can see fields on both sides for specifying the bus
address and address type. Both sides also have a No Stop checkbox that allows you to generate a
message without a Stop cycle, if necessary, such that the next Address cycle will commence with a
Repeated Start cycle. The Run field on the send side allows you to specify the number of times that
debugger commands will be looped (including continuous looping). The Bytes field on the receive side
lets you enter the number of bytes that you want to read from the slave device at the specified bus
address.
C bus and the right
76
Figure 80. Debugger Window
Getting Started
The text box in the bottom portion of the Send area is for entering debugger commands. An entry in this
text box can be as simple as a single hexadecimal byte value to send. You can refer to the Interactive
Debugger chapter later for more details on all of the commands. For now, go ahead and enter the hex
value 3E into this box.
Even though there is no target attached to the analyzer, you are able to send the byte 3E to the bus. Click
on the Send button and the byte value should be echoed in the Receive section text box on the right side
of the window as shown below in Figure 81. Note that the option to echo the sent data (default) can be
controlled in the Debugger preferences (Tools | Preferences | Debugger Options). If turned off, the sent
data would not be shown in the receive section text box.
2
In Analyzer Supplied mode, the CAS-1000-I2C controller supplies the pull-up voltage for the I
C bus. If
you were still in Target Supplied mode, since there is no target connected there would be no pull-up
supply to the bus making the lines undefined when high. Therefore, any attempt to send or receive
messages would likely result in a timeout error. You can confirm and adjust the voltage source settings
from the Settings pane of the Configuration Manager (Tools | Configuration Manager… | Settings).
Getting Started
Figure 81. Byte Sent From the Debugger
77
Click on the Receive button now. The value FF will appear in the Receive area text box. Without a target
attached to communicate with, this is the only value that should ever be received since the bus is floating
high. Enter the number 3 in the Bytes field and then click on the Receive button again to tell the
debugger to read three bytes. The value FF will now be displayed three times in the text box as shown in
Figure 82 below.
78
Figure 82. Receive Three Bytes in the Debugger
Getting Started
Step 3 – Send While Monitoring
In order to see the bus traffic that is being generated by the Debugger, you need to start the Monitor to
collect data.
Go to the Monitor window by clicking on its entry in the Shortcut Bar. Click on the Run Single button in
the I2C Exerciser tool bar (indicated by the
If a message box comes up asking if you want to save the current Monitor trace data, click on the No
button. The Run Status tab on the Monitor Tools window will open and the Monitor will begin capturing
data. You may want to minimize the Monitor Tools window if it obstructs your view of the Debugger and
Monitor windows.
Go back to the Debugger window and click on the Send button.
Switch to the Monitor window by clicking on its entry in the Shortcut Bar. The trace list will display the
write message for the byte sent as shown in Figure 83 below. The NAK column indicates that the
message was not acknowledged since there are no devices connected to the analyzer which would be
able to respond to the message.
icon).
Getting Started
Figure 83. Capture of Debugger Send
79
Return to the Debugger window by clicking on the Debugger Shortcut Bar icon. You will now execute a
simple Debugger script. Refer to the Interactive Debugger chapter for details on using debugger script
commands. For now you will load a very short debugger script from a debugger control file.
Click on the Open Command File button in the tool bar (represented by the
button if prompted for saving the current Debugger commands. The Open Debugger Command File
dialog window will be displayed so that you can browse for the file. It is located in the “Demo” subfolder of
the I2C Exerciser examples folder. For a default installation, this would be “C:\Corelis Examples\I2C
Exerciser\Demo”. Find this subfolder and select the file named “tutorial.dcf” and then click on the Open
button. This debugger control file script will load into the Debugger window as shown in Figure 84 below.
icon). Click on the No
Figure 84. Tutorial Script Loaded Into Debugger
Notice the first line of the debugger script. This is a comment line that specifies the address mode (FE or
7F) that must be used with this script. The current address mode is shown in the status bar at the bottom
of the main window. It should report the default FE mode with the text, “AddrFormat: FE,” to match the
expected behavior of the script instructions. Recall from earlier in the chapter that this setting is changed
via the Formats tab of the Preferences dialog (Tools | Preferences...). When you save a debugger
command file, this line is automatically inserted at the beginning to remind you of the address mode
needed for the script to execute correctly.
80
Getting Started
Click on the Send button to execute the script and the bytes sent will be echoed to the Receive area text
box. Then return to the Monitor window to view the captured data. You will see in the trace list that the
bytes were sent to various bus addresses as specified by the script. This is shown in Figure 85 below.
Getting Started
Figure 85. Capture of Debugger Script
81
Step 4 – Manipulate Discrete I/O Signals
Suppose that you want to use the I/O 1 and I/O 2 general purpose lines to stimulate a target device. To
drive these signals, you must first set the discrete I/O modes to output. Open the Configuration Manager
by clicking on its entry in the I2C Exerciser’s Tools menu and then click on the Settings tab. Near the
bottom of the dialog there is a section called Input/Output Signals. Set both the I/O 1 and I/O 2 Function
fields to “Out, TTL” using the dropdown menus as shown in Figure 86 below. A custom voltage can also
be specified here, but leave it at the default 3.30 V. Click on the Close button when you are finished.
Figure 86. Set Discrete I/O Modes
Return to the Debugger window by clicking on the Debugger Shortcut Bar icon. Click on the File menu
and then click on New Debugger Command File… Enter the following commands into the empty Send
area text box:
// Discrete I/O Test
Address10 118
SetDiscrete 1 0
SetDiscrete 2 0
A1
SetDiscrete 2 1
2B
SetDiscrete 2 0
SetDiscrete 1 1
9F
SetDiscrete 2 1
E8
The first number that follows the SetDiscrete command specifies the line — either I/O 1 or I/O 2. The
second number specifies the state to which the signal will be set — high on 1 or low on 0. This script will
output a byte after setting each of the four possible combinations of signal states. Notice that the
Address10 command is used to specify that the messages will be sent to the 10-bit address 118 (hex).
82
Getting Started
Set the script to execute twice by entering a 2 in the Run field. Then click on the Send button to execute
the script. The contents of the Debugger window should appear as shown in Figure 87 below. Click on
the Monitor entry in the Shortcut Bar to return to the Monitor window. As shown below in Figure 88, the
trace list will display the messages that were sent to the 10-bit address 118 and you can see changes in
the I/O lines by observing to the I/O 1 and I/O 2 columns.
Figure 87. Debugger Discrete I/O Script
Getting Started
Figure 88. Monitor Debugger Discrete I/O Manipulation
83
Step 5 – Close the Debugger
Click on the Stop button in the I2C Exerciser tool bar (indicated by the icon) to stop the Monitor from
collecting data.
Return to the Run Status tab on the Monitor Tools window that was opened when data capturing
started—you may have to restore it from minimized state if you had minimized it earlier. Since you are
done capturing data, click on the Close button at the bottom of the window.
Click on the Debugger entry in the Shortcut Bar to return to the Debugger window and close the
debugger session by clicking on the X button in the upper right corner of the window. A message box will
come up as shown in Figure 89 below, giving you a chance to save your debugger script. Click on the No
button and the Debugger will close.
84
Figure 89. Debugger Close
Getting Started
Loading...