Scope vs. Logic analyzer

Timing vs. State

Using Timing and State

The four special clock channels capture data just like the normal channels when timing analysis is active. When state modes are used, data is not captured on the special clock channels.

Normal timing

A timestamp value is recorded when each sample is stored to memory and allows each sample’s elapsed time to be determined. Half of the GoLogic's memory is used to store the timestamp values, so the maximum number of samples which can be stored is halved. However, the effective memory depth actually increases because no redundant samples are stored and the time-span of the overall trace is much longer.

Choosing which channels can detect input signal changes is a powerful feature of transitional timing. Chapter 3 - Setup step two: channels describes how to specify which channels detect transitions.

Rather than over-sample the data, the CA0 "clock" channel is connected to the test circuit’s clock signal. The input signal connected to CA0 drives the GoLogic sampling and samples the data inputs synchronously with the test circuit. The data can be sampled on the rising edge, falling edge, or any edge of the CA0 clock channel. However, only the GoLogic-72 models support the "any edge" clock source.

The GoLogic supports state frequencies up to 125 MHz. However, the source clock signal cannot exceed 62.5 MHz when Both Edges is selected (which is an effective 125 MHz clock).

The GoLogic cannot determine the source clock signal's frequency. Therefore, you must enter the source clock’s frequency so the GoLogic software can display each sample’s elapsed time correctly. If no frequency is provided, the software assumes a 125 MHz external clock rate.

The CA1, CA2, and CA3 clock channels can be used as data inputs when simple state analysis is used.

Simple state

• The clock equation must have at least one edge.
• Rising and falling clock operands are grouped together.
• High and low clock operands are grouped together.
• Inside each group, clock operands are combined first using an OR operator.
• Edge-groups and level-groups are combined last with an AND operator...

(Rising S1 OR Falling LRE*) AND (Low S0 OR High S2)

• The GoLogic temporarily holds the first phase signals when the slave clock equation occurs.
• The second phase signals are combined with the first phase and stored to memory when the master clock equation occurs.
• Each clock equation obeys the same clock equation rules described in the simple state section.
• Four complex state options are available which define which channels are used to capture and how the GoLogic combines the first and second phases. These state options are...

Connect channels A00 through A07 to the shared signals. Channels A08 through A15 are left unconnected. When the slave equation occurs, the data on channels A00 through A07 is internally shifted to channels A08 through A15 and held temporarily. When the master equation occurs, the data stored in the first phase is combined with the new data on channels A00 through A07 and the resulting logic analyzer sample is stored to memory...

The signals connected to channels B00 and above are also stored with the master equation.

Connect channels A00 to A07, B00 to B07, and C00 to C07 to the shared signals. Channels A08 to A15, B08 to B15, and C08 to C15 are left unconnected. When the Slave equation is valid, the data on channels A00 to A07, B00 to B07, and C00 to C07 is internally shifted to channels A08 to A15, B08 to B15, and C08 to C15 and held temporarily. When the Master equation is valid, the data stored during the initial phase is combined with the new data on channels...

The signals connected to channels D00 and above are also stored with the master clock equation.

Connect channels A00 through A15 to the signals output in the initial phase. Connect channels B00 through D15 to the signals output in the final phase. When the Slave clock equation is valid, the data on channels A00 through A15 is held temporarily. When the Master clock equation is valid, the data from the initial phase is combined with the new data from channels B00 through D15 and the resulting logic analyzer sample is stored...

Connect channels A00 through B15 to the signals output in the initial phase. Connect channels C00 through D15 to the signals output in the final phase. When the Slave clock equation is valid, the data on channels A00 through B15 is held temporarily. When the Master clock equation is valid, the data from the initial phase is combined with the new data from channels C00 through D15 and the resulting logic analyzer sample is stored...

The serial bus edit controls are displayed when I2C timing, I2C state, CAN timing, LIN timing, SPI timing, RS232 timing, or bitstream timing modes are active...

Define the serial buses you wish to capture are display using the controls in this area...

