Fix #111, do not assume a specific core name

[jphickey]

Describe the contribution
Improve the module ID lookup when getting the CFE core text segment info.

• Ideally get the ID directly from what was loaded by startCfeCore
• As a fallback use the actual CFE core name from the configdata

Do not use a hardcoded name.

Fixes #111

Testing performed
Build and run unit tests

Expected behavior changes
VxWorks PSP should use the real module name, not assume cfe-core.o when getting text segment info

System(s) tested on
Ubuntu 20.04

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

[skliper]

CCB: 2020-10-14: Approved (pending test). Requesting ticket to add a functional test (not implemented is OK on platforms that don't support it).

[astrogeco]

@jphickey and @skliper did you all open the related ticket? Can you let me know when this is ready to merge?

[skliper]

New issue opened at #208 to add a functional test. From the CCB I recall @jphickey mentioned this change still needed to be tested on the hardware. Not sure if that was completed yet.

[jphickey]

Yes - I was able to run this on the MCP750 and confirm that I'm getting a valid result from CFE_PSP_GetCFETextSegmentInfo() and subsequently CFE is calculating a checksum as expected.

@astrogeco this should be OK to merge.

[jphickey]

Note - the part I am not able to test is the one where GetCfeCoreModuleID is provided - because this requires rebuilding the kernel. That can be tested at a later date. In the meantime using the default filename seems to work fine as long as you don't rename the file from what CMake actually built.

[skliper]

Note - the part I am not able to test is the one where GetCfeCoreModuleID is provided - because this requires rebuilding the kernel. That can be tested at a later date. In the meantime using the default filename seems to work fine as long as you don't rename the file from what CMake actually built.

Copy, fine by me.