usbasp problems

Post Reply
labs
Posts: 2
Joined: Sat Jan 07, 2012 5:38 pm
Country: -
Location: Elkins WV

usbasp problems

Post by labs » Sat Jan 07, 2012 6:31 pm

Hello, new here and trying to find an answer to a problem. I bought one of these usbasp programmers and followed the way undcon.com installed his using a female usb A plug, when I plug in the transmitter to the computer the transmitter beeps every second and when I try to read eeprom from transmitter I get this warning below. I wired the ribbon cable following

http://www.youtube.com/watch?v=2Yv2rCxf ... r_embedded

following this video and have even tried it with the female A plug removed and just plugged the programmer into a male to female cable I have checked my board wiring over and over anyone know what might be causing this problem ? thanks in advance for any help,I feel like I am just overlooking something .

avrdude.exe: warning: cannot set sck period. please check for usbasp firmware update.
avrdude.exe: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.01s

avrdude.exe: Device signature = 0x1e9602
avrdude.exe: Expected signature for ATMEGA128 is 1E 97 02
Double check chip, or use -F to override this check.

avrdude.exe done. Thank you.


=================================================================================
AVRDUDE done - exit code 1
=================================================================================


PNaz
Posts: 142
Joined: Tue Dec 27, 2011 5:28 pm
Country: -
Location: Kaleden (Twin Lake), British Columbia

Re: usbasp problems

Post by PNaz » Sat Jan 07, 2012 7:02 pm

I get the same warning about the sck but I have no problems with the programmer. Everything seems to work fine so I ignore the warning.

Paul
Last edited by PNaz on Sat Jan 07, 2012 8:44 pm, edited 1 time in total.

User avatar
MikeB
9x Developer
Posts: 17439
Joined: Tue Dec 27, 2011 1:24 pm
Country: -
Location: Poole, Dorset, UK

Re: usbasp problems

Post by MikeB » Sat Jan 07, 2012 7:32 pm

labs, what is the command line to avrdude? The processor on the 9x is an ATMEGA64, not an ATMEGA128, hence the signature warning.
The sck error may also be a problem on the command line asking for too fast a speed.

Mike.
erskyTx/er9x developer
The difficult we do immediately,
The impossible takes a little longer!

labs
Posts: 2
Joined: Sat Jan 07, 2012 5:38 pm
Country: -
Location: Elkins WV

Re: usbasp problems

Post by labs » Sun Jan 08, 2012 2:25 am

:roll: atmega 64 was the problem apparently I had changed it? or it was just set wrong, even though it still wanted to give warnings a few try's it loaded the ER9X no problems except...... in my excitement I forgot to save my old software :oops: and loaded the new, but its working fine, thanks for opening my eyes a little. had allot on my mind lately and I felt i was just overlooking something. Thanks guys very much!

User avatar
GrootWitbaas
Posts: 358
Joined: Tue Dec 27, 2011 8:57 pm
Country: -
Location: Germany

Re: usbasp problems

Post by GrootWitbaas » Sun Jan 08, 2012 10:03 am

you will never look for the old software, but if you do there is a link here :)
General trouble maker and wannabee Dev


B12
Posts: 41
Joined: Tue Dec 27, 2011 6:16 pm
Country: -
Location: Finland

Re: usbasp problems

Post by B12 » Sun Jan 08, 2012 12:39 pm

labs wrote: when I plug in the transmitter to the computer the transmitter beeps every second and when I try to read eeprom from transmitter I get this warning below.

avrdude.exe: warning: cannot set sck period. please check for usbasp firmware update.

avrdude.exe: Device signature = 0x1e9602
avrdude.exe: Expected signature for ATMEGA128 is 1E 97 02
Double check chip, or use -F to override this check.
The transmitter beebs every second because of the low voltage warning: The transmitter warning is set at 8.8V and the usb port supplies only 5V. This is normal and can be ignored.

The SCK-warning is normal and is to be ignored.

I also got the device signature warning when I first tried eepe. This was resolved by letting the "port" box empty in the eepe configuration. Do not put usb in the settings even though you are using usb programmer. I do not know why it is so.

Romolo
9x Developer
Posts: 1109
Joined: Sat Dec 31, 2011 12:11 am
Country: -
Location: Massa (MS), Tuscany, Italy

