// the setup routine runs once when you press reset:
void setup() {
// initialize the digital pin as an output.
pinMode(led, OUTPUT);
Serial.begin( 9600 );
}
// the loop routine runs over and over again forever:
void loop() {
digitalWrite(led, HIGH); // turn the LED on (HIGH is the voltage level)
delay(1000); // wait for a second
digitalWrite(led, LOW); // turn the LED off by making the voltage LOW
delay(1000);
Serial.println( "Testing..."); // debug output
}
I think the buty about Serial Relay is that you have two way communication. This makes the tiny environment look and feel almost like an Arduino.
If you want to utilize this feature you have to use SoftwareSerial, atleast that is my understanding.
On the other hand I can see the advantage of using the TinyDebugSerial: You can take a Arduino sketch an compile it for a tiny without midifying the Serial.print() statements.
I have tried using KnockBang on a Attiny13, with no luck
I get this error:
In file included from tiny_knockbang.cpp:1:
D:\arduino-1.01\arduino-1.0.1-windows (1)\arduino-1.0.1\libraries\TinyDebugKnockBang/TinyDebugKnockBang.h:55: error: 'fstr_t' does not name a type
D:\arduino-1.01\arduino-1.0.1-windows (1)\arduino-1.0.1\libraries\TinyDebugKnockBang/TinyDebugKnockBang.h:152: error: expected ',' or '...' before '*' token
I added these to the WProgram.h, which gave another error:
D:\arduino-1.01\arduino-1.0.1-windows (1)\arduino-1.0.1\libraries\TinyDebugKnockBang/TinyDebugKnockBang.h:156: error: 'DEC' was not declared in this scope
So I added #include "print.h" in the WProgram.h , and now it compiles and uploads.
When I open the serial monitor (19200 baud) and type a ! I get this error:
--- Knock-Bang fault: 15 ---
I was thinking it maybe had something to do with the clock speed which was 128kHz, so I tried at 9,6 mHz and got this error:
--- Knock-Bang fault: 11 ---
i get the correct respons from the serial monitor, when I use @,# and !
Erni:
So I added #include "print.h" in the WProgram.h , and now it compiles and uploads.
Excellent.
I was thinking it maybe had something to do with the clock speed which was 128kHz,
The minimum supported clock speed is 1 MHz. If I can remember, I'll put a check in the header file.
so I tried at 9,6 mHz and got this error:
--- Knock-Bang fault: 11 ---
i get the correct respons from the serial monitor, when I use @,# and !
fault_timeout_knock ... In the interrupt service routine, a knock was not detected within the time limit.
Other then a wire, is anything connected to MISO?
Try adding a 10K or 4.7K or 1K pullup resistor to MISO. And/or, if the wire on MISO connecting the programmer to the target is longish, try a shorter and/or fatter wire.
I have killed my poor little Attiny13, I think it was during fiddling with the fuses. It is totally unresponsive, I tried my USBasp and Pololu programmer but no luck.
I will report back as soon as my new chips arrive, oh so close ...
There has not been anything connected to MISO during this testing. I will try your tip with pullups.
Don't give up yet! Two things I've discovered about the t13...
After changing the clock choice (fuses), mine sometimes becomes unresponsive until I toggle power. Try toggling the target's power.
There is a minimum pulse time for RESET. All the processors I've used don't seem to care if the minimum is or is not met. Except the t13. If the pulse is too short, it will reset but refuse to enter programming mode. If you've changed the clock to 128 KHz, the minimum pulse maybe longer than the pulse provided by USBasp or Pololu. I know the minimum pulse is longer than the one provided by ArduinoISP. I just change TinyISP to provide the correct reset pulse for the t13 @ 128 KHz.
Bear in mind I also changed how build options are specified. If you decide to try TinyISP and need help getting it working the way it was just let me know.