The Read Data is always "0" in STM32H5 MCU

[fzh_ai_sidekick]

Dear Sir, 
I've been using CubeMonitor to monitor data for quite a while, and it really is a convenient tool.
I recently started developing a new system with new MCU, STM32H5.
However, when I use CubeMonitor to monitor the data, the data remains 0 all the time, as shown in the image.

I have checked the variable in the IDE, and the variables indeed have normal values.

I'm not sure if this is related to the STM32H5, because when I was using the STM32F3 before, everything was working fine.

 

I also used the NUCLEO-F303RE and NUCLEO-H563ZI to verify this issue.

I create a simple accurmated counting program, and on the F303, everything works fine.
But on the H563, the data always remains 0.

Does anyone know what might be causing this issue?

Best Regards,

 

 

 

I have noticed this post with same issue

https://community.st.com/t5/stm32cubemonitor-mcus/stmcubemonitor-doesn-t-work-with-stm32h503/m-p/704978#M1221

 

By changing the Access port to 1, it works correctly now.

 

Can I ask another question?

What's the meaning of this setting for access port?

 

[stephane.legargeant]

Hello @yang2 

STM32CubeMonitor use debug access port to retrieve the data inside the STM32.

Some devices have multiple debug access ports. It can be either because they have multiple cores or because some cores have multiple ports with different purposes (i.e. secure debug).

If the wrong access port is used, the variable is usually returned as 0.

The settings in the "variables node" indicates which access port must be used. In case of multicore chip, you may have two "variables nodes" with different A.P., to be able to read variables on both core with a single ST-Link connection.  

On the older single core STM32, the Access Port used was usually the port 0. But on more recent architecture, the port 1 is used more often. 

So when it is not working on port 0, it is good to try with port 1.

 

In case of H563, here is an extract of the Reference Manual :

59.4 Access ports

There are two access ports (AP) attached to the DP.
• System debug access port (AP0): Enables access to the DBGMCU and the system
ROM table via an APB bus.
• Cortex®-M33 debug access port (AP1): Enables access to the debug and trace
features integrated in the Cortex®-M33 processor core via its internal AHB bus.

We need to access the variables through AHB bus, so for H563 , the access port AP1 must be used.

 

Best regards

 

Hi, Stephane, 

I totally understand via your reply.

This is a good explanation. I am very grateful