-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add initial prototype Event Management files #1
base: main
Are you sure you want to change the base?
Conversation
warning: failed to compile/link with the app
/* | ||
* TODO: Fill in file header, if necessary. | ||
*/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does there need to be a file header for these files?
typedef struct | ||
{ | ||
uint32_t ReturnValue; | ||
} BPL_Status_t; | ||
|
||
#define BPL_STATUS_SUCCESS (0u) | ||
#define BPL_STATUS_ERROR_GENERAL (1u) | ||
#define BPL_STATUS_ERROR_INPUT_INVALID (2u) | ||
#define BPL_STATUS_ERROR_PROXY_INIT (3u) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume these should be moved to somewhere else (if we decide to keep the struct impl of the return types, as discussed).
BPL_EVM_ProxyCallbacks.Initialize_Impl = ProxyCallbacks.Initialize_Impl; | ||
BPL_EVM_ProxyCallbacks.SendEvent_Impl = ProxyCallbacks.SendEvent_Impl; | ||
|
||
/* TODO: immediately want to call the proxy init, or wait for a directive to do so? */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to address this TODO
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider removing the Initialize_Impl
function pointer entirely. Have the BPNode call CFE_EVS_Register (or any other initialization) directly.
now that things are working
using utassert_generate_stubs.pl
This reverts commit bd88db4.
Describe the contribution
This PR add prototype implementations for the BPLib's Event Management (EVM) design (part of the Core Infrastructure).
This design intends to abstract the cFS EVS API calls from the BP App, using a new EVM API the BPLib.
A related PR exists for BP app, here: keegan-moore/bp#1 .
Testing performed
make native.distclean
2.
make ENABLE_TESTS=false native.install
cd build-native-9.4.0/exe/cpu1
./core-cpu1
Expected behavior changes
A clear and concise description of how this contribution will change behavior and level of impact.
BPL_EVM_Initialize
instead ofCFE_EVS_Register
BPL_EVM_SendEvent
System(s) tested on
Additional context
N/A
Third party code
N/A
Contributor Info - All information REQUIRED for consideration of pull request
Keegan Moore, NASA/GSFC Code 582 (Flight Software Systems)