-
Notifications
You must be signed in to change notification settings - Fork 207
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
Clean up EVS ports implementation #93
Labels
Milestone
Comments
Imported from trac issue 62. Created by jphickey on 2015-06-04T12:13:01, last modified: 2019-04-03T17:41:37 |
Trac comment by jhageman on 2019-04-03 17:41:37: CCB 4/3/19: See also #94, coordinate solution with implementation of a PSP SendMessageToPort. |
skliper
changed the title
Clean up EVS_SendViaPorts() function
Clean up EVS ports implementation
Apr 27, 2021
skliper
added a commit
to skliper/cFE
that referenced
this issue
Apr 17, 2023
2 tasks
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Fix a few minor issues with EVS ports implementation:
Although a macro is used when checking bits of the "OutputPort" mask, the value is still effectively hard coded with the shift, so the macro cannot change without also breaking these checks (violates the spirit of using the macro to begin with). A simplification of the conditional will allow them to change independently (just mask and non-zero):
cFE/modules/evs/fsw/src/cfe_evs_task.c
Lines 831 to 847 in 73c338d
cFE/modules/evs/fsw/src/cfe_evs_task.c
Lines 885 to 901 in 73c338d
cFE/modules/evs/fsw/src/cfe_evs_utils.c
Lines 469 to 502 in 73c338d
When sending to multiple ports, the (essentially) same snprintf() is done for each one and only one digit in the string changes. Would be way more efficient to construct the later half of the string once, and change the port number.
The first issue should be resolved prior to integration with EDS as those macros become part of the EDS. Therefore they should be changeable without breaking the implementation that uses them. The second issue is just a performance/size enhancement.
The text was updated successfully, but these errors were encountered: