Facebook
Google
GitHub
Linkedin
I thought someone said in the thread that the bootloader is need to use the chip by itself
a timer that goes logic high or low every 15mins ( using tiny85 chip)
- Thread starter timtim1234
- Start date
1). ahh ok i see what you mean so once its "Setup" then a person can use 1mhz? I would assume it would just run the code slower which could be an issue if a person is using alot of timers,etc? is this correct?
2) change your -c to this -c stk500v1 for the arduino isp programmer
3). try it using avrduess just to see if it works then
They probably did but thats not true bootloader is for loading code but the chip will run code that's loaded with a programmer without the boot loader
plus you can have more code.
What you have posted you didn't burn a boot loader you set the fuses with the empty_all_hex
Last edited:
hummm what you mean i didn't burn a bootloader? I edited the boot loader ino? well i thought that is what it was doing when i click on burn bootloader??
ohh ok well so then i don't need that to make the chip run by itself. good to know!! i thought it was need for the chip to run
vrdude.conf" -v -pattiny85 -cstk500v1 -PCOM6 -b19200 -e -Uefuse:w:0xFF:m -Uhfuse:w:0b11010111:m -Ulfuse:w:0xE2:m "-Uflash:w:C:\Users\Admin\AppData\Local\Arduino15\packages\ATTinyCore\hardware\avr\1.5.2/bootloaders/empty/empty_all.hex:i"
Thats the no boot loader setting it loads the fuses
arduino use bootloader to program without a programmer like the uno,digspark, mega
Thats the no boot loader setting it loads the fuses
arduino use bootloader to program without a programmer like the uno,digspark, mega
Re post #242.
1 The cpu clock frequency has nothing to do with how many timers you can run. Running at a lower clock frequency reduces power consumption. It also means that you do not need tount as many instructions or timer/counter interrups for a given amount of time. A higher clock frequency gives higher resolution of a time interval 1 Mhz gives a resolution of 1 uS 8 Mhz gives a resolution of 125 nS.
2 Using stk500v1 as the programmer type gives a dilfferent error. avrdude can not even communicate with the programmer.
When using arduinoisp as the programer type avrdude can communicate with the programmer BUT the programmer can't communicate with the ATtiny85.
3 I am not going to try loading avrdudess again. I don't even know if we are both using the same operating system.
Les.
1 The cpu clock frequency has nothing to do with how many timers you can run. Running at a lower clock frequency reduces power consumption. It also means that you do not need tount as many instructions or timer/counter interrups for a given amount of time. A higher clock frequency gives higher resolution of a time interval 1 Mhz gives a resolution of 1 uS 8 Mhz gives a resolution of 125 nS.
2 Using stk500v1 as the programmer type gives a dilfferent error. avrdude can not even communicate with the programmer.
When using arduinoisp as the programer type avrdude can communicate with the programmer BUT the programmer can't communicate with the ATtiny85.
3 I am not going to try loading avrdudess again. I don't even know if we are both using the same operating system.
Les.
1). ahh ok that is good to know!!
2). humm that interesting.... did you say it worked at one time? If so, what change? Software installed? Hardware? install a usb driver? etc
3). sorry i forgot to say i am on Windows 10. I don't think that would cause a problem but........ even tho you don't want to load avrdudess doing so may tell you more what is going on.
Well......... funny you ask.... LOL i "HAD" the chip programmed and working, but the chip been reprogrammed with other code that I find on forums and I have been tweaking it, and playing with code that has nothing to do with a "timer"..lol . I kinda got sided tracked, one of the side effects of ADHD..lol
ohh I forgot to add I let some "smoke" out too, due to wiring "errors"..lol
We’ve all done it. Hopefully you bought more than one. I usually buy three if I need one.
I did buy more than one BUT they're at a couple of my friends house they are starting to mess around programming with it too..lol
LOL for sure!!! Ohh I must be learning a lot then!! Lol
This work good you need the .h files from here lots good examples there too. https://github.com/digistump/DigistumpArduino/tree/master/digistump-avr/libraries
Code:
//----------------------------------------
//ATtiny85 Module Interfaced with I2C OLED
//----------------------------------------
#include <DigisparkOLED.h>
#include <Wire.h>
//#include <iostream>
//---------------------------------------------------
#define SW 1
#define SW1 4
unsigned int i = 0;
unsigned long tm = 0;
//===================================================
void setup()
{
pinMode(SW,INPUT);
pinMode(SW1,INPUT);
oled.begin();
oled.clear();
oled.setFont(FONT8X16);
oled.setCursor(30, 0);
oled.print("Timer");
}
//===================================================
void loop()
{
if(digitalRead(SW) == HIGH) {delay(100); i++;}
oled.setFont(FONT8X16);
oled.setCursor(0, 2);
oled.print("Counter: ");
oled.setCursor(70, 2);
oled.println(i);
delay(100);
tm = i;
if(digitalRead(SW1) == HIGH)
do {
oled.setFont(FONT8X16);
oled.setCursor(0, 4);
oled.print("timer: ");
oled.setCursor(70, 4);
oled.println(tm);
delay(60000);
tm--;
} while (tm < 1);
}ok and what you mean h files from here? From the link you posted?? I see the link has good examples
