[Avr-eclipse-user] [ avr-eclipse-Bugs-3023718 ] wrong part when invoking avrdude to read fuses/lockbits

[SourceForge.net <no...@so...>]

Bugs item #3023718, was opened at 2010-07-01 11:16
Message generated for change (Comment added) made by innot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=928231&aid=3023718&group_id=189165

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Behavior
Group: v2.3
Status: Open
>Resolution: Accepted
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Thomas Holland (innot)
Summary: wrong part when invoking avrdude to read fuses/lockbits

Initial Comment:
When trying to read fuses or lockbits from AVRDude options page in project properties, the plugin outputs a wrong command line to invoke AVRDude:
avrdude -cavrisp2 -Pusb -pm16
this command fails saying "avrdude: initialization failed, rc=-1"
Since I'm using ATXMEGA128A1 mcu, the part specified in the command line doesn't reflects the project target hardware setting.
I think the command line should be: avrdude -cavrisp2 -Pusb -px128a1

This behavior is present also when trying to load the "Flash memory erase cycle counter" in the "other" page of AVRDude options.

P.S. My project is setup correctly as I can program my board and the fuses (when I set them manually).

Please take a look at this. Xmega devices uses a different type of initialization than traditional MEGA.


----------------------------------------------------------------------

>Comment By: Thomas Holland (innot)
Date: 2010-07-01 15:43

Message:
Some internal functions like "read fuses from MCU" try to automatically
detect which MCU type is connected. This was done as a safeguard against
user errors where the connected MCU is not the same as set for the
project.
They do this by passing -pm16 to avrdude and parsing the response from
avrdude (which will report the correct MCU type)

It seems that this autodetection fails with ATXmegas, but I don't have any
ATXmegas to test this (I just ordered an XPlain board as a remedy :-).

So, in the meantime could you please provide the full avrdude console
output? (If you haven't done this already please select
Window->Preferences...->AVR->AVRDude -> Log internal AVRDude output to
console).
This way I could already start to work on the bug while I wait for my
XPlain board.




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=928231&aid=3023718&group_id=189165