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 RTEMS network stack needs to be explicitly initialized in a platform-specific manner. However, the barebone/minimal BSP that runs the unit tests does not do this initialization. Therefore when running the network tests, it just gives an immediate error:
Describe the solution you'd like
Not clear at this point. The network init is quite board specific (refers to a specific nic driver) so probably doesn't fit as part of the OSAL BSP. Suggest just documenting this limitation.
Additional context
As the network tests only use the loopback address (127.0.0.1) it might be possible to bring up the RTEMS network stack with only this interface and no "real" nic. That might be a possibility to get these tests to run without making the BSP too complicated.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The RTEMS network stack needs to be explicitly initialized in a platform-specific manner. However, the barebone/minimal BSP that runs the unit tests does not do this initialization. Therefore when running the network tests, it just gives an immediate error:
Describe the solution you'd like
Not clear at this point. The network init is quite board specific (refers to a specific nic driver) so probably doesn't fit as part of the OSAL BSP. Suggest just documenting this limitation.
Additional context
As the network tests only use the loopback address (127.0.0.1) it might be possible to bring up the RTEMS network stack with only this interface and no "real" nic. That might be a possibility to get these tests to run without making the BSP too complicated.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: