Infineon PSOC Control C3 Debug Port Authentication and Provisioning

From SEGGER Knowledge Base
Jump to navigation Jump to search

The Infineon PSoC Control C3 series supports secure debug by using AP access authentication with a signed debug token. In addition, the device is provisioned (keys, debug policy, boot configuration and lifecycle assets) by running a signed provisioning DLM (Downloadable Module) in device SRAM. SEGGER implements both flows with Device Provisioner. For more information about Device Provisioner, refer to the Device Provisioner article.

PSoC Control C3 AP access authentication and device provisioning are implemented in the PCode_DevPro_Infineon_PSC3.pex script file.

Important notes

AP access authentication

  1. After successful AP access authentication, the enabled debug access is temporary and remains available only until the device is reset or power-cycled.
  2. A debug token cannot enable an access port that was permanently disabled by the device debug policy.
  3. The SYS-AP must remain available. If SYS-AP access is disabled by provisioning policy, the debugger cannot upload the token or communicate with the BootROM wait-for-application (WFA) flow.
  4. The debug token must match the device provisioning state and must be signed by the key expected by the BootROM.
  5. The debug token file is a binary file.

Device and token requirements

The PSoC Control C3 debug authentication mechanism is handled by the device BootROM.

A valid debug token must be generated as part of the Infineon provisioning flow. In practice, the token is generated by the Infineon provisioning tools (ModusToolbox-Edge-Protect-Security-Suite), during the provisioning of the device with a debug-enabled policy. The token is generated based on the device's unique identifiers and the provisioning state, and it is signed with a key expected by the BootROM.

  • Reference (Infineon):
    • 002-38998 - PSoC Control C3 MCU Programming Specification, Chapter 5.4 "Unlock the access to the CPU" and Appendix E.12/E.13.
    • AN240106 - Getting started with PSoC Control C3 security, debug token sections.
    • AN241344 - PSoC Control provisioning specification, DLM/wait-for-application (WFA) flow sections.
    • AN243376 - PSoC Control C3 (P/M) 6 MCU provisioning specification.
    • Edge Protect Tools documentation (tools/edgeprotecttools/docs/README_PSOCC3*.md in the ModusToolbox-Edge-Protect-Security-Suite).

Usage with other SEGGER tools

During the connection procedure of some tools or during debugging, a reset may be executed. This can cause the device to require authentication again.

To avoid an unintended reset after authentication, use one of the following options where applicable:

  • J-Flash: Delete the Reset init step under Options -> Project settings -> Init. steps.
  • Generic solution (all SEGGER tools): Include a J-Link Script file that overrides the ResetTarget() function. See ResetTarget() for details.
  • Ozone: In addition to overriding ResetTarget() in the J-Link script file, the TargetReset() function in the Ozone project file should be adjusted so the debugger attaches without relocking the target.

Device provisioning

  1. Provisioning permanently writes device assets (SFLASH, eFuse). Depending on the policy, some changes cannot be undone, e.g. setting prov_oem_complete to true, transitioning to the SECURE/PRODUCTION lifecycle stage, or setting an access port or debug pins to "Permanently Disable". Verify the policy before provisioning.
  2. The SYS-AP must be available. Provisioning is performed via the SYS-AP and the BootROM wait-for-application (WFA) flow.
  3. The provisioning DLM file must be a binary file. Intel HEX files are not supported and must be converted (see Creating the provisioning DLM).
  4. The provisioning DLM must be created for the exact device family (psoc_c3, psoc_c3x6 or psoc_c3x8). The RAM application inside the DLM is signed by Infineon for a specific family.
  5. The provisioning RAM application only runs in the lifecycle stage(s) it was built for (typically NORMAL_PROVISIONED). In any other lifecycle stage, the BootROM or the RAM application rejects the DLM.
  6. The device is reset at the end of a successful provisioning. If the new policy disables JTAG (debug_pins), only SWD can be used afterwards.

Locking/provisioning the device

Debug access is restricted through the PSoC Control C3 provisioning flow by programming the device debug policy and lifecycle-related assets. The provisioning data (policy, keys, certificates) is packed by Infineon's Edge Protect Tools into a DLM package, which consists of an Infineon-signed RAM application and the input parameters generated from the provisioning policy. The DLM package can be downloaded to the device and executed with the ProvisionDevice operation of the SEGGER script (see Device provisioning). During provisioning, the policy can configure APs as open, temporarily disabled and reopenable with a valid debug token, or permanently disabled. For secure-debug use, keep SYS-AP available and configure the required CPU APs for authenticated debug instead of permanent disable.

