download zipped Arduino_slow_ISP sketch, then start IDE ( i tried on 1.6.1 only ) and install sketch on your arduino programmer ( i tried on breadboard atmega328 on 8MHz ) connect attiny13 as you usual do
and this version of - Arduino_slow_ISP sketch - is sufficiently slow to burn 128KHz fuse and upload sketch, and also change to other fuses as well, I just tried all options.
common_ground:
OK, i find solution for Arduino as ISP and ATTINY13 on 128 KHz :
No change. I think it's time to try something new. Tomorrow I'll take another attiny13 to replace the current one and see if it is going to programmed, just in case I screwed something with schematic or managed to shortcut my poor attiny :). I will also try to find an AVR-fan-neighbor to borrow an external programmer.
grigorym:
No change. I think it's time to try something new. Tomorrow I'll take another attiny13 to replace the current one and see if it is going to programmed, just in case I screwed something with schematic or managed to shortcut my poor attiny :). I will also try to find an AVR-fan-neighbor to borrow an external programmer.
Only if you damage attiny13.Try with new one.
I just lock one ATTiny13 with standard ArduinoISP and unlock with Arduino_slow_ISP , work 100%. That makes using Arduino as excellent ISP programmer of choice.
I'll make one to be permanent, no need to buy anything else.
I program them at 128K all the time. I modified the Ardunio ISP program to run at a very low SPI rate
and it works with no problems. Make sure your wire connections are good.
smeezekitty:
I program them at 128K all the time. I modified the Ardunio ISP program to run at a very low SPI rate
and it works with no problems. Make sure your wire connections are good.
I was planning to disappear silently, but bad conscience brought me back to report my stupidity. Common_ground, I was trying to recover with your slow ISP not the attiny13, but the 555 timer chip :)). Surprisingly, it refused to be programmed :). @@@@!
So, reporting. Slow version of Arduino ISP successfully sets the fuses back and programs the chip. After that I was able to switch back to ordinary Arduino ISP. I went the whole process once again: programming with ordinary Arduino ISP the fuses for 128KHz, loosing control of the chip, uploading slow version of Arduino ISP and reprogramming the fuses and the sketch back.
Thank you very much for your assistance and patience. I'll mention the solution on a couple of places, where beginners like me stumbled upon 128KHz option.
As for USBTinyISP programmers, we do not have to change default_bitclock only in avrdude.conf, but we can change the parameters directly from the IDE environment (at least from 1.6.1), without changing avrdude.conf.
Open arduino-1.6.1\hardware\arduino\avr\programmers.txt in some text editor and change usbtiny section with this :
ElectroNick:
1.2K is a lot of bytes for a blink! The code must be not well optimized or sometin' . You can do plenty of useful things with 1K of command space. For example, here is a code for a 10-LED light chaser (can convert it into Cylon eyes or some other such blinking toy) and it compiles into only 562 bytes. In fact, there might even be some saving there still, I just didn't have too much time to optimize it.
I agree, 1.2k is a lot, i put an entire irrigation system in some 700 bytes in an attiny13 AND it has a blinking LED :-)
Hi all, I am about to start some t13 work again, is everything stable for me to use the cores with 1.6.3 ?
have there been any t13 core updates in the last 6 months or so ?
mcnobby:
Hi all, I am about to start some t13 work again, is everything stable for me to use the cores with 1.6.3 ?
have there been any t13 core updates in the last 6 months or so ?
Its a big ole thread now isnt it !!
The last update was in January. I have no idea about 1.6.x. I am always slow to upgrade Arduino
versions since they always seem to bork something lately.
Since there is a difference between version 1.6.3 and 1.6.4 in relation to the earlier 1.6.x versions, i decided to make the installation file for 1.6.4 (1.6.3) version only.
Just unpack file in ...\sketchbook\hardware folder.
Boards included :
I added some GCC Flags ( can be used from IDE menu - choose default if you do not like to use extra optimisation flags ) :
And i added millis() , micros(), delayMicroseconds() and set ADC clock for 16 KHz ( it is not set for 16 kHz originally )
If you use 128 KHz - default_bitclock must be slow down to -B50 and for 16 KHz to -B250 ( USBTinyISP)
common_ground:
Since there is a difference between version 1.6.3 and 1.6.4 in relation to the earlier 1.6.x versions, i decided to make the installation file for 1.6.4 (1.6.3) version only.
Just unpack file in ...\sketchbook\hardware folder.
Boards included :
I added some GCC Flags ( can be used from IDE menu - choose default if you do not like to use extra optimisation flags ) :
And i added millis() , micros(), delayMicroseconds() and set ADC clock for 16 KHz ( it is not set for 16 kHz originally )
If you use 128 KHz - default_bitclock must be slow down to -B50 and for 16 KHz to -B250 ( USBTinyISP)
Thanks for that brilliant setup!
One thing that is not really streamlined is the categories. I changed that. So now it is ATtiny13 with all the clock speed and all compiler options (only listed once for all speeds of course). Only 9.6MHz tested.
The pins are internally converted hence no need for pins_arduino. If you don't mind, I can add this to the next release for reference purposes. After I check it for accuracy at least
smeezekitty:
The pins are internally converted hence no need for pins_arduino. If you don't mind, I can add this to the next release for reference purposes. After I check it for accuracy at least
Yes, please add the pinout to the next core13 version
Buy why have you just uploaded the core files, and not a complete set of folders, including boards.txt?
The setup would be much simpler if you wouldn't need to dig through the whole forum post to find the correct files
hansibull:
Buy why have you just uploaded the core files, and not a complete set of folders, including boards.txt?
The setup would be much simpler if you wouldn't need to dig through the whole forum post to find the correct files
Because it is a royal pain in the BUTT to work with the *.txt that Arduino uses. When I wrote it, I couldn't figure it out myself. I kind of have it figured now but there are already working boards.txt out there.
Please help me out. I was expecting neoPixel lib to be able to handle 9.6MHz but looks like its not.
The neopixel code is unportable (it calls internal core functions rather than just the external ones)
It would need to be rewritten.