Bugs item #3176611, was opened at 2011-02-09 17:56
Message generated for change (Tracker Item Submitted) made by o_nn_o
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=928231&aid=3176611&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: None
Priority: 5
Private: No
Submitted By: Onno (o_nn_o)
Assigned to: Matthew McDougal (mmdoogie)
Summary: AVRDUDE uses -pnull
Initial Comment:
Problem:
I'm using the plugin for an atxmega32d4. This device is not officially supported by avrdude, but with a modified avrduce.conf file, it works fine from the commandline. (I configured the plugin to use this file as the AVRDude config file) When I want to setup the plugin to program my device (and I select the device from the list, or let it determine the device with the Load from MCU button) it show a warning "This MCU is not supported by AVRDude"
When I build and program the device, the programming fails because avrdude is called with -pnull in stead of -px32d4
If I select an other device (say atxmega32a4) it does start to program (avrdude is called with -px32a4) but it will fail because of the wrong device id
Solution:
Let me fill in the device id if the device is not supported by avrdude, or scan the custom configuration file to find out the device id.
Configuration:
avr-eclipse 2.3.4.20100807PRD
eclipse 3.6.1
eclipse CDT 7.0.1
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=928231&aid=3176611&group_id=189165
|
