Skip to main content
H
Hitesh
Associate II
March 2, 2024
Question

STM32H573I-DK: Cannot connect to access port 1

  • March 2, 2024
  • 4 replies
  • 4689 views

Hello,

 

Iam working o STM32H573I-DK Board when am trying to access board am getting trustzone issue.
I tried with Debug Authentication also but am unable to access board.
Find the attached description.

Hitesh_0-1709356028039.png

 

4 replies

Chloe Meunier
Chloe Meunier
ST Employee
March 6, 2024

Hello Hitesh,

is it the first time you are using the board? Dis you perform any operation with it? Did you try to close the device before or other things?

 

You can try to connect in "hot plug" mode and try to change the port number access.

If you perform a debug authentication what is the message returned?

 

Thank you

Chloé

P
pagurudeen
Associate
March 22, 2024

I'm using STM32H563ZIT6 controller and facing the same issue as above while trying to connect from STM32CubeProgrammer.

Just Powered up the board and trying to connect in normal mode through programming pins (SWDIO, SWCLK), I have verified the connections and I'm able to connect in Hot_plug mode and able to flash the code.

Then I tried flashing through STM32CubeIDE (Version 1.14.1) and the results are as below,

 

Target not halted after reset. Force halt

-------------------------------------------------------------------

STM32CubeProgrammer v2.15.0

-------------------------------------------------------------------

 

 

 

Log output file: C:\Users\USR\AppData\Local\Temp\STM32CubeProgrammer_a07196.log

ST-LINK SN : D

ST-LINK FW : V2J42S7

Board : --

Voltage : 3.30V

Error: Cannot connect to access port 1!

If you are trying to connect to a device with TrustZone enabled please try to connect with HotPlug mode.

If you are trying to connect to H5 device and your target is already locked with password or certificate, please open your device using Debug Authentication.

 

Encountered Error when opening C:\ST\STM32CubeIDE_1.14.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.1.100.202311100844\tools\bin\STM32_Programmer_CLI.exe

Error in STM32CubeProgrammer

Shutting down...

Exit.

 

 

Do i need to change any configurations to connect in the Normal Mode?

    E
    eptkst211
    Visitor II
    February 5, 2025

    I ran into this exact issue/error in my system, in which I use an embedded STM32. On my PCB, I included a pull-down resistor and toggle switch to set BOOT0 low (GND) or high (3V3) in case I needed to set it low or high. I mistakenly set BOOT0 high without realizing, and I encountered this exact error when trying to flash. When I switched BOOT0 back to low, my program flashed and ran exactly as I expected.

      K
      KaiOestreich_Incoretex
      Graduate
      April 21, 2026

      Boot Pins should be all pulled low as in the UART/USB Setting.
      I had success after getting the same Error by using DFU via the OTG USB C Port at the Bottom of the Device.
      Make sure to also power the board.

      You would go to the "stm32mp1" folder of the example image and run this:
      cd /home/USER/Downloads/stm32mp1-openstlinux-6.6-yocto-scarthgap-mpu-v26.02.18/images/stm32mp1/
      [USER@HOST stm32mp1]$ /home/USER/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin/STM32_Programmer_CLI -c port=usb1 -w flashlayout_st-image-weston/optee/FlashLayout_sdcard_stm32mp135f-dk-optee.tsv

      This is one way of doing it.

      Terms & ConditionsAccessibility statement