VelocityDRIVE-SP-2025.06 Release Notes

1. 2025.06

Version:            2025.06
Previous Version:   2025.03-1   (yyyy.mm-cnt)
Release date:       2025-07-08  (yyyy-mm-dd)
Type:               Roadmap release
YANG Catalog SHA:   5151bae07677b1501f9cf52637f2a38f

1.1. New Management Features

  1. HSR/PRP (IEC-62439-3): A new YANG and application module to add RedBox support has been added (details here).

  2. 802.1AS: Implement more YANG leaves to comply with AVNU and/or Automotive test suites.

    1. From ieee802-dot1as-ptp YANG, the use-mgt-log-gptp-cap-interval / mgt-log-gptp-cap-interval leaves are implemented.

    2. mchp-velocitysp-ptp has been extended with two new leaves ( oper-log-pdelay-req-interval and oper-log-sync-interval) to control the peer-delay and sync interval at stable state.

  3. DTLS settings in the CoAP server are now configured for MUP1 and IP individually (details here).

1.2. Board Configuration Features

  1. The EXTMOD sub-system has been extended to allow implementation of an external PHY driver. The basic driver model is described in this section. To activate the EXTMOD driver for a given port, use the extmod bool in the bridge section as described in bridge section.

  2. The board-config YANG has been extended with an extmod driver which can be used to assign GPIOs to be controlled by the EXTMOD code. See this section for more details.

  3. The board-config YANG can be used to configure per-interface 1588/PTP time-stamping calibration profiles. This allows the board vendor to provide base calibration numbers to get better 1588/PTP results without requiring users to set the egress-latency and ingress-latency leaves from the ieee1588-ptp YANG.

    1. Be aware that Microchip EVBs are now pre-calibrated using this facility. The calibration process is still not 100% complete, and further tuning may occur in future releases. This also means that users who have been setting egress-latency / ingress-latency manually will have to clear these numbers and re-do the calibration. The section can be referenced for instructions on how to do this calibration.

1.3. New images

This release introduces a new image variant where DTLS is enabled by default (also on MUP1). All images are offered in a variant with and without DTLS enabled by default. See LAN969x Firmware File Types and LAN966x Firmware File Types for more details.

1.4. Non-backwards compatible change

  1. All releases until (including 2025.03-1) have been using LittleFS internally to store the start-up config and data related to provisioning.

    1. In this release, LittleFS has been replaced with a simpler solution. The motivation for making this change is to optimize the footprint and due to MISRA compliance issues with LittleFS.

    2. Due to this, all saved configuration will be lost when updating from 2025.03(-1) to 2025.06.