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
NOTE: Not a fork since github limits users to a single fork and I have a fork open for the pending issue: #606 and so I just mirrored the repo and am referencing the new repo from this issue report; but it means it does not appear at: https://github.com/renode/renode-issue-reproduction-template/forks
Expected behaviour
The test starts two CPUs (one STM32F207, one STM32H723) to provide either end of a simple, hardwired IPv4 address, client-server echo test over Ethernet. This was done to provide both F2 and H7 EMAC models in a single issue. The server application listens for two connections on TCP port 7, echoing the data received. The client application connects to the server twice, sending data and verifying the result.
The main branch of the mirror will hang with neither the client nor the server cores processing Ethernet packets, such that the test.robot will timeout after 20-seconds of inactivity.
The fixed branch of the mirror provides the models needed to successfully complete the test.
Additional Information
As mentioned in the README.md for the mirror the models have been tested using IPv6 as well as IPv4, but this test just exercises IPv4 in a simple internal renode switch setup.
Do you plan to address this issue and file a PR?
Yes, at a point when the maintainers are happy with the fixes as provided in the fixed branch in the mirror.
The text was updated successfully, but these errors were encountered:
Description
The current renode STM32F2 and STM32H7 models do not implement complete EMAC functionality.
See issue template mirror:
https://github.com/RallySmith/renode-issue-stm32-emac
NOTE: Not a fork since github limits users to a single fork and I have a fork open for the pending issue:
#606 and so I just mirrored the repo and am referencing the new repo from this issue report; but it means it does not appear at: https://github.com/renode/renode-issue-reproduction-template/forks
Expected behaviour
The test starts two CPUs (one STM32F207, one STM32H723) to provide either end of a simple, hardwired IPv4 address, client-server echo test over Ethernet. This was done to provide both F2 and H7 EMAC models in a single issue. The server application listens for two connections on TCP port 7, echoing the data received. The client application connects to the server twice, sending data and verifying the result.
The
main
branch of the mirror will hang with neither the client nor the server cores processing Ethernet packets, such that the test.robot will timeout after 20-seconds of inactivity.The
fixed
branch of the mirror provides the models needed to successfully complete the test.Additional Information
As mentioned in the README.md for the mirror the models have been tested using IPv6 as well as IPv4, but this test just exercises IPv4 in a simple internal renode switch setup.
Do you plan to address this issue and file a PR?
Yes, at a point when the maintainers are happy with the fixes as provided in the
fixed
branch in the mirror.The text was updated successfully, but these errors were encountered: