S5U1C17001C ManUal
EPSOn
10-93
(C COMPilEr PaCkagE fOr S1C17 faMily) (Ver. 1.5.0)
10 DEBUggEr
c17 int_load
(load interrupt event file)
[SIM]
Operation
Loads an interrupt event file.
When an event condition written in the event file that has been loaded is met during program execution, the
designated interrupt occurs.
Event file format
Address_NMI_INT_Vector_Level_RES
//
Comment
Address_NMI_INT_Vector_Level_RES
Address_NMI_INT_Vector_Level_RES
Address_NMI_INT_Vector_Level_RES
:
Address_NMI_INT_Vector_Level_RES
Address
: Address to generate an event (000000–fffffe)
An interrupt occurs when the PC reaches this address.
NMI
:
1 = NMI request
0 = No NMI request
INT
:
1 = Interrupt request specified with the
Vector
and
Level
below
0 = No interrupt request
Vector
: Interrupt vector number (00–1f, valid when
INT
= 1)
Level
: Interrupt level (0–7, valid when
INT
= 1)
RES
:
1 = Reset request
0 = No reset request
The order of interrupt priority is
RES
>
NMI
>
Vector
.
A comment (alphanumeric characters) with "//" prefixed can be written on the right of each event line.
Format
c17 int_load
Filename
Filename
: Interrupt event file name
Usage example
(gdb)
c17 int_load event.txt
Loads the interrupt event file
event.txt
.
Example of event file
009002_0_1_10_3_0
An interrupt of which the interrupt vector number = 0x10 and interrupt level
= 3 occurs when PC = 0x9002.
009f02_0_0_00_0_1
A reset exception occurs when PC = 0x9f02.
004030_1_1_1c_7_0
An NMI occurs when PC = 0x4030. After that an interrupt of which
the interrupt vector number = 0x1c and interrupt level = 7 occurs when
interrupts are enabled.
004030_0_1_1c_7_1
A reset exception occurs when PC = 0x4030. Although an interrupt vector
number (= 0x1c) and an interrupt level (= 7) has been written, no interrupt
will occur even when interrupts are enabled because the
INT
parameter is set
to 0.
Notes
•
The
c17 int_load
command can only be used in simulator mode.
•
If the
c17 rst
command is executed when an interrupt event file has been loaded, the event sequence is
reset so that the events will be generated from the first line again.
•
Up to 256 events (event lines) can be written in an interrupt event file.
•
Up to 300 characters can be written in an event line.
10
Debugger
Summary of Contents for S5U1C17001C
Page 6: ......
Page 17: ...1 General S5U1C17001C Manual 1 General ...
Page 18: ......
Page 21: ...1 2 Install S5U1C17001C Manual 2 Installation ...
Page 22: ......
Page 29: ...3 SoftDev S5U1C17001C Manual 3 Software Development Procedures ...
Page 30: ......
Page 103: ...4 SrcFiles S5U1C17001C Manual 4 Source files ...
Page 104: ......
Page 121: ...5 IDE S5U1C17001C Manual 5 gnU17 iDE ...
Page 122: ......
Page 365: ...6 Compiler S5U1C17001C Manual 6 C Compiler ...
Page 366: ......
Page 385: ...7 Library S5U1C17001C Manual 7 library ...
Page 386: ......
Page 405: ...8 Assemblr S5U1C17001C Manual 8 assembler ...
Page 406: ......
Page 439: ...9 Linker S5U1C17001C Manual 9 linker ...
Page 440: ......
Page 449: ...10 Debugger S5U1C17001C Manual 10 Debugger ...
Page 450: ......
Page 626: ...11 Tools S5U1C17001C Manual 11 Other Tools ...
Page 627: ......
Page 696: ...S1C17 Family C Compiler Package Quick Reference Reference ...