avr_monitor_data_s Struct Reference
[Monitor Data]

---

Detailed Description

Data used by the target monitor to save registers and to do communication

Some advantages and disadvantages

• + Stack is separated from the application stack, if the application stack is corrupt the monitor can still run
• + The SP can be changed by the monitor

• - The monitor save and restore block becomes a little more complicated (larger code)

Todo:

jbirkler. One idea is to skip the regs in avr_monitor_data_t and only use a dedicated stack that can hold all registers too. The monitor entry and exit block should be a little simpler: -Push to get some temp working regs -Set SP to dedicated area -Push everything to dedicated area -Host knows in what order the monitor pushes things on the dedicated stack and can restore registers .

Data Fields

• avr_registers_t regs
• avr_hw_bp_flag_t hw_bp_flags
• uint8_t continue_cmd
• avr_breakpoint_t breakpoint [AVR_MONITOR_NUM_BREAKPOINTS]
• uint8_t stack [AVR_MONITOR_STACK_SIZE]

---

Field Documentation

avr_registers_t avr_monitor_data_s::regs

0x00: Saved registers

avr_hw_bp_flag_t avr_monitor_data_s::hw_bp_flags

0x25: Enabled hardware breakpoints, each bit correspond to a hw break point

uint8_t avr_monitor_data_s::continue_cmd

avr_monitor_run_mode_t

avr_breakpoint_t avr_monitor_data_s::breakpoint[AVR_MONITOR_NUM_BREAKPOINTS]

0x27: Software bp addresses. 0 if entry not used

uint8_t avr_monitor_data_s::stack[AVR_MONITOR_STACK_SIZE]

0x2F: Make sure the monitor stack is large enough. When the size is changed here, remember to also change the value used in the inline assembly. 15 bytes is used right now.

---