• Total serial buses - Up to 32 serial buses can be captured and displayed together. Select "0" buses to hide all converted serial bus data. Different serial bus types can be captured and displayed together.
• Re-convert open data - Since the conversion process requires significant CPU time, captured data is automatically converted from raw serial form to parallel values only when new trace data is captured or a project file is opened. However, the "Re-convert" button allows you to adjust the serial bus definitions and then re-convert the data. This is a very handy feature when you aren't certain of the bus parameters. We recommend capturing a small trace of 8K samples while experimenting so the conversion process is fast as possible.
• Type - Choose the serial bus type. The GoLogic supports I2C, CAN, LIN, SPI, RS232 (UART), and generic bitstreams. Other serial buses can be captured and viewed in the WaveForm window, but only these bus types are converted from raw serial form to parallel values. To analyze other serial buses, you can create custom Plug-Ins using the GoLogic PlugIn Development Kit (PDK). The PDK is available as a free download on the NCI web site.
• Name - Enter a meaningful name for each serial bus if two or more I2C buses are defined. If only one bus is being captured, the bus name can be left to the default name.
• Data - Choose the source data to convert.
• Speed - Choose the I2C bus speed. The GoLogic uses this option to determine the sampling rate. If two or more serial buses are defined, the GoLogic always uses a 125MHz sampling rate to ensure all buses are captured accurately.
• Trigger bus - When I2C timing or state mode is active, the I2C bus connected to CA0 and CA1 is always used for triggering. This is a hardware limitation inside the GoLogic when I2C timing or state mode is used.
• SCL - Choose the channel connected to the I2C clock signal. If you want to trigger on this I2C bus, then select CA1 for the clock and CA0 for the data signal. Otherwise, you can connect any channels to the I2C bus. The software automatically creates a channel group for this signal in the "Step 2: Channels" tab. A line in the WaveForm window is also automatically inserted to display both the raw clock signal and the converted I2C bus.
• SDA - Choose the channel connected to the I2C data signal. If you want to trigger on this I2C bus, then select CA1 for the clock and CA0 for the data signal. Otherwise, you can connect any channels to the I2C bus. The software automatically creates a channel group for this signal in the "Step 2: Channels" tab. A line in the WaveForm window is also automatically inserted to display both the raw data signal and the converted I2C bus.

Once all your serial buses are defined, you can switch back to Transitional Timing mode and use the generalized TriggerForms instead of the specialized serial bus TriggerForms. This allows you to trigger on an unrelated signal like a hardware interrupt while capturing serial buses.

Motorola's documentation on the SPI bus is required reading before using SPI timing. SPI bus definition can vary between implementations, and you must know exactly how your SPI bus operates.

The serial bus edit controls are displayed when I2C timing, I2C state, CAN timing, LIN timing, SPI timing, RS232 timing, or bitstream timing modes are active...

Define the serial buses you wish to capture are display using the controls in this area...

• Total serial buses - Up to 32 serial buses can be captured and displayed together. Select "0" buses to hide all converted serial bus data. Different serial bus types can be captured and displayed together.
• Re-convert open data - Since the conversion process requires significant CPU time, captured data is automatically converted from raw serial form to parallel values only when new trace data is captured or a project file is opened. However, the "Re-convert" button allows you to adjust the serial bus definitions and then re-convert the data. This is a very handy feature when you aren't certain of the bus parameters. We recommend capturing a small trace of 8K samples while experimenting so the conversion process is fast as possible.
• Type - Choose the serial bus type. The GoLogic supports I2C, CAN, LIN, SPI, RS232 (UART), and generic bitstreams. Other serial buses can be captured and viewed in the WaveForm window, but only these bus types are converted from raw serial form to parallel values. To analyze other serial buses, you can create custom Plug-Ins using the GoLogic PlugIn Development Kit (PDK). The PDK is available as a free download on the NCI web site.
• Name - Enter a meaningful name for each serial bus if two or more SPI buses are defined. If only one bus is being captured, the bus name can be left to the default name.
• Data - Choose the source data to convert.
• Mode - Choose the SPI bus mode. See the "SPI Mode" topic below for details.
• Width - Enter the number of bits in each bus value. Packet widths from 2 to 64 bits are supported.
• CLK period - Measure the time between two adjacent rising edges on the CLK signal and enter this value. The GoLogic uses this time-value to determine the sampling rate. If two or more serial buses are defined, the GoLogic always uses a 125MHz sampling rate to ensure all buses are captured accurately.
• Trigger bus - When SPI timing mode is active, any SPI bus can be used for triggering. Check this box if you want to trigger on this SPI bus. Only one bus can be used for triggering, so checking one box disables all the others.
• CLK - Choose the channel connected to the SPI clock signal. The software automatically creates a channel group for this signal in the "Step 2: Channels" tab. A line in the WaveForm window is also automatically inserted to display both the raw clock signal and the converted SPI bus.
• MISO - Choose the channel connected to the SPI "Master In Slave Out" signal. The software automatically creates a channel group for this signal in the "Step 2: Channels" tab. A line in the WaveForm window is also automatically inserted to display both the raw MISO signal and the converted SPI bus.
• MOSI - Choose the channel connected to the SPI "Master Out Slave In" signal. The software automatically creates a channel group for this signal in the "Step 2: Channels" tab. A line in the WaveForm window is also automatically inserted to display both the raw MOSI signal and the converted SPI bus.
• Bit-order - Choose the order the serial bits are used in the converted parallel values.

