microchip-pic-avr-tools / pyedbglib Goto Github PK

i wonder what the best way is to ask a question? I do not have an issue but more some questions about API usage.
i would like to use the debug functions from avr8protocol.
like step,run, etc. but i have no idea how to setup a session so i can use these commands.

With this library being able to talk to a debugger probe like the mEDGB et cetera, does Microchip have plans to create another program that opens up a GDB server and uses this library to facilitiate the low-level debugging?

I've seen something like this in the ATMega4809 + UPDI configuration at https://github.com/stemnic/pyAVRdbg/blob/master/main.py, but it's definitely not feature-complete or working for all MCUs.

I was specifically thinking about the ATMega328P XPlained-mini, which has a mEDGB probe on-board and could speak debugWire to the ATMega328P.

pip 23.2 is issuing the following warning.

DEPRECATION: pyedbglib 2.22.0.7 has a non-standard dependency specifier pyserial>=3.5*. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of pyedbglib or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at pypa/pip#12063

Think it is an issue that is going to give problems later, if it is not addressed?

I use MPLAB SNAP. And i try pymcuprog ping
But i can not connect. Mainly because the used device is not a HID device.
So is there something i miss? Is it a bug? Has this been actual tested with MPLAB SNAP ?

It seems that the function activate_physical is broken when called for an Xmega device and all other instances where the command CMD_AVR8_ACTIVATE_PHYSICAL does not actually return a device ID. The culprit is very likely found in the lines 296/297 where the device ID is logged despite being checked to not be there (if not device_id).