Re: usbasp problems

Post by Romolo » Tue Jan 24, 2012 10:04 am

You have selected wrong MCU, stock 9x has an ATMEGA64A not ATMEGA128 .....

migtrib
Posts: 2
Joined: Mon Jan 23, 2012 4:12 pm
Country: -

Re: usbasp problems

Post by migtrib » Wed Jan 25, 2012 4:01 pm

Romolo wrote:You have selected wrong MCU, stock 9x has an ATMEGA64A not ATMEGA128 .....
What should be selected as MCU ?
Because there is no support for ATMEGA64A.

I have a similar problem regarding ATMEGA64A.

I tried to submit requests with avrdude (by eepe) by using mcu ATMEGA64, code m64.

This is an attempt to read EEPROM from ATMEGA64A:

EDIT by MOD to place the code in code tags

Code: Select all

=================================================================================
AVRDUDE Iniciado\n
C:/Arquivos de programas/eePe/avrdude.exe -c usbasp -p m64 -P usb -U
eeprom:r:C:/tur-ori-eeprom.hex:i
=================================================================================
avrdude.exe: warning: cannot set sck period. please check for usbasp
firmware update.
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.
=================================================================================
AVRDUDE done - exit code 1
=================================================================================

------------------
This is an attempt to read EEPROM from ATMEGA64A, executing now with -vvvv:
------------------

=================================================================================
AVRDUDE Iniciado\n
C:/Arquivos de programas/eePe/avrdude.exe -c usbasp -p m64 -vvvv -P
usb -U eeprom:r:C:/eeprom-ori.bin:r
=================================================================================
avrdude.exe: Version 5.10, compiled on Jan 19 2010 at 10:45:23
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2009 Joerg Wunsch
System wide configuration file is "C:\Arquivos de programas\eePe\avrdude.conf"
Using Port : usb
Using Programmer : usbasp
avrdude.exe: seen device from vendor ->www.fischl.de<-
avrdude.exe: seen product ->USBasp<-
AVR Part : ATMEGA64
Chip Erase delay : 9000 us
PAGEL : PD7
BS2 : PA0
RESET disposition : dedicated
RETRY pulse : SCK
serial program mode : yes
parallel program mode : yes
Timeout : 200
StabDelay : 100
CmdexeDelay : 25
SyncLoops : 32
ByteDelay : 0
PollIndex : 3
PollValue : 0x53
Memory Detail :
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ---------- ---------
eeprom 4 20 64 0 no 2048 8 0 9000 9000 0xff 0xff
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ---------- ---------
flash 33 6 128 0 yes 65536 256 256 4500 4500 0xff 0xff
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ---------- ---------
lfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ---------- ---------
hfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ---------- ---------
efuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ---------- ---------
lock 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ---------- ---------
calibration 0 0 0 0 no 4 0 0 0 0 0x00 0x00
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ---------- ---------
signature 0 0 0 0 no 3 0 0 0 0 0x00 0x00
Programmer Type : usbasp
Description : USBasp, http://www.fischl.de/usbasp/
avrdude.exe: auto set sck period (because given equals null)
avrdude.exe: warning: cannot set sck period. please check for usbasp
firmware update.
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.
=================================================================================
AVRDUDE done - exit code 1
=================================================================================

--------------
This is an attempt to read FLASH from ATMEGA64A, with -vvvv:
--------------

