Replies: 45 comments 219 replies
-
Beta Was this translation helpful? Give feedback.
-
|
Great! I'm not sure if the new release will be v7.3 or v8.0; time will tell. Avrdude has become so powerful and versatile now, and I can't really imagine what kind of functionality would require an 8.0 bump. I'm really hoping that we can get some interest in #907, as this would be a really neat feature since it would remove the need to figure out the ever-changing COM port number on Windows or the often long and hard-to-remember path on Mac. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
@dl8dtl @MCUdude and @stefanrueger Just wondering if we want to have the avrdude 7.3 release by the end of the year (say Christmas time). It seems to me we have enough enhancements and bug fixes to have another release. |
Beta Was this translation helpful? Give feedback.
-
|
I got some avr16EB32 today. I can test avrdude v7.3 if needed. |
Beta Was this translation helpful? Give feedback.
-
|
You can download pre-built binaries for your system here, if you scroll a little. mingw or msvc should be OK for Windows I think |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for responding. Is there an exe for windows? I cannot build the program. |
Beta Was this translation helpful? Give feedback.
-
|
There should be an .exe file in the src folder 
|
Beta Was this translation helpful? Give feedback.
-
|
yes i found it thank yo |
Beta Was this translation helpful? Give feedback.
-
|
Regarding a major # bump, the general idea was to bump it if something (commandline handling, option defaults, config file) is going to be incompatible with the previous version. |
Beta Was this translation helpful? Give feedback.
-
|
A 7.3 release before the end of this year would be nice. Not as big as the 7.1->7.2 bump, but still great improvements overall. |
Beta Was this translation helpful? Give feedback.
-
|
Indeed it would be good to have some AVR EB chips to carry out the test. I am lazy to deal with raw chips but rather I prefer to buy the Curiosity Nano board for new chips when they are available (I have bought Curiosity Nano board for ATtiny1627, AVR128DB48, AVR64DD32 and AVR64EA48). Currently the board is not available for the AVR EB yet. |
Beta Was this translation helpful? Give feedback.
-
|
I have ordered samples from Microchip Direct, but it will take between 7 and 12 weeks for them to arrive. |
Beta Was this translation helpful? Give feedback.
-
|
Other than closing the current PRs, anything you have in mind before the avrdude 7.3 release? I think @stefanrueger mentioned the following improvement. And maybe further improvement on sigrow reading using AVRISP. |
Beta Was this translation helpful? Give feedback.
-
Perhaps map symbolic register names to |
Beta Was this translation helpful? Give feedback.
-
|
Just wondering if you still want to address the following issue in 7.3 release or deal with it later. |
Beta Was this translation helpful? Give feedback.
-
|
Depends. If I don't manage to do so within the next two weeks then I most likely won't be able to do so before 7.3 |
Beta Was this translation helpful? Give feedback.
-
|
No issues. I think we are okay to leave Issue #1537 after 7.3 release in case you do not have the time. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
I have now done all I wanted to do before the next release and plan to see the current PRs through to merging, including the contribution by @Ho-Ro. Will be going on hols for a couple of weeks from 5 Dec. As far as I am concerned, we could do a code freeze after the currently open PRs are merged and start testing. I'd be happy to address all occurring issues, if any, before Xmas, and would be available for a pre-Xmas release. Whaddya think @dl8dtl @MCUdude @mcuee @mariusgreuel? |
Beta Was this translation helpful? Give feedback.
-
|
... and if someone (different from me) wanted to take on #1582 during the code freeze that would be great, but not essential... |
Beta Was this translation helpful? Give feedback.
-
|
I want to create a new PR when #1574 is merged to support JTAG2 and JTAG3 programmers. It shouldn't be too much work I think. Apart from this, I'm fine with a "features freeze". |
Beta Was this translation helpful? Give feedback.
-
|
Good plans. Thanks. FYI: I will also be on holiday for about two weeks from 5-Dec-2023 to 18-Dec-2023. |
Beta Was this translation helpful? Give feedback.
-
|
Great. Now we are almost there other than @MCUdude's intention to continue the work of merged PR #1574 -- to add JTAG2 and JTAG3 support. |
Beta Was this translation helpful? Give feedback.
-
|
Sooo, I am preparing to merge the current batch of PRs. After which I'll put my feet up for everyone with some gear to test git main. There'll be an award for the most problems found (double points for seg faults). Then, once I get the green light I'll try to see whether I can cope with the notes that @dl8dtl left for releasing a new version 😄 |
Beta Was this translation helpful? Give feedback.
-
|
I should be able to carry out some simple tests over the weekend for the current PRs, since I will have access to the HW then. After that I can also give git main some tests with my programmers. |
Beta Was this translation helpful? Give feedback.
-
|
I tested v7.3, it just hangs like avrdude cannot find the com port. FYI I use a snap debugger connected to the USB port. I am using : avrdude -C avrdude.conf -c snap_updi -p avr32DD20 -B 4.0 -e -U flash:w:flash.hex:a -U eeprom:w:eep.hex:a I have a few AVR16EB32's to test with if anyone has any ideas why it's not working with my programmer. |
Beta Was this translation helpful? Give feedback.
-
|
@avrfreak Rework instruction: |
Beta Was this translation helpful? Give feedback.
-
|
Yes I have done the mod. The same programmer is working with V7.0 & V7.2 but does nothing with V7.3. |
Beta Was this translation helpful? Give feedback.
-
|
@avrfreak Based on your description of the issue, this is a regression from avrdude 7.2. Therefore, please help to provide the log for avrdude 7.2 as well. |
Beta Was this translation helpful? Give feedback.
-
|
Here are the logs you requested. The same programmer, device, wires, power, usb port was used with both avrdude versions. I just ran V7.3 then immediately ran V7.2. |
Beta Was this translation helpful? Give feedback.
-
|
I tried V7.3 a second time: |
Beta Was this translation helpful? Give feedback.
-
|
I don't use a Windows computer regulary, so I'm afraid I can't help here. Maybe @mcuee can provide a known good, statically linked binary for you? AFAIK there hasn't been any significant changes to USB implementation side of things since the 7.2 release, so it's weird that you're facing issues. Let's hope another binary will make it work. |
Beta Was this translation helpful? Give feedback.
-
|
I will create a new issue based on your reports. Let's continue the discussion there. |
Beta Was this translation helpful? Give feedback.
-
|
OK, git main is ready to be tested for the next release v7.3. Please do your worst (and remember finding seg faults gives double points!) @mcuee @MCUdude @dl8dtl @Ho-Ro . And remember, @SpenceKonde, speak now or hold your peace forever. |
Beta Was this translation helpful? Give feedback.
-
|
@askn37 |
Beta Was this translation helpful? Give feedback.
-
|
Currently, as far as I can see (macos/windows combination and various UPDI compatible products up to AVR-EA), I haven't found any practical concerns with avrdude-main. And AVR-EB hasn't arrived yet. That's all that's not confirmed at this point. |
Beta Was this translation helpful? Give feedback.
-
|
@askn37 Many thanks, and yes, please do some testing with the lastest git main! |
Beta Was this translation helpful? Give feedback.
-
|
I tested both versions msvc & mingw on windows 10 with a snap debugger as the programmer. They are both working with older Dx devices but not with the new AVREB. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, but then you can't switch back to AVR mode, which Avrdude requires. |
Beta Was this translation helpful? Give feedback.
-
|
I manually switched it back to avr mode |
Beta Was this translation helpful? Give feedback.
-
How did you manage to do this? |
Beta Was this translation helpful? Give feedback.
-
|
I used an older version of MPLAB IPE from another computer. I think only when the AVREB devices are programmed in the newest version of MPLAB IPE, the programmer is switched to PIC mode. In my case it stayed that way. When I tested it this morning, AVRDUDE V7.2 did not work after I programmed an AVR16EB until I used the programmer with an older version of MPLAB IPE. After that it worked with avrdude V7.0 & V7.2. I am not 100% sure on this, it seems strange that the programmer would be in PIC mode after programming an AVR device with the newest MPLAB IPE. I could do some more testing for every scenario but I do not want to brick the programmer! I seem to remember there was a way to select the mode from the menu (AVR Mode or PIC MODE) but I can't remember where I saw this MPLAB or AS7 or even which version??? |
Beta Was this translation helpful? Give feedback.
-
|
See #1596. I'm working on a solution for Avrdude. |
Beta Was this translation helpful? Give feedback.
-
1. Windows 10/11 x64 Test Results SummaryLast updated on 2024-02-01 MSYS2 mingw64 build (main binaries to test)
MSVC64 build (simple tests only)
Arduino avrdude-packing build (simple tests only)
2. Linux and macOS and tests summary: to be updatedmacOS (ARM64), Linux (x64 and Raspberry Pi OS): Simple tests Linux x86_64 : Ubuntu 20.04 64bit version. Simple tests only
Linux (Raspberry Pi OS on RPi 400, Debian 12 based) : Simple tests only
macOS 14.x (ARM64, mac Mini M1 2020): Simple tests only
macOS 14.x (x86_64 using Rosetta 2 emulation, mac Mini M1 2020) : Simple tests only
3. BSD platforms -- sanity check onlyFreeBSD 14 x86_64 virtual machine or Intel J4125 Mini PC physical machine
OpenBSD 7.4 x86_64 virtual machine or Intel N4500 Mini PC physical machine
NetBSD 9.3 x86_64 virtual machine
|
Beta Was this translation helpful? Give feedback.
-
|
Found one issue under macOS 14.3. |
Beta Was this translation helpful? Give feedback.
-
|
This one may be an issue with the test script. |
Beta Was this translation helpful? Give feedback.
-
|
I need to troubleshoot |
Beta Was this translation helpful? Give feedback.
-
|
It seems to me that there is a connection issue and now it is okay. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
I just committed two minor commits for README.md. |
Beta Was this translation helpful? Give feedback.
-
|
Not too sure if we want to mention FreeBSD and OpenBSD/NetBSD. |
Beta Was this translation helpful? Give feedback.
-
|
@dl8dtl |
Beta Was this translation helpful? Give feedback.
-
macOS tests summaryiMac 24-inch 2021 (ARM64) macOS 14.2.1
Configuration summary:General product test resultsArduino UNO WiFi Rev,2 : PASS Arduino Nano Every : PASS Arduino YUN Rev.2 : Crash and Brick? Why? Firmware has broken up. On hold until DFU is repaired. Curiosity Nano AVR128DB32 : PASS Curiosity Nano AVR64EA48 : PASS Curiosity Nano ATtiny1627 : PASS |
Beta Was this translation helpful? Give feedback.
-
|
JTAG2UPDI clone with support for NVMCTRL versions 0, 2, 3, 4, and 5 run test NVM V0 : PASS run test NVM V2 : PASS run test NVM V3 : PASS no test NVM V4 : Haven't gotten it yet run test NVM V5 : PASS |
Beta Was this translation helpful? Give feedback.
-
|
microUPDI DIY UPDI programmer Installed on homemade ARDUINO LEONARDO compatible board run test MVM V0 : PASS run test NVM V2 : FAIL This firmware seems to be very old and seems to have an issue with the 24bit addressing mode. This board's "1.19 (rel. 57)" seems to be newer than the microUPDIcore's firmware "1.13". MPLABX6.10 recognizes it as a miniUPDI kit, but it cannot be selected from the ATmega4809/AVR128DB32 project. 
|
Beta Was this translation helpful? Give feedback.
-
|
I guess this may be normal as the firmware may be only for NVM V1. |
Beta Was this translation helpful? Give feedback.
-
|
I tried changing the wiring of Xplained Mini ATtiny416 and connecting AVR128DB32, but I confirmed the same phenomenon. Regarding mEDBG, it seems reasonable to conclude that Dx/Ex is not supported. It is also important to note that NVM version 0 devices and others are separate AT Pack files. SRAM? In the data that seems to be, there are traces of successful reading of UPDI "SIB" and traces of failure of UPDI's "LD PTR 16bit" command. |
Beta Was this translation helpful? Give feedback.
-
|
ArduinoISP (sketch) : installed on ARDUINO UNO (ATmega328P) Probably the most used AVR writer implementation in the world. Actually, this is only used for bootloader setup. This is a typical application for STK500v1 over serial and works well if you can tolerate the 19200bps slowness. This implementation only supports his FUSE and FLASH on ISP (SPI) enabled chips. To force EEPROM to be skipped, you need to modify 'test-avrdude' slightly. run test ATmega328P : PASS run test ATmega32U4 : PASS run test ATtiny2313 : PASS run test ATtiny85 : PASS run test ATtiny13 : PASS |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Other than PR #1614, I think we should be able to close the other PRs soon. I think we are in a good shape to release avrdude 7.3 once PR #1627 are reviewed to be good to be merged. Any other things you have in mind for avrdude 7.3 release? Just wondering if you have some time to carry out some sanity tests. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Sounds good to me. |
Beta Was this translation helpful? Give feedback.
-
|
Hopefully @MCUdude is able to carry out the tests for AVR DU part soon. |
Beta Was this translation helpful? Give feedback.
-
|
I think avrdude git main is pretty good now. The issue found are mainly with the I'd like to carry out more tests of the Probably we can aim the release of avrdude next Friday (9-Feb-2024). 10-Feb-2024 is Chinese New Year holiday. ;-) |
Beta Was this translation helpful? Give feedback.
-
|
Looks like |
Beta Was this translation helpful? Give feedback.
-
|
Just wondering when you will receive the AVR DU part and carry out the tests. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
OK, new release candidate is now ready with bug fixes from previous discussions and test-avrdude script. Planning to release as v7.3 on Friday unless there are further bug fixes to be done. |
Beta Was this translation helpful? Give feedback.
-
|
I saw there is a patch from DragonFly BSD to support avrdude 7.1 with ther DPorts system. I will try to test it to see if avrdude git main works or not under DragonFly BSD. https://github.com/DragonFlyBSD/DPorts/tree/master/devel/avrdude |
Beta Was this translation helpful? Give feedback.
-
|
Still after applying the patch, it still does not work under DragonFly BSD. |
Beta Was this translation helpful? Give feedback.
-
Does that always appear or only after your patch? This line works for me in GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu) |
Beta Was this translation helpful? Give feedback.
-
|
The bash script error only happens after the patch and it is the same situation under Ubuntu Linux 20.04 version, quite strange. |
Beta Was this translation helpful? Give feedback.
-
|
I have finished the testing of The only issue which may not be related to the script is Issue #1649. As far as I am concerned, I have finished the testing of avrdude for 7.3 release. Hopefully I can close #1649 as soon as possible. It is a strange issue though since @askn37 can not reproduce the issue under his macOS system. Hopefully @MCUdude can try under his macOS system as well later -- but I expect that he would not have issues ith the Arduino Nano Every under macOS. |
Beta Was this translation helpful? Give feedback.
-
Brilliant - How about releasing sometime Wed 7 Feb somewhere on earth, ie, Tue 6 Feb 11.00 GMT to Thu 8 Feb 11.59 GMT |
Beta Was this translation helpful? Give feedback.
-
|
Yes, that will be a good plan. |
Beta Was this translation helpful? Give feedback.
-
|
It looks like I may have an AVR-DU Curiosity Nano in my mailbox on Monday. Just in time to do some tests before the 7.3 release! |
Beta Was this translation helpful? Give feedback.
-
|
@mcuee @MCUdude @askn37 and others have done extensive testing. Many thanks a lot all round. Is there a way we can record
I still think it would be wonderful if we had a short section in the .pdf/.html documentation about (current) limitations. For anyone wanting to join the testing, give the Some Windows environments require |
Beta Was this translation helpful? Give feedback.
-
|
I have documented the knows limitations here and I just did some updates to list down the issues I know of. FAQ page may need some updates. |
Beta Was this translation helpful? Give feedback.
-
|
I believe among @MCUdude @askn37 and me, we have covered most of the common programmers. OS coverage outside of Windows/macOS/Linux is not that great though as I only carry out sanity tests for a few programmers. I think we have to live with that. BSD users and other users are minority. |
Beta Was this translation helpful? Give feedback.
-
|
@MCUdude's test combinations are pretty comprehensive. [Please update if you have more not mentioned in earlier posts] |
Beta Was this translation helpful? Give feedback.
-
|
My test summary mentioned in earlier post. 1. Windows 10/11 x64 Test Results SummaryLast updated on 2024-02-01 MSYS2 mingw64 build (main binaries to test)
MSVC64 build (simple tests only)
Arduino avrdude-packing build (simple tests only)
2. Linux and macOS and tests summary: to be updatedmacOS (ARM64), Linux (x64 and Raspberry Pi OS): Simple tests Linux x86_64 : Ubuntu 20.04 64bit version. Simple tests only
Linux (Raspberry Pi OS on RPi 400, Debian 12 based) : Simple tests only
macOS 14.x (ARM64, mac Mini M1 2020): Simple tests only
macOS 14.x (x86_64 using Rosetta 2 emulation, mac Mini M1 2020) : Simple tests only
3. BSD platforms -- sanity check onlyFreeBSD 14 x86_64 virtual machine or Intel J4125 Mini PC physical machine
OpenBSD 7.4 x86_64 virtual machine or Intel N4500 Mini PC physical machine
NetBSD 9.3 x86_64 virtual machine
|
Beta Was this translation helpful? Give feedback.
-
|
@askn37 tested the following under macOS (maybe more). |
Beta Was this translation helpful? Give feedback.
-
AVR-DU testingThe first AVR-DU tests look promising! Tested on an AVR-DU Curiosity Nano. Will perform some tests with the SerialUPDI and jtag2updi later this evening: |
Beta Was this translation helpful? Give feedback.
-
|
@askn37 The other thing I have not considered is that the fuses are evaluated when the MCU resets, so |
Beta Was this translation helpful? Give feedback.
-
|
I found that there was a concern with the implementation of JTAG2UPDI (clone). You must wait until NVMCTRL_STATUS is completely complete before performing a RESET. Under normal operation, it is unlikely that the same memory address would be written to in a short period of time, so this phenomenon probably did not occur. This fix still requires (Maybe chip erase doesn't set the busy bit in NVMCTRL_STATUS?) |
Beta Was this translation helpful? Give feedback.
-
I usually use 0xD9 when drawing the bootloader. Before I knew it, it became 0xFF. I believe the RESET was inserted during a single erase/write command. |
Beta Was this translation helpful? Give feedback.
-
Is that a bug in avdude? Please raise an issue if so. |
Beta Was this translation helpful? Give feedback.
-
No. The reason why FUSE could not be written was a problem on the firmware side. It is not yet fully understood why, after a chip erase, another read/write can begin before the EEPROM is completely erased. It seems normal to read and write FLASH immediately, so it may be a chip-specific characteristic that has not been tested in detail. |
Beta Was this translation helpful? Give feedback.
-
|
What about serialupdi? Will you be able to test for t too?
Dawid
Wiadomość napisana przez Hans ***@***.***> w dniu 02.02.2024, o godz. 17:45:
AVR-DU testing
The first AVR-DU tests look promising! Tested on an AVR-DU Curiosity Nano. Will perform some tests with the SerialUPDI and jtag2updi later this evening:
$ ./test-avrdude -d 0 -p "-c pkobn_updi -p avr64du32"
Testing avrdude version 7.2-20230720
Prepare "-c pkobn_updi -p avr64du32" and press 'enter' or 'space' to continue. Press any other key to skip
✅ 0.243 s: fuse access: clear, set and read eesave fuse bit
✅ 0.243 s: fuse access: set eesave fusebit to delete EEPROM on chip erase
✅ 0.232 s: chip erase
✅ 5.827 s: flash -U write/verify holes_rjmp_loops_65536B.hex
✅ 2.113 s: flash -T write/verify holes_rjmp_loops_65536B.hex
✅ 0.267 s: eeprom check whether programmer can flip 0s to 1s
✅ 1.895 s: eeprom -U write/verify holes_pack_my_box_256B.hex
✅ 3.602 s: eeprom -T write/verify holes_{the_five_boxing_wizards,pack_my_box}_256B.hex
✅ 2.132 s: chip erase and spot check flash is actually erased
✅ 0.453 s: spot check eeprom is erased, too
✅ 1.812 s: usersig -T/-U write/read random_data_512B.bin
—
Reply to this email directly, view it on GitHub<#1473 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAMBKNZE7ZGAKSYZAEC2EGLYRUJ2XAVCNFSM6AAAAAA2VQAUDCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DGNBYG4YDS>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Looks very promising! Excellent work @dbuchwald! There seem to be an issue with usersig/userrow: serialupdi userrow -vvvv |
Beta Was this translation helpful? Give feedback.
-
|
Sorry you had to encounter that, I was really hoping it would work out of the box.
The error you are receiving is caused by the fact that you are trying to write 512 bytes, which means repeating store/pointer increment 512 times. This protocol has a limit on repetition number of 256, which means that different command should be used (instead of writing single byte 512 times it should be writing 2-byte word 256 times) - at least this would be my guess at this moment.
This, however, points at much bigger issue that I need to investigate further. My suggestion would be: I will file a bug tomorrow, these chips are not widely available anyway, and I will look into it further.
As for 7.3 release - this issue should not block it.
Last but not least, could you test this specific scenario using latest version of pymcuprog? I’m really curious whether it works, and if it does, is there any difference in operation.
Thanks and sorry,
Dawid
… On 2 Feb 2024, at 20:41, Hans ***@***.***> wrote:
What about serialupdi? Will you be able to test for it too?
Looks very promising! Excellent work @dbuchwald <https://github.com/dbuchwald>!
$ ./test-avrdude -d 0 -p "-c serialupdi -P ch340 -p avr64du32"
Testing avrdude version 7.2-20230720
Prepare "-c serialupdi -P ch340 -p avr64du32" and press 'enter' or 'space' to continue. Press any other key to skip
✅ 0.525 s: fuse access: clear, set and read eesave fuse bit
✅ 0.510 s: fuse access: set eesave fusebit to delete EEPROM on chip erase
✅ 0.510 s: chip erase
✅ 3.962 s: flash -U write/verify holes_rjmp_loops_65536B.hex
✅ 2.282 s: flash -T write/verify holes_rjmp_loops_65536B.hex
✅ 0.564 s: eeprom check whether programmer can flip 0s to 1s
✅ 3.028 s: eeprom -U write/verify holes_pack_my_box_256B.hex
✅ 5.573 s: eeprom -T write/verify holes_{the_five_boxing_wizards,pack_my_box}_256B.hex
✅ 2.356 s: chip erase and spot check flash is actually erased
✅ 0.718 s: spot check eeprom is erased, too
❌ 3.751 s: usersig -T/-U write/read random_data_512B.bin (failed command below)
$ avrdude -qq -c serialupdi -P ch340 -p avr64du32 -l /tmp/test-avrdude.log.7nGMfD -T "erase usersig; write usersig ./test_files/random_data_512B.bin" -T flush -U usersig:r:/tmp/test-avrdude.tmp.oFvsps:r -U usersig:v:/tmp/test-avrdude.tmp.oFvsps:r -T "erase usersig" -T flush -U usersig:v:./test_files/0xff_512B.hex:i
One or more AVRDUDE "-c serialupdi -P ch340 -p avr64du32" tests failed. Do you want to retry this particular test? (y/n): n
There seem to be an issue with usersig/userrow:
serialupdi userrow -vvvv
$ avrdude -cserialupdi -pavr64du32 -P ch340 -T 'write userrow 0 "The quick brown fox jumpes over the lazy dog"' -vvvv
avrdude: Version 7.2-20230720
Copyright the AVRDUDE authors;
see https://github.com/avrdudes/avrdude/blob/main/AUTHORS
System wide configuration file is /usr/local/etc/avrdude.conf
User configuration file is /Users/hans/.avrduderc
Using port : /dev/cu.usbserial-1420
Using programmer : serialupdi
avrdude: opening serial port ...
avrdude: sending 1 bytes [0x00]
avrdude: ser_send: . [00]
avrdude: ser_recv: . [00]
AVR Part : AVR64DU32
Programming modes : UPDI, SPM
Memory Size Pg size Offset
-----------------------------------------
eeprom 256 1 0x1400
flash 65536 512 0x800000
fuses 16 1 0x1050
fuse0/wdtcfg 1 1 0x1050
fuse1/bodcfg 1 1 0x1051
fuse2/osccfg 1 1 0x1052
fuse5/syscfg0 1 1 0x1055
fuse6/syscfg1 1 1 0x1056
fuse7/codesize 1 1 0x1057
fuse8/bootsize 1 1 0x1058
fusea/pdicfg 2 1 0x105a
lock 4 1 0x1040
prodsig/sigrow 128 128 0x1080
signature 3 1 0x1080
tempsense 4 1 0x1084
sernum 16 1 0x1090
bootrow 256 256 0x1100
userrow/usersig 512 512 0x1200
io 4160 1 0
sram 8192 1 0x6000
sib 32 1 0
Variants Package F max T range V range
-------------------------------------------------------------------
AVR64DU32-VQFN/TQFP QFP32 32 MHz [-40 C, 85 C] [1.8 V, 5.5 V]
Programmer Type : serialupdi
Description : SerialUPDI
avrdude: STCS 0x08 to address 0x03
avrdude: sending 3 bytes [0x55, 0xc3, 0x08]
avrdude: ser_send: U [55] . [c3] . [08]
avrdude: ser_recv: U [55] . [c3] . [08]
avrdude: STCS 0x80 to address 0x02
avrdude: sending 3 bytes [0x55, 0xc2, 0x80]
avrdude: ser_send: U [55] . [c2] . [80]
avrdude: ser_recv: U [55] . [c2] . [80]
avrdude: LDCS from 0x00
avrdude: sending 2 bytes [0x55, 0x80]
avrdude: ser_send: U [55] . [80]
avrdude: ser_recv: U [55] . [80]
avrdude: ser_recv: 0 [30]
avrdude: received 1 bytes [0x30]
avrdude: UDPI init OK
avrdude: UPDI link initialization OK
avrdude: LDCS from 0x0B
avrdude: sending 2 bytes [0x55, 0x8b]
avrdude: ser_send: U [55] . [8b]
avrdude: ser_recv: U [55] . [8b]
avrdude: ser_recv: . [82]
avrdude: received 1 bytes [0x82]
avrdude: sending 2 bytes [0x55, 0xe6]
avrdude: ser_send: U [55] . [e6]
avrdude: ser_recv: U [55] . [e6]
avrdude: ser_recv: A [41] V [56] R [52] [20] [20] [20] [20] [20] P [50] : [3a] 4 [34] D [44] : [3a] 1 [31] - [2d] 3 [33] M [4d] 2 [32] [20] ( [28] A [41] 2 [32] . [2e] K [4b] V [56] 0 [30] 0 [30] S [53] . [2e] 0 [30] ) [29] . [00]
avrdude: received 32 bytes [0x41, 0x56, 0x52, 0x20, 0x20, 0x20, 0x20, 0x20, 0x50, 0x3a, 0x34, 0x44, 0x3a, 0x31, 0x2d, 0x33, 0x4d, 0x32, 0x20, 0x28, 0x41, 0x32, 0x2e, 0x4b, 0x56, 0x30, 0x30, 0x53, 0x2e, 0x30, 0x29, 0x00]
avrdude: received SIB: [AVR P:4D:1-3M2 (A2.KV00S.0)]
avrdude: Device family ID: AVR
avrdude: NVM interface: P:4
avrdude: Debug interface: D:1
avrdude: PDI oscillator: 3M2
avrdude: Extra information: (A2.KV00S.0)
avrdude: NVM type 4: 24-bit, word oriented
avrdude: STCS 0x08 to address 0x03
avrdude: sending 3 bytes [0x55, 0xc3, 0x08]
avrdude: ser_send: U [55] . [c3] . [08]
avrdude: ser_recv: U [55] . [c3] . [08]
avrdude: STCS 0x80 to address 0x02
avrdude: sending 3 bytes [0x55, 0xc2, 0x80]
avrdude: ser_send: U [55] . [c2] . [80]
avrdude: ser_recv: U [55] . [c2] . [80]
avrdude: LDCS from 0x00
avrdude: sending 2 bytes [0x55, 0x80]
avrdude: ser_send: U [55] . [80]
avrdude: ser_recv: U [55] . [80]
avrdude: ser_recv: 0 [30]
avrdude: received 1 bytes [0x30]
avrdude: UDPI init OK
avrdude: entering NVM programming mode
avrdude: LDCS from 0x0B
avrdude: sending 2 bytes [0x55, 0x8b]
avrdude: ser_send: U [55] . [8b]
avrdude: ser_recv: U [55] . [8b]
avrdude: ser_recv: . [82]
avrdude: received 1 bytes [0x82]
avrdude: sending reset request
avrdude: STCS 0x59 to address 0x08
avrdude: sending 3 bytes [0x55, 0xc8, 0x59]
avrdude: ser_send: U [55] . [c8] Y [59]
avrdude: ser_recv: U [55] . [c8] Y [59]
avrdude: UPDI writing key
avrdude: sending 2 bytes [0x55, 0xe0]
avrdude: ser_send: U [55] . [e0]
avrdude: ser_recv: U [55] . [e0]
avrdude: sending 8 bytes [0x20, 0x67, 0x6f, 0x72, 0x50, 0x4d, 0x56, 0x4e]
avrdude: ser_send: [20] g [67] o [6f] r [72] P [50] M [4d] V [56] N [4e]
avrdude: ser_recv: [20] g [67] o [6f] r [72] P [50] M [4d] V [56] N [4e]
avrdude: LDCS from 0x07
avrdude: sending 2 bytes [0x55, 0x87]
avrdude: ser_send: U [55] . [87]
avrdude: ser_recv: U [55] . [87]
avrdude: ser_recv: . [10]
avrdude: received 1 bytes [0x10]
avrdude: key status: 0x10
avrdude: sending reset request
avrdude: STCS 0x59 to address 0x08
avrdude: sending 3 bytes [0x55, 0xc8, 0x59]
avrdude: ser_send: U [55] . [c8] Y [59]
avrdude: ser_recv: U [55] . [c8] Y [59]
avrdude: sending release reset request
avrdude: STCS 0x00 to address 0x08
avrdude: sending 3 bytes [0x55, 0xc8, 0x00]
avrdude: ser_send: U [55] . [c8] . [00]
avrdude: ser_recv: U [55] . [c8] . [00]
avrdude: LDCS from 0x0B
avrdude: sending 2 bytes [0x55, 0x8b]
avrdude: ser_send: U [55] . [8b]
avrdude: ser_recv: U [55] . [8b]
avrdude: ser_recv: ( [28]
avrdude: received 1 bytes [0x28]
avrdude: LDCS from 0x0B
avrdude: sending 2 bytes [0x55, 0x8b]
avrdude: ser_send: U [55] . [8b]
avrdude: ser_recv: U [55] . [8b]
avrdude: ser_recv: . [08]
avrdude: received 1 bytes [0x08]
avrdude: entered NVM programming mode
avrdude: reading 1 bytes from 0x000F01
avrdude: ST_PTR to 0x000F01
avrdude: sending 5 bytes [0x55, 0x6a, 0x01, 0x0f, 0x00]
avrdude: ser_send: U [55] j [6a] . [01] . [0f] . [00]
avrdude: ser_recv: U [55] j [6a] . [01] . [0f] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: LD8 from ptr++
avrdude: sending 2 bytes [0x55, 0x24]
avrdude: ser_send: U [55] $ [24]
avrdude: ser_recv: U [55] $ [24]
avrdude: ser_recv: . [12]
avrdude: received 1 bytes [0x12]
avrdude: Received chip silicon revision 0x12
avrdude: Chip silicon revision: 1.2
avrdude: AVR device initialized and ready to accept instructions
Reading | | 0% 0.00 s
avrdude: LDCS from 0x0B
avrdude: sending 2 bytes [0x55, 0x8b]
avrdude: ser_send: U [55] . [8b]
avrdude: ser_recv: U [55] . [8b]
avrdude: ser_recv: . [08]
avrdude: received 1 bytes [0x08]
avrdude: LD from 0x001080
avrdude: sending 5 bytes [0x55, 0x08, 0x80, 0x10, 0x00]
avrdude: ser_send: U [55] . [08] . [80] . [10] . [00]
avrdude: ser_recv: U [55] . [08] . [80] . [10] . [00]
avrdude: ser_recv: . [1e]
avrdude: received 1 bytes [0x1e]
avrdude: LD from 0x001081
avrdude: sending 5 bytes [0x55, 0x08, 0x81, 0x10, 0x00]
avrdude: ser_send: U [55] . [08] . [81] . [10] . [00]
avrdude: ser_recv: U [55] . [08] . [81] . [10] . [00]
avrdude: ser_recv: . [96]
avrdude: received 1 bytes [0x96]
avrdude: LD from 0x001082
avrdude: sending 5 bytes [0x55, 0x08, 0x82, 0x10, 0x00]
avrdude: ser_send: U [55] . [08] . [82] . [10] . [00]
avrdude: ser_recv: U [55] . [08] . [82] . [10] . [00]
avrdude: ser_recv: ! [21]
avrdude: received 1 bytes [0x21]
Reading | ################################################## | 100% 0.02 s
avrdude: device signature = 0x1e9621 (probably avr64du32)
avrdude: processing -T write userrow 0 "The quick brown fox jumpes over the lazy dog"
avrdude: (write) writing 45 bytes starting from address 0x00
Caching | | 0% 0.00 s
avrdude: reading 32 bytes from 0x001200
avrdude: ST_PTR to 0x001200
avrdude: sending 5 bytes [0x55, 0x6a, 0x00, 0x12, 0x00]
avrdude: ser_send: U [55] j [6a] . [00] . [12] . [00]
avrdude: ser_recv: U [55] j [6a] . [00] . [12] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: repeat 32
avrdude: sending 3 bytes [0x55, 0xa0, 0x1f]
avrdude: ser_send: U [55] . [a0] . [1f]
avrdude: ser_recv: U [55] . [a0] . [1f]
avrdude: LD8 from ptr++
avrdude: sending 2 bytes [0x55, 0x24]
avrdude: ser_send: U [55] $ [24]
avrdude: ser_recv: U [55] $ [24]
avrdude: ser_recv: . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
avrdude: received 32 bytes [0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff]
avrdude: reading 32 bytes from 0x001220
avrdude: ST_PTR to 0x001220
avrdude: sending 5 bytes [0x55, 0x6a, 0x20, 0x12, 0x00]
avrdude: ser_send: U [55] j [6a] [20] . [12] . [00]
avrdude: ser_recv: U [55] j [6a] [20] . [12] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: repeat 32
avrdude: sending 3 bytes [0x55, 0xa0, 0x1f]
avrdude: ser_send: U [55] . [a0] . [1f]
avrdude: ser_recv: U [55] . [a0] . [1f]
avrdude: LD8 from ptr++
avrdude: sending 2 bytes [0x55, 0x24]
avrdude: ser_send: U [55] $ [24]
avrdude: ser_recv: U [55] $ [24]
avrdude: ser_recv: . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
avrdude: received 32 bytes [0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff]
avrdude: reading 32 bytes from 0x001240
avrdude: ST_PTR to 0x001240
avrdude: sending 5 bytes [0x55, 0x6a, 0x40, 0x12, 0x00]
avrdude: ser_send: U [55] j [6a] @ [40] . [12] . [00]
avrdude: ser_recv: U [55] j [6a] @ [40] . [12] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: repeat 32
avrdude: sending 3 bytes [0x55, 0xa0, 0x1f]
avrdude: ser_send: U [55] . [a0] . [1f]
avrdude: ser_recv: U [55] . [a0] . [1f]
avrdude: LD8 from ptr++
avrdude: sending 2 bytes [0x55, 0x24]
avrdude: ser_send: U [55] $ [24]
avrdude: ser_recv: U [55] $ [24]
avrdude: ser_recv: . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
avrdude: received 32 bytes [0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff]
avrdude: reading 32 bytes from 0x001260
avrdude: ST_PTR to 0x001260
avrdude: sending 5 bytes [0x55, 0x6a, 0x60, 0x12, 0x00]
avrdude: ser_send: U [55] j [6a] ` [60] . [12] . [00]
avrdude: ser_recv: U [55] j [6a] ` [60] . [12] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: repeat 32
avrdude: sending 3 bytes [0x55, 0xa0, 0x1f]
avrdude: ser_send: U [55] . [a0] . [1f]
avrdude: ser_recv: U [55] . [a0] . [1f]
avrdude: LD8 from ptr++
avrdude: sending 2 bytes [0x55, 0x24]
avrdude: ser_send: U [55] $ [24]
avrdude: ser_recv: U [55] $ [24]
avrdude: ser_recv: . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
avrdude: received 32 bytes [0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff]
avrdude: reading 32 bytes from 0x001280
avrdude: ST_PTR to 0x001280
avrdude: sending 5 bytes [0x55, 0x6a, 0x80, 0x12, 0x00]
avrdude: ser_send: U [55] j [6a] . [80] . [12] . [00]
avrdude: ser_recv: U [55] j [6a] . [80] . [12] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: repeat 32
avrdude: sending 3 bytes [0x55, 0xa0, 0x1f]
avrdude: ser_send: U [55] . [a0] . [1f]
avrdude: ser_recv: U [55] . [a0] . [1f]
avrdude: LD8 from ptr++
avrdude: sending 2 bytes [0x55, 0x24]
avrdude: ser_send: U [55] $ [24]
avrdude: ser_recv: U [55] $ [24]
avrdude: ser_recv: . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
avrdude: received 32 bytes [0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff]
avrdude: reading 32 bytes from 0x0012A0
avrdude: ST_PTR to 0x0012A0
avrdude: sending 5 bytes [0x55, 0x6a, 0xa0, 0x12, 0x00]
avrdude: ser_send: U [55] j [6a] . [a0] . [12] . [00]
avrdude: ser_recv: U [55] j [6a] . [a0] . [12] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: repeat 32
avrdude: sending 3 bytes [0x55, 0xa0, 0x1f]
avrdude: ser_send: U [55] . [a0] . [1f]
avrdude: ser_recv: U [55] . [a0] . [1f]
avrdude: LD8 from ptr++
avrdude: sending 2 bytes [0x55, 0x24]
avrdude: ser_send: U [55] $ [24]
avrdude: ser_recv: U [55] $ [24]
avrdude: ser_recv: . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
avrdude: received 32 bytes [0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff]
avrdude: reading 32 bytes from 0x0012C0
avrdude: ST_PTR to 0x0012C0
avrdude: sending 5 bytes [0x55, 0x6a, 0xc0, 0x12, 0x00]
avrdude: ser_send: U [55] j [6a] . [c0] . [12] . [00]
avrdude: ser_recv: U [55] j [6a] . [c0] . [12] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: repeat 32
avrdude: sending 3 bytes [0x55, 0xa0, 0x1f]
avrdude: ser_send: U [55] . [a0] . [1f]
avrdude: ser_recv: U [55] . [a0] . [1f]
avrdude: LD8 from ptr++
avrdude: sending 2 bytes [0x55, 0x24]
avrdude: ser_send: U [55] $ [24]
avrdude: ser_recv: U [55] $ [24]
avrdude: ser_recv: . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
avrdude: received 32 bytes [0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff]
avrdude: reading 32 bytes from 0x0012E0
avrdude: ST_PTR to 0x0012E0
avrdude: sending 5 bytes [0x55, 0x6a, 0xe0, 0x12, 0x00]
avrdude: ser_send: U [55] j [6a] . [e0] . [12] . [00]
avrdude: ser_recv: U [55] j [6a] . [e0] . [12] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: repeat 32
avrdude: sending 3 bytes [0x55, 0xa0, 0x1f]
avrdude: ser_send: U [55] . [a0] . [1f]
avrdude: ser_recv: U [55] . [a0] . [1f]
avrdude: LD8 from ptr++
avrdude: sending 2 bytes [0x55, 0x24]
avrdude: ser_send: U [55] $ [24]
avrdude: ser_recv: U [55] $ [24]
avrdude: ser_recv: . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
avrdude: received 32 bytes [0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff]
avrdude: reading 32 bytes from 0x001300
avrdude: ST_PTR to 0x001300
avrdude: sending 5 bytes [0x55, 0x6a, 0x00, 0x13, 0x00]
avrdude: ser_send: U [55] j [6a] . [00] . [13] . [00]
avrdude: ser_recv: U [55] j [6a] . [00] . [13] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: repeat 32
avrdude: sending 3 bytes [0x55, 0xa0, 0x1f]
avrdude: ser_send: U [55] . [a0] . [1f]
avrdude: ser_recv: U [55] . [a0] . [1f]
avrdude: LD8 from ptr++
avrdude: sending 2 bytes [0x55, 0x24]
avrdude: ser_send: U [55] $ [24]
avrdude: ser_recv: U [55] $ [24]
avrdude: ser_recv: . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
avrdude: received 32 bytes [0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff]
avrdude: reading 32 bytes from 0x001320
avrdude: ST_PTR to 0x001320
avrdude: sending 5 bytes [0x55, 0x6a, 0x20, 0x13, 0x00]
avrdude: ser_send: U [55] j [6a] [20] . [13] . [00]
avrdude: ser_recv: U [55] j [6a] [20] . [13] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: repeat 32
avrdude: sending 3 bytes [0x55, 0xa0, 0x1f]
avrdude: ser_send: U [55] . [a0] . [1f]
avrdude: ser_recv: U [55] . [a0] . [1f]
avrdude: LD8 from ptr++
avrdude: sending 2 bytes [0x55, 0x24]
avrdude: ser_send: U [55] $ [24]
avrdude: ser_recv: U [55] $ [24]
avrdude: ser_recv: . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
avrdude: received 32 bytes [0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff]
avrdude: reading 32 bytes from 0x001340
avrdude: ST_PTR to 0x001340
avrdude: sending 5 bytes [0x55, 0x6a, 0x40, 0x13, 0x00]
avrdude: ser_send: U [55] j [6a] @ [40] . [13] . [00]
avrdude: ser_recv: U [55] j [6a] @ [40] . [13] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: repeat 32
avrdude: sending 3 bytes [0x55, 0xa0, 0x1f]
avrdude: ser_send: U [55] . [a0] . [1f]
avrdude: ser_recv: U [55] . [a0] . [1f]
avrdude: LD8 from ptr++
avrdude: sending 2 bytes [0x55, 0x24]
avrdude: ser_send: U [55] $ [24]
avrdude: ser_recv: U [55] $ [24]
avrdude: ser_recv: . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
avrdude: received 32 bytes [0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff]
avrdude: reading 32 bytes from 0x001360
avrdude: ST_PTR to 0x001360
avrdude: sending 5 bytes [0x55, 0x6a, 0x60, 0x13, 0x00]
avrdude: ser_send: U [55] j [6a] ` [60] . [13] . [00]
avrdude: ser_recv: U [55] j [6a] ` [60] . [13] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: repeat 32
avrdude: sending 3 bytes [0x55, 0xa0, 0x1f]
avrdude: ser_send: U [55] . [a0] . [1f]
avrdude: ser_recv: U [55] . [a0] . [1f]
avrdude: LD8 from ptr++
avrdude: sending 2 bytes [0x55, 0x24]
avrdude: ser_send: U [55] $ [24]
avrdude: ser_recv: U [55] $ [24]
avrdude: ser_recv: . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
avrdude: received 32 bytes [0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff]
avrdude: reading 32 bytes from 0x001380
avrdude: ST_PTR to 0x001380
avrdude: sending 5 bytes [0x55, 0x6a, 0x80, 0x13, 0x00]
avrdude: ser_send: U [55] j [6a] . [80] . [13] . [00]
avrdude: ser_recv: U [55] j [6a] . [80] . [13] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: repeat 32
avrdude: sending 3 bytes [0x55, 0xa0, 0x1f]
avrdude: ser_send: U [55] . [a0] . [1f]
avrdude: ser_recv: U [55] . [a0] . [1f]
avrdude: LD8 from ptr++
avrdude: sending 2 bytes [0x55, 0x24]
avrdude: ser_send: U [55] $ [24]
avrdude: ser_recv: U [55] $ [24]
avrdude: ser_recv: . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
avrdude: received 32 bytes [0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff]
avrdude: reading 32 bytes from 0x0013A0
avrdude: ST_PTR to 0x0013A0
avrdude: sending 5 bytes [0x55, 0x6a, 0xa0, 0x13, 0x00]
avrdude: ser_send: U [55] j [6a] . [a0] . [13] . [00]
avrdude: ser_recv: U [55] j [6a] . [a0] . [13] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: repeat 32
avrdude: sending 3 bytes [0x55, 0xa0, 0x1f]
avrdude: ser_send: U [55] . [a0] . [1f]
avrdude: ser_recv: U [55] . [a0] . [1f]
avrdude: LD8 from ptr++
avrdude: sending 2 bytes [0x55, 0x24]
avrdude: ser_send: U [55] $ [24]
avrdude: ser_recv: U [55] $ [24]
avrdude: ser_recv: . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
avrdude: received 32 bytes [0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff]
avrdude: reading 32 bytes from 0x0013C0
avrdude: ST_PTR to 0x0013C0
avrdude: sending 5 bytes [0x55, 0x6a, 0xc0, 0x13, 0x00]
avrdude: ser_send: U [55] j [6a] . [c0] . [13] . [00]
avrdude: ser_recv: U [55] j [6a] . [c0] . [13] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: repeat 32
avrdude: sending 3 bytes [0x55, 0xa0, 0x1f]
avrdude: ser_send: U [55] . [a0] . [1f]
avrdude: ser_recv: U [55] . [a0] . [1f]
avrdude: LD8 from ptr++
avrdude: sending 2 bytes [0x55, 0x24]
avrdude: ser_send: U [55] $ [24]
avrdude: ser_recv: U [55] $ [24]
avrdude: ser_recv: . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
avrdude: received 32 bytes [0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff]
avrdude: reading 32 bytes from 0x0013E0
avrdude: ST_PTR to 0x0013E0
avrdude: sending 5 bytes [0x55, 0x6a, 0xe0, 0x13, 0x00]
avrdude: ser_send: U [55] j [6a] . [e0] . [13] . [00]
avrdude: ser_recv: U [55] j [6a] . [e0] . [13] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: repeat 32
avrdude: sending 3 bytes [0x55, 0xa0, 0x1f]
avrdude: ser_send: U [55] . [a0] . [1f]
avrdude: ser_recv: U [55] . [a0] . [1f]
avrdude: LD8 from ptr++
avrdude: sending 2 bytes [0x55, 0x24]
avrdude: ser_send: U [55] $ [24]
avrdude: ser_recv: U [55] $ [24]
avrdude: ser_recv: . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff] . [ff]
avrdude: received 32 bytes [0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff]
Caching | ################################################## | 100% 0.25 s
avrdude: synching cache to device ...
Writing | | 0% 0.00 s
avrdude: UPDI writing key
avrdude: sending 2 bytes [0x55, 0xe0]
avrdude: ser_send: U [55] . [e0]
avrdude: ser_recv: U [55] . [e0]
avrdude: sending 8 bytes [0x65, 0x74, 0x26, 0x73, 0x55, 0x4d, 0x56, 0x4e]
avrdude: ser_send: e [65] t [74] & [26] s [73] U [55] M [4d] V [56] N [4e]
avrdude: ser_recv: e [65] t [74] & [26] s [73] U [55] M [4d] V [56] N [4e]
avrdude: LDCS from 0x07
avrdude: sending 2 bytes [0x55, 0x87]
avrdude: ser_send: U [55] . [87]
avrdude: ser_recv: U [55] . [87]
avrdude: ser_recv: [20]
avrdude: received 1 bytes [0x20]
avrdude: key status: 0x20
avrdude: sending reset request
avrdude: STCS 0x59 to address 0x08
avrdude: sending 3 bytes [0x55, 0xc8, 0x59]
avrdude: ser_send: U [55] . [c8] Y [59]
avrdude: ser_recv: U [55] . [c8] Y [59]
avrdude: sending release reset request
avrdude: STCS 0x00 to address 0x08
avrdude: sending 3 bytes [0x55, 0xc8, 0x00]
avrdude: ser_send: U [55] . [c8] . [00]
avrdude: ser_recv: U [55] . [c8] . [00]
avrdude: LDCS from 0x0B
avrdude: sending 2 bytes [0x55, 0x8b]
avrdude: ser_send: U [55] . [8b]
avrdude: ser_recv: U [55] . [8b]
avrdude: ser_recv: $ [24]
avrdude: received 1 bytes [0x24]
avrdude: invalid length
Writing | -------------------------------------------------- | 0% 0.02 s
avrdude serialupdi_write_userrow() [serialupdi.c:546] error: writing USER ROW failed
avrdude: serialupdi_write_byte(userrow, 0x0000, 0x54)
avrdude: ST to 0x001200
avrdude: sending 5 bytes [0x55, 0x48, 0x00, 0x12, 0x00]
avrdude: ser_send: U [55] H [48] . [00] . [12] . [00]
avrdude: ser_recv: U [55] H [48] . [00] . [12] . [00]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: sending 1 bytes [0x54]
avrdude: ser_send: T [54]
avrdude: ser_recv: T [54]
avrdude: ser_recv: @ [40]
avrdude: received 1 bytes [0x40]
avrdude: serialupdi_read_byte(userrow, 0x0000)
avrdude: LD from 0x001200
avrdude: sending 5 bytes [0x55, 0x08, 0x00, 0x12, 0x00]
avrdude: ser_send: U [55] . [08] . [00] . [12] . [00]
avrdude: ser_recv: U [55] . [08] . [00] . [12] . [00]
avrdude: ser_recv(): programmer is not responding
avrdude: serialupdi_recv(): programmer is not responding
avrdude: LD operation recv failed
avrdude writeCachePage() [avrcache.c:301] error: userrow access error at addr 0x0000
avrdude: leaving NVM programming mode
avrdude: sending reset request
avrdude: STCS 0x59 to address 0x08
avrdude: sending 3 bytes [0x55, 0xc8, 0x59]
avrdude: ser_send: U [55] . [c8] Y [59]
avrdude: ser_recv: U [55] . [c8] Y [59]
avrdude: sending release reset request
avrdude: STCS 0x00 to address 0x08
avrdude: sending 3 bytes [0x55, 0xc8, 0x00]
avrdude: ser_send: U [55] . [c8] . [00]
avrdude: ser_recv: U [55] . [c8] . [00]
avrdude: STCS 0x0C to address 0x03
avrdude: sending 3 bytes [0x55, 0xc3, 0x0c]
avrdude: ser_send: U [55] . [c3] . [0c]
avrdude: ser_recv: U [55] . [c3] . [0c]
avrdude done. Thank you.
—
Reply to this email directly, view it on GitHub <#1473 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMBKN3TSL6GQW2TZUKXUW3YRU6NJAVCNFSM6AAAAAA2VQAUDCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DGNJQGI3DC>.
You are receiving this because you were mentioned.
|
Beta Was this translation helpful? Give feedback.
-
No need to apologize! There are only so much you can do without testing on actual hardware... I'm still impressed with how well it works for everything else. I'm not all that familiar with the pymcuprog syntax. I wasn't able to write to userrow... |
Beta Was this translation helpful? Give feedback.
-
|
Hey, I don't know if you got an e-mail notification, I have filed the bug here: You can also find fix candidate here: https://github.com/dbuchwald/avrdude/tree/issue_1655 I was also wondering if it was a mistake, that the USERROW size is 512 but bits, not bytes - this would make it consistent with other chips, like the EA family which has 64 bytes of this memory type, but I checked atpack and indeed it seems to be correct size. WHY?! |
Beta Was this translation helpful? Give feedback.
-
|
Wow, excellent results for the AVR DU parts. Great work @dbuchwald. Thanks for testing @MCUdude: should your test
not read rather than What's happening here? |
Beta Was this translation helpful? Give feedback.
-
Much nicer if that's done automatically - one less thing to remember for a new release |
Beta Was this translation helpful? Give feedback.
-
|
I will remove the Draft status from the #1663 PR once it can be merged. |
Beta Was this translation helpful? Give feedback.
-
|
While you are at this, can you look at this issue as well if possible? Thanks. The auto-tools scripts are pretty broken but @MCUdude still likes it. |
Beta Was this translation helpful? Give feedback.
-
|
I would be using CMake/build.sh if it was as easy to work with as make. IIRC @stefanrueger has created his own make wrapper around CMake.
|
Beta Was this translation helpful? Give feedback.
-
Somehow I do not see an issue with build.sh as I copy the two files to the other directory avrdude_bin. I also add PR number in the file name as well to differentiate the PRs. For test-avrdude, I copy the executable file and configure file to the tools directory, and use -e option to specify the location. I can actually use the same avrdude_bin directory but I choose to copy to save a bit of typing. |
Beta Was this translation helpful? Give feedback.
-
Indeed this is essential for my Windows avrdude testing. |
Beta Was this translation helpful? Give feedback.
-
|
I now consider @mcuee @MCUdude @dbuchwald @askn37 @dl8dtl if you notice anything critical, speak up now or hold your peace forever 😉 |
Beta Was this translation helpful? Give feedback.
-
I consider avrdude 7.3 done as well. To me, the version number change for auto-tools is nice to have but not a blocker for avrdude 7.3 release. |
Beta Was this translation helpful? Give feedback.
-
|
Great, avrdude 7.3 has been released. Online documentation deployed as well. |
Beta Was this translation helpful? Give feedback.
-
Just want to start the discussion early. It is unlikely we are going for a new version soon, maybe a Chirstmat gift or New Year gift will be very good.
Beta Was this translation helpful? Give feedback.
All reactions