Once all your serial buses are defined, you can switch back to Transitional Timing mode and use the generalized TriggerForms instead of the specialized serial bus TriggerForms. This allows you to trigger on an unrelated signal like a hardware interrupt while capturing serial buses.

CPHAS is the clock "phase" value. CPOL is the clock "polarity" value. These values define how the serial SPI bits are latched. Motorola defines the four SPI bus modes as follows…

The following timing diagram illustrates the SPI bus modes…

Since each SPI implementation differs and the SS* signal can either be a "frame" or a "chip select" mechanism, the GoLogic software does NOT use the SS* signal in the SPI timing mode setup. Of course, you can connect a spare channel and capture the SS* signal if needed.

The GoLogic cannot trigger on RS232 bus values. We recommend using the "Immediate" TriggerForm to capture all bus activity and then searching the captured data using the RS232 search tools.

The serial bus edit controls are displayed when I2C timing, I2C state, CAN timing, LIN timing, SPI timing, RS232 timing, or bitstream timing modes are active...

Define the serial buses you wish to capture are display using the controls in this area...

• Total serial buses - Up to 32 serial buses can be captured and displayed together. Select "0" buses to hide all converted serial bus data. Different serial bus types can be captured and displayed together.
• Re-convert open data - Since the conversion process requires significant CPU time, captured data is automatically converted from raw serial form to parallel values only when new trace data is captured or a project file is opened. However, the "Re-convert" button allows you to adjust the serial bus definitions and then re-convert the data. This is a very handy feature when you aren't certain of the bus parameters. We recommend capturing a small trace of 8K samples while experimenting so the conversion process is fast as possible.
• Type - Choose the serial bus type. The GoLogic supports I2C, CAN, LIN, SPI, RS232 (UART), and generic bitstreams. Other serial buses can be captured and viewed in the WaveForm window, but only these bus types are converted from raw serial form to parallel values. To analyze other serial buses, you can create custom Plug-Ins using the GoLogic PlugIn Development Kit (PDK). The PDK is available as a free download on the NCI web site.
• Name - Enter a meaningful name for each UART signal.
• Data - Choose the source data to convert.
• Baud - Select (or enter) the bits-per-second used for the UART bus. You can choose from the common baud rates listed or enter a custom baud in the control's edit area. Fractional baud rates are supported.
• Logic - Select the logic-type used for the raw signals. If you are connected to the raw, inverted-logic +/-12V RS232 signal, then choose the "Raw" logic option. If you are connected to the processed, TTL logic on a UART chip, then choose the "TTL" option. Whenever possible, we recommend capturing from a UART chip. The UART provides cleaner signals which the GoLogic software will interpret more reliably.
• Chan - Choose the channel connected to the UART signal. The software automatically creates a channel group for this signal in the "Step 2: Channels" tab. A line in the WaveForm window is also automatically inserted to display both the raw signal and the converted UART bus.
• Bit-order - Choose the order the serial bits are used in the converted parallel values. The bits can arrive Least Significant Bit first (LSB) or Most Significant Bit first (MSB).
• Width - Enter the number of bits in each bus data value. Packet widths from 2 to 64 bits are supported.
• Parity - Choose the type of parity bit used in each packet.
• Stop-bits - Choose the number of stop-bits in each packet.

