2023-04-25 07:22 AM - edited 2023-11-20 07:09 AM
Hello, I noticed that using the X-CUBE-TOF Package with the STM32WL55JC Nucleo-Board has an issue with the I2C-Peripheral(I2C-2).
This genrates the I2C code in the IDE.
And the Sensor can be derived.
while if I define the Sensor bus IO:
The Generated code is without the I2C
And the Sensor is not discovered.
Is that normal? should I define something to make the I2C code get generated or this is a bug in the CUBEMX-Package for ToF?
Thank you
Amir
Solved! Go to Solution.
2024-01-11 08:08 AM
Hello again @AElgh
After a deep check, we find out that when you define I2C2 or any other I2C to be used in the X-Cube-TOF, the I2C code will be generated inside the stm32wlxx_nucleo_bus.c file . And if not, the I2C code get generated in the main.c file.
Best Regards.
STTwo-32
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.
2023-04-26 01:20 AM
Hello @AElgh and welcome to ST Community.
I reproduced your problem and I had the same issue .
I will report the problem internally to the appropriate team to be treated .
thanks again for your question.
Issam
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.
2024-01-11 08:08 AM
Hello again @AElgh
After a deep check, we find out that when you define I2C2 or any other I2C to be used in the X-Cube-TOF, the I2C code will be generated inside the stm32wlxx_nucleo_bus.c file . And if not, the I2C code get generated in the main.c file.
Best Regards.
STTwo-32
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.