There is a limit on the operating clock speed based on VCC. Higher speeds are not possible at lower voltages. There's a chart in the datasheet, I believe.Anyway, it's possible you experimentally determined the limit. I'd be curious to know what speed are you running the '85.-br
Like billroy, I'm only speculating but I'm not sure VCC versus clock speed will be it. My power source of choice for ATTiny85 projects is a single CR2032 and I've never had an issue with them operating at 8MHz (I always burn that speed too). Though to be fair, I'm not doing serial comms in anything I'm referring to here.Perhaps it's worth consulting the data sheet to see also what voltage the ATTiny is producing for a HIGH signal at 3V. You might just find you've gone below where the Uno reads a HIGH, so your serial comms have become a stream of zeroes to the receiving side.Cheers ! Geoff
I just tryed:Attiny85v @8mHzTinyDebugSerial at 9600A (fresh) CR2032No problem with Serial.print() in serial monitorAnd with SoftwareSerialSame result, I am able to communicate with the tiny both waysI am using these Fuses (BOD disabled)L: E2 H: D7 E: FF
The speed of the internal oscillator varies with voltage. Use a lower baud rate to compensate.
In member function 'void TinyDebugSerial::begin(long int)', inlined from 'void setup()' at rose.cpp:19:/Users/lukasz/Documents/Arduino/hardware/tiny/cores/tiny/TinyDebugSerial.h:694: error: call to 'TinyDebugSerialBadBaud' declared with attribute error: Serial (TinyDebugSerial) supports three baud rates: 9600, 38400, or 115200.
I have no problems running the chip, it really only has to do with serial output. I've gotten it to even output "PWN" (software on a few pins) on 5 pins, so it seems like it's pushing it hard. But I will check out the datasheet, I didn't think to check if it's outputting enough power for HIGH on arduino.