=================================================================================
AVRDUDE Iniciado\n
C:/Arquivos de programas/eePe/avrdude.exe -c usbasp -p m64 -vvvv -P
usb -U flash:r:C:/flash-ori.bin:r
=================================================================================
avrdude.exe: Version 5.10, compiled on Jan 19 2010 at 10:45:23
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2009 Joerg Wunsch
System wide configuration file is "C:\Arquivos de programas\eePe\avrdude.conf"
Using Port : usb
Using Programmer : usbasp
avrdude.exe: seen device from vendor ->www.fischl.de<-
avrdude.exe: seen product ->USBasp<-
AVR Part : ATMEGA64
Chip Erase delay : 9000 us
PAGEL : PD7
BS2 : PA0
RESET disposition : dedicated
RETRY pulse : SCK
serial program mode : yes
parallel program mode : yes
Timeout : 200
StabDelay : 100
CmdexeDelay : 25
SyncLoops : 32
ByteDelay : 0
PollIndex : 3
PollValue : 0x53
Memory Detail :
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ---------- ---------
eeprom 4 20 64 0 no 2048 8 0 9000 9000 0xff 0xff
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ---------- ---------
flash 33 6 128 0 yes 65536 256 256 4500 4500 0xff 0xff
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ---------- ---------
lfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ---------- ---------
hfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ---------- ---------
efuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ---------- ---------
lock 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ---------- ---------
calibration 0 0 0 0 no 4 0 0 0 0 0x00 0x00
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ---------- ---------
signature 0 0 0 0 no 3 0 0 0 0 0x00 0x00
Programmer Type : usbasp
Description : USBasp, http://www.fischl.de/usbasp/
avrdude.exe: auto set sck period (because given equals null)
avrdude.exe: warning: cannot set sck period. please check for usbasp
firmware update.
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.
=================================================================================
AVRDUDE done - exit code 1
=================================================================================
Any Clues ?

thanks
migtrib
migtrib

User avatar
cre8tiveleo
Posts: 1434
Joined: Tue Dec 27, 2011 6:13 pm
Country: -
Location: Ontario,(GTA North)
Contact:

Re: usbasp problems

Post by cre8tiveleo » Wed Jan 25, 2012 6:21 pm

