I soldered at 300 degree celcius. Again tried on new PCB.. same ..device not detected.. device signature read = 0x000000 What should be the length of track between ISP connector on PCB & microcontroller. Should power supply circuit be kept away from ISP tracks ?
Regards, John On Thu, Sep 6, 2012 at 7:08 PM, John cliffer <john17...@gmail.com> wrote: > >> > http://helix.air.net.au/files/4613/4609/6931/avrdude-5.11svn1102-win32.zip > > This contains an exe & config file. Is it right binary build for it ? > > > On Thu, Sep 6, 2012 at 7:07 PM, John cliffer <john17...@gmail.com> wrote: > >> >> As it's only one particular AVR device that's got problems with your >> USBasp, the question whether it's a firmware issue (rather than >> something with avrdude itself) remains though. >> >> yes problem is comming with AT90CAN128. >> Atmega32 is working fine for me. >> >> AT90CAN128 Device signature is read as -- 0x000000 , by avrdude . >> I dont know where the problem is. I have verified the circuit many times >> here . >> Its the same ISP ckt on hardware which i have used for years. >> >> >> Kind Regards, >> John >> >> On Thu, Sep 6, 2012 at 7:03 PM, John cliffer <john17...@gmail.com> wrote: >> >>> >> , but you should at least try the latest release (version 5.11) as >>> well. >>> >>> What is the right path for it ? >>> >>> >>> On Thu, Sep 6, 2012 at 6:48 PM, Joerg Wunsch <j...@uriah.heep.sax.de>wrote: >>> >>>> As John cliffer wrote: >>>> >>>> > >>>> http://helix.air.net.au/files/4613/4609/6931/avrdude-5.11svn1102-win32.zip >>>> > >>>> > Is it right package for avrdude to use USBASP ? >>>> >>>> It's a development snapshot, rather than a regular release. >>>> >>>> If you've got problems with that, it's certainly good to report them >>>> here (as the developers are listening here), but you should at least >>>> try the latest release (version 5.11) as well. If 5.11 works but the >>>> above snapshot doesn't, please tell us. >>>> >>>> As it's only one particular AVR device that's got problems with your >>>> USBasp, the question whether it's a firmware issue (rather than >>>> something with avrdude itself) remains though. I'm afraid only the >>>> author of the USBaps can help in debugging firmware problems. >>>> >>>> -- >>>> cheers, J"org .-.-. --... ...-- -.. . DL8DTL >>>> >>>> http://www.sax.de/~joerg/ NIC: JW11-RIPE >>>> Never trust an operating system you don't have sources for. ;-) >>>> >>>> _______________________________________________ >>>> avrdude-dev mailing list >>>> avrdude-dev@nongnu.org >>>> https://lists.nongnu.org/mailman/listinfo/avrdude-dev >>>> >>> >>> >> > _______________________________________________ avrdude-dev mailing list avrdude-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/avrdude-dev
