second step_programming on Arduino IDE



this time, I decided to give my fabISP that I have produced on the 3rd week a chance, using my windows running computer.



open up Arduino's IDE terminal and make sure of the following

1. tools>board>ATtiny
2. tools>processor>ATtiny44
3. tools>clock>20mHz external
4. tools>programmer>usbtinyisp
5. then hit tools>burn bootloader


after making sure that your hardware is properly being represented in IDE, it's time to speak to your microcontroller (ATtiny44) to get it do something nice, for example blinking the LED you have mounted on your PCB! IDE offers a nice set of generic examples and the 'blink' one can be accessed through the root shown above



ideally, arduino wants you to use IDE on an arduino board, but you can definitely use your printed PCB. One of the most critical points is to make sure the pin numbers of your microcontroller corresponds to arduino's pin numbers!



in my case, my LED was connected to attiny44's pin 6 which apparently means pin 7 on arduino. Thus I changed all the pin specifications on the blink code to 7 (the generic pin number came as 13 on the code).



that life-changing moment when LED blinks...

first step_programming in C

I have decided to program my echo-world board on Ubuntu, using AVRISP mkII at the archshop



steps to be followed:

A.download "hello.ftdi.44.echo.c" and "hello.ftdi.44.echo.c.make" and "term.py" files from htm embedded programming page and make sure to save them to the same directory.

B. open up your terminal

C. type the following:

1. $ make -f hello.ftdi.44.echo.c.make

wait for response:


2. $ sudo make -f hello.ftdi.44.echo.c.make program-avrisp2-fuses

wait for response:


3. $ sudo make -f hello.ftdi.44.echo.c.make program-avrisp2

wait for response:


4. $ python term.py /dev/ttyUSB0 115200

* if you are using a fabisp, then change "avrisp2" to "usbtiny" on the C code above!

D.wait for the term.py windows to show up in which what you type will be echoed by the ATtiny44 microcontroller!