Instructions with
full resolution
(2 Ps)
Branch on
0
1
2
Instructions with
lower resolution
(6 Ps)
Instructions with
lower resolution
(6 Ps)
Instructions with
lower resolution
(6 Ps)
Change conditional
conditional address
address
Change conditional
address
Change conditional
address
N2HET Functional Description
962
SPNU563A – March 2018
Copyright © 2018, Texas Instruments Incorporated
High-End Timer (N2HET) Module
Figure 23-5. Multi-Resolution Operation Flow Example
23.2.1.7 Debug Capability
The N2HET supports breakpoints to allow you to more easily debug your N2HET program.
provides an illustration of the breakpoint mechanism.
The steps to enable an N2HET breakpoint are:
1. Make sure the device nTRST pin is high, since N2HET breakpoints are disabled whenever this pin is
low. (Normally this is handled automatically when a JTAG debugger is attached).
2. Attach a JTAG debugger and connect to the device that has been already programmed with the
N2HET code that needs to debugged. (downloading to on-chip flash is outside the scope of this
section).
3. Execute the CPU program at least until the point where the N2HET program RAM has been initialized
by the CPU.
4. Open a memory window in the N2HET registers.
5. Make sure HETEXC2.DEBUGSTATUSFLAG bit is cleared.
6. Open a memory window on the N2HET RAM
7. Set bit 22 in the program field of the instruction(s) on which you wish to break. Note that this instruction
will be executed
before
the N2HET is halted - slightly different from how CPU breakpoints behave.
8. Make sure the CPU and N2HET are running, if they are halted then restart the CPU through the JTAG
emulator (N2HET will start when the CPU starts).
9. Both the CPU and N2HET will halt when breakpoint is reached.
When the N2HET is halted, its state machines are frozen but all of the N2HET control registers can be
accessed through the JTAG emulator interface.
The current N2HET instruction address can be inspected by reading the HETADDR register; this should
be pointing to the instruction that caused the breakpoint.