Project

General

Profile

User story #791

Patch RealTimeThreadSyncrhonisation (from FAT-tools)

Added by André Neto about 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Start date:
08.04.2021
Due date:
% Done:

0%

Estimated time:
Git branch (link):
Git merge to develop (link):
SVN commit (link/?p=rev):

Description

https://vcis-gitlab.f4e.europa.eu/aneto/MARTe2-components/-/compare/develop...DiagnosticCrio#7a207f5396f3fa5829e59b3540bd26d5f8c4adf2
https://vcis-gitlab.f4e.europa.eu/aneto/MARTe2-components/-/compare/develop...DiagnosticCrio#cd58b8f0074f034650fc3e38232ad9231912a2e8
https://vcis-gitlab.f4e.europa.eu/aneto/MARTe2-components/-/compare/develop...DiagnosticCrio#1c31d0a2143af387864edc09064342a62f5f45d4
https://vcis-gitlab.f4e.europa.eu/aneto/MARTe2-components/-/compare/develop...DiagnosticCrio#a491e4d7097658d4b4cd9b967d7f8dce251c4bcf

See also: #779

History

#1 Updated by André Neto about 4 years ago

  • Subject changed from Patch RealTimeThreadAsyncBridge (from FAT-tools) to Patch RealTimeThreadSyncrhonisation (from FAT-tools)

#2 Updated by André Neto almost 4 years ago

  • Status changed from Code: Impl to Closed

If the parameter WaitForNext is set to 1, the synchronisation thread will first reset and then wait on the event semaphore. This can be useful if cycles were lost and the thread should wait for the next synchronisation cycle. The default behaviour (WaitForNext=0) is to first wait and then reset the semaphore and, as a consequence, if the semaphore had already been posted, it will not wait.

Merged with develop at 3b45257e8716e9b68c35a35704f23fdff838818e

#3 Updated by André Neto almost 4 years ago

  • Description updated (diff)

Also available in: Atom PDF