Once all your serial buses are defined, you can switch back to Transitional Timing mode and use the generalized TriggerForms instead of the specialized serial bus TriggerForms. This allows you to trigger on an unrelated signal like a hardware interrupt while capturing serial buses.

The GoLogic cannot trigger on CAN bus values. We recommend using the "Immediate" TriggerForm to capture all bus activity and then searching the captured data using the CAN search tools.

When I2C timing, I2C state, CAN timing, LIN timing, SPI timing, RS232 timing, and generic bitstream timing modes are active, the serial bus definition controls are displayed...

Define the serial buses you wish to capture are display using the controls in this area...

• Total serial buses - Up to 32 serial buses can be captured and displayed together. Select "0" buses to hide all converted serial bus data. Different serial bus types can be captured and displayed together.
• Re-convert open data - Since the conversion process requires significant CPU time, captured data is automatically converted from raw serial form to parallel values only when new trace data is captured or a project file is opened. However, the "Re-convert" button allows you to adjust the serial bus definitions and then re-convert the data. This is a very handy feature when you aren't certain of the bus parameters. We recommend capturing a small trace of 8K samples while experimenting so the conversion process is fast as possible.
• Type - Choose the serial bus type. The GoLogic supports I2C, CAN, LIN, SPI, RS232 (UART), and generic bitstreams. Other serial buses can be captured and viewed in the WaveForm window, but only these bus types are converted from raw serial form to parallel values. To analyze other serial buses, you can create custom Plug-Ins using the GoLogic PlugIn Development Kit (PDK). The PDK is available as a free download on the NCI web site.
• Name - Enter a meaningful name for each CAN signal.
• Data - Choose the source data to convert.
• Baud - Select (or enter) the bits-per-second used for the CAN bus. You can choose from the common baud rates listed or enter a custom baud in the control's edit area. Fractional baud rates are supported.
• Logic - Select the logic-type used for the raw signals. The CAN physical layer is not defined by the Bosch® specification. If your raw signals use inverted-logic, then choose the "Inverted" logic option. If your raw signals use positive-logic , then choose the "Normal" option.
• Chan - Choose the channel connected to the CAN signal. The software automatically creates a channel group for this signal in the "Step 2: Channels" tab. A line in the WaveForm window is also automatically inserted to display both the raw signal and the converted CAN bus.

Once all your serial buses are defined, you can switch back to Transitional Timing mode and use the generalized TriggerForms instead of the specialized serial bus TriggerForms. This allows you to trigger on an unrelated signal like a hardware interrupt while capturing serial buses.

The GoLogic cannot trigger on LIN bus values. We recommend using the "Immediate" TriggerForm to capture all bus activity and then searching the captured data using the LIN search tools.

The serial bus edit controls are displayed when I2C timing, I2C state, CAN timing, LIN timing, SPI timing, RS232 timing, or bitstream timing modes are active...

Define the serial buses you wish to capture are display using the controls in this area...

• Total serial buses - Up to 32 serial buses can be captured and displayed together. Select "0" buses to hide all converted serial bus data. Different serial bus types can be captured and displayed together.
• Re-convert open data - Since the conversion process requires significant CPU time, captured data is automatically converted from raw serial form to parallel values only when new trace data is captured or a project file is opened. However, the "Re-convert" button allows you to adjust the serial bus definitions and then re-convert the data. This is a very handy feature when you aren't certain of the bus parameters. We recommend capturing a small trace of 8K samples while experimenting so the conversion process is fast as possible.
• Type - Choose the serial bus type. The GoLogic supports I2C, CAN, LIN, SPI, RS232 (UART), and generic bitstreams. Other serial buses can be captured and viewed in the WaveForm window, but only these bus types are converted from raw serial form to parallel values. To analyze other serial buses, you can create custom Plug-Ins using the GoLogic PlugIn Development Kit (PDK). The PDK is available as a free download on the NCI web site.
• Name - Enter a meaningful name for each LIN signal.
• Data - Choose the source data to convert.
• Baud - Select (or enter) the bits-per-second used for the LIN bus. You can choose from the common baud rates listed or enter a custom baud in the control's edit area. Fractional baud rates are supported.
• Version - Choose the LIN bus version.
• Logic - Select the logic-type used for the raw signals. If your raw signals use inverted LIN logic, then choose the "Inverted" logic option. If your raw signals use normal LIN logic , then choose the "Normal" option.
• Chan - Choose the channel connected to the LIN signal. The software automatically creates a channel group for this signal in the "Step 2: Channels" tab. A line in the WaveForm window is also automatically inserted to display both the raw signal and the converted LIN bus.

