Hi, set stm32H750 tim, Error in 'deviceManage/Function-Call Subsystem/Timers': Initialization commands cannot be evaluated. TIMERS_Config function : Can not find which APB timer TIM1 is connected to.Default preference value STM32TIMAPB set to APB1 is

[lling.1]

Hi, set  stm32H750 tim, Error in 'deviceManage/Function-Call Subsystem/Timers': Initialization commands cannot be evaluated. TIMERS_Config function : Can not find which APB timer TIM1 is connected to.Default preference value STM32TIMAPB set to APB1 is used.

[Cyril FENARD]

Hi @Community memberngyuan​ ,

The root cause is understood; the 5.4.0 release was not ready for the H7 family.

Some corrections are made for the next delivery of STM32-MAT/TARGET V5.6.0 planned for the end of Q1 2020.

TIMER blocks have been improved to be able to be used with models using H743ZI2 on our side.

Regards

Cyril

[Cyril FENARD]

Hi @Community memberngyuan​ l,

The STM32-MAT/TARGET V5.6.0 was released in the last days of March 2020.

This release is paired with STM32CubeMx V5.6.0 and with MATLAB R2018b.

This is the consolidation of the previous version V5.4.0 with some enablers for the NUCLEO-H743ZI2.

Regards.

Cyril.

[DHofe.1]

Hi @Cyril FENARD​ 

I have the same issues with the new release installed. I'm not able to configure and use Timers in my Simulink environment.

Like you can see I'm getting an infinite loop of this error and I need to abort Matlab.

I hope you can help me with this issue.

Best regards,

Dominik

[Cyril FENARD]

Hi @DHofe.1​ ,

Have you tried the following example provided with version V5.6.0 of the STM32-MAT/TARGET tools:

STM32demos\Test\TIMER\H743ZI2\H743ZI2_Timer1.slx

It works straight out of the box.

Can you check your installations and your MATLAB session, in particular the path recorded in the tool?

>> version

ans =

  '9.5.0.1265761 (R2018b) Update 6'

>> cd STM32

>> getpref('STM32')

>> path

>> rmdir slprj s

Regards.

Cyril

[DHofe.1]

Hi @Cyril FENARD​ 

Thank you for your fast answer! Yeah I tried to load the example and it worked without a problem. What is really strange I think.

I executed the required commands and you can find the results in the attached log file.

Update: I tried to configure a second timer in the provided example and I got the same error like before. So I think there is just TIM1 which works properly.

Regards.

Dominik

[Cyril FENARD]

Hi @DHofe.1​  ,

It seems that interoperability with the ioc file for the H7 family and timers is not sufficient with this version of the STM32-MAT/TARGET tool.

Sorry for the problem.

Regards.

Cyril

[DHofe.1]

Ok, but in the release notes of the newest STM32 MAT/Target is written that the H7-Family is supported. Can you estimate when this will be fixed or at least can you tell me if you're working on this problem at the moment?

[lling.1]

Tim is out of trouble now, but the number of adc channels has a problem。

[DHofe.1]

Hi @Community memberngyuan​ 

Have you tried to use another timer than timer 1? Because this is the only one which works for me. The ADC I never tried before.

[DHofe.1]

Hi @Cyril FENARD​ 

I made some more tests and figured out that the problem occurs only if I use Timers which are connected to the APB1 bus. Do you have an idea why this could be a problem?

Best regards

[银侯.1]

Hi, I have the same problem. Although I use the latest version of STM32-MAT/TARGET-5.6.0, I can only use TIM1, 8, 15, 16, 17. Other timers have the same problem as you. How do you solve it?

[DHofe.1]

Hi

To be honest we decided to not use the STM32-MAT/TARGET anymore because it is to buggy and really slow in compiling. I implemented the software directly in the STM32CubeIDE and communicate directly over the USB port with Matlab using their serialport implementation.

Kind regards