AVR16EB32 datasheet(19/46 Pages) MICROCHIP

19 / 46 page

AVR16EB32 Curiosity Nano

On-Board Debugger

User Guide

DS50003605B - 19

The figure below shows the monitoring of the Digital state of a mechanical switch connected to a

debug GPIO in the MPLAB Data Visualizer.

Figure 3-3. Monitoring Debug GPIO with MPLAB Data Visualizer

Debug GPIO channels are timestamped, so the resolution of DGI GPIO events is determined by the

resolution of the DGI Timestamp module.

Important: Although signal bursts of higher frequency can be captured, the

frequency range of signals for which debug GPIO can be used is up to about

2 kHz. Attempting to capture signals above this frequency will result in data

saturation and overflow, which may cause the DGI session to be aborted.

3.6.2

Timestamping

When captured by the debugger, DGI sources are timestamped. The timestamp counter

implemented in the Curiosity Nano debugger increments at a 2 MHz frequency, providing a

timestamp resolution of a half microsecond.

3.7

Device Configuration Protection

The on-board debugger on the AVR16EB32 Curiosity Nano has a protection mechanism intended

to prevent the MCU from being rendered unrecoverable, especially when using drag-and-drop

programming. Disabling the programming and debugging interface, or permanently locking

memories are features of some MCUs that are not conducive to evaluation on a development kit

platform.

The protection mechanism works by intercepting write operations to the relevant fuses and

conditionally masking the addresses and values written.

Info: The protection mechanism is intended to prevent making

accidental

irreversible changes. Users intentionally making irreversible changes do so at

their own risk.

AVR16EB32 Datasheet(PDF) 19 Page - Microchip Technology