Mercurial > public > ostc4
view wiki/Make Firmware File.md @ 976:0b81ac558e89 Evo_2_23
Devbugfix UART buffer cleaning:
In the previous version a buffer cleaning function was used which resets the ringbuffer read index. As result the processing of data was stopped until the DMA write comes to the index 0. When reaching it the complete buffer was proceeded including possibly invalid data.
The usage of the cleanbuffer function was replaced by the flush buffer function (meaning the data is discarded but the data index is maintained). There was already a function for this. Because the function was 99% the same as the read function, it was integrated into the ReadData function. Calling the function with parameter flush = 1 will result in a buffer flush.
The workaround of the previous revision was updated to only be applied in case a DiveO2 sensor is operated in stand alone mode.
| author | Ideenmodellierer |
|---|---|
| date | Wed, 29 Jan 2025 17:21:20 +0100 (7 weeks ago) |
| parents | 0e7c16dd774d |
| children |
line wrap: on
line source
# How to Make an Uploadable Firmware File for the OSTC4 # Generated BIN files from the SMT32 Workbench need modification in order to be installed via the OSTC Companion onto the OSTC4. ## Build Command Line Tools ## These can be found in /ostc4pack (For Windows, CPP sources available) ## Run the Tools Manually ## 1. Copy generated BIN files (From the Release or debug directory) into /ostc4pack. Or: Modify .bat files to point to your Release or debug directory. 2. run step1_create_OSTC_RTE_upload.bat and/or step1_create_OSTC4_firmware_upload_bin.bat (Depending on which part you made changes) 3. run step2_create_OSTC4update_bin.bat to create final OSTC4update_xxxxxx.bin, with xxxxxx being the current date in YYMMDD format. This will add important checksums required for the OSTC4's bootloader to accept the file. ## Upload this file with the OSTC Companion software to the OSTC4 ## See http://forum.heinrichsweikamp.com/read.php?7,19186 on how to get and use the "OSTC companion"