Standardize formatting of Licence.md.

Author: SpenceKonde

LICENSE.md

@@ -1,4 +1,15 @@
-# GNU LESSER GENERAL PUBLIC LICENSE
+# DxCore, megaTinyCore, and ATTinyCore are released under the LGPL version 2.1
+All files included with these package are covered by this unless
+otherwise noted. *Some included files and libraries are covered by other
+licenses.* Any file licensed under terms other than the LGPL 2.1 will have
+prominent notice of such at the top of the file, including the full text
+of the boilerplate, as well as applicable license files in the directory.
+
+Files licensed under the LGPL 2.1 may have that text abbreviated for
+readability. The LGPL 2.1 license text is reproduced below verbatim
+with no modifications beyond markdown formatting.
+
+## GNU LESSER GENERAL PUBLIC LICENSE
 
 Version 2.1, February 1999
 
@@ -166,13 +177,13 @@ portion of it, thus forming a work based on the Library, and copy and
 distribute such modifications or work under the terms of Section 1
 above, provided that you also meet all of these conditions:
 
--   **a)** The modified work must itself be a software library.
--   **b)** You must cause the files modified to carry prominent
+- **a)** The modified work must itself be a software library.
+- **b)** You must cause the files modified to carry prominent
     notices stating that you changed the files and the date of
     any change.
--   **c)** You must cause the whole of the work to be licensed at no
+- **c)** You must cause the whole of the work to be licensed at no
     charge to all third parties under the terms of this License.
--   **d)** If a facility in the modified Library refers to a function
+- **d)** If a facility in the modified Library refers to a function
     or a table of data to be supplied by an application program that
     uses the facility, other than as an argument passed when the
     facility is invoked, then you must make a good faith effort to
@@ -283,7 +294,7 @@ copyright notice for the Library among them, as well as a reference
 directing the user to the copy of this License. Also, you must do one
 of these things:
 
--   **a)** Accompany the work with the complete corresponding
+- **a)** Accompany the work with the complete corresponding
     machine-readable source code for the Library including whatever
     changes were used in the work (which must be distributed under
     Sections 1 and 2 above); and, if the work is an executable linked
@@ -294,22 +305,22 @@ of these things:
     the user who changes the contents of definitions files in the
     Library will not necessarily be able to recompile the application
     to use the modified definitions.)
--   **b)** Use a suitable shared library mechanism for linking with
+- **b)** Use a suitable shared library mechanism for linking with
     the Library. A suitable mechanism is one that (1) uses at run time
     a copy of the library already present on the user's computer
     system, rather than copying library functions into the executable,
     and (2) will operate properly with a modified version of the
     library, if the user installs one, as long as the modified version
     is interface-compatible with the version that the work was
     made with.
--   **c)** Accompany the work with a written offer, valid for at least
+- **c)** Accompany the work with a written offer, valid for at least
     three years, to give the same user the materials specified in
     Subsection 6a, above, for a charge no more than the cost of
     performing this distribution.
--   **d)** If distribution of the work is made by offering access to
+- **d)** If distribution of the work is made by offering access to
     copy from a designated place, offer equivalent access to copy the
     above specified materials from the same place.
--   **e)** Verify that the user has already received a copy of these
+- **e)** Verify that the user has already received a copy of these
     materials or that you have already sent this user a copy.
 
 For an executable, the required form of the "work that uses the
@@ -334,11 +345,11 @@ library, provided that the separate distribution of the work based on
 the Library and of the other library facilities is otherwise
 permitted, and provided that you do these two things:
 
--   **a)** Accompany the combined library with a copy of the same work
+- **a)** Accompany the combined library with a copy of the same work
     based on the Library, uncombined with any other
     library facilities. This must be distributed under the terms of
     the Sections above.
--   **b)** Give prominent notice with the combined library of the fact
+- **b)** Give prominent notice with the combined library of the fact
     that part of it is a work based on the Library, and explaining
     where to find the accompanying uncombined form of the same work.
 

Programming.md

