A low-power wireless prototyping module designed deep in the heart of Texas
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Nathan L. Conrad 554884252c Update B.Mask text 5 years ago
bgtex.3dshapes Add layout 5 years ago
bgtex.pretty Fix mounting holes on F.Fab 5 years ago
ref Add layout 5 years ago
.gitattributes Create and assign footprints 5 years ago
.gitignore Add script to generate board plots 5 years ago
README Improve kipy dependency description in README 5 years ago
bgtex-cache.lib Add layout 5 years ago
bgtex.dcm Use a proper power symbol for VSPI 5 years ago
bgtex.kicad_pcb Update B.Mask text 5 years ago
bgtex.lib Hide BGM220P schematic symbol no-connect pin 5 years ago
bgtex.pro Disabled Eco1/Eco2 layers 5 years ago
bgtex.sch Do not populate C1 5 years ago
fp-lib-table Create and assign footprints 5 years ago
plot.py Do not populate C1 5 years ago
release Improve release script stdout 5 years ago
sym-lib-table Capture schematic 5 years ago

README

bgtex

BGTEX schematic and PCB design


DEPENDENCIES

- KiCad version 5.1.6 for macOS.  Results with previous or subsequent versions
  will likely vary.
- kipy (https://git.alt-tek.com/alt-tek/kipy) is useful to simplify executing
  scripts with KiCad's Python environment.  It is required to generate board
  plots with plot.py for releases.
- tea (https://gitea.com/gitea/tea) is required to generate releases.  Install
  and write your API token to ~/.config/git.alt-tek.com/api-token.  Restrict
  access to your API token by setting its file permissions accordingly
  (i.e. 'chmod 600 ~/.config/git.alt-tek.com/api-token').
- In order to generate releases, SSH must be configured for git.alt-tek.com
  such that SSH Git commands can be executed without explicitly specifying an
  SSH identity or private key


RELEASING

1. See above dependencies
2. Create an annotated Git tag for the release commit using
   "git tag -a v<version> -m 'Version <version>' <commit>" where version is the
   board version in X.Y.Z form and <commit> is the commit hash
   (e.g. "git tag -a v1.2.3 -m 'Version 1.2.3' d15c0cafe")
3. Push the tag upstream (i.e. 'git push origin tags/v<version>')
4. Use the release script to build the release and upload it as a draft
   (i.e. './release <version>')
5. Review the release draft.  If it is ready for pre-release or production,
   publish it.