FreeEMS Issues - Firmware
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000169||Firmware||Init & Config||public||2011-06-16 15:38||2011-06-28 10:45|
|Target Version||0.3.0||Fixed in Version|
|Issue Type||New Feature|
|Risk of Breakage||low|
|Summary||0000169: Create DDL and implement it|
|Description||We need to create a master file that contains both data, structure, versions and so on.|
From this file we will generate any number of different formats containing the default data and the structures that hold it.
There are two main outputs:
1) C code - headers with structs and initialisation code using those headers and holding the default data
2) XML/JSON/etc - structure definitions, default data definitions, meta data, human descriptions, versions, etc. For use in tuning applications wishing to communicate with the firmware. This will either generate two files or one with optional data. A tuning package should be able to pick up this file and talk to the device showing some form of simplistic UI for the available tunable items.
Additionally, we should look into compressing the structure and meta data stuff and storing it in flash on the actual device to be returned in pieces upon request. This may or may not be possible, but if it is, would allow a self contained firmware which doesn't need any external files to function with external software - very clean. It could be that the size of such data would be prohibitive, though.
A somewhat messy thread on the subject exists here:
And an older one about the same stuff here:
This is a priority for 0.3.0 with some number of 0.2.X releases between 0.2.0 and then.
|Steps To Reproduce|
|Tags||No tags attached.|