KIT_TC1797_SK Infineon Technologies, KIT_TC1797_SK Datasheet - Page 30

• Manufacturer Part Number: KIT_TC1797_SK
• Description: KIT STARTER AUDO FUTURE TC1797
• Manufacturer: Infineon Technologies
• Series: Audo Futurer
• Type: MCUr

Specifications of KIT_TC1797_SK

• Contents: Board, Adapters, Cables, CD, Power Supply
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant
• For Use With/related Products: TC1797
• Other names: KITTC1797SKIN

Errata Sheet
Functional Deviations
interrupts are enabled before entry to Halt mode, or where interrupts are
temporarily enabled during Halt mode. In this case an interrupt may be latched
whilst the CPU is in Halt mode, and subsequently disabling interrupts during
Halt mode, by setting ICR.IE = 0
, will not prevent the interrupt from being
B
serviced immediately upon exit from Halt mode.
It should be noted that no corruption of the program flow is associated with this
issue and that it affects debugging only, primarily the debugger single-stepping
functionality. The problem may or may not be visible whilst debugging,
dependent upon the implementation of single-stepping by the debugger. If
single-stepping is implemented by the debugger setting Break-Before-Make
(BBM) breakpoints on all instructions except the next to be executed, then if this
problem occurs the next instruction when single-stepping will be the first
instruction of the interrupt handler. However, if single-stepping is implemented
by setting a Break-After-Make (BAM) breakpoint on the next instruction to be
executed, or a BBM breakpoint on the next but one instruction, the problem will
not be visible. In this case, when single-stepping, the interrupt handler will be
executed in its entirety before returning to the interrupted program flow and the
breakpoint being taken after the next instruction to be single-stepped.
Workaround
As described previously, this problem affects debug only and in this case the
taking of the interrupt immediately upon exit from Halt mode cannot be avoided
if the conditions to trigger the problem occur. However, the debugger single-
stepping functionality may be implemented in such a way that this problem does
not directly affect the user, as follows:
Upon first hitting a breakpoint, the debugger should read and hold the current
interrupt enable status from ICR.IE. Interrupts should then be disabled by
setting ICR.IE = 0
.
B
If the next debugger action is to single-step, a BAM breakpoint should be placed
on the next instruction to be executed and the CPU re-started. In this case a
previously latched interrupt may be serviced, but will not result in a further
breakpoint being flagged until the interrupt handler returns and the next
instruction intended to be single-stepped is executed.
Subsequent single-step operations may be implemented using any appropriate
method, since interrupts will be disabled before Halt mode is entered.
TC1797, EES-AC, ES-AC, AC
30/101
Rel. 1.3, 18.12.2009