xedbg

Its been a while since I used the native serial on rPi, but it has worked in past (admittedly its not under regression test). Have you followed the advice on...

Hi @kristofmulier, Yes, I saw this, and sorry for not responding. Our current strategy for binaries uses pyinstaller - as used in the iotprovision package - but we have not...

Hi @kristofmulier I know its probably not what you were expecting... but the iotprovision binary released today can be 'skinned' into an executable pymcuprog, if that is useful. https://github.com/microchip-pic-avr-tools/iotprovision-bin

@demetriopitasi Pymcuprog supports all AVR devices with UPDI interface, and all PIC devices for which a Curiosity Nano exists. So there are some PIC18 devices already: https://github.com/microchip-pic-avr-tools/pymcuprog/tree/main/pymcuprog/deviceinfo/devices Background: PIC devices...

Hi @paulskirk53 - pymcuprog allows for programming several segments in several sessions, and thus does not erase the device before programming. Before release 3.13 the solution from platformio was to...

Thanks for the input - logged as DSG-4313 We will have to take a closer look at this suggestion. Many users feel its most valuable to receive early feedback when...

@paulskirk53 - please verify which version of pymcuprog you are running since this --erase switch was added not long ago. `pymcuprog --version`

Indeed - you are right about the history, but its not political. It's just not a simple thing to change in the stack the way its constructed (its also the...

Hi @Kedarius I did have a look into this once on a fun-friday and found that it was quite a can-of-worms. pymcuprog started its life (and still is) a CICD...

Indeed - i see your problem... A fairly "cheap" solution might be to sub-class that exception and add a new member which contains the ID which is detected. It would...