@@ -1,4 +1,4 @@
-## Programming the ATtiny parts
+# Programming the ATtiny parts
 
 All parts supported by ATTinyCore can be programmed using ISP (also called ICSP or SPI programming), using the SCK, MISO, MOSI and Reset pins. Most breakout boards (including all the ones I sell) provide a 6-pin (2x3) ISP programming header that matches the 6-pin connector used on common programmers. You will need an ISP programmer - the USBAsp and USBTinyISP programmers are readily available from ebay, amazon, aliexpress and many other vendors, typically for prices of around $3. If you get a USBAsp, be sure to get one with the 10-pin to 6-pin adapter. You can also use another Arduino (I know the AVR-based ones work, eg, nano, uno, pro mini - I can't make any promises about the fancier, non-AVR boards) using the Arduino as ISP sketch; upload this sketch to the board, and then place a approx. 10uF (within a factor of 10) capacitor between reset and ground on that Arduino (this disables autoreset - it must be removed before you try to upload a different sketch).
 
@@ -8,7 +8,7 @@ In the following sections, the "programmer" is the ISP programmer or Arduino run
 
 We recommend that everyone enable Verbose Uploads - in Preferences, under "Show Verbose Output During", check "Upload" (we recommend unchecking "Compiling" unless chasing down a mysterious compile failure, as it produces a lot of output that usually isn't relevant).
 
-### Programming via ISP (for burning bootloader, and uploading to non-optiboot boards)
+## Programming via ISP (for burning bootloader, and uploading to non-optiboot boards)
 Ensure that you have connected all necessary external components (see [Wiring Guide](Wiring.md). If you have an ISP programmer with the 6-pin header, and a 6-pin header on the board, connect it to the board. If you are using Arduino as ISP, the connections are:
 
 * Vcc of programmer to Vcc of target
@@ -43,7 +43,7 @@ If burning the bootloader, do Tools -> Burn Bootloader. You should see output on
 
 If uploading a sketch, click upload. You should see output on the console reporting that the sketch was successfully uploaded.
 
-#### FTDI in bitbang mode?
+## FTDI in bitbang mode?
 Go search aliexpress, or ebay, or whatever the equivalent is in your country. You will find a blue "FTDI" serial adapter. Look through the designs on offer until you see one with a mini USB connector a switch to select voltage, an unmarked 2x3 set of pins in the middle, and the normal FTDI pinout. The build quality is abysmal, the last batch I got, it felt like the solder had been severely oxidized, the chip was off center on most of them, and obviously the FTDI chip is one of the counterfeits (which seem to work just as well as any that I've tried.... they run under $2 US on aliexpress. That mysterious 2x3 header? Yeah, that's for ISP programming using synchronous bitbang mode. This option enables it, a feature that in and of it self makes this the best of the FT232 clone adapter boards, and quite an appealing package. It can have the added diode and/or resistors to act as a UPDI programmer on modern AVRs connected permanently and still do ISP like this!
 For other FT232RL adapters that break out the modem control lines, it's:
 
@@ -58,7 +58,7 @@ Note that this can only be done with FT232RL's.
 
 This is not the same as the protocols that involve any-old-serial-adapter's modem control lines, generally using a pulse on TX in place of SCK, and reading one bit at a time from a modem control input amd semdomg the same. Those are agonizingly slow, only a desperation tactic to get optiboot onto something when you've just got nothing. They are not supported by this core.
 
-### Programming via Serial (Optiboot)
+## Programming via Serial (Optiboot)
 
 Ensure that you have connected all necessary external components (see [Wiring Guide](Wiring.md)), including the autoreset circuit. Unless you are using a breakout/development board where the bootloader was preinstalled, you must use an ISP programmer to "burn bootloader" as described above before you can reprogram it via serial. If you have a board with the 1x6 pin "FTDI" serial header, and a programmer with the same pinout, they can be connected directly, otherwise, make the following connections:
 
@@ -76,7 +76,7 @@ On the t841, t441, t1634, and t828, pages are erased on blocks of four. The boot
 **Warning about Optiboot on non ATtiny828 devices**
 On parts that do not have hardware bootloader support (only the 828 has that), Optiboot uses "Virtual Boot" to rewrite the vector table as it writes the flash, using the EE_RDY vector to store the address that the program starts at. The problem arises if there is a very poorly timed interruption - for example, a mis-timed reset pulse after programming has started, or a brownout that causes a reset. If this happens at just the wrong moment, the first page of flash can be erased, but not rewritten. While that sounds unlikely, it has been encountered twice in internal testing. When this happens, the part will require ISP programming to unbrick. See #398. Until this issue is resolved, **Optiboot is not for production.** That is to say, if devices are to be deployed in a situation where they will be reprogrammed via serial "in the field", but where ISP programming is impractical, this is not a safe solution.
 
-### Tips and Tricks
+## Tips and Tricks
 * If you have a breakout board with holes for the 6-pin header, but don't want to solder pin header onto it, no problem. Just put a plug a piece of pin header into the connector on the programmer, insert it in the holes, and hold it at an angle, applying gentle pressure to make sure the pins make contact while you run the programming command. I use this technique routinely - it's how I used to bootload the boards I sell; you can also buy a "pogo-pin adapter" which has 6 spring loaded pins, which is a bit easier to handle (this is what I use now).
 
 * Be sure you are plugging in the connector on the top of the board - if it is plugged in backwards, but on the correct side, it will not damage the board; if you don't know which way to orient the connector, you can try them both, and the one that works is correct. However, if you were to put the header in on the wrong side of the board, it would likely damage the board.

README.md

@@ -54,11 +54,11 @@ ATTinyCore supports classic ATtiny parts. It does not support any other AVR devi
 * [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 many of them have a peripheral selection to make most classic AVRs turn gteen with envy (like a 3227 or 3226's peripera;s beat the stuffing out of many classic AVR parts, including the 328pb
 * [ATtiny13/13A](https://github.com/MCUdude/MicroCore/) are supported by MicroCore by @MCUdude - 2k of flash is the lower cutoff for ATTinyCore.
 * The ATtiny28L is not supported by any Arduino core. It is older than the hills, weirder than quantum physics... AND IT DOESN'T HAVE RAM! IT ONLY HAS REGISTERS! Put it back into the museum case where you got it before the security guards notice it missing from the "prehistoric man and computing" exhibit.
-* ATtiny 4/5/10/11 and the 10x tinyAVRs, or any other "AVRrc" (reduced core) parts/ these combine minuscule memory sizes with a gimped CPU. [Try this core](https://github.com/technoblogy/attiny10core) if you are a masochist and extremely space constrained. The core has to cut significant parts of the API in order to fit. These parts are kinda lousy - there is a point when trying to use smaller and smaller microcontrollers stops being fun and starts being just annoying. These parts, for example. With the exception of the ATtiny28L, and some discontinued parts not included on this list, any other AVR more capable that these things, and it's not like the discount for losing all that functionality is worth it. 
+* ATtiny 4/5/10/11 and the 10x tinyAVRs, or any other "AVRrc" (reduced core) parts/ these combine minuscule memory sizes with a gimped CPU. [Try this core](https://github.com/technoblogy/attiny10core) if you are a masochist and extremely space constrained. The core has to cut significant parts of the API in order to fit. These parts are kinda lousy - there is a point when trying to use smaller and smaller microcontrollers stops being fun and starts being just annoying. These parts, for example. With the exception of the ATtiny28L, and some discontinued parts not included on this list, any other AVR more capable that these things, and it's not like the discount for losing all that functionality is worth it.
 * Anything with "ATmega" in the name - you want [one of MCUDude's cores](https://github.com/MCUdude/) - he has one for almost every ATmega part. '
 * The ATmegaXXcN and XXmN where X is the flash size and N is a small number. There is no core supporting these rarely seen or discussed classic AVRs. The c's are a follow-on to the ATCAN series (the older CAN parts are supported by some of MCUDude's cores) and the m series the follow-on to the PWM-centric parts of the same vintage (The more recent modern AVRs - namely the tinyAVR 1-series and Dx-series - have a Type D timer, which was clearly inspired by the PWM controller on those parts, making it interesting to those who study feature evolution semiconductors).
 * AVR Dx-series (AVR128DA64, etc) - [the crown jewel of the AVR product line](https://github.com/SpenceKonde/), supported by my DxCore.
-* AVR Ex-series (AVR64EA48, AVR32EB32, not yet for sale) will also be supported by DxCore ones the datasheets is available to clear up a few remaining questions about the EA and a ton of questions about the EB. 
+* AVR Ex-series (AVR64EA48, AVR32EB32, not yet for sale) will also be supported by DxCore ones the datasheets is available to clear up a few remaining questions about the EA and a ton of questions about the EB.
 
 ## Quick Gotchas/FAQ list
 ### Having trouble? read these first!

avr/LICENSE.md

@@ -1,4 +1,15 @@
-# GNU LESSER GENERAL PUBLIC LICENSE
+# DxCore, megaTinyCore, and ATTinyCore are released under the LGPL version 2.1
+All files included with these package are covered by this unless
+otherwise noted. *Some included files and libraries are covered by other
+licenses.* Any file licensed under terms other than the LGPL 2.1 will have
+prominent notice of such at the top of the file, including the full text
+of the boilerplate, as well as applicable license files in the directory.
+
+Files licensed under the LGPL 2.1 may have that text abbreviated for
+readability. The LGPL 2.1 license text is reproduced below verbatim
+with no modifications beyond markdown formatting.
+
+## GNU LESSER GENERAL PUBLIC LICENSE
 
 Version 2.1, February 1999
 
@@ -166,13 +177,13 @@ portion of it, thus forming a work based on the Library, and copy and
 distribute such modifications or work under the terms of Section 1
 above, provided that you also meet all of these conditions:
 
--   **a)** The modified work must itself be a software library.
--   **b)** You must cause the files modified to carry prominent
+- **a)** The modified work must itself be a software library.
+- **b)** You must cause the files modified to carry prominent
     notices stating that you changed the files and the date of
     any change.
--   **c)** You must cause the whole of the work to be licensed at no
+- **c)** You must cause the whole of the work to be licensed at no
     charge to all third parties under the terms of this License.
--   **d)** If a facility in the modified Library refers to a function
+- **d)** If a facility in the modified Library refers to a function
     or a table of data to be supplied by an application program that
     uses the facility, other than as an argument passed when the
     facility is invoked, then you must make a good faith effort to
@@ -283,7 +294,7 @@ copyright notice for the Library among them, as well as a reference
 directing the user to the copy of this License. Also, you must do one
 of these things:
 
--   **a)** Accompany the work with the complete corresponding
+- **a)** Accompany the work with the complete corresponding
     machine-readable source code for the Library including whatever
     changes were used in the work (which must be distributed under
     Sections 1 and 2 above); and, if the work is an executable linked
