Hello,
The MSP 3.x Device Compliance Matrix has been officially retired and will no longer be distributed due to a change in how new MCD devices are certified as MSP compliant.
Why the change?
As MCD product managers now have the responsibility for ensuring that their firmware releases are MSP compliant, MCD will be the source of the information on whether a newer MCD device or release is MSP compliant.
For new MCD devices, the assumption made is that a single standard process should apply to all devices that claim to be MSP compliant and that there are no known issues or limitations of MSP support for such devices unless it is documented into the collateral for that device.
As noted in the TAVT announcement, MCD product managers will more than likely denote whether their devices are MSP compliant in their associated collateral. IMPORTANT: The MCD Device Product Manager will be the ultimate authority on whether the latest MCD hardware is MSP 3.x compliant (e.g. MC75, MC55 etc).
As there are 'older' MCD products that have been deployed, the BU understands the need for a central document where the field can ascertain the current MSP support for those units (legacy units, units that fall outside of MCD etc).
This support will be reflected in the MSP 3.x Release Notes.
This is how you should interpret the devices denoted in the Release Notes, in addition to the special restrictions that need to be considered in order to support those devices.
Questions? Please don't hesitate to pose them here or to me directly.
Regards,
Daphanie
2 Replies
Thanks Daphanie, what about ADC devices (i.e. the MK's)? Will they be treated the same way? Are they clear on this process as well?
Chris, the MKs are listed in the section at the back of the MSP Release Notes. For the MK500 and newer MK devices, you should still check with the device Product Manager for compliance status.