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.

Sign up for GitHub

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

Jump to bottom

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

Merged
merged 2 commits into from
Apr 26, 2024
Merged

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

merged 2 commits into from
Apr 26, 2024

Commits on Feb 22, 2024

  1. ports: Remove side effects from CC_ASSERT calls 

    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.
    Philip Vedin committed Feb 22, 2024
    Configuration menu
    Copy the full SHA
    2f0e146 View commit details
    Browse the repository at this point in the history

  2. pf_cmina: Fix ARP response after factory reset 

    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.
    Philip Vedin committed Feb 22, 2024
    Configuration menu
    Copy the full SHA
    e3fdf7e View commit details
    Browse the repository at this point in the history