Mcu Operation Mode - Fujitsu SOFTUNE F2 MC-16 User Manual

Software for developing programs for the f2 mc-16 family of microprocessors / microcontrollers
Hide thumbs Also See for SOFTUNE F2 MC-16:
Table of Contents

Advertisement

CHAPTER 2 DEPENDENCE FUNCTIONS
2.3.1.2

MCU Operation Mode

There are two MCU operation modes as follows:
• Debugging Mode
• Native Mode
■ Setting MCU Operation Mode
Set the MCU operation mode.
There are two operation modes: the debugging mode, and the native mode.
Choose either one using the SET RUNMODE command.
At emulator start-up, the MCU is in the debugging mode.
The data access to internal bus may not be detected by emulator in native mode. Therefore, when the MCU
operation mode is changed, all the following are initialized:
- Data breakpoints
- Data monitoring break
- Event condition settings
- Sequencer settings
- Trace measurement settings and trace buffer
■ Debugging Mode
All the operations of evaluation chips can be analyzed, but their operating speed is slower than that of mass-
produced chips.
■ Native Mode
Evaluation chips have the same timing as mass-produced chips to control the operating speed. Note that the
restrictions the shown in Table 2.3-1 are imposed on the debug functions.
Table 2.3-1 Restrictions on Debug Functions in Native Mode
Applicable series
Common to all series
140
Restrictions on debug functions
- When a data read access occurs on the MCU internal bus, the internal bus
access information is not sampled and stored in the trace buffer.
- Even when a data break or event (data access condition) is set for data on the
MCU internal bus, it may not become a break factor or sequencer-triggering
factor.
- The coverage function may fail to detect an access to data on the MCU
internal bus.

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Softune workbench

Table of Contents