Once all your serial buses are defined, you can switch back to Transitional Timing mode and use the generalized TriggerForms instead of the specialized serial bus TriggerForms. This allows you to trigger on an unrelated signal like a hardware interrupt while capturing serial buses.

The GoLogic cannot trigger on Bitstream bus values. We recommend using the "Immediate" TriggerForm to capture all bus activity and then searching the captured data using the LIN search tools.

The serial bus edit controls are displayed when I2C timing, I2C state, CAN timing, LIN timing, SPI timing, RS232 timing, or bitstream timing modes are active...

Define the serial buses you wish to capture are display using the controls in this area...

• Total serial buses - Up to 32 serial buses can be captured and displayed together. Select "0" buses to hide all converted serial bus data. Different serial bus types can be captured and displayed together.
• Re-convert open data - Since the bitstream bus requires that you define where the conversion must begin in the trace data. Since this position probably changes with each trace capture, the captured data is converted to parallel values only when the "Re-convert" button is clicked. For convenience, the "re-convert data" button can also be added to the main toolbar.
• Type - Choose the serial bus type. The GoLogic supports I2C, CAN, LIN, SPI, RS232 (UART), and generic bitstreams. Other serial buses can be captured and viewed in the WaveForm window, but only these bus types are converted from raw serial form to parallel values. To analyze other serial buses, you can create custom Plug-Ins using the GoLogic PlugIn Development Kit (PDK). The PDK is available as a free download on the NCI web site.
• Name - Enter a meaningful name for each bitstream bus.
• Data - Choose the source data to convert.
• Logic - Select the logic-type used for the raw signals. Choosing inverted logic will invert the data bits.
• Clk period - Enter the time which describes the clock period. If the clock signal does not to have a 50% duty cycle, just enter double the elapsed time for a valid pulse. A precise value isn't important. The clock period just tells the GoLogic software how fast to sample the input signals. Entering a valid clock period also allows the conversion software to ignore glitches and runt-pulses in the data. This makes the bitstream conversion more robust.
• Clk edge - Choose the clock edge where the data bits should be latched: rising. falling, or both edges.
• CLK - Choose the channel connected to the clock signal. The software automatically creates a channel group for this signal in the "Step 2: Channels" tab. A line in the WaveForm window is also automatically inserted to display both the raw signal and the converted bitstream bus.
• Data - Choose the channel connected to the data signal. The software automatically creates a channel group for this signal in the "Step 2: Channels" tab. A line in the WaveForm window is also automatically inserted to display both the raw signal and the converted bitstream bus.
• Width - Enter the number of bits in each bus data value. Packet widths from 2 to 64 bits are supported.
• Start at... - Define the trace data position where the bitstream conversion starts each time the "re-convert data" button is clicked. Except when the "first sample" or "trigger" options are used, the raw bitstream data is not automatically converted each time a new trace is captured. When any moveable data marker is used as the start position, you must first place the marker on the data then click the "re-convert data" button.

Once all your serial buses are defined, you can switch back to Transitional Timing mode and use the generalized TriggerForms instead of the specialized serial bus TriggerForms. This allows you to trigger on an unrelated signal like a hardware interrupt while capturing serial buses.

The “(A&B only)” note indicates that the GoLogic operates in 36-channel mode when this option is selected. This option allows a 1M GoLogic-72 to capture 2M samples across 36 channels. Likewise, a 2M GoLogic-72 can capture 4M samples across 36 channels.

Note: The GoLogic-36 does not support the double-depth option.