Difference between revisions of "AVR Drivers"

AVR Drivers (view source)

Revision as of 15:26, 25 June 2013

402 bytes added , 15:26, 25 June 2013

m

Added details

JackCY

confirmed

36

edits

@@ Line 127: / Line 127: @@
 Now everything is installed and set up. You should be able to plug in your USB programmer with the cable leading to the clip. Attach the clip to the Atmel chip right-side up with at least the 5 critical pins wired correctly.
+Be aware that AVRDUDE does not officially support ATtiny13A and you will be using AVRDUDE with ATtiny13 setting "-p t13" instead of unsupported "-p t13a". The difference I found were lockbits when reading with ATtiny13A with it's proper setting compared to ATtiny13 setting. Otherwise it could work if you know what you're doing.
 Now open a command window in Windows (or whatever you are in) and typing this command at the C: prompt:
@@ Line 132: / Line 134: @@
    avrdude -p t13 -c usbasp -n
-The command above calls up avrdude. "-p t13" means you are talking to an Atmel ATTiny13A chip. "-c usbasp" says you are using the USBASP controller. "-n" means no writing, since we're not actually doing anything yet. With USB, you shouldn't have to enter the port number, but some people have to go find out what port the USB is assigned to and if it is Port 2, they add "-P com2" after usbasp.
+The command above calls up avrdude. "-p t13" means you are talking to an Atmel ATTiny13 chip (but could unofficially work with ATtiny13A as well and most use it so). "-c usbasp" says you are using the USBASP controller. "-n" means no writing, since we're not actually doing anything yet. With USB, you shouldn't have to enter the port number, but some people have to go find out what port the USB is assigned to and if it is Port 2, they add "-P com2" after usbasp.
 The command above should generate a message that the AVR device is initialized and ready to accept instructions. If the connection is not working, you will get something like