Filter
Top Products
6 Troubleshooting
6.13 Debug operation has not worked well
Isn’t the resource of a Monitor Program used?
When using the resource of the Monitor Program in debug, a communication error or an
unexpected operation may occur. Therefore, note that the resource of the Monitor
Program should not be used.
a. Peripheral (Serial I/O)
The BUSY, SCLK, TxD and RxD pins are used for communications between the Target
MCU and KD30/KD3083. Do not connect a user I/O to these pins.
Related section: [5.4 Peripheral Function Related Limitations] 1)
b. SFR (UART association)
Do not modify registers associated with UARTi (including the port register and port
direction register allocated to the Serial I/O) on a User Program. When modifying ports
other than the serial port, modify it with the read-modify write instruction (BSET, BCLR,
etc.).
Related section: [5.2.2 A limitation item about the C language] (1) - (a)
c. RAM
Do not use a Monitor Program RAM on a User Program. The Monitor Program RAM is
allocated from the lowest-order address in RAM which the Target MCU has. However,
there is no Monitor Program RAM since R8C/Tiny has special debug RAM.
Related section: [5.3 Memory Map Limitations]
d. Flash ROM (Excluding Fixed Vector Table)
Do not overlap a User Program with a Monitor Program ROM. When the User Program
overlaps with the Monitor Program, the KD30/KD3083 indicate an error (Error 16256:
“The specified area includes the debugging monitor memory area.”).
Related section: [5.2.2 A limitation item about the C language] (1) - (c)
[5.3 Memory Map Limitations]
76