@@ -294,22 +305,22 @@ of these things:
     the user who changes the contents of definitions files in the
     Library will not necessarily be able to recompile the application
     to use the modified definitions.)
--   **b)** Use a suitable shared library mechanism for linking with
+- **b)** Use a suitable shared library mechanism for linking with
     the Library. A suitable mechanism is one that (1) uses at run time
     a copy of the library already present on the user's computer
     system, rather than copying library functions into the executable,
     and (2) will operate properly with a modified version of the
     library, if the user installs one, as long as the modified version
     is interface-compatible with the version that the work was
     made with.
--   **c)** Accompany the work with a written offer, valid for at least
+- **c)** Accompany the work with a written offer, valid for at least
     three years, to give the same user the materials specified in
     Subsection 6a, above, for a charge no more than the cost of
     performing this distribution.
--   **d)** If distribution of the work is made by offering access to
+- **d)** If distribution of the work is made by offering access to
     copy from a designated place, offer equivalent access to copy the
     above specified materials from the same place.
--   **e)** Verify that the user has already received a copy of these
+- **e)** Verify that the user has already received a copy of these
     materials or that you have already sent this user a copy.
 
 For an executable, the required form of the "work that uses the
@@ -334,11 +345,11 @@ library, provided that the separate distribution of the work based on
 the Library and of the other library facilities is otherwise
 permitted, and provided that you do these two things:
 
--   **a)** Accompany the combined library with a copy of the same work
+- **a)** Accompany the combined library with a copy of the same work
     based on the Library, uncombined with any other
     library facilities. This must be distributed under the terms of
     the Sections above.
--   **b)** Give prominent notice with the combined library of the fact
+- **b)** Give prominent notice with the combined library of the fact
     that part of it is a work based on the Library, and explaining
     where to find the accompanying uncombined form of the same work.