Update README.md
This commit is contained in:
anabolyc
GitHub
39
README.md
39
README.md
@@ -5,6 +5,8 @@
|
||||
|
||||
ATtiny 1616 Development Board is a small and handy development board built around new generation of ATiny series. It is pin and size compartible with Arduino Nano board and can be used as it's direct replacement (with certain limitations). It can be programmed using both Arduino IDE and Platformio IDE, as well as vanilla console tools.
|
||||
|
||||
|
||||
|
||||
## Motivation
|
||||
|
||||
I'm a big fan of early ATtiny series chips, I even made my own [ATtiny Flasher](https://sonocotta.com/attiny-flasher/) tool for productive development and few educational kites based on ubiquitous ATtiny85. Time has come to extend my horizons and look into modern line of ATtiny chips, specifically so called 1-series and 2-series line of MCUs.
|
||||
@@ -58,21 +60,48 @@ Spence Konde created another great [writeup](https://github.com/SpenceKonde/AVR-
|
||||
|
||||
Method (c) is disqualified on 1-Series chip because of RESET/UPDI pin collision, and both (a) and (b) work equally well. Difference being what is easier for you: (a) dedicate Arduino Nano board for programming or (b) do solder job on your usb-serial adapter.
|
||||
|
||||
|
||||
|
||||
### Arduino IDE
|
||||
|
||||
...
|
||||
Use Arduino 1.8.x, Core doesn't work with 2.X versions of Arduino at the moment of writing.
|
||||
|
||||
Add [http://drazzy.com/package_drazzy.com_index.json](http://drazzy.com/package_drazzy.com_index.json) to board manager
|
||||
|
||||
|
||||
|
||||
After that you should install megaTinyCore from Board Manager
|
||||
|
||||
|
||||
|
||||
Select ATtiny1616 as target and other necessary settings in the board settings after
|
||||
|
||||
|
||||
|
||||
### Platformio IDE
|
||||
|
||||
...
|
||||
After installing [Plarformio IDE](https://platformio.org/platformio-ide), open [sample project](/firmware/t1616-starter). Run `Build` command to install necessary tools and libraries.
|
||||
|
||||
Next run `Upload: tiny1616-jtag2updi` task if you're using jtag2updi programmer, or `Upload: tiny1616-serialupdi` task if using modified Serial adapter method. In both cases you can use `Upload and Monitor` task.
|
||||
|
||||
## Hardware
|
||||
|
||||
...
|
||||
|
||||
|
||||
## Firmware
|
||||
|
||||
...
|
||||
-  ATTINY1616 MCU
|
||||
-  CH340E USB-Serial Adapter connected to Hardware Serial
|
||||
-  WS2812B RGB LED
|
||||
-  UPDI Programming and Debug header
|
||||
-  Hardware Push button
|
||||
-  VIN disconnect - cut this line to disconnect LDO chip and power-on LED, recommended for low-power applications
|
||||
-  RES disconnect - short this line to enable auto-RESET functionality with Optiboot bootloader (read below)
|
||||
|
||||
### Auto reset with Optiboot
|
||||
|
||||
As [explained](https://github.com/SpenceKonde/megaTinyCore) in many details by Spence, 1-Series chips cannot provide Arduino-like one-click-upload with Optiboot behavior without some sacrifice. Reason for that is pin collision: UPDI and RESET are the same pin, so you need to decide which you'd prefer. If you use auto-reset, you lose UPDI, specifically possibility to change fuses easily (this is important in my opinion). If you use UPDI you need 2 connections to your MCU - one via programming interface, another one for Serial communication.
|
||||
|
||||
Personnaly I prefer to keep UPDI and use direct programming without custom bootloader, having extra wire is minor inconvinience for me, but losing fuses permanently is not an option.
|
||||
|
||||
## Where to buy
|
||||
|
||||
|
||||
Reference in New Issue
Block a user