Provisioning flow

The ProvisionDevice operation performs the following steps:

  1. Read the lifecycle stage (LCS) from the device.
  2. Acquire the device in BootROM wait-for-application (WFA) mode.
  3. Download the DLM package to SRAM (0x34003000) via the SYS-AP.
  4. Start the BootROM validation of the DLM package. The BootROM then launches the RAM application.
  5. Wait for the RAM application to finish (timeout: 20 s) and evaluate the status reported in BOOT_DLM_STATUS. The provisioning succeeded if the status is 0xF2A00001.
  6. Reset the device and read back the lifecycle stage.

Device names

The Device parameter uses the Infineon Edge Protect Tools target names (see edgeprotecttools device-list):

Device family Device parameter
PSoC Control C3 (P/M)5 psoc_c3
PSoC Control C3 (P/M)6 psoc_c3x6
PSoC Control C3 (P/M)7, C3 (P/M)8 psoc_c3x8

Usage

DevPro -operation [operation_name] -if SWD -speed 1000 [-SetConfigVal parameter_name=value] -ScriptFile PCode_DevPro_Infineon_PSC3.pex
Operation Parameters Values Description
DebugAccessPortAuth DebugCertFile Filename Path to the debug_token.bin which is used to unlock the CM33 access port.
Device psoc_c3, psoc_c3x6, psoc_c3x8 Device family of which the access port should be opened. See Device names.
DebugCertKeyType OEM_ROT, PROT_FW Selects the key type used to sign the debug token. OEM_ROT is used for a token signed with the OEM root-of-trust key. PROT_FW is used for a token signed with the protected-firmware root-of-trust key.
ProvisionDevice ProvDlmFile Filename Path to the provisioning DLM package in binary format (e.g. prov_dlm.bin).
Device psoc_c3, psoc_c3x6, psoc_c3x8 Device family of the device to be provisioned. See Device names.

Examples

AP access authentication

Command

DevPro.exe -operation DebugAccessPortAuth -SetConfigVal DebugCertFile="debug_token.bin" -SetConfigVal DebugCertKeyType=OEM_ROT -SetConfigVal Device=psoc_c3 -ScriptFile "PCode_DevPro_Infineon_PSC3.pex" -if SWD -speed 1000

Output

Command line: -operation DebugAccessPortAuth -SetConfigVal DebugCertFile=debug_token.bin -SetConfigVal DebugCertKeyType=OEM_ROT -SetConfigVal Device=psoc_c3 -ScriptFile PCode_DevPro_Infineon_PSC3.pex -if SWD -speed 1000
Firmware: J-Link V12 compiled Mar 26 2026 10:14:53
S/N: 602004466

J-Link log: AP access authentication succeeded.

Device provisioning

Command

DevPro.exe -operation ProvisionDevice -SetConfigVal ProvDlmFile="prov_dlm.bin" -SetConfigVal Device=psoc_c3 -ScriptFile "PCode_DevPro_Infineon_PSC3.pex" -if SWD -speed 1000

Output

Command line: -operation ProvisionDevice -SetConfigVal ProvDlmFile=prov_dlm.bin -SetConfigVal Device=psoc_c3 -ScriptFile PCode_DevPro_Infineon_PSC3.pex -if SWD -speed 1000
Firmware: J-Link V12 compiled Mar 26 2026 10:14:53
S/N: 602004466

J-Link log: Life cycle state (BOOTROW[15:0]): 0x0000C0E9
J-Link log:   LCS: NORMAL_PROVISIONED
J-Link log: Target acquired in WFA mode, BootROM waits for DLM package
J-Link log: DLM package uploaded, size [bytes]: 0x0000A280
J-Link log: Waiting for RAM application completion...
J-Link log: BOOT_DLM_STATUS: 0xF2A00010
J-Link log: BOOT_DLM_STATUS: 0xF2A00001
J-Link log: RAM application executed successfully
J-Link log: Life cycle state (BOOTROW[15:0]): 0x0000C0E9
J-Link log:   LCS: NORMAL_PROVISIONED
J-Link log: Provisioning succeeded