-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CFE TIME fails to build when CFE_TIME_CFG_SIGNAL set to TRUE #78
Comments
Imported from trac issue 47. Created by jphickey on 2015-05-18T11:19:47, last modified: 2019-07-03T12:48:08 |
Trac comment by jphickey on 2015-05-18 11:22:02: Needs review by the CCB as to what the best course of action should be. |
Trac comment by jhageman on 2019-04-01 09:40:24: CCB 3/27/2019 - discussed removing unimplemented configuration options. Assigning to Alan for review. Edit - fixed CCB date typo |
Trac comment by acudmore on 2019-04-03 11:23:39: I would like to do a survey to see if anyone has used this option. If we decide it's necessary, it should be implemented using a PSP function since this is a very platform specific feature, not part of an OS. If we do remove it, it involves removing a TIME command and at least one telemetry point. If we decide to remove it, maybe we should document it as deprecated (in the code and config file ) and remove it as part of a future TIME subsystem simplification. |
Trac comment by jhageman on 2019-07-03 12:48:08: Moved unfinished 6.6.1 issues to next minor release |
See also #302 |
The CFE_TIME_CFG_SIGNAL configuration macro will add calls to a function {{{OS_SelectTone()}}} if it is set to TRUE.
However, OS_SelectTone is neither prototyped nor implemented in any released version of CFE or OSAL, as far as I can tell. It does not seem to be documented anywhere what this is supposed to do.
It is currently not possible to build CFE with this configuration set to TRUE due to this problem.
Calling this a minor defect for now, as it only appears when using this configuration option.
The text was updated successfully, but these errors were encountered: