cancel
Showing results for 
Search instead for 
Did you mean: 

Can't connect to STM32H755 after changing boot option byte

mt7883
Associate

Hello,

after changing one of the BCM4/7 boot option bytes of my Nucleo STM32H755 board with STM32CubeProgrammer, I can't connect to the MCU any more. When trying to connect with STM32CubeProgrammer, I get

Error: Unable to read device id from ROM table

Error: ST-LINK error (DEV_CONNECT_ERR)

 

Is this related to the change in option bytes or did the board get damaged somehow?

Thanks and regards,

Martin

1 ACCEPTED SOLUTION

Accepted Solutions
TDK
Guru

Try connecting using access port 3 instead of access port 0.

If you feel a post has answered your question, please click "Accept as Solution".

View solution in original post

3 REPLIES 3
TDK
Guru

Try connecting using access port 3 instead of access port 0.

If you feel a post has answered your question, please click "Accept as Solution".
mt7883
Associate

Wow, this works, thanks a lot!

I just double checked: When I turn option BCM7 back on I can connect again on port 0. When I turn BCM7 off I can only connect on port 3.

Hello @mt7883 ,

Read this new article.

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.