Skip to main content
dieter 123
dieter 123
Associate III
May 10, 2017
Solved

libraries in cubemx not consistent

  • May 10, 2017
  • 2 replies
  • 1063 views
Posted on May 10, 2017 at 10:44

Hi

the TSC library built in cubeMX repositories is not consitent.

Where do I find the evry latest release?

in STM32Cube_FW_L4_V1.7.0/  this version is used: V2.2.0 / 01-February-2016

in STM32Cube_FW_L0_V1.9.0/ this version is used: V2.0.0 / 22-April-2014

see release notes under

STM32Cube/Repository/********Middlewares/ST/STM32_TouchSensing_Library/Release_Notes.html

#tsc #stm32-cubemx
This topic has been closed for replies.
Best answer by Amel NASRI
Posted on May 10, 2017 at 16:18

Yes, currently this is the one embedded in other packages.

2 replies

Amel NASRI
Amel NASRI
Technical Moderator
May 10, 2017
Posted on May 10, 2017 at 13:29

Hi

dieter.dieter

‌,

I agree with you that we have to align versions of libraries embedded in our STM32Cube packages.

Your remark is valid and is reported internally asking to use the same version ofSTM32_TouchSensing_Library in CubeL0 as other packages (L4/F3/F0).

-Amel

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.
dieter 123
dieter 123Author
Associate III
May 10, 2017
Posted on May 10, 2017 at 16:15

Thanks

st.mcu

and what is the latest version? this one?::::: V2.2.0 / 01-February-2016

Amel NASRI
Amel NASRIAnswer
Technical Moderator
May 10, 2017
Posted on May 10, 2017 at 16:18

Yes, currently this is the one embedded in other packages.

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.
Amel NASRI
Amel NASRI
Technical Moderator
December 14, 2018

Hello,

The last version of Touch library (V2.2.0 / 01-February-2016) is embedded in STM32CubeL0 V1.11.0.

-Amel

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.
Terms & ConditionsAccessibility statement