
User’s Manual U13737EJ2V0UM00
41
CHAPTER 5 CAUTIONS
This chapter describes cautions that apply to debugging a load module incorporating the RX850, using the ID850
integrated debugger (including the RD850).
5.1
Next-Step Execution
When debugging a load module that incorporates the RX850, observe sthe following three points when executing
the next step.
(1) Do not next-step execute the ext_tsk.
Tasks which are next-step executed (hereafter known as target tasks) simply terminate, and no break occurs.
Even if a break occurs, it may occur during processing after sta_tsk is issued for the next target task (or a task
sharing a task with the target task).
Even if no break has occurred, it may occur by selecting
"Execute(X)
menu bar in the main window.
→
Stop"
or
"Execute
→
Stop"
in the
(2) Be careful with next-step execution of tasks for which ter_tsk can be performed.
If ter_tsk is performed during next-step execution, the target task simply terminates and no break occurs.
Even if a break occurs, it may occur during processing after sta_tsk is issued for the next target task (or a task
sharing a task with the target task).
Even if no break has occurred, a break may occur by selecting
"Execute(X)
the menu bar in the main window.
→
Stop"
or
"Execute
→
Stop"
in
(3) Next-step execution may not function appropriately during RX processing.
A break may occur inside a subroutine.
5.2
Reserved Words
Symbols reserved by the RX850 and RD850 are listed below.
5.2.1
RX definition symbols
The RX and RX configurators are defined as external symbols, and are referenced by the RD850.
RX850*
Sit*
SysIntEnt
RX system call name
5.2.2
Cautions on program creation for RD850 users
To realize useful debugging functions using the RX850 for the RD850, the RX850 and RD850 have reserved
symbols (see section
5.2.1 RX definition symbols
).
Using symbols that have the same name as these reserved symbols will interfere with the debugging functions of
the RD850.
Do not use the reserved symbols of the RX and RD850 in user programs.