FS32K116LAT0MLFT Secure debug

[mumumilmil]

I am trying to set password if I have debug SW. using fs32k116lat0mlft, cyclone fx.

In Cyclone image creation, Renesas’si RH850 has check box that sets to password 16bit, but Arm fs32k116lat0mlft hasn’t setting password. Is it possible to set password when I try to debug?

Our device has SWD to debug.

[davidtosenovjan]

There is no censorship support on S32K1 device.

There is option to use "Backdoor Comparison Key" mechanism but it is not natively supported by debugger. You can see example here:

https://community.nxp.com/t5/S32K-Knowledge-Base/Example-S32K144-Verify-Backdoor-Access-Key-S32DS1-3...

[betty54summers]

While some microcontrollers like the Renesas RH850 have a dedicated setting for a debug password during image creation, the NXP S32K116 does not have this feature in the same manner. The security features for the S32K116, including the ability to disable debug access, are typically controlled through specific Flash Configuration Field (FCF) settings. These settings are part of the application code or the initialization process and are written to non-volatile memory. To secure the device and prevent unauthorized debugging via SWD, you would need to configure these FCF registers within your software, often at the project setup or a bootloader stage. This is a deliberate, code-based action rather than a simple checkbox option in the Cyclone FX programmer's interface MyCardStatement

[betty54summers]

I am trying to set password if I have debug SW. using fs32k116lat0mlft, cyclone fx.

In Cyclone image creation, Renesas’si RH850 has check box that sets to password 16bit, but Arm fs32k116lat0mlft hasn’t setting password. Is it possible to set password when I try to debug?

Our device has SWD to debug.

While some microcontrollers like the Renesas RH850 have a dedicated setting for a debug password during image creation, the NXP S32K116 does not have this feature in the same manner. The security features for the S32K116, including the ability to disable debug access, are typically controlled through specific Flash Configuration Field (FCF) settings. These settings are part of the application code or the initialization process and are written to non-volatile memory. To secure the device and prevent unauthorized debugging via SWD, you would need to configure these FCF registers within your software, often at the project setup or a bootloader stage. This is a deliberate, code-based action rather than a simple checkbox option in the Cyclone FX programmer's interface MyCardStatement