-
Couldn't load subscription status.
- Fork 13
Description
Hello,
I am working on generating pinctrl.dtsi files for each STM32 family to integrate HAL/LL into the Zephyr OS ecosystem.
I observed that the STM32U385RGTxQ.xml file (https://github.com/STMicroelectronics/STM32_open_pin_data/blob/master/mcu/STM32U385RGTxQ.xml) contains only one pin definition for sai1_fs_a. However, the Nucleo U385RG Q datasheet (https://www.st.com/resource/en/datasheet/stm32u385cg.pdf, page 85) shows additional signals available on AF13 linked to PB9 and PE4.
Similarly, the STM32U375CETx.xml file shows the same behavior (see https://www.st.com/resource/en/datasheet/stm32u375ce.pdf, page 83).
On the other hand, PE4 is correctly linked with the SAI1_FS_A signal in the STM32U385VGIx.xml and STM32U375VGIx.xml files.
I have also noticed the same issue with the SAI1_FS_B signal. For some XML files, the PE9 pin is not associated with the signal, unlike what is shown in the datasheets for U375 and U385, where it is available with AF13.