(well, only until you use a 12v pulse to get around it) THIS WILL BRICK YOUR ATtiny412 CHIP *. TinyAVR Fuse uPDI Programming ATtiny212 ATtiny214 ATtiny412 ATtiny414 ATtiny416 ATtiny417 ATtiny814 ATtiny816 ATtiny817 ATtiny1614 ATtiny1616 ATtiny1617 Is there some fiddly bits needed to make fuse programming work? Is this programming firmware supposed to be able to program the fuses? Application Code Section End (default is 0x00) System Configuration 1 (default is 0x07) SYSCFG0 = CRCSRC_NOCRC_gc| RSTPINCFG_GPIO_gc, System Configuration 0 (default is 0xC4) //Be aware, this breaks future programming Oscillator Configuration (default is 0x02) Watchdog Configuration (default is 0x00) Apparently this structure needs to be packed from This will make the chip unable to be reprogrammed Set the fuse so the uPDI will be a GPIO. In particular, I am trying to take over the uPDI/RST pin as GPIO, and I can tell the fuse must not be getting set, because I can still reprogram the chip :-) I can get the example fuse code for the AVRTiny to compile, but the fuses do not seem to get set in the device. ![]() I do have a question about programming the fuses though. Works great.įor reference, here is the command line I am using to program my ATtiny412:Īvrdude.exe -c jtag2updi -P com5 -p t412 -e -U flash:w:Tiny412Blink.hex I have it running on an unmodified Seeeduino v4.2 set to 3.3v (a bargain at $US6.90). I don't know if anyone has yet looked at doing this for "Xtiny" (which is what these new, UPDI based AVRs based on the Xmega range are generically referred to as). But that's still just a tiny subset of the 300+ models of AVR that there are. ![]() So for other chips you might find it listed there - in which case you'd follow the associated link, download the additional core and add to your Arduino installation - then it should be able to support that added chip. Some people have developed these for other models of AVR: For the Arduino system to support a different micro it needs a new "core" added. (so implementations of things like digitalWrite(), analogRead(), Serial.begin(), etc that work with those specific models). The Arduino installation has "core" support for each of those. In the 8bit AVR range that basically means ATmega32U4, ATmega328P, ATmega2560, ATmega168. Specifically the "Processor" column - *those* are the "Arduino processors". HopCode wrote: or is if they were an Arduino. I've got an idea the for a board using these chips that the wearable crowd would eat for breakfast. Let me get this straight, so if I take these steps I can pretty much use these chips as if they were an arduino? ie use adafruit libraries and program in a way I know and love? If so then dude, you're a damn legend, and why the heck is there only one other person to have cottoned on? You're a damn hero in my eyes and your praise deserves to be sung!!Īnother question I have (I am a complete noob when comes to electronic circuit design, apart from badly designing a nano clone), if I was designing a circuit for one of these new attiny chips would I only need one exposed pin for UPDI programming? Is that what 1-wire means? If so then these chips are just bonkers cool, no blooming ICSP of FTDI headers on a board that take up so much space! I'm just really really grateful, and wanted to say thank you for your commendable work! ![]() I just signed up to say thank you El Tangas! I've been interested about these new chips but thought it was a complete mission to program, but seems like you've done everything so you can use these chips in the Arduino environment.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |