tim2 of stm32h753: 32-bit counter can only count up to 65,536.

[chenwei97]

[Tesla DeLorean]

Perhaps look at and show the code that's running on the part.

The generated code and the print output routines will be far more informative as to why it's not working as expected.

Definitely 32-bit, inspect registers with debugger. 

[chenwei97]

Ok, thank you. Here I'll ask my friend about the code that runs in this part.
In this case, it doesn't necessarily mean the sector has gone bad, does it

[Tesla DeLorean]

>>In this case, it doesn't necessarily mean the sector has gone bad, does it

I don't understand what you mean.

Show the generated code, the configuration screens aren't helping me understand the source of the problem.

Make sure you're not reading the TIM2->CNT value into a smaller variable and truncating.

[chenwei97]

void HAL_TIM_IC_CaptureCallback(TIM_HandleTypeDef *htim)
{
    if(htim->Instance==TIM2)
    {
      if(htim->Channel==HAL_TIM_ACTIVE_CHANNEL_1
      {
        up_value=HAL_TIM_ReadCapturedValue(htim,HAL_TIM_ACTIVE_CHANNEL_1);          
        up_counter=__HAL_TIM_GET_COUNTER(htim);

This is the latest test for capturing peripherals, with no captured values at all

[chenwei97]

In the test of capturing peripherals, both upvalue and downvalue should have been captured, but the corresponding values were not obtained at all, they were both 0. That is to say, there is no corresponding hardware for capturing

[chenwei97]

On a microcontroller with a frequency of 480M, when running this code, the interrupt can only run up to 70K

[AScha.3]

Clock-tree setting shows: cpu running at 64 MHz. Why this ?

>On a microcontroller with a frequency of 480M, when running this code, the interrupt can only run up to 70K

Seems you run the 480M cpu at 64M . right ?

[Tesla DeLorean]

Show the variable definitions 

[MM..1]

super screens and code parts, but stil dont show if your up_value and other is realy

volatile uint32_t up_value...