Thank you very much for IDE 1.6.0 version, works out of the box, which is helpful for beginners like myself. However, a strange recurring feature for all my atmega chips - if I try to burn the bootloader first (only fuses, I know, I know), it fails with some out-of-sync or something. Uploading the blink sketch works (though the sketch produces longer blick delays). Burning the bootloader-fuses after that - works, and the uploading the blick sketch again works perfectly as expected.
I encountered that while programing the atmega328 chip and thought i made a mistake somewhere. But now it repeated again with your compilation for attiny13! Am I missing something?
grigorym:
However, a strange recurring feature for all my atmega chips
I'm not sure i understand you completely. This installation is only for ATtiny13 and has nothing to do with atmega mcu (they use a settings that is in a different location).
Can you explain it more clearly.
What programmer you use?
If you use USBTinyISP then maybe flash timing is problem and here you have a solution for this: ATTiny flash timing problem
I use Arduino as ISP and USBTinyISP and it works well with both.
common_ground:
I'm not sure i understand you completely. This installation is only for ATtiny13 and has nothing to do with atmega mcu (they use a settings that is in a different location).
Can you explain it more clearly.
What programmer you use?
I am using Arduino as ISP (using Nano board). Only the wierd behaviour (having to upload sketch first, and only then setting the fuses worked) on ATtiny13 matched the one I noticed on 328, so I mentioned it here.
Are you sure your configuration option "attiny13.name=Attiny13 @ 128 KHz (internal watchdog oscillator)" works as expected? In my case IDE says it is missing "upload.tool=arduino:avrdude" and ".bootloader.tool=arduino:avrdude". However, having added those I must have locked my ATtiny13, it does not respond anymore.
P.S. May I take some more time to read the whole thread? I definitely must not be the only one to try this 128KHz option
grigorym:
2. Are you sure your configuration option "attiny13.name=Attiny13 @ 128 KHz (internal watchdog oscillator)" works as expected? In my case IDE says it is missing "upload.tool=arduino:avrdude" and ".bootloader.tool=arduino:avrdude". However, having added those I must have locked my ATtiny13, it does not respond anymore.
128 KHz option was just copied from a previous settings and I did not adjust it for 1.6.x, and it can not be used with a standard Arduino as ISP , as a rookie you should avoid using internal watchdog oscillator , I'm sorry i have not been thinking, this option had to be deleted, and who knows how to use it, can easily be set manually.
If you tried, it means your ATtiny13 is locked and here you have a good procedure how to unlock :reset-clock-fuse-bits on ATTiny13, i tried this procedure, works well and it's easy to use, only instead
avrdude -p attiny13 -P usb -c usbtiny -tuF
you should put
avrdude -p attiny13 -P usb -c arduino -tuF
But others fuse settings should work with Arduino as ISP without problems , i just tried them all again.
grigorym:
2. Are you sure your configuration option "attiny13.name=Attiny13 @ 128 KHz (internal watchdog oscillator)" works as expected? In my case IDE says it is missing "upload.tool=arduino:avrdude" and ".bootloader.tool=arduino:avrdude". However, having added those I must have locked my ATtiny13, it does not respond anymore.
P.S. May I take some more time to read the whole thread? I definitely must not be the only one to try this 128KHz option
I've used the 128KHz many times. The issue here is the tiny13 cpu clock is too slow for some ISP programmers SCK clock speeds.
In order to program at these very low speeds is you need an ISP programmer that will support the Bitclock rate adjustment from avrdude -B option. There are several programmers that will support this option, AVRispMKII, USBtinyISP(some versions may not work correctly), and USBASP(new firmware versions). I've even add my own 16KHz clock rate option that works with this bitclock rate adjustment.
ArduinoasISP will not work at these very slow speeds.
For avrdude -B option, you should specify at least -B50.
To program via the IDE, then you will need to change the Global defaults in the avrdude.conf file.
Some where around line 335:
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.