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

Fix ARP response after RCP factory reset, CC_ASSERT calls #576

Merged
merged 2 commits into from
Apr 26, 2024

Conversation

pvedin
Copy link

@pvedin pvedin commented Feb 22, 2024

No description provided.

Since p-net may be compiled without asserts
(e.g. release builds for STM32Cube), it could be
the case that expressions with side effects were
not evaluated; this would cause incorrect behaviour.

While the rt-kernel port does not use CC_ASSERT,
it has also been changed in the same manner for
consistency.
Automated RT-Tester: DCP_ResetToFactory (v2.44)
When performing a Reset Communication Parameter factory reset,
the IP suite is zeroed. However, this was only done to p-net's
non-volatile storage. Thus, p-net would respond to ARP requests destined
to the old IP address until the IP address is changed or after a reset.

This commit also resets the network interface.
@pyhys pyhys requested a review from hefloryd April 23, 2024 12:40
@pyhys pyhys merged commit 6930de2 into rtlabs-com:master Apr 26, 2024
pvedin pushed a commit to pvedin/p-net that referenced this pull request Apr 30, 2024
 rtlabs-com#576 added an additional call to pnal_set_ip_suite.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants