Hello @DMeie.2,
The first advice I can give you is to start from one of our board and understand how the features are rendered by the MC Workbench. Understanding ST boards is the best way to understand how we translated the schematic into the board description.
The description of the ThreeShunt_AmplifiedCurrents is fully documented here:
STM32MotorControl:Motor Control Boards Description - stm32mcu
As stated in the doc, yes, you need to connect these pins to an ADC. Currently the board manger does not check that the pins are valid. A connection algorithm creates all the possible options for all the features that will be proposed by the workbench. In case of pin incompatibility between IPs and signals requirement, the connection algorithm will not be able to find the expected solution. The best advice I can give you is to use the same hardware IPs as the one we used.
> What about Alternate Function routing for design flexibility?
Look at how we addressed this point in our boards, or read our documentation 😉
What is the general approach for setting up a custom board in this regard?
Well, I think now you got the point. the best approach is to validate that the MCSDK can fulfill your needs with our development boards, (from hardware and algorithm point of view), and once validated describe your board targeting the same hardware IPs. Once your json is ready, import it in the WB, and check that you can select all your features, and generate the code. Once the project is ready, the last step is to compile it. All these tasks can be done (and should be done) before starting your board development.
But let me ask you one question: How do you develop your schematic of your custom inverter board ? Do you use ST schematic as a reference?
Regards
Cedric
