AVRDUDE not erasing locked UPDI device #1124

avrfreak · 2022-10-12T12:26:55Z

I am using avrdude with a Microchip Snap Debugger as a UPDI programmer only (no debugging).
Everything works really well with the SNAP programmer with only one exception:
If you program the lock bits, you can no longer access the target device using avrdude.

The same thing happens when using jtag2updi as the programmer. This is avrdude related and not a hardware issue.

Here is the error log:

C:\Test_Snap>avrdude -C avrdude.conf -c snap_updi -p avr64db28 -P usb -B 0.2 -e -U flash:w:test.hex:a -U eeprom:w:test.eep:a
avrdude: usbhid_open(): No device found

         Vtarget                      : 3.11 V
         JTAG clock megaAVR/program   : 1000 kHz
         JTAG clock megaAVR/debug     : 100 kHz
         PDI/UPDI clock Xmega/megaAVR : 5000 kHz

avrdude: AVR device initialized and ready to accept instructions

Reading |                                                    | 0% 0.00s
avrdude:
Device is locked! Chip erase required to unlock.
avr_read(): error reading address 0x0000
    read operation failed for memory "signature"
avrdude: error reading signature data for part "AVR64DB28", rc=-68
avrdude: Received FamilyID: "AVR    "
avrdude: Expected FamilyID: ""
         Double check chip, or use -F to override this check.

avrdude done.  Thank you.
`

to program the same device when the target is not locked is working:

`
C:\Test_Snap>avrdude -C avrdude.conf -c snap_updi -p avr64db28 -P usb -B 0.2 -e -U flash:w:test.hex:a -U eeprom:w:test.eep:a
avrdude: usbhid_open(): No device found

         Vtarget                      : 3.02 V
         JTAG clock megaAVR/program   : 1000 kHz
         JTAG clock megaAVR/debug     : 100 kHz
         PDI/UPDI clock Xmega/megaAVR : 5000 kHz

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.07s

avrdude: Device signature = 0x1e9619 (probably avr64db28)
avrdude: erasing chip
avrdude: reading input file "test.hex"
avrdude: input file test.hex auto detected as Intel Hex
avrdude: writing flash (13036 bytes):

Writing | ################################################## | 100% 0.73s

avrdude: 13036 bytes of flash written
avrdude: verifying flash memory against test.hex:
avrdude: input file test.hex auto detected as Intel Hex

Reading | ################################################## | 100% 0.48s

avrdude: 13036 bytes of flash verified
avrdude: reading input file "test.eep"
avrdude: input file test.eep auto detected as Intel Hex
avrdude: writing eeprom (32 bytes):

Writing | ################################################## | 100% 0.16s

avrdude: 32 bytes of eeprom written
avrdude: verifying eeprom memory against test.eep:
avrdude: input file test.eep auto detected as Intel Hex

Reading | ################################################## | 100% 0.07s

avrdude: 32 bytes of eeprom verified

avrdude done.  Thank you.

The text was updated successfully, but these errors were encountered:

mcuee · 2022-10-13T01:30:36Z

Looks like -e does not work as per designed. Strange.

Reference comment from:

Use byte-wise read/write when page size is 1 in terminal cache #1121 (comment)

MCUdude · 2022-10-13T06:19:24Z

Thanks for reporting @avrfreak!

I'm able to reproduce the issue, and it seems to be a problem on all UPDI parts, since, unlike classic AVRs, they don't reveal their device signature when locked.

As a temporary solution, you can add the -F flag to force erasing even though Avrdude.

$ ./avrdude -cpkobn_updi -p avr64dd32 -e

         Vtarget                      : 3.31 V
         PDI/UPDI clock Xmega/megaAVR : 100 kHz
avrdude: AVR device initialized and ready to accept instructions

Reading |                                                    | 0% 0.00savrdude: Device is locked! Chip erase required to unlock.
avr_read_mem(): error reading address 0x0000
    read operation failed for memory signature
