HWData » Historie » Version 6
Maximilian Seesslen, 10.10.2022 11:58
| 1 | 1 | Maximilian Seesslen | h1. HWData |
|---|---|---|---|
| 2 | |||
| 3 | 5 | Maximilian Seesslen | h2. Intro |
| 4 | |||
| 5 | Campo specifies layouts for hardware data and configuration. |
||
| 6 | "Campo":http://hase.seesslen.net/redmine/projects/campo/wiki/HwData_Structures |
||
| 7 | "Miniminutnik":http://hase.seesslen.net/redmine/projects/miniminutnik_sw/wiki/EEPROM |
||
| 8 | |||
| 9 | * 0x20 Bytes Production-Data (common) |
||
| 10 | * 0x20 Bytes Board-Config (specific) |
||
| 11 | * 0x20 Bytes Application configuration (specific, redundant) |
||
| 12 | |||
| 13 | 6 | Maximilian Seesslen | This production data should neither be store in hw- nor sw-repository. |
| 14 | An products-global database may irritate, having all boards in one table with same serial number. |
||
| 15 | An per-project-database should be created. |
||
| 16 | The ".campo" has to contain an function to migrate hw-config information from the database to the c-structure for gdb. |
||
| 17 | 5 | Maximilian Seesslen | |
| 18 | 2 | Maximilian Seesslen | h2. Where to store production database |
| 19 | 1 | Maximilian Seesslen | |
| 20 | * Production-Repository in HW for all products |
||
| 21 | 4 | Maximilian Seesslen | * One database for all? There is specific configuration data. |
| 22 | ** Abstract specific configuration as option bytes? |
||
| 23 | ** Make it generic; MCU; solder option; Counter; |
||
| 24 | ** Show info from board-table |
||
| 25 | 1 | Maximilian Seesslen | * Run script in SW-Repo to write hwdata (There is already the bringup software. But repo should not change by produced PCBs) |