Skip to content
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

Tests that use network stack do not run on RTEMS #705

Open
jphickey opened this issue Dec 22, 2020 · 2 comments
Open

Tests that use network stack do not run on RTEMS #705

jphickey opened this issue Dec 22, 2020 · 2 comments

Comments

@jphickey
Copy link
Contributor

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:

[BEGIN] 01 TestDatagramNetworkApi
rtems-net: network sema obtain: network not initialised

fatal error, exiting

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.

@skliper
Copy link
Contributor

skliper commented Dec 28, 2020

I like the suggestion of just bringing up the loopback interface for the OSAL BSP.

@jphickey
Copy link
Contributor Author

I like the suggestion of just bringing up the loopback interface for the OSAL BSP.

Yes, this would be a good solution if it can work. But we need to:

  1. determine if its possible at all (i.e. does RTEMS have a null device/loopback only mode for its IP stack)
  2. figure out how to make it work/coexist/not interfere in cases where a real BSP is used that has a real NIC.

jphickey pushed a commit to jphickey/osal that referenced this issue Aug 10, 2022
jphickey pushed a commit to jphickey/osal that referenced this issue Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants