cancel
Showing results for 
Search instead for 
Did you mean: 

How to enable the STM32 H series microcontroller from accessing read and write through debugger and USB for unauthorized user

subhamdeyece61
Associate

To secure USB against unauthorized usage while maintaining regular operation, implement authentication and encryption for all USB communication, ensuring only authorized devices or users can access the interface for parameter and log management, open-source information, and updates.

1. how to enable and disable the stm32 for booting using a debug probe / stm32 flasher from unauthorized access

2. How to enable and disable the USB access from Unauthorized access

3. Even after locking also authorized user can read and write in the stm32

we can do it manually by setting the RDB for read access and WRP for write access but we want it to do it at runtime in software.

 

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Bubbles
ST Employee

Hi @subhamdeyece61,

those are basic things and the STM32H5 should have no problem fulfilling these requirements.

1) There's BOOT_LOCK and the unauthorized debug access can be prevented by provisioning the device with DA passcode and advancing the product state to closed.

2) If it's bootloader access, then it's by BOOT_LOCK, if user USB stack, then it's up to the application to implement necessary authentication.

3) Yes, there's a Debug Authentication (DA) functionality.

See for example here:

Security:Debug Authentication for STM32H5 - stm32mcu

BR,

J

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

View solution in original post

1 REPLY 1
Bubbles
ST Employee

Hi @subhamdeyece61,

those are basic things and the STM32H5 should have no problem fulfilling these requirements.

1) There's BOOT_LOCK and the unauthorized debug access can be prevented by provisioning the device with DA passcode and advancing the product state to closed.

2) If it's bootloader access, then it's by BOOT_LOCK, if user USB stack, then it's up to the application to implement necessary authentication.

3) Yes, there's a Debug Authentication (DA) functionality.

See for example here:

Security:Debug Authentication for STM32H5 - stm32mcu

BR,

J

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.