| Age | Commit message (Collapse) | Author |
|---|
|
This table is the result of running:
./tools/resistor_selector.py --output pcb/versions.tsv
Additionally the table was manually edited. The first column now
contains version strings to reserve resistor combinations.
This is used to keep track of existing versions, their resistor values
and related ADC values. The latter will be added to the firmware too.
|
|
Making them active-low makes it easier to reset the MCU. For the wipe
functionality it does not make a role since it will simply be defined in
Devicetree.
|
|
This voltage divider provides an analog voltage between GND and +3.3V to
indicate which hardware revision this board is.
Thus the same firmware image can be used on multiple PCB versions
compensating the hardware differences in software.
The resistor combinations are calculated by
`tools/resistory_selector.py`.
|
|
This reduces the electrical contacts which is possible and necessary
because of size constraints.
|
|
These files seem to be present since KiCad 9.0 and should not be tracked
with version control.
|
|
|
|
This can be used to order the PCB depending on the manufacturers
software capabilities.
|
|
Using the installation step to copy selected artifacts into one folder
was anyway a hack.
This commit shows that the complexity can be reduced by adding copy
targets. The `build/artifacts` folder contains the selected artifacts,
they are always up to date, the user does not have to call the install
step separately and the target definitions do not require
install-related keyword arguments.
|
|
A static site generator is currently not really required. A static
index.html is currently sufficient.
|
|
This makes the build system code way less hacky and more modular.
|
|
These important design files should be deployed with the website.
|
|
This allows to install the PCB-related files easier to the website which
is built with Meson.
|
|
KiCad based on the not committed user settings saves backups in
iot-contact-backups. Excluding those backups from Git is important to
not double-track changes.
|
|
|
|
|
|
|
|
This makes it easier to keep the descriptions and the text inside the
schematic in sync.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Power over Ethernet (PoE) has the disadvantage that GND is significantly
below earth. This requires that GND of a PoE-powered device is never
attached to earthed devices.
In production use cases this is no problem. The earth lines are
isolated.
Nevertheless for debugging it is sometimes useful to connect measuring
equipment like logic analyzers and oscilloscopes to the board. This is
not possible with PoE. Thus an alternative earth-based 5V power input is
useful.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This simplifies the CMake code and the paths inside the build folder.
|
|
|
|
|
|
|
|
This is the starting point for the PCB development.
|
|
|
|
|
|
|
|
It is planned to switch to Ethernet instead of LoRa for communication.
Thus the custom PCB with the STM32WL MCU does not make sense anymore. To
get started the Ethernet variant will use a ST NUCLEO board to avoid
creating a custom PCB first.
|
|
This IC has a small footprint and will provide the 3.3 V for the
microcontroller.
|
|
|
|
|
|
|
|
This makes the KiCad project a valid PCB as a minimal starting point.
|
|
|
|
Based on UM2592 the development kit Nucleo WL55JC which is used for
firmware development is based on the STM32WL55JCI7 microcontroller.
Thus this MCU should be a good starting point for now.
|
|
|
