HWData¶

Intro¶

Campo specifies layouts for hardware data and configuration.
Campo
Miniminutnik

• 0x20 Bytes Production-Data (common)
• 0x20 Bytes Board-Config (specific)
• 0x20 Bytes Application configuration (specific, redundant)

This production data should neither be store in hw- nor sw-repository.
An products-global database may irritate, having all boards in one table with same serial number.
An per-project-database should be created.
The ".campo" has to contain an function to migrate hw-config information from the database to the c-structure for gdb.
In the production repository there is can script which calls the campo script in the software repository.

The production repository holds the bringup binaries and an own ".campo" which contain an function to
migrate hw-config information from the database to the c-structure for gdb.

Where to store production database¶

• Production-Repository in HW for all products
• One database for all? There is specific configuration data.
  • Abstract specific configuration as option bytes?
  • Make it generic; MCU; solder option; Counter;
  • Show info from board-table
• Run script in SW-Repo to write hwdata (There is already the bringup software. But repo should not change by produced PCBs)