Mercurial > public > ostc4
view ostc4pack/README.linux @ 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 | 9c77cfe8c2b2 |
children |
line wrap: on
line source
README.linux ------------ 1. Compile the pack utilities cd src make checksum_final_add_fletcher make OSTC4pack_V4 2. Edit create_full_update_bin.sh Set BUILD_PATH to the location where you build the individual parts of the firmware using the OpenSTM23 IDE. Set BUILD_TYPE the either Debug or Release (or any other build style you defined in the OpenSTM23 IDE). Set the "build project names" as defined in the OpenSTM23 IDE. 3. Simpy run create_full_update_bin.sh Run it in the ostc4pack folder of the repository, and a file with name like OSTC4_<date>.bin is created containg the individual blobs.