As I get closer to actually filling the paludarium with water, plants and eventually animals, I need to put a lot of focus on the electronics. The lighting armature on top, or as I like to call it, the Canopy is fully electronic. Without electronics the lights won’t even go on… High time to put some work into the Canopy to upgrade this piece of hardware to version 2.0.<\/p><\/blockquote>\n
Inside the Canopy I have 12 Atmel AVR controllers (ATtiny2013’s). These tiny controllers have been programmed in three flavors: LED, HALOGEN and FAN units. You guessed it, each type of controller has its own code. Luckily I programmed a single code, and when compiling this code I can tell the code which type it is supposed to compile. These little AVR controllers are programmed in C:<\/p>\n #include “main.h” Code snippet. This is the main() function where all stuff gets initialized<\/em><\/p>\n No I will not bore you with all of the code here \ud83d\ude42<\/p>\n This old code that I have for these controllers has proven to be pretty stable. Yet I need to change some minor things, and add or change some features. After a short while I got the compiling environment (an antique version 6 of the ImageCraft AVR compiler<\/a>) up and running again. I could now compile the code again. At my first attempt, I compiled the most complex code, the LED version. Compilation was a success, device was 98% percent full… I’d better not find NEW features cause they’d never fit. If you think these controllers only have 2KB of flash (yes 2 KILObytes, 2048 bytes and not Megabytes or Gigabytes), 98% is pretty darn full. Still, it works so I’m not complaining. As nice as compiling may sound, the compiled code had to be actually programmed into the chips. For that, you need a programmer. Time to dive into my box of old projects, and there it was: The glorious AVR programmer for ATmega32 and ATtiny2313 chips:<\/p>\n My good old programmer for Atmel Mega32 and Attiny2313 chips<\/p><\/div>\n Yes it is no high-tech. Ok it is somewhat oldish. Ok ok, it is totally oldskool. Is that a USB port? Yes, but I only use USB to power the thing. The large connector in front is actually a PC parallel port connection. I had to search in order to find a PC that still has a parallel port. Why not upgrade to a USB programmer? Uhmmm basically because this one still works \ud83d\ude1b<\/p>\n I had an old version of Claudio Lanconelli’s PonyProg<\/a> that I used to shoot the chips. After some testing I managed to read, write and erase the ATtiny2313 chips. <\/p>\n Mission accomplished!<\/strong> I now can alter the code, reprogram the 12 chips in the Canopy and start playing around. On to the next-of-many things to get going.<\/p>\n","protected":false},"excerpt":{"rendered":" As I get closer to actually filling the paludarium with water, plants and eventually animals, I need to put a lot of focus on the electronics. The lighting armature on top, or as I like to call it, the Canopy … Read more
\nFirst things first: Getting the code compiling again<\/strong><\/p>\n
\n#include “serial.h”
\n#include “timer.h”
\n#include “pwm.h”
\n#include “eeprom.h”
\nint main (void)
\n{
\n for (;;)
\n {
\n \/* Set initial levels of the hardware outputs *\/
\n outp(0xFF, PORTB); \/* All input lines pullup, outputs push TTL to high *\/
\n outp(0xe3, PORTD); \/* All input lines pullup, outputs push TTL to high except DigExp *\/
\n \/* Init of hardware: I\/O directions *\/
\n outp(0x1C, DDRB); \/* PB0-7 are all inputs except PB2,3,4 *\/
\n outp(0x3e, DDRD); \/* PD0-7 are all inputs except PD5=OC0B and PD1=TX, also PD2-PD4 *\/
\n \/* Init the modules *\/
\n InitEEPROM();
\n InitSerial();
\n InitPWM();
\n InitTimer();\t\/* incorporates sei(); call to globally enable interrupts *\/
\n while (1)
\n {
\n }
\n }
\n}
<\/p>\n
\n
\nProgramming the ATtiny2313’s<\/strong><\/p>\n![\"My](\"http:\/\/paluweb.nl\/wp-content\/uploads\/2013\/08\/IMG_3453.jpg\")
<\/a>