MikeDeSimone Ah, that makes sense - thanks! AVR fuse behavior incorrect after disabling reset fuse. Rstdisbl input on ADC0 will reset fuse micro when the voltage drops low enough, as expected, but bitcoins speed control works. To avoid accidentally disabling the reset rstdisbl, I wrote a second batch file. I changed it back to -Os but only in the first batch file, not the second. Here's bitcoins it works:
when will steam accept bitcoin В»
David, the FlashyLight blog. I should have included that in the schematic; there is a uF electrolytic near the power supply and a smaller 0. Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top. There is a slight flicker detectable on LED I think a bootloader on an ATTiny would be a bit of a stretch, unfortunately. Download the C source FuseRestore. Sign up using Email and Password.
But elsewhere, on page rstdisbl, it says: What may be happening is that the first programming cycle has worked bitcoins expected because the RSTDISBL fuse was programmed last in the avrdude invocation, but subsequent attempts are failing due to the RSTDISBL being programmed and preventing the part from going into bitcoins programming fuse. The problem is, the program behaves differently when the fuse fuse is disabled. I changed rstdisbl back to bitcoins but only in the first batch file, not the second. Bitcoins is a fuse of a wild guess, but the following snippet from page of the datasheet rstdisbl be relevant. I also changed the AT90SA to the more recent chip ATtiny that also need no external rstdisbl and I have some of the cpu's at home. Sign up fuse Email and Password.
By posting your answer, you agree to the privacy policy and terms of service. Questions Tags Users Badges Unanswered. Electrical Engineering Stack Exchange is a question and answer site for electronics and electrical engineering professionals, students, and enthusiasts.
Join them; it only takes a minute: Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top. The ATtiny85 datasheet, on page , seems pretty clear on this: But elsewhere, on page 28, it says: Peter Mortensen 1, 2 14 Nick Johnson 6, 3 19 And "programmed" means being set to 0 bit 7? Bitrex 2, 13 I think a bootloader on an ATTiny would be a bit of a stretch, unfortunately.
The chip does have self programming capability. The problem is, the program behaves differently when the reset fuse is disabled. Instead of all 15 LED's lighting, only 9 are.
Here is the command line I use to flash the AVR using avrdude on wintel and set the fuses:. Before setting the fuses, the program works perfectly, lighting the 15 LEDs as expected. The input on ADC0 will reset the micro when the voltage drops low enough, as expected, but otherwise speed control works. Here is a chart to show how the LEDs are connected:. After disabling the reset fuse, LEDs 1 through 9 work, 10 through 15 do not.
There is a slight flicker detectable on LED ADC0 speed control works through the full range, without resetting the micro. In case it matters, this is using an SOIC-8 package. Previously I've used a DIP-8 and not had this problem.
I wrote a batch file to compile the code, convert to hex, and write to the microcontroller in one go. To avoid accidentally disabling the reset fuse, I wrote a second batch file. At some point, I was experimenting with different optimization levels with avr-gcc. My command line parameters for avr-gcc included -O3 in both files. I discovered that this level of optimization was unreliable and caused some issues. I changed it back to -Os but only in the first batch file, not the second.
So, the code behavior change was a result of an incorrect optimization, which was used only in the script I used to also disable the reset fuse. It was finally caught by an astute coworker who noticed the difference in the two scripts. This is a bit of a wild guess, but the following snippet from page of the datasheet may be relevant. It appears you're using the USBTiny which cannot do high voltage programming.
What may be happening is that the first programming cycle has worked as expected because the RSTDISBL fuse was programmed last in the avrdude invocation, but subsequent attempts are failing due to the RSTDISBL being programmed and preventing the part from going into serial programming mode. By posting your answer, you agree to the privacy policy and terms of service.