Hardware

h1. HWData

h2. Intro

Campo specifies layouts for hardware data and configuration.
"Campo":http://hase.seesslen.net/redmine/projects/campo/wiki/HwData_Structures
"Miniminutnik":http://hase.seesslen.net/redmine/projects/miniminutnik_sw/wiki/EEPROM

* 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.



h2. Where to store production database

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