1. 

   rhine2k11
   Member

   hello,

   i am encountering this problem suddenly from today morning ... whenever i am trying to burn some code i get this message ..

   C:\Windows\WinAVR-20100110\bin\avrdude.exe -C C:\Windows\WinAVR-20100110\bin\avrdude.conf -p m16 -P usb -c usbasp -U hfuse:r:C:\Users\Rhine\AppData\Local\Temp\hfuse1411310152233524947.hex:r -U lfuse:r:C:\Users\Rhine\AppData\Local\Temp\lfuse473921481349726365.hex:r

   avrdude.exe: error: programm enable: target doesn't answer. 1
   avrdude.exe: initialization failed, rc=-1
   Double check connections and try again, or use -F to override
   this check.

   avrdude.exe done. Thank you.

   However , i have checked all connections . they are fine . I use the same code, same burner, same programmer for a different mcu , the code burns with no issues . I cant even disable the jtag on the board due to this . Please help.

   Thanks and Regards,

   Debrup

   • Submit this to Script & Style
   • Share this on Blinklist
   • Share this on del.icio.us
   • Digg this!
   • Post this on Diigo
   • Share this on Reddit
   • Buzz up!
   • Stumble upon something good? Share it on StumbleUpon
   • Share this on Technorati
   • Share this on Mixx
   • Post this to MySpace
   • Submit this to DesignFloat
   • Share this on Facebook
   • Tweet This!
   • Email this to a friend?
   • Promote this on Orkut
   • Suggest this article to ToMuse
   • Subscribe to the comments for this post?
   • Share this on Linkedin
   • Seed this on Newsvine
   • Share this on Devmarks
   • Add this to Google Bookmarks
   • Add this to Mister Wong
   • Add this to Izeby
   • Share this on Tipd
   • Share this on PFBuzz
   • Share this on FriendFeed
   • Mark this on BlogMarks
   • Blog this on Blogger
   • Submit this to Twittley
   • Share this on Fwisp
   • Moo this on DesignMoo!
   • Share this on BobrDobr
   • Add this to Yandex.Bookmarks
   • Add this to Memory.ru
   • Add this to 100 bookmarks
   • Add this to MyPlace
   • Submit this to Hacker News
   • Send this page to Print Friendly
   • Bump this on DesignBump
   • Add this to Ning
   • Post this to Identica
   • Save this to Xerpi
   • Share this on Wikio
   • Tip this to TechMeme
   • Sphinn this on Sphinn
   • Post this to Posterous
   • Grind this! on Global Grind
   • Ping this on Ping.fm
   • Submit this to NUjij
   • Submit this to eKudos
   • Submit this to Netvouz
   • Submit this to Netvibes
   • Share this on Fleck
   • Share this on Blogosphere News
   • Blend this!
   • Add this to Wykop!
   • Engage with this article!
   • Share this on Hyves
   • Push this on Pusha
   • Bookmarks this on Hatena Bookmarks
   • Store this link on MyLinkVault
   • Submit this to SlashDot
   • Add to a lense on Squidoo
   • Submit this story to Propeller
   • Submit this to FAQpal
   • Clip this to Evernote
   • Submit this to Meneame
   • Submit this to Bitacoras
   • Submit this link to JumpTags
   • Share this on Bebo
   • Submit tip to N4G
   • Submit this to Strands
   • Share this on Tumblr
   • Add this to Stumpedia
   • Post this to Current
   • Share this on Plurk

   Posted 4 months ago #
2. 

   rudr_p
   Member

   target mcu is not working or try with other programmer

   Posted 4 months ago #
3. 

   rhine2k11
   Member

   what are the odds ? the mcu got fried ?

   Posted 4 months ago #
4. 

   rudr_p
   Member

   yea or you may have disabled isp through fuses

   Posted 4 months ago #
5. 

   Mahesh
   Administrator

   I wanted to know which software are you using for programming and which programmer are you using to transfer? Because if you are using ilabs avr hid programmer then you have to select in device stk500v2 and in port avrdoper, if you are programming using avrdude else if you are programming using any other software then please inform, I will have a look into it.

   Mahesh Murty
   Senior Fellow
   ilabs The Robotics and Embedded Systems Research Lab

   Posted 4 months ago #
6. 

   rudr_p
   Member

   @ mahesh
   he says other mcu burns with same programmer so mostly it is burned or some fuse jhol jhal.

   Posted 4 months ago #
7. 

   rhine2k11
   Member

   Fixed it . Used the jumper and edited the fuse hex from the working mcu . Working fine now . Wasn't a problem with the mcu .

   Posted 4 months ago #
8. 

   rudr_p
   Member

   so what was wrong with the fuse

   Posted 4 months ago #
9. 

   rhine2k11
   Member

   couldn't pinpoint the exact reason because i couldn't read the fuses with burn-o-mat. But setting the jumper on the programmer allowed me to atleast read the fuse hex. Copied the l and r vals from the working mcu and set it on this one and it works like a breeze . I dont however understand why the mcu changed the fuse all by itself. I didnt do any mumbojumbo on it . Will have to figure this thing out.

   Posted 4 months ago #
10. 

    rudr_p
    Member

    wow magic magic :p

    Posted 4 months ago #

RSS feed for this topic

Reply

You must log in to post.