mcuee
commented
1 year ago I tried the bootloader and it does not work either.
Then I tried the option without bootloader and now the board seems to be bricked. I will see how I can revive the board using PICKit 4 (HV UPDI).
It is my fault though as I did not notice that both the two options for reset requires HV UPDI programmer. Looks like a bug though to me.
PS C:\work\avr\avrdude_test\avrdude_bin> .\avrdude_git -c pkobn_updi -p avr64dd32 -v
avrdude_git: Version 7.0-20221026 (a101899)
Copyright (c) Brian Dean, http://www.bdmicro.com/
Copyright (c) Joerg Wunsch
System wide configuration file is C:\work\avr\avrdude_test\avrdude_bin\avrdude.conf
Using Port : usb
Using Programmer : pkobn_updi
avrdude_git: found CMSIS-DAP compliant device, using EDBG protocol
AVR Part : AVR64DD32
RESET disposition : dedicated
RETRY pulse : SCK
Serial program mode : yes
Parallel program mode : yes
Memory Detail :
Block Poll Page Polled
Memory Type Alias Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- -------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
fuse0 wdtcfg 0 0 0 0 no 1 1 0 0 0 0x00 0x00
fuse1 bodcfg 0 0 0 0 no 1 1 0 0 0 0x00 0x00
fuse2 osccfg 0 0 0 0 no 1 1 0 0 0 0x00 0x00
fuse4 tcd0cfg 0 0 0 0 no 1 1 0 0 0 0x00 0x00
fuse5 syscfg0 0 0 0 0 no 1 1 0 0 0 0x00 0x00
fuse6 syscfg1 0 0 0 0 no 1 1 0 0 0 0x00 0x00
fuse7 codesize 0 0 0 0 no 1 1 0 0 0 0x00 0x00
fuse8 bootsize 0 0 0 0 no 1 1 0 0 0 0x00 0x00
fuses 0 0 0 0 no 9 16 0 0 0 0x00 0x00
lock 0 0 0 0 no 4 1 0 0 0 0x00 0x00
tempsense 0 0 0 0 no 2 1 0 0 0 0x00 0x00
signature 0 0 0 0 no 3 1 0 0 0 0x00 0x00
prodsig 0 0 0 0 no 125 125 0 0 0 0x00 0x00
sernum 0 0 0 0 no 16 1 0 0 0 0x00 0x00
userrow usersig 0 0 0 0 no 32 32 0 0 0 0x00 0x00
data 0 0 0 0 no 0 1 0 0 0 0x00 0x00
eeprom 0 0 0 0 no 256 1 0 0 0 0x00 0x00
flash 0 0 0 0 no 65536 512 0 0 0 0x00 0x00
Programmer Type : JTAGICE3_UPDI
Description : Curiosity nano (nEDBG) in UPDI mode
ICE HW version : 0
ICE FW version : 1.23 (rel. 91)
Serial number : MC020019502HIP000484
Vtarget : 3.31 V
PDI/UPDI clock Xmega/megaAVR : 100 kHz
avrdude_git: bad response to AVR sign-on command: 0xa0
avrdude_git: retrying with external reset applied
avrdude_git: bad response to AVR sign-on command: 0xa0
avrdude_git: retrying with external reset applied
avrdude_git main() error: initialization failed, rc=-1
- double check the connections and try again
- use -B to set lower ISP clock frequency, e.g. -B 200kHz
- use -F to override this check
avrdude_git done. Thank you.
SpenceKonde
MCUdude
It's probably better to create a separate issue, so we can keep the discussion on point.
When helping out with the Avrdude project I found out that the existing, pre-compiled bootloaders bundled to DxCore didn't work properly with the new AVR-DD series. I'm able to establish a connection with the target, but I can't read and write to EEPROM or flash. The bootloader I'm using is
optiboot_dx64_ser0_alt_8sec.hexThe errors you're seeing below are outputted from the development version of Avrdude, but I'm getting the same result when using Avrdude 6.3.
Have you @SpenceKonde tried to get Optiboot to work on the AVR-DD series?
The pre-compiled bootloader hex file I'm using is generated by a command line tool called
srec_cat, and is not a "real" program, but is only used as a test to see if the bootloader is actually able to do its job. It's a file containing 32256 0xAA's, starting from address 512.srec_cat -generate 0x200 0x8000 -repeat_data 0xaa -o 0xaa_32256b.hex -IntelHere are the fuse settings:
I can establish communication with the bootloader:
But I can't write anything to memory.
EEPROM:
Flash: