Skip to content
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

Fix #965, remove OSAL ID from App/LibInfo struct #1017

Merged
merged 1 commit into from
Dec 1, 2020

Conversation

jphickey
Copy link
Contributor

Describe the contribution
Removes the Module ID from the App/Lib info telemetry structures.

Fixes #965

Testing performed
Build and sanity test CFE
Run all unit tests

Expected behavior changes
App and Lib info telemetry structures no longer contain the "ModuleId" value from OSAL.

System(s) tested on
Ubuntu 20.04

Additional context
CFE code should be distinct about the types used in messages vs. the types used at runtime. They may need to be different depending on mission architecture (i.e. mixing 32 and 64 bits, different local platform-specific sizes of things, etc). All message definitions should be in the proper app-specific message typedef files and must have mission scope, not platform scope.

The "osal_id_t" type isn't defined in any of the CFE message/interface header files for use within telemetry, but this was included in the AppInfo and LibInfo telemetry structures.

This ID is an ephemeral runtime value and is not relevant to a ground system or anything outside CFE, so it makes most sense to simply remove this ID from the telemetry structure. Note that all commands are name-based, not ID-based, hence why this ID is not really useful.

The alternative would be to use CFE_ES_ResourceID_t type instead. This is the same underlying value but defined in ES rather than OSAL, in the typedefs file with all other message types.

Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.

@jphickey jphickey added the CCB:Ready Ready for discussion at the Configuration Control Board (CCB) label Nov 16, 2020
The "osal_id_t" type isn't defined in any of the CFE message/interface
header files for use within telemetry.

This ID is an ephemeral runtime value and is not relevant to a ground
system or anything outside CFE, so it makes most sense to simply
remove this ID from the telemtry structure.  Note that all commands
are name-based, not ID-based, hence why this ID is not really useful.
@astrogeco
Copy link
Contributor

CCB 2020-11-18 APPROVED

  • Missing an update from @jphickey local repo

@jphickey
Copy link
Contributor Author

Commit 720525e is the corrected version (it actually just changes a little bit less than the original with the hope of reducing merge conflicts)

@astrogeco astrogeco added IC-20201124 and removed CCB:Ready Ready for discussion at the Configuration Control Board (CCB) labels Dec 1, 2020
@astrogeco astrogeco changed the base branch from main to integration-candidate December 1, 2020 17:25
@astrogeco
Copy link
Contributor

@jphickey can you clear the conflicts here?

@jphickey jphickey merged commit c4950a6 into nasa:integration-candidate Dec 1, 2020
@jphickey
Copy link
Contributor Author

jphickey commented Dec 1, 2020

@astrogeco - conflict resolved in the IC branch.

@jphickey jphickey deleted the fix-965-osal-ids-tlm branch December 3, 2020 17:53
@skliper skliper added this to the 7.0.0 milestone Sep 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Avoid OSAL IDs in messages/data files
3 participants