Changes

Overview

• The minimum e2 Studio version for FSP v6.5.0 is e2 Studio 2026-04.2
• The previous version of e2 Studio used with FSP v6.3.0 and FSP v6.4.0 was e2 Studio 2025-12
• e2 Studio 2025-12 has known issues with the pin configuration tooling that is accessed within the project configuration view, which is the - "Pins" tab of an open solution or project configuration
• e2 Studio 2026-04 provides fixes for most pin configuration tooling issues that are present in the previous version
• This guide serves to document remaining known issues and to provide workarounds for different affected project types

Affected Project Types

Generally, any project chain which contains three or more projects will see issues with the pin configuration tooling.

• A solution counts towards the project chain length. For example, a (Solution + Project) would count as a project chain of length two.
• Pin configuration actions like assignments, unassignments, and configuration changes that are meant to appear downstream in the project chain beyond the project in which they are made, may fail to propagate correctly.

FSP Solution Templates which create affected project chains include the following.

• Single Core, TrustZone (Solution + Secure Project + Nonsecure project)
• Multicore, Flat (Solution + CPU0 Project + CPU1 Project)
• Multicore, TrustZone (Solution + CPU0 Secure Project + CPU1 Secure Project + CPU0 Nonsecure Project + CPU1 Nonsecure Project)

The currently available choices of Bare Metal, FreeRTOS, or ThreadX for a template do not matter since those categories only affect the inclusion of additional packs or configuration and do not affect project chain length.

Known Issues

1. Unassignment of pin mode followed by reassignment of pin mode in the solution pin configuration which includes a simultaneous change in a generic setting, results in that generic setting becoming partly unoverridable and unable to show override tooltips in any downstream projects.

Workarounds for Affected Project Types

Note

"project chain" refers to the combination of the solution (if present) and all projects. "project" only refers to a project and not a solution.

Consult the below legend to understand the pin configuration UI elements referred to in the workarounds.

e2 Studio Pin Configuration UI

Workaround For Known Issue 1

When assigning a pin mode in the solution which was previously unassigned, do not change any additional settings of the pin.

1. Assign the pin with its desired mode, then save and rebuild the solution.
2. Change any additional settings of the pin after this step.
3. As a final, optional step, the generated ra_gen/pin_data.c of each project may be verified for correct pin configurations.