Device Signature incorrect

[GoogleCodeExporter]

What steps will reproduce the problem?
Simply check communication after fixing PCB reset issue (missing connection)
1. avrdude -c usbtiny -p m328p

What is the expected output? What do you see instead?
avrdude: Device signature = 0x1e9514
avrdude: Expected signature for ATMEGA328P is 1E 95 0F

What version of the product are you using? On what operating system?
V.4

Please provide any additional information below.
Corrected PCB bug of missing Reset connection to Pin1 Atmel328p

Firmware seems not loaded (board is not working yet

Original issue reported on code.google.com by Albertwa...@gmail.com on 15 Mar 2013 at 1:23

Attachments:

• 328P_error.txt

[GoogleCodeExporter]

Try changing your device name to 'M328' rather than 'M328P'. Please reply back 
if this fixes your problem.

Original comment by mrpilot...@gmail.com on 15 Mar 2013 at 2:43

[GoogleCodeExporter]

Just tried now, but m328 is not recognized by the system, once I m328 is used 
instead I get the long list of Atmel microP available and the 328 is not there 
only 328P

Original comment by Albertwa...@gmail.com on 15 Mar 2013 at 2:50

[GoogleCodeExporter]

please see the txt file with the Atmel codes available

Original comment by Albertwa...@gmail.com on 15 Mar 2013 at 2:55

Attachments:

• 328_error1.txt

[GoogleCodeExporter]

Ok fixed the problem with a tweak of the AVRdude.conf file as described in this 
post
http://www.instructables.com/id/Bootload-an-ATmega328/step6/ATmega328-PU-workaro
und/

I would recommend to post this solution since I suppose it going to be an issue 
in case Digikey send the PU version instead of the P version of the 328

Thanks

Original comment by Albertwa...@gmail.com on 15 Mar 2013 at 3:58

[GoogleCodeExporter]

The device signature 1E9514 is correct for the ATMega328. The commands that you 
copied from the Wiki assume you bought the ATMega328P. The "P" version is more 
popular because it allows lower power consumption states for mobile (battery 
operated) applications. Since you bought the non-"P" version, you need to edit 
your .conf file to add the missing controller. I read the directions for how to 
do that a few weeks ago, but I didn't bookmark it and now it's not showing up 
for my search. I think it was in a tutorial by Lincomatic, but I wouldn't swear 
to it.  Alternately, you could just buy another chip with the "P". They're 
pretty cheap. 

You could also try my guide for burning HEX files with Atmel Studio. Look under 
the Wiki section. The Studio IDE knows how to talk to ATMega328 chips (That's 
the chip I'm using too) and it's simple point and click. If you do this, I 
HIGHLY recommend skipping the new Atmel Studio 6 because I'm finding that it's 
a huge, bloated, buggy, steaming pile of bovine excrement. Use the much older, 
but rock-solid, AVR Studio 4.19 available here: 
http://www.atmel.com/tools/avrstudio4.aspx

Another reason to use the older tool is that AVR Studio 4.19 takes only 5 
minutes to download and install versus the 3-4 hour ordeal I endured to load 
Studio 6.

Original comment by mrpilot...@gmail.com on 15 Mar 2013 at 4:03

[GoogleCodeExporter]

Original comment by chris1howell83 on 29 Apr 2013 at 2:07

• Changed state: Done