Forgot one...
Features...
- Direct output for tone on pin 4. Sound quality is a bit better and no CPU time is needed.
Forgot one...
Features...
How to burn the bootloader to an attiny85 i will try this because i had one free for these trying. Wich .hex i have to burn with a ISP?
I have been using the pre-release of this for about a week now, its very nice
and Thank you very much
Wonderful work!
Is the Servo library working?
Thanks!
Thank you all for the kind words and encouragement.
Is the Servo library working?
No. If you (or anyone else) is willing to test I can provide the changes to Servo.cpp that should get it working.
Please take a moment to click a few checkboxes...
http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1285276725
http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1285316262
Clicked.
I plan on using Tiny 84 and 85 at 8MHz for tiny robots and I need the Servo Lib, the SoftwareSerial Lib, the EEPROM Lib and the analog read (if there is support) at the moment. After successful tests I'll make dedicated boards for these chips. The idea is to have 6 and 3 servo connectors plus serial or sensor connectors on the boards. All servo positions will be saved in the EEPROM so the user can connect the board to the PC using a FTDI cable and set new servo positions as new moves that are later played back directly on board.
So I am willing to do any tests you can throw at me.
Clicked.
Thanks!
I plan on using Tiny 84 and 85 at 8MHz
For the next few weeks, my efforts are restricted to the 84 core. The 85 processor is next.
for tiny robots
Excellent!
and I need the Servo Lib
For Servo to work with the 84 processor a minor change must be made to the Servo.cpp source file. The file is located in the {ArduinoRoot}\libraries\Servo directory. On line #103 should be this...
SIGNAL (TIMER1_COMPA_vect)
Change it to this...
#if defined( TIMER1_COMPA_vect )
SIGNAL (TIMER1_COMPA_vect)
#else
SIGNAL (TIM1_COMPA_vect)
#endif
Once this change has been tested, I'll ask for it to be applied the official version.
the SoftwareSerial Lib
I've been using NewSoftSerial (@ 9600 baud) with success. I'll switch to SoftwareSerial and report back.
Bear in mind that, from the factory, the internal oscillator may not be accurate enough for serial communications. The oscillator can be tuned (using the OSCCAL register) to be accurate enough.
the EEPROM Lib
There is a bug in <avr/eeprom.h> that prevents it from working with the 84 processor. There's a replacement file in the Arduino Tiny download that I belive fixes the problem.
and the analog read (if there is support)
There is support. I've tested the three analogReference modes1 and all eight analog input pins. It all seems to work.
After successful tests I'll make dedicated boards for these chips. The idea is to have 6 and 3 servo connectors plus serial or sensor connectors on the boards. All servo positions will be saved in the EEPROM so the user can connect the board to the PC using a FTDI cable and set new servo positions as new moves that are later played back directly on board.
Nice!
So I am willing to do any tests you can throw at me.
Two things need to be tested...
tone may not be working correctly. I need someone to measure the frequency generated. Ideally with the processor at 1 MHz and 8 MHz.
Servo. I currently don't have the means to test the Servo library with the 84 processor.
Any help you're willing to contribute is greatly appreciated!
1 Be sure to read the datasheet! The analogReference modes for the 84 processor are a bit different from the 168 / 328 processor.
ATTiny84 has SPI. I've not seen where one of these has been used with any Arduino yet.
MAX3110E, MAX3111E
I'll switch to SoftwareSerial and report back
...testing has not gone well.
NewSoftSerial works at least to 9600 baud (I haven't tried higher rates). SoftwareSerial won't work at 2400 baud. Unfortunately, NewSoftSerial adds almost 2K; SoftwareSerial is considerably smaller.
SPI
.. is a quite trivial matter. It is a part of 019 now, isn't it? Here a library
http://www.arduino.cc/playground/Code/Spi
NSS
.. can be simplified a little bit, especially when you constrain to a few bit-rates only. It can be re-written using USI. The size of the receive buffer must most likely also be reduced.
I have ordered some 84 chips - I cannot start testing before next week.
spi lib doesnt work with the 84, as its handled though the USI, course you can bit bang it nearly as fast on any pins you want
NSS.. can be simplified a little bit, especially when you constrain to a few bit-rates only
Trimming the bit-rate tables will help but not by much.
There are a few spots in the SoftwareSerial source where it looks like the person who wrote it assumed the clock would be a specific rate (probably 16 MHz). I suspect SofwareSerial can be made more reliable with less effort than trying to trim NewSoftSerial.
It can be re-written using USI
Not for me. I need PA6 and Timer 1 for tone.
The size of the receive buffer must most likely also be reduced.
In my case, it can be eliminated! I'm only sending for debug purposes.
spi lib doesnt work with the 84
Does it need to? Who's using SPI with an 84 processor? Please post if you're using SPI with an 84 processor.
im using it to send out to shift registers , but I found it easier to just bitbang pins manually (not digitalWrite) and the speed difference is negligible and I can use any pins I want vs the USI needs to be on the same 2 pins as everything else the USI controls
if you need input, well thats a different ball
I set out to make a smaller core for the '84 processor and ended up with...
In theory, this core is a bit more portable to other Tiny processors than the standard core.
I'm disappointed in the memory savings. There are some changes that would probably make it bit smaller but the speed increase would diminish considerably.
Which is more important ... Faster or less memory?
if you look at this link :
http://code.google.com/p/codalyze/wiki/CyzRgb
in the source code, they have an implementation of i2c master/slave using USI from tiny44 and tiny45.
Maybe it could be usefull for you to make wire library working on tiny.
hm I am going to say memory because there is always the option to use an external clock and if one uses a oscillator package its only eating up one pin, adding memory not so easy ...
course in a perfect world, both! ;D
im using it to send out to shift registers , but I found it easier to just bitbang pins manually (not digitalWrite)
Would digital*Fast functions be useful to you?
@moustic:
Maybe it could be usefull for you to make wire library working on tiny.
Do you have a need for the Wire library to work on an ATtiny84 processor? 85 processor? Any other tiny processor?
hm I am going to say memory because there is always the option to use an external clock and if one uses a oscillator package its only eating up one pin, adding memory not so easy ...
Good point. Also, there seem to be more posts about "I'm out of memory" than "My application is too slow". It seems that most "too slow" applications can be sped up using a different design.
course in a perfect world, both!
Well, so far I've managed a bit of both.
I'm trying to have a I2C clock working with a tiny85.
I found this web site with this code.
I don't use it in arduino env, but I think It should be really easier if I could use arduino environement and librairies to develop on my tiny.
a great usage for tiny and i2c is to pilot an RGB led. (like BlinkM )