Skip to content

Commit c13aec5

Browse files
authored
More updates!
The editor froze and I had to submit or lose everything, this is finishing off the work from the previous commit.
1 parent 45f20d6 commit c13aec5

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

README.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,13 @@ Currently included are:
1414

1515
Shield means the Arduino is designed to plug in from beneath your PCB; socket means it is designed to plug in from above.
1616

17+
## Comments, Requests, Bugs & Contributions
18+
All are welcome. Please file an Issue or Pull Request at https://github.com/Alarm-Siren/arduino-kicad-library
19+
20+
## License
21+
Copyright 2017, Nicholas Parks Young. Some Rights Reserved.
22+
This library is licensed under the GNU LGPL v2.1, which can be found in file LICENSE.txt.
23+
1724
## Library Setup
1825
To add this library to your KiCad Project, do the following steps:
1926
1. Copy the source files to your Project. Make sure that the Arduino.pretty folder structure is preserved.
@@ -25,21 +32,14 @@ To add this library to your KiCad Project, do the following steps:
2532
7. In the new line of the table, set Library Path to "$(KIPRJMOD)\Arduino.pretty" and ensure Plugin Type is "KiCad". Options and Description can be left blank. You should set Nickname to something descriptive - like "Arduino" for example!
2633
8. All done: you are now ready to use these schematic components and footprints!
2734

28-
## Comments, Requests, Bugs & Contributions
29-
All are welcome. Please file an Issue or Pull Request at https://github.com/Alarm-Siren/arduino-kicad-library
30-
31-
## License
32-
Copyright 2017, Nicholas Parks Young. Some Rights Reserved.
33-
This library is licensed under the GNU LGPL v2.1, which can be found in file LICENSE.txt.
34-
3535
## A note about Power and Reset pins
3636

3737
### Power
3838
On the Arduino Platform, it is not possible to categorically state that the power pins are "power inputs" or "power outputs", as that depends on exactly how you're using the Arduino. For example, if you're powering the Arduino from USB then GND, +3.3V and +5V would be power outputs and VIN would do nothing, whereas if you're powering the Arduino from a battery via your Sheild then VIN and GND are power inputs whilst +5V and +3.3V are power outputs. There are other, more esoteric possibilities too.
3939

4040
Regardless of the above, I needed to make a decision about what electrical type to apply to these pins. I could use something like Passive or Unspecified, but then KiCad's Electrical Rules Checker (ERC) tool would not be effective in catching errors on these pins at all, whilst using Power Output means it objects to you joining pins together (for example, joining all the GND pins into a common net) even when that's OK in some situations.
4141

42-
Therefore, I have decided to use Power Input as this presents the least issues.
42+
Therefore, I have decided to use Power Input as this presents the least issues. This means if you're actually using any of the power pins as Power Outputs in your schematic, by default the ERC will complain that the relevant nets are undriven. To fix this you will need to add a special "PWR_FLAG" component to the affected net.
4343

4444
### Reset
4545
Reset pins on the Arduino Platform have interesting electrical characteristics, which mean that no KiCad electrical type exactly matches their functionality. I settled on Open Collector as the nearest candidate, but unlike a true Open Collector pin on an integrated circuit, the reset pins on the Arduino Platform have an internal weak pull-up, and the reset button that can strongly pull low, so your circuit needs to be able to cope with all these situations.

0 commit comments

Comments
 (0)