This forum has moved to forum.jeelabs.net - this read-only archive is for reference only!
Hi,
I'm trying to use the Inputplug as a sort of mini-arduino. The plug looks like an ideal platform for small automation jobs. Does anyone have any experience in using the arduino platform to program a ATtiny45 using an ISP. One could use a JeeNode and a "Flash Board" to program the Inputplug. The plug itself has all its pins available on the headers and the analog mux can be used to expand it's I/O cap.
Can this be done without reverting to AVRstudio etc...
I've done it with one of the other ATtinys, not the 45 though.
Having a look on the Arduino forums as there seem to be quite a few people doing this kind of thing, and it was there I found everything I needed to get going with my Attiny.
http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1189970096/6
This looks as an other interesting startpoint:
http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1255541325/0
Update... I got a set of ATtiny45 core files from http://sites.google.com/site/elettronicaarduinoesperimenti/Home/arduino-ide-and-attiny45/attiny45.zip?attredirects=0 Added a line to the boards.txt file : ##############################################################
attiny45.name=Arduino w ATtiny45
attiny45.upload.protocol=stk500 attiny45.upload.maximumsize=4096 attiny45.upload.speed=19200
attiny45.bootloader.lowfuses=0xdf attiny45.bootloader.highfuses=0xca attiny45.bootloader.path= attiny45 attiny45.bootloader.file=ATmegaBOOT.hex attiny45.bootloader.unlockbits=0x3F attiny45.bootloader.lockbits=0x0F
attiny45.build.mcu=attiny45 attiny45.build.fcpu=8000000L attiny45.build.core=attiny45
Got the ispflash sketch running on my JeeNode that was ISP connected using a breadboard to an attiny45
And...
It uploaded.. Now check if it works and go for the InputPlug..
Good news. Sounds like an interesting project.
But no succes for now..
Uploading seems to work but afterwards the attiny45 does not blink my led.. and I get an error during upload:
avrdude: please define PAGEL and BS2 signals in the configuration file for part ATtiny45
This one baffels me... Any ideas?
btw: I found core files for the attiny85 http://www.cheesefactory.us/arduinocores/
seems that the avrdude.conf file that comes with arduino environment does not define there PAGEL and BS2 for the tiny45 (have not found what they do)
BUT... after mounting a 10k resistor on the reset pin the chip runs my code !!
Now there is however a data check error after programming but it seems to be running fine !
avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0076
0x61 != 0x60
avrdude: verification error; content mismatch
does anybody know how to check or set the clockspeed.. I have the impression taht it is running at a very low speed..
with a sketch:
void loop()
{
digitalWrite(ledPin, HIGH); // set the LED on
delay(1); // wait for a second
digitalWrite(ledPin, LOW); // set the LED off
delay(1); // wait for a second
}
I think the les flashes at approx 30 Hz so the delay(1) results in a delay(33) could that be correct ?
That error message is bogus - ignore it.
I've been using the Flash Board (what else) to flash the Input Plug with the code it needs for multiplexing, and do it from the command line with avr-gcc, avrude, etc (on MacOSX). Always get that error - has something to do with support for that particular chip.
Here are the fuse settings I use, extracted from my Makefile:
# default, i.e. int RC osc, but no div/8, i.e. 8 MHz i.s.o. 1 MHz avrdude -p $(MCU) $(ISP) -qq -U lfuse:w:0xE2:m -U hfuse:w:0xDF:m -U efuse:w:0xFF:m
Ignore the message. Your problem must be something else.
PS. If you're interested in that sort of low-end ATtiny stuff: I've had a "Slave Plug" under wraps for some time, with room for two 8-SOIC ATtiny85's and port headers.
If you're willing to share your experiments here, email me - I can send you a board/plug with an ATTiny85 on it.
Been meaning to get to it ... but 48-hour days are still too short (yeah, mine are, or at least they feel like it :)
Yes, I'm interested.
trying to flash the input-plug is not working for now.. As I got a verification error on the chip, the plug give another error:
avrdude: please define PAGEL and BS2 signals in the configuration file for part ATtiny45
avrdude: verification error, first mismatch at byte 0x0000
0x1a != 0x0a
avrdude: verification error; content mismatch
now at byte 0x00 perhaps my breadboard with extension /patch cables gives some problems ?
YES ! I got the plug working ! shorter cables did not do the trick, but first I tried to burn a boot-loader which failed (lock-fuses error ?) but a retry of burning my blink sketch did successfully burn the code.
Strange effect: the plug runs faster ! my delay(1) results in a 2 mSec delay
now for understanding what and why.
Ah, now that is interesting... Although I don't get the verify error message with the ATtiny I've played with - source of which JC has given away ;-) - I have found that sometimes I can't get a program to "take" either. I haven't managed to work out the logic to it, but found that flashing the fuses will get things going again, and then after that I'm usually fine to just program away repeatedly.
Re the delay issue, I seem to recall having to tell Arduino that the chip was running at 8Mhz somewhere in the config when I was defining the new destination... I'll see if I can find where to do that.
Oh, hang on, you've already got that... I didn't initially see it in the copy of your boards.txt because of the line break problems.
This is mine... I can't vouch for the fuse settings in this file though, I don't set the fuses with Arduino.
attiny84.name=ATtiny84 attiny84.upload.protocol=stk500 attiny84.upload.maximumsize=8192 attiny84.upload.speed=19200 attiny84.upload.using=arduinoisp attiny84.bootloader.lowfuses=0xe2 attiny84.bootloader.highfuses=0xdd attiny84.bootloader.extendedfuses=0xff attiny84.bootloader.path=attiny attiny84.bootloader.file=fake.hex attiny84.bootloader.unlockbits=0xff attiny84.bootloader.lockbits=0x0fc attiny84.build.mcu=attiny84 attiny84.build.fcpu=8000000L attiny84.build.core=arduino
Do you use a complete different arduino dir (including all tools) for the attiny ? your core dir is set to arduino, which is the same as the default environment. I've copied the new core code into a different dir so that the compiler just switches the core code depending on the selected board..
I think that trying to burn a bootloader (fake.hex) is just used for setting the fuses. In my case: I used a brandnew attiny45 with the factory-default fuses, after trying to burn the bootloader the fuses where set as defined in the boards file.
What happed with the verify-error is still a mystery, but for now I've hooked up my inputPlug to a JeeNode on a breadboard and burning an app is as simple as using the arduino environment with an standard arduino/JeeNode.
boards.txt
##############################################################
attiny45.name=Arduino w ATtiny45
attiny45.upload.protocol=stk500
attiny45.upload.maximumsize=4096
attiny45.upload.speed=19200
attiny45.bootloader.lowfuses=0xdf
attiny45.bootloader.highfuses=0xca
attiny45.bootloader.path= attiny45
attiny45.bootloader.file=ATmegaBOOT.hex
attiny45.bootloader.unlockbits=0x3F
attiny45.bootloader.lockbits=0x0F
attiny45.build.mcu=attiny45
attiny45.build.fcpu=8000000L
attiny45.build.core=attiny45 <= this is the core-dirname
##############################################################
attiny84.name=ATtiny84
attiny84.upload.protocol=stk500
attiny84.upload.maximumsize=8192
attiny84.upload.speed=19200
attiny84.upload.using=arduinoisp
attiny84.bootloader.lowfuses=0xe2
attiny84.bootloader.highfuses=0xdd
attiny84.bootloader.extendedfuses=0xff
attiny84.bootloader.path=attiny
attiny84.bootloader.file=fake.hex
attiny84.bootloader.unlockbits=0xff
attiny84.bootloader.lockbits=0x0fc
attiny84.build.mcu=attiny84
attiny84.build.fcpu=8000000L
attiny84.build.core=attiny84
I use my Arduino install for everything. ATmega328p, ATmega168, ATtiny84.
I got my config from a post on the arduino forums, and just created a new folder under C:\Program Files\arduino-0018\hardware\ called "ATtiny84".
I believe the build.core entry refers to a subdirectory below the individual hardware entries...
My boards.txt is in
C:\Program Files\arduino-0018\hardware\ATtiny84
That contains
C:\..\hardware\ATtiny84\bootloaders
C:\..\hardware\ATtiny84\bootloaders\attiny (which just contains fake.hex)
C:\..\hardware\ATtiny84\cores
C:\..\hardware\ATtiny84\cores\arduino (this contains all the core files).
my current setup still needs an attempt to burn the boodloader before it accepts a normal program cycle.. Always the exit is data-check error if you do not burn the fake bootloader first..
Hmmm...
I wonder if there is something in the programmer that isn't set/reset quite right until a bootloader/fuse write is attempted?
You're using JC's flash sketch and programmer too aren't you? I've seen it happen with both my programmers. One is a JeeNode V4 with JC's eeprom equipped ISP board, the other is a JeeNode SMD with a little home made board on the top to provide the FTDI and ISP links. It's a pin for pin copy of the JeeLabs board, minus the eeprom.
@JC have you ever seen any behaviour like this?
update.. I switched from a breadboard ISP to the flashboard and for now that seems to solve the programming problems. so... bye, bye, breadboard and hello flashboard.
made a nice standalone thingamajiggle:
inputplug connected via the mux to 7seg display, dipswitches, twocolor led an two tactile switches.. and then there is still a port left for serial communication !
now JC's slaveboard...