This web page refers to our older busTRACE 7.0 which is no longer shipping. Click here for details on our latest generation busTRACE software.
This WEB page comes from the busTRACE 7.0 User's Manual. (Table of Contents)
You can configure busTRACE to let it know which CDBs you want it to capture or, alternatively, which CDBs you want it to not capture. The CDB Filter is set down in kernel mode and causes the specified CDB requests to be skipped and not captured. This is the key difference from our ability to filter I/O activity from view. When you filter I/O activity from view, the I/O is captured, it is still in memory, it is only filtered from view.
This feature can be useful to save your capture buffer space for only those CDB requests that you are interested in capturing. This feature is only applicable to devices that process CDBs.
You can set a CDB Filter in one of several places
The filter dialog box gives you three options on how you want to create a CDB Filter:
When you click on the Add button, you are shown a list of all the available CDB opcodes that you can add to the list. For example:
Simply select the CDB opcode that you would like to add to your list and then click on the Add button below.
As you can see above, it is easy to define which CDB opcodes you want to capture or which ones you do not want to capture. If you choose our Advanced Editor option, you can enter a boolean equation to create any number of possibilities for the CDB filter.
The boolean equation follows 'C' programming constructs. The following examples should help you better understand how to set an advanced mode CDB Filter.