Closed urjaman closed 11 months ago
The patch is up (and i'm on a train) -- the device datasheet actually says two hardware breakpoints, but makes no mention of data vs code.
I loaded up that project for debugging in Microchip (ugh) Studio (yeah you can do that, you just need to configure avr-gcc for -gdwarf-2 ...), and tried to set the same data breakpoint:
I think that answer that, there are no data breakpoints for ATtiny3217. Now i need to investigate how to make avarice expose that properly to gdb..
So i've figured this stuff out; i'll be reporting the details in a (WIP) PR, no point to leave this dangling, so closing.
Okay, so, i added support for attiny3217, and the first thing i tried to do was to watch a global 8-bit variable and run, like this:
Meanwhile avarice reported this:
That EDBG documentation lists that response as AVR8_FAILURE_ILLEGAL_BREAKPOINT
so I'm assuming UPDI just can't do this (or we're doing it wrong)?
The EDBG doc says UPDI supports one breakpoint, but i'm not sure if it can be a data watchpoint, and then, slot=2 sounds wrong... I dont' have the time to investigate further right now, but wanted to just put this out ASAP.
(Meanwhile i'll put the attiny3217 support patch up...)