XMega PDI_ICE Memory Breakpoints

Memory Breakpoints implemented now!

rh
Administrator
Avatar
Gender:
Location: Germany
Age: 24
Homepage: e-lab.de
Posts: 5558
Registered: 03 / 2002
Subject:

XMega PDI_ICE Memory Breakpoints

 · 
Posted: 30.03.2014 - 23:42  ·  #1
@all,
the AVRco dongle ISP3-USB and ISP3-X now support memory breakpoints
with PDI debugging of XMegas.
Because of the limited PDI debug resources in the XMegas it is not possible
to have a code breakpoint at the same time with a memory breakpoint.

This is supported:
1..2 code breakpoints, no memory breakpoint
or
1 memory breakpoint, no code breakpoint

Of course the source can contain any count of programmed breakpoints:
"Debug_Break".

A memory breakpoint for example helps to find out an unexpected access to
any byte in the IO and SRAM area. Not usable with EEprom.
Sometimes a bug in the code can destroy/overwrite memory locations and
this is very hard to find what the reason for this is. Placing a memory breakpoint
onto such a location and this location is accessed, read, write or both, the
program is immediately halted on the following opcode and the reason for
this access can be found.

Attention:
These function can only be used when the ISP3 dongle/ICE has the latest firmware!!
REV 140330_xxxx.pupd

rolf
Attachments
Memory Breakpoint Dialog
Filename: MemBreakDlg.jpg
Filesize: 36.8 KB
Title: Memory Breakpoint Dialog
Download counter: 147
opens the Memory Breakpoint dialog
Filename: MemBreakBtn.jpg
Filesize: 4.21 KB
Title: opens the Memory Breakpoint dialog
Download counter: 139
Selected quotes for multi-quoting:   0

Registered users in this topic

Currently no registered users in this section

The statistic shows who was online during the last 5 minutes. Updated every 90 seconds.
MySQL Queries: 15 · Cache Hits: 15   38   53 · Page-Gen-Time: 0.01898s · Memory Usage: 2 MB · GZIP: on · Viewport: SMXL-HiDPI