Everything
2.4.3 Debugging the GTM

This section describes the methods to enable the debugging facilities for the generic timer IP module (GTM) from Robert Bosch GmbH, operation of each facility, and notes on usage if the selected microcontroller incorporates the GTM.

Caution

The simulator does not support debugging of this module.

 

In some statements, the states of the GTM are referred to in a similar way as in the Main window as follows.

Table 2.3

States of the Microcontroller

Displayed Item

State of the GTM

Standby

A clock signal is not being supplied to the GTM.

Disable

The selected multi-channel sequencer (MCS) is not activated.

-

Enabling the debugging facilities

When the GTM is to be debugged, make the following settings.

[Connection with Target Board] category on the [Connect Settings] tab in the Property panel.

[Debug the GTM function] property

Yes

[MCS to be debug] property

MCS to be debugged

With the above settings, it is possible to select a channel of the MCS which is specified for [MCS to be debugged] in the Statusbar of the Main window or in the Debug Manager panel, as the targets for debugging.

 

Example

When "MCS0" is specified for [MCS to be debugged], the channels of that MCS are displayed as the targets for debugging in the Debug Manager panel.

Figure 2.8

Example of the Display in the Debug Manager Panel

 

-

Operation of individual facilities

When the GTM is selected as the target for debugging, each facility behaves as described below.

(1)

Execution of a program

Synchronous execution and synchronous breaks are available for all channels of the selected MCS.

(2)

Events

Valid events are specifiable for all channels of the MCS.

(3)

Memory

The RAM of the MCS is accessible. The displayed addresses are those in the memory space of the MCS which is selected for the [MCS to be debugged] property.

(4)

I/O registers

The I/O registers in the GTM are accessible.

The displayed addresses are those in the memory space of the GTM.

(5)

CPU registers

The CPU registers for each channel of the MCS are accessible.

-

Notes on usage

(1)

If this debugging facility is not used, the GTM is handled in the same way as other peripheral IP modules.

(2)

If this facility is used, the following facilities are not available.

-

LPD output of software tracing

-

External trigger input

-

External trigger output

-

Measuring CAN bus reception processing times

-

Pseudo-error Debugging

-

Debugging CAN Bus Reception Procedures

(3)

The following facilities are not available in debugging of the GTM.

-

Software break

-

Collect Execution History of Programs

-

Measure Execution Time of Programs

-

Measure Performance

-

Set an Action into Programs

-

Exclusive Control Checking Tool

(4)

The mode selected for the [Debug mode] property in the [Multi-core] category on the [Debug Tool Settings] tabbed page in the Property panel affects some aspects of the operation in the following ways.

-

Selecting [Sync debug mode]

When a channel of the MCS is selected as the target for debugging and [Go to Here] is selected from the context menu, the CPU does not proceed with synchronous execution.

-

Selecting [Async debug mode]

When a CPU is selected as the target for debugging and [Standby] is displayed as the state of the GTM, all channels of the MCS also proceed with synchronous execution. When all CPUs enter the break state while [Standby] is being displayed as the state of the GTM, a synchronous break is also generated for all channels of the MCS.

(5)

When a channel of the MCS is selected as the target for debugging, the CPU does not proceed with synchronous stepped execution.

(6)

Access-type events cannot be set for the I/O registers.

(7)

When the GTM is selected as the target for debugging and [Standby] is displayed as the state of the GTM, the following facilities are not available.

-

Displaying or modifying memory

-

Displaying or modifying CPU registers

-

Setting, editing, and deleting breakpoints

-

Executing or stopping programs