avrdude: error reading signature data for part "AVR64DD32", rc=-3
avrdude: Received FamilyID: "AVR    "
avrdude: Expected FamilyID: ""
         Double check chip, or use -F to override this check.

avrdude done.  Thank you.



$ ./avrdude -cpkobn_updi -p avr64dd32 -e -F

         Vtarget                      : 3.31 V
         PDI/UPDI clock Xmega/megaAVR : 100 kHz
avrdude: AVR device initialized and ready to accept instructions

Reading |                                                    | 0% 0.00savrdude: Device is locked! Chip erase required to unlock.
avr_read_mem(): error reading address 0x0000
    read operation failed for memory signature
avrdude: error reading signature data for part "AVR64DD32", rc=-3
avrdude: Received FamilyID: "AVR    "
avrdude: Expected FamilyID: ""
avrdude: erasing chip

Reading | ################################################## | 100% 0.01s

avrdude: Device signature = 0x1e961a (probably avr64dd32)

avrdude done.  Thank you.

MCUdude · 2022-10-13T06:28:40Z

However, there is a pattern here we can look for to determine that we're dealing with a locked chip.
We do get the avrdude: AVR device initialized and ready to accept instructions message which indicated that we in fact can communicate with the chip. We also know that we're dealing with a chip with UPDI. Since no chip can have a signature of 0x000000, it means that the chip has to be locked and avrdude should force a reset command as long as the -e flag is passed.

This would be the logic we'll ve to implement:

No communication with the target but the programmer is initialized?
- Target has UPDI?
  - -e flag passed?
    - [Force erase command]

