You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The CFE PSP has historically duplicated some logic that was also in the OSAL BSP. In an effort to consolidate this and have only one basic BSP implementation, the CFE PSP should be an extension of the OSAL BSP rather than duplicating the logic.
Describe the solution you'd like
The first step to accomplish this is to have the CFE final link also include the osal_bsp library in the final link.
Additional context
Including osal_bsp should not affect existing builds as long as it is included after the PSP, so the linker will not pull in duplicate symbols. It should be effectively a no-op/ignored in the current build but enables a future transition to using the osal-provided BSP for startup.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered:
Withdrawing this -- my cross-platform testing showed it didn't work as originally planned. Replaced by #581 instead, which seems to work on all platforms so far.
Is your feature request related to a problem? Please describe.
The CFE PSP has historically duplicated some logic that was also in the OSAL BSP. In an effort to consolidate this and have only one basic BSP implementation, the CFE PSP should be an extension of the OSAL BSP rather than duplicating the logic.
Describe the solution you'd like
The first step to accomplish this is to have the CFE final link also include the
osal_bsp
library in the final link.Additional context
Including
osal_bsp
should not affect existing builds as long as it is included after the PSP, so the linker will not pull in duplicate symbols. It should be effectively a no-op/ignored in the current build but enables a future transition to using the osal-provided BSP for startup.Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: