after making a usbtiny isp programmer and using it for 6 months, i was looking at making another one for carrying around. i like the simplicy of the usbtiny isp design but would like to make it even smaller and take less parts. one thing in the original design that i want to change is to eliminate the use of clock crystal. one solution i found is that v-usb drivers supports the 16.5Mhz internal oscillator on attiny25/45/85 devices. so i start out this project to have usbtiny isp employs v-usb for usb communication. the immediate benefits is that it saves space and have less component counts (no more crystals).
description from http://www.xs4all.nl/~dicks/avr/usbtiny/
USBtiny is a software implementation of the USB low-speed protocol for the Atmel ATtiny microcontrollers. Of course, it will also work on the ATmega series. The software is written for an AVR clocked at 12 MHz. At this frequency, each bit on the USB bus takes 8 clock cycles, and with a lot of trickery, it is possible to decode and encode the USB waveforms by software. The USB driver needs approximately 1250 to 1350 bytes of flash space (excluding the optional identification strings), depending on the configuration and compiler version, and 46 bytes RAM (excluding stack space). The C interface consists of 3 to 5 functions, depending on the configuration.
description from http://www.obdev.at/products/vusb/
V-USB is a software-only implementation of a low-speed USB device for Atmel's AVR microcontrollers, making it possible to build USB hardware with almost any AVR microcontroller, not requiring any additional chip.
video on construction and usage
Step 1: Features and Parts
* programming logic from usbtiny isp, mature avr-dude support
* small foot-print
* minimal components
* powers target device
note that the io lines to the target mcus are not protected. you can add 1k-2k resistors to SCK and MOSI and protect against possible wrong connections
based on the works found at
v-usb from framework http://www.obdev.at/vusb/
usbtiny isp http://www.xs4all.nl/~dicks/avr/usbtiny/
* attiny45/85 (85 is more easier to come by)
* 3.6v zener diodes (1n747,BZX79,..avoid 1W types)
* 68ohm resistor x 2
* 1.5K resistor
* mini breadboard 170 tiepoints
* usb cable (dollar shop usb printer cable is fine)
* 1k/2k resistors for io lines protection (optional)
* a working avr programmer (yes, it's a catch22, we need one to make one)
* working avr programming environment
Step 2: Breadboard Layout, Schematic, and Construction
* follow breadboard layout, there ain't that may components, 3 resistors, 2 diodes, 1 cap, plus an 8 pin mcu.
* get a dollar shop usb printer cable cut off the printer end, there will be 4 exposed wire, secure and make them into a 4 pin male header, we will use it to connect to the breadboard. consult schematic for layout and pin assignment (J1).
* watch out for diode polarity.
building and flashing the project
the project was built in a linux ubuntu lucid box with avr-gcc toolchain. it is assumed you already have such an environment, or you can find out from the internet how to setup one up. source codes are gnu gpl v2 licensed from inheritence.
the source code follows a convention recommended by v-usb, you can download the source package vusbtiny.tgz and untarred in into a project directory. within your source directory, there is a main.c, which is my version of modified usbtiny programmer. and a usbdrv sub-directory, which contains the v-usb layer. please observe licensing term from the above two projects when building this. my source on the programmer logic is based on Dick Streefland version and not the ladyada version (although they are almost the same).
for those who do not have a build too-chain, you can use the following binary
click to download vusbtiny.hex
and use avrdude to flash firmware
avrdude -c usbtiny -p t45 -e -V -U flash:w:usbtiny.hex
(if your device is a tiny85, replace -p t45 w/ -p t85)
source can be download here
click to download vusbtiny.tgz
untar the source package into your working directory
tar -zxvf vusbtiny.tgz
* do cd vsubtiny, to change into vusbtiny working directory
* ajust makefile for target device according to the chip you will be using. i.e. PROGRAMMER_MCU=t45 or t85
* do a make
* attach your favorite ISP programmer
* modify makefile and change your avrdude parameters if needed. the stock one assumes USBTiny programmer. i.e. AVRDUDE_PROGRAMMERID=usbtiny
* flash firmware via make install
after flashing firmware, we need to properly set the fuse, we are using pin 1 reset as io in this project
* ppl clock used as required by v-usb layer for usb timing
* reset pin disabled as we need to use it as io
avrdude -c usbtiny -p t45 -V -U lfuse:w:0xe1:m -U hfuse:w:0x5d:m -U efuse:w:0xff:m
this setting disables further programming via 5V SPI as we need the RESET pin (pin1) for io. you will need access to a HVSP programmer to recover the fuse.
Step 3: Usage and Application
direct flashing on breadboard
if you are using vusbtiny to flash 8 pin AVR devices, you can just press your target device on top of the programmer device. the programmer had been designed so that the programming pins matches w/ targets. there is one trick though, you will need to isolate pin 2 and 3 on the programmer mcu, as they are the USB D+ and D- pins connecting to the PC. i use a cut of scotch tape to achieve this, you can see it on the photos. show below is a tiny13v "riding" on the tiny45, ready to receive firmware.
ISP flashing via jumper
to program a target circuit via ISP (in-system programming), you need an ISP cable. here i am not using the standard 2x3 or 2x5 pin headers. instead i am using a 1x6 jumper which is more breadboard friendly, you can make 2x3 or 2x5 pin header by mapping them to J2 as shown on the breadboard layout and schematics. the following photo shows an tiny2313 ready to get flashed via ISP.
* cannot flash the firmware? check your original programmer, might need to adjust timing via -B flag in avrdude. try to read chip 1st, may be a bad fuse, may be your chip need an external clock signal. you may need to fix your chip back to default 1st.
* check connections
* if use different io pins, check code and connections
* you may substitute zener diodes w/ 500mw, 400mw types
* you may try reduce R3 value to 1.2K or less
* you are more likely to encounter avrdude timing problems, try -B flag of avrdude, have a shorter USB cable all helps
Participated in the