(Note that this can only be applied for chips with UPDI. The Arduino as ISP programmer has a "bug" that results in an avrdude: AVR device initialized and ready to accept instructions message for classic AVRs, regardless if there is communication with the target or not.

MCUdude · 2022-10-13T06:44:14Z

The SerialUPDI programmer has a slightly different output and forcing the erase command doesn't work at all for JTAG2UPDI.

SerialUPDI output

$ ./avrdude -cserialupdi -p atmega4808 -e

avrdude: UPDI link initialization OK
avrdude: Device is locked
avrdude: NVM type 0: 16-bit, page oriented write
avrdude: Entering NVM programming mode
avrdude: Timeout waiting for device to unlock
avrdude: Failed to enter NVM programming mode: device is locked
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x000000 (retrying)

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x000000 (retrying)

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x000000
avrdude: Yikes!  Invalid device signature.
         Double check connections and try again, or use -F to override
         this check.

avrdude: Leaving NVM programming mode

avrdude done.  Thank you.



$ ./avrdude -cserialupdi -p atmega4808 -e -F

avrdude: UPDI link initialization OK
avrdude: Device is locked
avrdude: NVM type 0: 16-bit, page oriented write
avrdude: Entering NVM programming mode
avrdude: Timeout waiting for device to unlock
avrdude: Failed to enter NVM programming mode: device is locked
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x000000 (retrying)

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x000000 (retrying)

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x000000
avrdude: Yikes!  Invalid device signature.
avrdude: Expected signature for ATmega4808 is 1E 96 50
avrdude: erasing chip
avrdude: Device is locked
avrdude: Attempting device erase
avrdude: Leaving NVM programming mode

avrdude done.  Thank you.



$ ./avrdude -cserialupdi -p atmega4808

avrdude: UPDI link initialization OK
avrdude: NVM type 0: 16-bit, page oriented write
avrdude: Entering NVM programming mode
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x1e9650 (probably m4808)
avrdude: Leaving NVM programming mode

avrdude done.  Thank you.

JTAG2UPDI output

$ ./avrdude -cjtag2updi -p atmega4808 -e -F

avrdude: AVR device initialized and ready to accept instructions

Reading |                                                    | 0% 0.00savrdude: jtagmkII_program_enable(): bad response to enter progmode command: RSP_ILLEGAL_MCU_STATE
avrdude: jtagmkII_program_enable(): bad response to enter progmode command: RSP_ILLEGAL_MCU_STATE
avrdude: jtagmkII_read_byte(): bad response to read memory command: RSP_ILLEGAL_MCU_STATE
avr_read_mem(): error reading address 0x0000
    read operation not supported for memory signature
avrdude: error reading signature data for part "ATmega4808", rc=-2
avrdude: error reading signature data, rc=-2
avrdude: jtagmkII_program_disable(): bad response to leave progmode command: RSP_ILLEGAL_MCU_STATE

avrdude done.  Thank you.

avrfreak · 2022-10-13T06:44:33Z

When reading the ASI System Status register of a locked UPDI mcu, the response will be 0x83 (Lockstatus = 1). I believe the erase method & key is the same for all UPDI chips. I checked into this a few months back when I was getting sick and tired of having to erase the device with Studio7 every time. All that needs to be done is to send the erase key, and then a reset instruction. I did this on an ATtiny2313. It just erases and nothing else. I wouldn't know how to modify & compile avrdude.

MCUdude · 2022-10-13T07:33:19Z

All that needs to be done is to send the erase key, and then a reset instruction.

Sounds reasonable. However, when looking at the ASI System Status register, it's not obvious to me why it would return 0x83 when locked. We should probably check the least significant bit instead since this is the bit that indicates if the part is locked or not.

MCUdude · 2022-10-13T07:46:50Z

I've taken a closer look at the root cause. The main problem is that the function avr_unlock isn't ran. This is caused by avr_signature, since this returns 0 (LIBAVRDUDE_SUCCESS) when reading the "valid" signaure that is 0x000000. This skips the entire unlock logic that's already there. I may be able to come up with a hacky solution, but @stefanrueger usually has clever ideas on how problems like this can be solved in an elegant way.

avrdude/src/main.c

Lines 1186 to 1232 in e14e5d2

    
           sig_again: 
        
             usleep(waittime); 
        
             if (init_ok) { 
        
               rc = avr_signature(pgm, p); 
        
               if (rc != LIBAVRDUDE_SUCCESS) { 
        
                 if (rc == LIBAVRDUDE_SOFTFAIL && (p->prog_modes & PM_UPDI) && attempt < 1) { 
        
                   attempt++; 
        
                   if (pgm->read_sib) { 
        
                      // Read SIB and compare FamilyID 
        
                      char sib[AVR_SIBLEN + 1]; 
        
                      pgm->read_sib(pgm, p, sib); 
        
                      avrdude_message(MSG_NOTICE, "%s: System Information Block: \"%s\"\n", 
        
                                      progname, sib); 
        
                     if (quell_progress < 2) 
        
                       avrdude_message(MSG_INFO, "%s: Received FamilyID: \"%.*s\"\n", progname, AVR_FAMILYIDLEN, sib); 
        
                     if (strncmp(p->family_id, sib, AVR_FAMILYIDLEN)) { 
        
                       avrdude_message(MSG_INFO, "%s: Expected FamilyID: \"%s\"\n", progname, p->family_id); 
        
                       if (!ovsigck) { 
        
                         avrdude_message(MSG_INFO, "%sDouble check chip, " 
        
                                 "or use -F to override this check.\n", 
        
                                 progbuf); 
        
                         exitrc = 1; 
        
                         goto main_exit; 
        
                       } 
        
                     } 
        
                   } 
        
                   if(erase) { 
        
                     erase = 0; 
        
                     if (uflags & UF_NOWRITE) { 
        
                       avrdude_message(MSG_INFO, "%s: conflicting -e and -n options specified, NOT erasing chip\n", 
        
                                       progname); 
        
                     } else { 
        
                       if (quell_progress < 2) 
        
                         avrdude_message(MSG_INFO, "%s: erasing chip\n", progname); 
        
                       exitrc = avr_unlock(pgm, p); 
        
                       if(exitrc) goto main_exit; 
        
                       goto sig_again; 
        
                     } 
        
                   } 
        
                 } 
        
                 avrdude_message(MSG_INFO, "%s: error reading signature data, rc=%d\n", 
        
                   progname, rc); 
        
                 exitrc = 1; 
        
                 goto main_exit; 
        
               } 
        
             }

MCUdude · 2022-10-13T10:18:38Z

OK, I totally fell down the rabbit hole. I'll submit a PR, and then we can discuss the solution I've come up with

Resolves issue avrdudes#1124

avrfreak · 2022-10-14T01:04:32Z

avrdude_message(MSG_INFO, "%s: Received FamilyID: "%.*s"\n", progname, AVR_FAMILYIDLEN, sib);

Yes you are right to just check bit 0. I just did a quick erase program to fill my needs. I found that every device I tested either returns 0x82 (10000010) or 0x83 (10000011). Strange how only bit 1 & bit 7 read as 1 while the other reserved (bit 6) reads 0.

I think if the lockstatus bit = 1, and the -e option is enabled, avrdude should just erase the chip. (not sure if this was already mentioned in the next thread. I will go over there now and have a look)

Thanks MCUdude

mcuee · 2022-10-16T11:26:03Z

The SerialUPDI programmer has a slightly different output and forcing the erase command doesn't work at all for JTAG2UPDI.

Oops, I did not read this properly. Now I need to learn how to use Microchip SNAP with this Nano 4808 board.

PS C:\work\avr\avrdude_test\avrdude_bin> .\avrdude_pr1125 -c jtag2updi -P COM13 -p atmega4808 -qq -t
avrdude> dump lock
>>> dump lock
0000  c5                                                |.               |

avrdude> dump signature
>>> dump signature
0000  1e 96 50                                          |..P             |

avrdude> write lock 0 0xc6
>>> write lock 0 0xc6
avrdude> flush
>>> flush
avrdude> dump lock
>>> dump lock
0000  c6                                                |.               |

avrdude> quit
>>> quit
avrdude_pr1125.exe: jtagmkII_reset(): bad response to reset command: RSP_ILLEGAL_MCU_STATE
avrdude_pr1125.exe: jtagmkII_close(): bad response to sign-off command: RSP_ILLEGAL_MCU_STATE

PS C:\work\avr\avrdude_test\avrdude_bin> .\avrdude_pr1125 -c jtag2updi -P COM13 -p atmega4808 -qq -F -e
avrdude_pr1125.exe: jtagmkII_reset(): bad response to reset command: RSP_ILLEGAL_MCU_STATE
avrdude_pr1125.exe: initialization failed, rc=-1
avrdude_pr1125.exe: Yikes!  Invalid device signature.
avrdude_pr1125.exe: Expected signature for ATmega4808 is 1E 96 50
avrdude_pr1125.exe: jtagmkII_close(): bad response to sign-off command: RSP_ILLEGAL_MCU_STATE

mcuee · 2022-10-16T12:52:20Z

@MCUdude
Somehow I can not get PR #1125 to work even with Microchip SNAP.

Connection as per the pinout from your MegaCoreX and SNAP user guide (Section 10.3.2, DS50002787C-page 38 )
https://github.com/MCUdude/MegaCoreX#nano-4808
https://ww1.microchip.com/downloads/en/DeviceDoc/50002787C.pdf

SNAP Pin -- Nano 4808 Pin
2 (TVDD) -- 3.3V
3 (GND) -- GND
4 (PGD) -- UPDI

PS C:\work\avr\avrdude_test\avrdude_bin> .\avrdude_pr1125.exe -c snap_updi -p atmega4808 -e
avrdude_pr1125.exe: usbhid_open(): No device found

                    Vtarget                      : 3.33 V
                    JTAG clock megaAVR/program   : 1000 kHz
                    JTAG clock megaAVR/debug     : 100 kHz
                    PDI/UPDI clock Xmega/megaAVR : 100 kHz
avrdude_pr1125.exe: initialization failed, rc=-1
                    Double check connections and try again, or use -F to override
                    this check.


avrdude_pr1125.exe done.  Thank you.

PS C:\work\avr\avrdude_test\avrdude_bin> .\avrdude_pr1125.exe -c snap_updi -p atmega4808 -e -F
avrdude_pr1125.exe: usbhid_open(): No device found

                    Vtarget                      : 3.33 V
                    JTAG clock megaAVR/program   : 1000 kHz
                    JTAG clock megaAVR/debug     : 100 kHz
                    PDI/UPDI clock Xmega/megaAVR : 100 kHz
avrdude_pr1125.exe: initialization failed, rc=-1
avrdude_pr1125.exe: AVR device initialized and ready to accept instructions
avrdude_pr1125.exe: Device signature = 0x000000 (retrying)
avrdude_pr1125.exe: Device signature = 0x000000 (retrying)
avrdude_pr1125.exe: Device signature = 0x000000
avrdude_pr1125.exe: Yikes!  Invalid device signature.
avrdude_pr1125.exe: Expected signature for ATmega4808 is 1E 96 50

avrdude_pr1125.exe done.  Thank you.

Edit to add: I will try out the modification mentioned here (remove pull-down R48 and add external pull-up resistor to the SNAP). I have another Nano 4808 so I can test whether the connection is good there or not.
http://ww1.microchip.com/downloads/en/DeviceDoc/ETN36_MPLAB%20Snap%20AVR%20Interface%20Modification.pdf

mcuee · 2022-10-16T13:08:48Z

@avrfreak Just wondering if you can test PR #1125 with your SNAP as well, thanks.

avrfreak · 2022-10-16T15:14:27Z

what is the fix another avrdude version?

MCUdude · 2022-10-16T15:59:13Z

Works with my (modified) SNAP:

$ ./avrdude -csnap_updi -patmega4808
avrdude: usbhid_open(): No device found

         Vtarget                      : 5.05 V
         JTAG clock megaAVR/program   : 1000 kHz
         JTAG clock megaAVR/debug     : 100 kHz
         PDI/UPDI clock Xmega/megaAVR : 100 kHz
avrdude: AVR device initialized and ready to accept instructions

Reading |                                                    | 0% 0.00savrdude: Device is locked! Chip erase required to unlock.
avr_read_mem(): error reading address 0x0000
    read operation failed for memory signature
avrdude: error reading signature data for part "ATmega4808", rc=-3
avrdude: Received FamilyID: "megaAVR"
         Double check chip, or use -F to override this check.

avrdude done.  Thank you.



$ ./avrdude -csnap_updi -patmega4808 -e
avrdude: usbhid_open(): No device found

         Vtarget                      : 5.06 V
         JTAG clock megaAVR/program   : 1000 kHz
         JTAG clock megaAVR/debug     : 100 kHz
         PDI/UPDI clock Xmega/megaAVR : 100 kHz
avrdude: AVR device initialized and ready to accept instructions

Reading |                                                    | 0% 0.00savrdude: Device is locked! Chip erase required to unlock.
avr_read_mem(): error reading address 0x0000
    read operation failed for memory signature
avrdude: error reading signature data for part "ATmega4808", rc=-3
avrdude: Received FamilyID: "megaAVR"
avrdude: erasing chip

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e9650 (probably m4808)

avrdude done.  Thank you.

mcuee · 2022-10-16T23:33:04Z

what is the fix another avrdude version?

With PR #1125, you can get the binary from github action.
https://github.com/avrdudes/avrdude/actions/runs/3242268904

For example, 32bit mingw build here.
https://github.com/avrdudes/avrdude/suites/8756501063/artifacts/396837252
64bit mingw build here.
https://github.com/avrdudes/avrdude/suites/8756501063/artifacts/396837255

avrfreak · 2022-10-17T01:45:59Z

does not work at all.

C:\avrdude-mingw-x86_64>avrdude -C avrdude.conf -c snap_updi -p avr128db28 -P usb -B 0.2 -e -U flash:w:test.hex:a -U eeprom:w:test.eep:a
avrdude: usbhid_open(): No device found

         Vtarget                      : 4.98 V
         JTAG clock megaAVR/program   : 1000 kHz
         JTAG clock megaAVR/debug     : 100 kHz
         PDI/UPDI clock Xmega/megaAVR : 5000 kHz

the same programmer works with the previous version but won't program a locked chip.

MCUdude · 2022-10-17T05:53:58Z

@avrfreak the programmer issue is not related to this PR. But if you look at the Avrdude output, you can see that you've set the UPDI clock to 5000kHz. That won't work fore sure! Try using -B4 or similar instead of -B0.2

mcuee · 2022-10-17T07:14:40Z

@MCUdude and @stefanrueger

BTW, the avrdude: usbhid_open(): No device found message is a false alarm. We should downgrade that.

Right now the codes look through different USB PIDs and for sure will print out this error message. We should only print out this as an error message when all three USB PIDs are not found.

https://github.com/avrdudes/avrdude/pull/791/files

mcuee · 2022-10-17T11:19:20Z

@MCUdude

Once I modify the SNAP as per Microchip ETN36, yes I can confirm the temp workaround works (-F -e).

PS C:\work\avr\avrdude_test\avrdude_bin> .\avrdude_git -c snap_updi -p m4808 -F -e
avrdude_git.exe: usbhid_open(): No device found

                 Vtarget                      : 4.65 V
                 JTAG clock megaAVR/program   : 1000 kHz
                 JTAG clock megaAVR/debug     : 100 kHz
                 PDI/UPDI clock Xmega/megaAVR : 100 kHz
avrdude_git.exe: AVR device initialized and ready to accept instructions

Reading |                                                    | 
0% 0.00savrdude_git.exe: Device is locked! Chip erase required to unlock.
avr_read_mem(): error reading address 0x0000
    read operation failed for memory signature
avrdude_git.exe: error reading signature data for part "ATmega4808", rc=-3
avrdude_git.exe: Received FamilyID: "megaAVR"
avrdude_git.exe: erasing chip

Reading | ################################################## | 100% 0.02s

avrdude_git.exe: Device signature = 0x1e9650 (probably m4808)

avrdude_git.exe done.  Thank you.

mcuee · 2022-10-17T11:22:52Z

@MCUdude

And PR #1125 fixed the issue. Tested with SNAP.

PS C:\work\avr\avrdude_test\avrdude_bin> .\avrdude_pr1125 -c snap_updi -p m4808
avrdude_pr1125.exe: usbhid_open(): No device found

                    Vtarget                      : 4.65 V
                    JTAG clock megaAVR/program   : 1000 kHz
                    JTAG clock megaAVR/debug     : 100 kHz
                    PDI/UPDI clock Xmega/megaAVR : 100 kHz
avrdude_pr1125.exe: AVR device initialized and ready to accept instructions

Reading |                                                    | 
0% 0.00savrdude_pr1125.exe: Device is locked! Chip erase required to unlock.
avr_read_mem(): error reading address 0x0000
    read operation failed for memory signature
avrdude_pr1125.exe: error reading signature data for part "ATmega4808", rc=-3
avrdude_pr1125.exe: Received FamilyID: "megaAVR"
                    Double check chip, or use -F to override this check.

avrdude_pr1125.exe done.  Thank you.

PS C:\work\avr\avrdude_test\avrdude_bin> .\avrdude_pr1125 -c snap_updi -p m4808 -e
avrdude_pr1125.exe: usbhid_open(): No device found

                    Vtarget                      : 4.65 V
                    JTAG clock megaAVR/program   : 1000 kHz
                    JTAG clock megaAVR/debug     : 100 kHz
                    PDI/UPDI clock Xmega/megaAVR : 100 kHz
avrdude_pr1125.exe: AVR device initialized and ready to accept instructions

Reading |                                                    | 
0% 0.00savrdude_pr1125.exe: Device is locked! Chip erase required to unlock.
avr_read_mem(): error reading address 0x0000
    read operation failed for memory signature
avrdude_pr1125.exe: error reading signature data for part "ATmega4808", rc=-3
avrdude_pr1125.exe: Received FamilyID: "megaAVR"
avrdude_pr1125.exe: erasing chip

Reading | ################################################## | 100% 0.02s

avrdude_pr1125.exe: Device signature = 0x1e9650 (probably m4808)

avrdude_pr1125.exe done.  Thank you.

mcuee · 2022-10-17T11:52:29Z

ElTangas/jtag2updi#66 (comment)

Hello, due to the way "-F" and "-e" options operate in avrdude, jtag2updi can't currently unlock chips that way. You need to enter interactive mode "-F -t" and then use the "erase" command.

Note: You must build jtag2updi with DISABLE_HOST_TIMEOUT defined for terminal mode to work.

Indeed the trick by the author of jtag2updi works.

I was hoping no need to rebuild with DISABLE_HOST_TIMEOUT option but it did not work.

PS C:\work\avr\avrdude_test\avrdude_bin> echo "erase"  | .\avrdude_git -c jtag2updi -P COM4 -p m4808 -qq -F -t
avrdude_git.exe: jtagmkII_reset(): bad response to reset command: RSP_ILLEGAL_MCU_STATE
avrdude_git.exe: initialization failed, rc=-1
avrdude_git.exe: Yikes!  Invalid device signature.
avrdude_git.exe: Expected signature for ATmega4808 is 1E 96 50
avrdude> >>> erase
avrdude_git.exe: erasing chip
avrdude>

PS C:\work\avr\avrdude_test\avrdude_bin> echo "dump lock" | .\avrdude_git -c jtag2updi -P COM4 -p m4808 -qq  -t
avrdude> >>> dump lock
0000  c5                                                |.               |

avrdude>

mcuee · 2022-10-17T12:00:24Z

For jtag2updi, PR #1125 does not help but it does not make things worse either, it is the same as git main.

PS C:\work\avr\avrdude_test\avrdude_bin> echo "erase"  | .\avrdude_pr1125 -c jtag2updi -P COM4 -p m4808 -qq -t
avrdude_pr1125.exe: jtagmkII_reset(): bad response to reset command: RSP_ILLEGAL_MCU_STATE
avrdude_pr1125.exe: initialization failed, rc=-1
                    Double check connections and try again, or use -F to override
                    this check.

PS C:\work\avr\avrdude_test\avrdude_bin> echo "erase"  | .\avrdude_pr1125 -c jtag2updi -P COM4 -p m4808 -qq -F -t
avrdude_pr1125.exe: jtagmkII_reset(): bad response to reset command: RSP_ILLEGAL_MCU_STATE
avrdude_pr1125.exe: initialization failed, rc=-1
avrdude_pr1125.exe: Yikes!  Invalid device signature.
avrdude_pr1125.exe: Expected signature for ATmega4808 is 1E 96 50
avrdude> >>> erase
avrdude_pr1125.exe: erasing chip
avrdude>

Resolves issue avrdudes#1124

mcuee added the bug Something isn't working label Oct 12, 2022

MCUdude added a commit to MCUdude/avrdude that referenced this issue Oct 13, 2022

Fix issue where locked UPDI devices couldn't be erased

88dd393

Resolves issue avrdudes#1124

MCUdude mentioned this issue Oct 13, 2022

Fix UPDI erase when target is locked #1125

Merged

MCUdude added a commit to MCUdude/avrdude that referenced this issue Oct 13, 2022

Fix issue where locked UPDI devices couldn't be erased

bfec594

Resolves issue avrdudes#1124

stefanrueger linked a pull request Oct 17, 2022 that will close this issue

Fix UPDI erase when target is locked #1125

Merged

stefanrueger closed this as completed in #1125 Oct 17, 2022

MCUdude added a commit to MCUdude/avrdude that referenced this issue Oct 19, 2022

Fix issue where locked UPDI devices couldn't be erased

f3d1c06

Resolves issue avrdudes#1124

MCUdude added a commit to MCUdude/avrdude that referenced this issue Oct 20, 2022

Fix issue where locked UPDI devices couldn't be erased

3bf9db0

Resolves issue avrdudes#1124

MCUdude added a commit to MCUdude/avrdude that referenced this issue Oct 20, 2022

Fix issue where locked UPDI devices couldn't be erased

afe0af5

Resolves issue avrdudes#1124

MCUdude added a commit to MCUdude/avrdude that referenced this issue Oct 20, 2022

Fix issue where locked UPDI devices couldn't be erased

3ecca5d

Resolves issue avrdudes#1124

mcuee mentioned this issue Feb 5, 2024

New attiny404 unprogrammable (RSP_ILLEGAL_MCU_STATE) #1660

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

AVRDUDE not erasing locked UPDI device #1124

AVRDUDE not erasing locked UPDI device #1124

avrfreak commented Oct 12, 2022 •

edited by MCUdude

Loading

mcuee commented Oct 13, 2022 •

edited

Loading

MCUdude commented Oct 13, 2022

MCUdude commented Oct 13, 2022

MCUdude commented Oct 13, 2022

avrfreak commented Oct 13, 2022

MCUdude commented Oct 13, 2022

MCUdude commented Oct 13, 2022

MCUdude commented Oct 13, 2022

avrfreak commented Oct 14, 2022

mcuee commented Oct 16, 2022

mcuee commented Oct 16, 2022 •

edited

Loading

mcuee commented Oct 16, 2022

avrfreak commented Oct 16, 2022

MCUdude commented Oct 16, 2022

mcuee commented Oct 16, 2022

avrfreak commented Oct 17, 2022 •

edited by MCUdude

Loading

MCUdude commented Oct 17, 2022

mcuee commented Oct 17, 2022 •

edited

Loading

mcuee commented Oct 17, 2022 •

edited

Loading

mcuee commented Oct 17, 2022 •

edited

Loading

mcuee commented Oct 17, 2022

mcuee commented Oct 17, 2022

AVRDUDE not erasing locked UPDI device #1124

AVRDUDE not erasing locked UPDI device #1124

Comments

avrfreak commented Oct 12, 2022 • edited by MCUdude Loading

mcuee commented Oct 13, 2022 • edited Loading

MCUdude commented Oct 13, 2022

MCUdude commented Oct 13, 2022

MCUdude commented Oct 13, 2022

avrfreak commented Oct 13, 2022

MCUdude commented Oct 13, 2022

MCUdude commented Oct 13, 2022

MCUdude commented Oct 13, 2022

avrfreak commented Oct 14, 2022

mcuee commented Oct 16, 2022

mcuee commented Oct 16, 2022 • edited Loading

mcuee commented Oct 16, 2022

avrfreak commented Oct 16, 2022

MCUdude commented Oct 16, 2022

mcuee commented Oct 16, 2022

avrfreak commented Oct 17, 2022 • edited by MCUdude Loading

MCUdude commented Oct 17, 2022

mcuee commented Oct 17, 2022 • edited Loading

mcuee commented Oct 17, 2022 • edited Loading

mcuee commented Oct 17, 2022 • edited Loading

mcuee commented Oct 17, 2022

mcuee commented Oct 17, 2022

avrfreak commented Oct 12, 2022 •

edited by MCUdude

Loading

mcuee commented Oct 13, 2022 •

edited

Loading

mcuee commented Oct 16, 2022 •

edited

Loading

avrfreak commented Oct 17, 2022 •

edited by MCUdude

Loading

mcuee commented Oct 17, 2022 •

edited

Loading

mcuee commented Oct 17, 2022 •

edited

Loading

mcuee commented Oct 17, 2022 •

edited

Loading