Hello,
after upgrading to eclipse 2018-09 and installing the avr-plugin 2.4.1 it is not possible to read fuse settings or mcu type using the avrisp-mkII programmer. Using avrdude the communication is o.k.
Used settings: ATtiny13, usb-port
1) console output from avr-plugin:
Launching /usr/bin/avrdude -cavrispmkII -Pusb -px128a3
Output:
avrdude: stk500v2_command(): error in CMD_XPROG: Timeout
avrdude: stk600_xprog_program_enable(): XPRG_CMD_ENTER_PROGMODE failed
avrdude: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.
avrdude: stk500v2_command(): error in CMD_XPROG: Failed
avrdude: stk600_xprog_program_disable(): XPRG_CMD_LEAVE_PROGMODE failed
avrdude done. Thank you.
avrdude finished
I've no idea why an Atmega128x has been choosen - the project settings say: ATtiny13
2) linux console output:
$/home# avrdude -cavrispmkII -Pusb -p attiny13 -Enoreset -F -U lfuse:r:-:i
avrdude: WARNING: -E option not supported by this programmer type
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
avrdude: Device signature = 0x1e9007 (probably t13)
avrdude: reading lfuse memory:
Reading | ################################################## | 100% 0.00s
avrdude: writing output file "<stdout>"
:010000006A95
:00000001FF
avrdude: safemode: Fuses OK (E:FF, H:FF, L:6A)
avrdude done. Thank you.</stdout>
Is it possible to check whether the selected settings have been recognized by avr-plugin?
Thanks in advance,
Reinhold
I have had this issue for many years, until I found the 2.4.2 plugin that fixed the issue for another user. It did not fix the issue for me.
The logic of this escapes me from the fact that every use of the avr plugin requires that I set the proper target. You would think it would try with the existing target settings first, then fall back. As you can see from the output, the basic logic seems to work, as far as the first query returns the proper device. In my case the ATtiny85 (as 't85') but the software does not parse it properly? On the next query is seems to default to some unknown device without even attempting a read from the set target.
Any protection to the user is pretty voided by that you have to select 'direct hex values' just to read the target, but it's actually a 'write hex values'. All need do is have the query fail, then the next upload sets the fueses to whatever is in the field. Good thing I have a HVSP... You should be able to read them anyway without selecting 'direct hex values'.
Not knowing the restraints on the people writting this code, it seems like never been properly fixed. I do appreciate all the efforts so, thanks to all of you...
Sorry about the gripes...
The console did not include the actuall avrdude call that created the list of known micros, even after expanding the size of the buffer. I assume that it's for parsing purposes.
Here is the output from the latest plugin that I have 2.4.2.
Eclipse
Version: 2019-03 (4.11.0)
Build id: 20190314-1200
Output from console window:
Thanks, if you need more information, please contact me.
Jack :)