ATtiny 1634、828、x313、x4、x41、x5、x61、x7 和 x8 的 Arduino 内核_C语言

# ATTinyCore **Universal** Arduino support for almost every classic tinyAVR device! Supports ATtiny 1634, 2313/4313, 24/44/84, 441/841, 25/45/85, 261/461/861, 87/167, 48/88, 43 and 828. Supports programming vis ISP, Serial (Optiboot - all parts with >4k flash, and all parts with 4k flash for which an 8k version is available) or VUSB (Micronucleus - where appropriate) ## State of ATTinyCore Development of ATTinyCore is proceeding in the v2.0.0-dev branch. **PLEASE DO NOT SUBMIT PR's AGAINST the "MASTER" BRANCH YOUR CHANGES WILL BE LOST UPON THE NEXT RELEASE IF YOU DO NEW CHANGES NEED TO GO INTO v2.0.0-dev** (which will be my next project after DxCore 1.3.7 release this week) ## We desperately need testing help here **THE 2.0.0-dev branch IS NOW READY FOR PUBLIC TESTING VIA MANUAL INSTALLATION** It i **CRITICAL** that we get as much testing done as possible because **BASICALLY NOTHING HAS BEEN TESTED**, and virtually no files are without major fundamnental changes! *There are 272 different versions of micronucleus built (and part of the 2.0.0-dev branch now), and optiboot will dwarf that number!* 0 of those have been teted. Obviously we are leaning *very* heavily on automation of configuration generation for this release. Half of the tinyNeoPixel speeds have had the assembly routines modified in major ways (there's no more stupid menu for the port), but they are untested. I have a TON of irons in the fire right now, and I am trying to get this out and stop delaying it and delaying it. If you find problems with 2.0.0-dev (you can just create a "hardware" folder in your sketchbook and sync the repo to that location to nanually install - no need to do anything wacky like on my other cores), create an issue, start a discusion, or hell even just email me with info, just get the information to me somehow. Thank you users! ## [Check it out, we have "discussions" now!](https://github.com/SpenceKonde/ATTinyCore/discussions) Let's use that, not gitter. ### Current **strongly** recommended IDE version: 1.8.13 or later. Users of 1.6.x versions should use caution with any board manager packages as the handling of dependency versions, at least under 1.6.9, appears to be severely broken, such that installing one packages can break others. For example, DxCore won't work if ATYTinyCore is installed on 1.6.9! - both cores correctly specify their requirements, but the IDE does not use the correct versions of the toochain. It is likely that similar bugs involving other tools also manifest here. Use 1.8.13 or similar recent version if at all possible; if you are unwilling or unable to update your main Arduino IDE version, a "portable" installation is recommended - the separate copy of IDE *with portable installation* should ensure that what you do in that version does not effect the other version - if you can't use 1.8.13, a portable 1.6.9 version will achieve the same thing, only without the other fixes and improvements that went into the IDE since then. ### [Installation](Installation.md) ### [Wiring and required external components](Wiring.md) ### [Using with Micronucleus boards](avr/extras/UsingMicronucleus.md) ### [Programming Guide](Programming.md) ### [Migration Guide - moving to ATTinyCore from a different ATtiny board package](Migration.md) ## ATtinyCore Universal This core supports the following processors - essentially every "classic" tinyAVR processor that makes sense to use with Arduino. The modern (post-2016 release) tinyAVR parts have their own core, as there is practically zero code at the core level that can be shared with classic parts (in exchange for the cores being totally different, sketches can often be moved between these with little to no effort - not always, but often) Click the processor name for part-specific information: * [ATtiny441, 841](avr/extras/ATtiny_x41.md) (With or without Optiboot or Micronucleus bootloader) * [ATtiny1634](avr/extras/ATtiny_1634.md) (With or without Optiboot bootloader) * [ATtiny87, 167](avr/extras/ATtiny_x7.md) (with or without Optiboot or Micronucleus bootloader) * [ATtiny25, 45, 85](avr/extras/ATtiny_x5.md) (With or without Optiboot or Micronucleus bootloader) * [ATtiny24, 44, 84](avr/extras/ATtiny_x4.md) (With or without Optiboot or Micronucleus bootloader) * [ATtiny261, 461, 861](avr/extras/ATtiny_x61.md) (With or without Optiboot bootloader) * [ATtiny48, 88](avr/extras/ATtiny_x8.md) (With or without Optiboot or Micronucleus bootloader) * [ATtiny828](avr/extras/ATtiny_828.md) (With or without Optiboot bootloader) * [ATtiny2313, 4313](avr/extras/ATtiny_x313.md) (no bootloader) * [ATtiny43](avr/extras/ATtiny_43.md) (no bootloader) Variants of these are also supported (such as the ATtiny1634R, ATtiny2313A or ATtiny85V) ### Non-supported parts * [tinyAVR 0/1/2-series](https://github.com/SpenceKonde/megaTinyCore/) Modern tinyAVR (with 0, 1, or 2 as next-to-last digit) are supported by my megaTinyCore instead. They are totally different in every way except the "t-word" in the name, and the fact that they're great parts and work well with Arduino. * [ATtiny13/13A](https://github.com/MCUdude/MicroCore/) are supported by MicroCore by @MCUdude * ATtiny26 are not supported by any Arduino core. They are the obsolete predecessor to the '261, which itself is ancient). I will accept a PR to add support but will not use my own limited development time for such old and uninspiring parts. * ATtiny 4/5/10/11 and any other "AVRrc" (reduced core) parts. [Try this core](https://github.com/technoblogy/attiny10core) ## Quick Gotcha list - having trouble, read these! **Windows users must install Micronucleus drivers manually** If you want to use Micronucleus (VUSB) boards on Windows, you must manually install the drivers - Arduino does not run "post-install" tasks for third party libraries (though I am told they recognized how nonsensical this is - a malicious core could still run whatever commands it wanted to by telling the IDE that was how to compile sketches for these boards - and will be changing this in the future. Note also that the 1.5.0 release does not include working micronucleus upload tool for Windows, this is resolved in 1.5.2. During the install process it will print the path of a post_install.bat that it skipped running. Running that will install the drivers - it's easiest if you copy/paste it, as after installation the drivers will be located in `C:\Users\YourUserName\AppData\Local\Arduino15\packages\ATTinyCore\tools\micronucleus\2.5-azd1\` Or they can be downloaded from the following URL https://azduino.com/bin/micronucleus/Drivers-Digistump(win).zip . Unzip, run the installation batch file. **avrdude: error: could not find USB device with vid=0x16c0 pid=0x5dc vendor=`www.fischl.de` product='USBasp'** Vaguely recent versions of AVRdude appear to have dropped a few versions of the firmware. If this is the first time you'd installed something that triggered an update here, you may have problems with AVRdude. The solution, thankfully, is straightforward.. . 1. Download Zadig from http://zadig.akeo.ie 2. Plug in USBasp 3. Start zadig 4. Options > List all devices 5. Select USBasp from the drop down menu 6. Select libusbK(v3.0.7.0) driver 7. Click Install **This core includes part specific documentation - click the links above for your family of chips and READ IT** These describe issues and "gotchas" specific to certain chips. Be sure to review this documentation! **problems dynamically linking libusb-0.1 on linux** can occur if Arduino was installed through the Snap package manager. The Arduino IDE should always be installed from the tarball available from http://arduino.cc, never from a package manager. **There is a bug in the IDE that causes compilation errors with some combinations of boards and submenu options** on 1.8.5 and earlier on Windows. The symptom of this is an error ending in something like C:\Users\yourusername\AppData\Local\Temp\arduino_build_131884/..\arduino_cache_186227\core