make sure you don't have any cold solder joints. (if you wired it correctly? proper pin to socket, etc.)
leave port setting blank (burn>config avrdude configuration, port should be blank) (this is something everyone overlooks, it's been said many times, in many forums)
make sure you have the latest drivers, don't just overwrite the ones you have, you need to uninstall the old ones, then install the new ones.

just my two cents.

migtrib
Posts: 2
Joined: Mon Jan 23, 2012 4:12 pm
Country: -

Re: usbasp problems

Post by migtrib » Wed Jan 25, 2012 9:58 pm

Thankts
cr8tive_leo wrote:make sure you don't have any cold solder joints. (if you wired it correctly? proper pin to socket, etc.)
leave port setting blank (burn>config avrdude configuration, port should be blank) (this is something everyone overlooks, it's been said many times, in many forums)
make sure you have the latest drivers, don't just overwrite the ones you have, you need to uninstall the old ones, then install the new ones.

just my two cents.
When we realize it did not worked we redone all the solder joins.
As for the drivers, we use the same station to read and write another radio that has ATMEGA64, work just fine.

I would like to leave a question here to all people of the list if anyone had been successful communicating
by usbasp to the *** ATMEGA64A ***
migtrib

User avatar
GrootWitbaas
Posts: 358
Joined: Tue Dec 27, 2011 8:57 pm
Country: -
Location: Germany

Re: usbasp problems

Post by GrootWitbaas » Thu Jan 26, 2012 10:10 am

M64 works fine.

Based on your post above, can you tell me what Version board you have, if possible post a picture of you connections inside. I'm taking a wild guess here, you have a Ver1 board and soldered to the pads. you need to solder one to the Resistor/Chip, not the pad ....this is only a guess, but I think this is what is wrong. See this here (yes it is for SP board, but shows the Ver of the board)
General trouble maker and wannabee Dev

Romolo
9x Developer
Posts: 1109
Joined: Sat Dec 31, 2011 12:11 am
Country: -
Location: Massa (MS), Tuscany, Italy

Re: usbasp problems

Post by Romolo » Thu Jan 26, 2012 11:54 am

migtrib wrote: When we realize it did not worked we redone all the solder joins.
As for the drivers, we use the same station to read and write another radio that has ATMEGA64, work just fine.

I would like to leave a question here to all people of the list if anyone had been successful communicating
by usbasp to the *** ATMEGA64A ***
I have an usbasp inside my radio, and it works flawless. I also modified the usbasp changing the USB port to have a female one
Have a look here for the result: viewtopic.php?f=25&t=25

davodavo
Posts: 2
Joined: Fri Feb 10, 2012 1:43 am
Country: -

Re: usbasp problems

Post by davodavo » Fri Feb 10, 2012 1:47 am

GrootWitbaas wrote:you will never look for the old software, but if you do there is a link here :)
That is only a link to the manual, does anyone have the correct link? :?:

Romolo
9x Developer
Posts: 1109
Joined: Sat Dec 31, 2011 12:11 am
Country: -
Location: Massa (MS), Tuscany, Italy

Re: usbasp problems

Post by Romolo » Sat Feb 11, 2012 1:53 pm

Here is the link...

viewtopic.php?f=37&t=89#p617

User avatar
GrootWitbaas
Posts: 358
Joined: Tue Dec 27, 2011 8:57 pm
Country: -
Location: Germany

Re: usbasp problems

Post by GrootWitbaas » Sat Feb 11, 2012 8:49 pm

Fixed the link in the original post ...sory
General trouble maker and wannabee Dev

User avatar
erazz
9x Developer
Posts: 682
Joined: Tue Dec 27, 2011 6:25 pm
Country: -
Location: NJ-USA
Contact:

Re: usbasp problems

Post by erazz » Sat Feb 11, 2012 9:08 pm

migtrib wrote:
Romolo wrote:You have selected wrong MCU, stock 9x has an ATMEGA64A not ATMEGA128 .....
What should be selected as MCU ?
Because there is no support for ATMEGA64A.

I have a similar problem regarding ATMEGA64A.

I tried to submit requests with avrdude (by eepe) by using mcu ATMEGA64, code m64.

This is an attempt to read EEPROM from ATMEGA64A:
=================================================================================
AVRDUDE Iniciado\n
C:/Arquivos de programas/eePe/avrdude.exe -c usbasp -p m64 -P usb -U
eeprom:r:C:/tur-ori-eeprom.hex:i
=================================================================================
avrdude.exe: warning: cannot set sck period. please check for usbasp
firmware update.
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.
=================================================================================
AVRDUDE done - exit code 1
=================================================================================

Any Clues ?

thanks
migtrib


Please don't post outputs with -vvv on them. It's excruciatingly long and doesn't contain any real information.
The first one (quoted above) was quite sufficient.

It tells us that for some reason the programmer cannot talk to the MCU. 99.9% of the time it's due to a bad connection.
Are you using the Smartieparts board? If so, you might want to try and clean the pads with alcohol. Sometimes they have a film on them that causes this problem.
It could laso be a so called "v1" board with a pad that is placed on the wrong pin. Look up the wiring tutorails to find out what kind of board you have.
If you're using a protostack usbasp programmer the cause is most likely to be wrong wiring or bad solder joint. Recheck everything.
Z

BEWARE - WE ARE IN THE AIR!!!
What goes up... Should be controlled by a 9X!

User avatar
cre8tiveleo
Posts: 1434
Joined: Tue Dec 27, 2011 6:13 pm
Country: -
Location: Ontario,(GTA North)
Contact:

usbasp problems

Post by cre8tiveleo » Sat Feb 11, 2012 9:12 pm

We should call the boards Rev 1 and Rev 2, instead of V1 and v2.

Revision sounds better for hardware, and won't confuse the poop out of people.

Or at least rev1 for the board with proper pad to work with the sp board, and original board for the pcb with the pad in the wrong place.

:D


---
I am here: http://maps.google.com/maps?ll=44.003107,-79.457278

User avatar
rperkins
Posts: 1422
Joined: Sun Jan 08, 2012 12:51 pm
Country: -

Re: usbasp problems

Post by rperkins » Sat Feb 11, 2012 10:21 pm

cre8tiveleo wrote:We should call the boards Rev 1 and 2, instead of V1 an
I like that idea
Vx -for original firmware version, which also denotes Tx protocol.
Revx -for mainboard version which primarily matters to smartie parts users.

Spelling mistake fixed by your friendly MOD

User avatar
wheelspinner20
Posts: 175
Joined: Tue Dec 27, 2011 6:22 pm
Country: -
Location: Michigan, U.S.

Re: usbasp problems

Post by wheelspinner20 » Sat Feb 11, 2012 10:49 pm

smartie parts users
Its Smartieparts

See-- http://www.smartieparts.com/shop/
no more quippy little latin phrases.! Its old

User avatar
rperkins
Posts: 1422
Joined: Sun Jan 08, 2012 12:51 pm
Country: -

Re: usbasp problems

Post by rperkins » Sat Feb 11, 2012 11:56 pm

Oops. So sorry


Post Reply

Return to “PROGRAMMERS”