Images » Historie » Revision 5
Revision 4 (Maximilian Seesslen, 18.11.2024 18:00) → Revision 5/7 (Maximilian Seesslen, 18.11.2024 18:00)
h1. Images
Would be nice to have firmware images containing board id which is verified before flashing.
The cmake scripts should produce this. Arena knows the board id. It can be added to the generated cmake file which is included.
Kokon could provide the make target for the image.
* xml file
* base64 encoded binary blob
An image file could contain multiple images. For example canswitch should automatically flash the correct version according to the variant/used controller.
Or even all images of an squeezer run.
* Board ID; HW-Variant has different board id because different build; solder variant is in eeprom
h2. Multiple files for single node
* Multimedia may be available for external flash.
* Board code
* Firmware version
* Component
** 0: main
** 1: external media flash
When flashing node X, it gets an board code, e.g 0x02000001. For this board code, there must be one main file for component 0. But there may be an file for 0x0200FFFF.
<pre><code class="xml">
<?xml>
<kokon>
<device article="0x0200">
<compnent co="0">
<articlecode>0x02000001</articlecode>
<data></data>
</compnent>
<compnent co="1">
<articlecode>0x02000001</articlecode>
<articlecode>0x02000002</articlecode>
<articlecode>0x02000101</articlecode>
<data></data>
</compnent>
</kokon>
</code></pre>
Would be nice to have firmware images containing board id which is verified before flashing.
The cmake scripts should produce this. Arena knows the board id. It can be added to the generated cmake file which is included.
Kokon could provide the make target for the image.
* xml file
* base64 encoded binary blob
An image file could contain multiple images. For example canswitch should automatically flash the correct version according to the variant/used controller.
Or even all images of an squeezer run.
* Board ID; HW-Variant has different board id because different build; solder variant is in eeprom
h2. Multiple files for single node
* Multimedia may be available for external flash.
* Board code
* Firmware version
* Component
** 0: main
** 1: external media flash
When flashing node X, it gets an board code, e.g 0x02000001. For this board code, there must be one main file for component 0. But there may be an file for 0x0200FFFF.
<pre><code class="xml">
<?xml>
<kokon>
<device article="0x0200">
<compnent co="0">
<articlecode>0x02000001</articlecode>
<data></data>
</compnent>
<compnent co="1">
<articlecode>0x02000001</articlecode>
<articlecode>0x02000002</articlecode>
<articlecode>0x02000101</articlecode>
<data></data>
</compnent>
</kokon>
</code></pre>