User`s manual
12.2.5 Hardware Event
• The debugger does not support a command fetch (Fetch) or an interrupt as a hardware event.
• If you specify word-length (2-byte length) data from an odd address as an event in the following
data accesses, the event is not detected. Also, even when any other bit of the address that
contains a specified bit is accessed during bit access, the event may become effective.
- Hardware Break Event
- Real-time Trace Event
- Time Measurement Event
• In PID settings, always be sure to specify an even address for the Address area.
• Examples to specify the event for data access with its value comparison.
Address Access size 16bit data bus 8bit data bus
Even Address WORD
ex.: mov.w #1234h, 8000h
Address: 8000h
Data: 1234h
Data Mask: Don't care
<-
Even Address BYTE
ex.: mov.b #34h, 8000h
Address: 8000h
Data: 34h
Data Mask: 00FFh
<-
Odd Address WORD
ex.: mov.w #1234h, 8001h
Not supported <-
Odd Address BYTE
ex.: mov.b #34h, 8001h
Address: 8001h
Data: 3400h
Data Mask: FF00h
Address: 8001h
Data: 34h
Data Mask: 00FFh
12.2.6 CPU rewrite
• When you use the CPU of M32C/8x series, please don't rewrite the block 0. If you did, emulator
gets out of control.
• When you use the CPU of M16C/70 group, the most significant address of the last block 4KB
(FFF000h - FFFFFFh) becomes FFFFFAh only in using emulator. Please note it when you use
the software command. And please don't use the software command "program" to FFFFFCh -
FFFFFFh.
• When you enabled CPU rewrite mode, you can not use the debug functions below:
- Setting address match interrupt break points
- Setting software break points to the internal flash ROM
- COME execution to the internal flash ROM
• You can not use the functions below to the CPU rewrite control program (from setting CPU
rewrite mode select bit to clearing it). If you use these functions, it may be unable to shift to CPU
rewrite mode, or the contents of a flash ROM may be unable to be read to normalcy.
- Single step
- Software break points
- Hardware break points
- COME execution
To see the data which were rewritten by the program, break the program out of the CPU rewrite
control program and see by dump window, memory window, and so on.
264