Release 2.9 1.6

[Junior Martinez (jmartinez-silabs)]

Problem / Feature

What is being fixed? What is the feature being added? Examples:

• Fix crash on startup
• Fixes #12345 Frobnozzle is leaky (exactly like that, so GitHub will auto-close the issue).

Change overview

What's in this PR

Testing

How was this tested?

• If unit tests were added, how do they cover this issue?
• If unit tests existed, how were they fixed/modified to prevent this in future?
• If new unit tests are not added, why not?
• If integration tests were added, how do they verify this change?
• If new integration tests are not added, why not?
• If manually tested, what platforms controller and device platforms were manually tested, and how?
• If no testing is required, why not?

[cursor]

PR Summary

High Risk
Changes manufacturing-date handling, attestation CSR subject limits, and Series 3 credentials flash layout—errors can break factory provisioning or device attestation for new builds.

Overview
Adds provisioning release 2.9 aligned with release_2.9-1.6, including new per-chip *_mfd generator firmware entries in devices.yaml and a 2.9 row in versions.yaml documenting YYYYMMDD manufacturing dates and a Series 3 credentials base address change to avoid manufacturing-token collisions.

Firmware/storage API updates support that behavior: ProvisionStorage tightens kCommonNameMax to 64 (RFC 5280) and adds GetManufacturingDateSuffix alongside the existing date getters; AttestationKey documents a fixed kSubjectNameLengthMax buffer for CSR subjects that include Matter VID/PID OIDs. bluet.py now resolves modules.util via client/python on sys.path.

The PR also introduces bundled provision config (parameters.yaml, OpenSSL csa_openssl.cnf with Matter VID OID, silabs_creds.tmpl) used by the provisioning toolchain.

^{Reviewed by Cursor Bugbot for commit 4df04a1. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{Reviewed by Cursor Bugbot for commit 4df04a1. Configure here.}

[cursor]

Common name length mismatch

Medium Severity

kCommonNameMax is reduced to 64 on-device, but common_name in the added parameters config still has no max, so the host can accept names longer than storage and CSR subject limits allow.

Additional Locations (1)

• provision/config/parameters.yaml#L427-L432

 

^{Reviewed by Cursor Bugbot for commit 4df04a1. Configure here.}

[Junior Martinez (jmartinez-silabs)]

This was just a test. Only changes coming from 2.9 are coming from provision artifact. They should come from provision repo directly.