-
Notifications
You must be signed in to change notification settings - Fork 25
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
Use fixed size types for addresses and address offsets in tables/tlm/cmd #26
Labels
Comments
See also nasa/cFE#2093 |
skliper
changed the title
Use cfe_es_memaddress and cfe_es_offset types for tables and telemetry
Use cfe_es_memaddress and cfe_es_offset types for tables/tlm/cmd
Jun 6, 2022
3 tasks
skliper
changed the title
Use cfe_es_memaddress and cfe_es_offset types for tables/tlm/cmd
Use fixed size types for addresses and address offsets in tables/tlm/cmd
Jun 6, 2022
skliper
pushed a commit
to skliper/CS
that referenced
this issue
Sep 9, 2022
Fix nasa#24, Resolve strict cppcheck style warnings
thnkslprpt
added a commit
to thnkslprpt/CS
that referenced
this issue
Jun 11, 2023
…/tlm/cmd structs
2 tasks
thnkslprpt
added a commit
to thnkslprpt/CS
that referenced
this issue
Mar 23, 2024
…/tlm/cmd structs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist (Please check before submitting)
Is your feature request related to a problem? Please describe.
Changing telemetry and table sizes depending on platform (32 vs 64 bit) when using the cpuaddr type in structures.
Describe the solution you'd like
Use cfe_es_memaddress and cfe_es_offset types for tables and telemetry and define those types as 64 bits. If space is an issue, users can redefine these types as 32-bit.
From CCB:2022-04-27
EDIT:
CFE_ES_MemAddress_t
andCFE_ES_MemOffset_t
are the actual types that should be usedDescribe alternatives you've considered
Leave as is, redefine telemetry sizes based on platform in the "ground system"
Additional context
None
Requester Info
Gerardo E. Cruz-Ortiz, NASA
The text was updated successfully, but these errors were encountered: