My AVR programmer dose not recognize the chip
Moderators: adafruit_support_bill, adafruit

My AVR programmer dose not recognize the chip

by micropad on Sat Dec 15, 2012 3:04 am

Dear All,
I am new for AVR
I build my own AVR programmer


software - PonyProg

Hardware test is Ok

unfortunately it does not recognize the the MY AT MEGA 32A MCU

Device missing or unknown device (-24)
Please advice
Posts: 1
Joined: Sat Dec 15, 2012 12:49 am

Re: My AVR programmer dose not recognize the chip

by franklin97355 on Sat Dec 22, 2012 3:14 pm

Sounds like you need to post to their website and ask.
User avatar
Posts: 8232
Joined: Mon Apr 21, 2008 2:33 pm
Location: Lacomb, OR.

Re: My AVR programmer dose not recognize the chip

by eventhorizon on Mon Dec 24, 2012 1:11 am

For your first programmer, I suggest you use this programmer instead: DASA-3. Also, take note that making a programmer comes with a matching program, or see if it's compatible with AVRDude.

So here's a quick step-by-step to get you up:
-Download WINAVR first, then install it.
-After installing, open up CMD (command prompt), then simply type in: "avrdude -h" (without the quotes). If a help option came out
then you have successfully installed avrdude.
-Now, type in: "avrdude -c ?". This will give you a list of compatible/supported programmers by avrdude.
-I'm still suggesting you build the DASA-3 programmer.
-Find out what number your serial port is in. The on-board serial port is usually on COM1, though, if you are using a USB-Serial, find
the COM port number from the "Device Manager".
-Find out what AVR you are using, now let's assume that you are using ATMEGA8 for this example.
-Power up your AVR and programmer with 5v, connect the programmer, then type in: "avrdude -P COM1 -c dasa3 -p atmega8 -v".

At this point if it still can't recognize the chip:
-Make sure your AVR and programmer is receiving power
-Connections are correct
-Your programmer is compatible with your program, or
-You are using the correct serial port.

Possible things that might be causing the problem:
-Faulty components
-Using a banned USB-Serial (you need a PL2303 based USB-Serial one), or
-You just don't know what you are doing.
Out of one hole, and into another.
Posts: 114
Joined: Tue Jan 25, 2011 6:09 pm
Location: Quezon City, Philippines