Mercurial > public > ostc4

view wiki/Make Firmware File.md @ 814:26ae9e8f24fd

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Dev Bugfix: O2 values of new detected sensors were shown as invalid: In the previous version sometime O2 values were shown as invalid (red) after a autodetection cycle was run. After sleep/wakeup cycle the status were shown correct. Rootcause was that the out of bounds detection is based on the divesettings while the HW menu were only updating the common settings regarding active / inactive sensors. The problem has been solved by adding an divesettings update within the HW / sensor menu.
author Ideenmodellierer
date Sun, 03 Sep 2023 17:58:12 +0200
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"