pin conflict on MCSDK board designer

[Drache_Tek_On_ST]

picture tells all. the resolver says these two functions have conflicting IP settings but the settings themselves apparently not.

[Gael A]

Hello,

The Phase Voltage Sensing is always used in addition to the Current Sensing feature, it must observe a few rules :

• It must use the same number of ADC than Current Sensing (2 or 3, since this is an HSO only feature)
• It must use the same ADCs as Current Sensing too, but the order does not matter.
• Ex : Current Sensing: U->ADC1 ; V->ADC2 ; W->ADC3 and Phase Voltage: U->ADC3 ; V->ADC1 ; W->ADC2 is possible
• In case of 2-ADC, the used ADCs for Current Sensing and Phase Voltage must be complementary !
• Ex1 : Current Sensing: U->ADC1 ; V->ADC1 ; W->ADC2 and Phase Voltage: U->ADC1 ; V->ADC2 ; W->ADC2 is possible
• Ex2 : Current Sensing: U->ADC2 ; V->ADC1 ; W->ADC2 and Phase Voltage: U->ADC1 ; V->ADC2 ; W->ADC2 is NOT possible

[LJim]

I encountered the same issue.

Everything works fine when I generate the HSO project using MCSDK 6.4.0 with a custom inverter board,

but when I open the project with MCSDK 6.4.1 Board Designer, an error occurs.

MCU: STM32G431CBU6

Pin assignment in project generated by MCSDK 6.4.0: