xedbg
Which error message comes out (from down in the stack) at the point of failure? Edit: If you are using the mEDBG with TPI on that Xplained Nano... then the...
For a start, this output here: `get parameter (scope 0x12, section 1, parm 32)` indicates that it is attempting to read the "mega programming clock" - this is not relevant...
Yes, indeed :/ There are housekeeping calls which need to be made on the general-purpose debuggers, but many of those are optional on the mEDBG on kits. So working with...
Well, technically these are three separate protocols in parallel: ISP on 0x11, TPI on 0x14 and all-the-rest on 0x12... so something is fishy in there, probably as a result of...
Yes - all of these tools are equivalent in the way they work with PIC/AVR/MIPS/PIC32C/SAM
> > Yes - all of these tools are equivalent in the way they work with PIC/AVR/MIPS/PIC32C/SAM > > So basically PICKit 5, MPLAB ICD 5 and MPLAB ICE 4...
Not quite right, but close. AVR generations refer primarily to the codebase architecture and not the hardware directly and uses the 'n'G notation as you see in the pack changelogs....
My classification accounts for legacy Atmel debuggers. (There is no relationship between "GEN5" and "5G")
Hi @ygoe When you install Python you have the option to "add scripts folder to path" which is the trick you missed. Many tools (like pymcuprog) install with a small...
you can just install it in "editable mode" by changing to your git source folder and using: `pip install -e .`