Motor Control Workbench and STM32CubeIDE doesn´t work !

I don't represent ST so I can't address your first question, but ST acquired Atollic and they are trying to cosolidate their tools into the CubeIDE going forward, but they are in transition phase so things are in flux. Just remember that you aren't paying for any of this, so you can't complain too much 8-)

stm32f3xx_hal_exti.h is part of STM32Cube Firmware Library. By default these files are installed in %USERNAME%/STM32Cube/Repository/ STM32Cube_FW_F*_V*, where the asterick is for the version of the firmware being used, for example, the latest is for STM32F3xyz is STM32Cube_FW_F3_V1.11.0. When you ran Workshop, it asked you whave version of the Firmware that you would be using and the project that it generated should have copied the files from the Repository to your project under the Drivers folder. I just ran a test case with SW4 and in the project folders is "Drivers/STM32Gxx_HAL_Driver/Inc" which includes the *.exti.h file in question. If the file isn't there for some reason, just put it there manually from the Firmware Repository files.

So you should check that you have the correct version of the firmware installed for your target processor AND

that the Workshop generated project has a path/link defined to this specific include folder. It should show up under "Drivers" in the Project Explorer. You can right click "properties" of the resource in the Project Explorer and it will show you the path to that resource.

Note: When you run code generator from Workshop, after it is complete if you click on the text on the screen it will open a log file with all of the test that provides a detailed description of what it was doing. Much of this is Java template generation, but the end of it includes the folder paths for the source and header files. This can be useful for debugging if you have to get into the details.

ok,

i tried to choose other boards.

But a question: what means ST by Nucleo F401RE DAC is Emulated ?

And if i try to build the generated SC with SW4 and Nucleo L476RG i get only pointer warnings, how can i fix it ?

I don't know what is meant by "DAC is Emulated". I'd have to see the context. On some boards they used a PWM-output through a low pass filter to simulate an analog output.

You're having a bunch of compiler errors that you shouldn't be having. All I can suggest is to switch to another account or another computer and start again as it seems your installation is corrupted Or dump the Motor Control Workshop (MCW) altogether and start with one of the existing setups like SPN7 or SPN8, (search ST.com for these). You originally stated that you wanted to use Nucleo F303RE & IHM08M1. That's just the X-NUCLEO-IHM08M1 kit and you can use SPN8 code for that. Then you would not have to hassle with MCW code generation. You'd have to import that code into your IDE. I would suggest Atollic V9.2 as I've had better success with that than with CubeIDE (and the compile times are quicker).

I'm using the P-NUCLEO-IHM001 kit (F302R8 + IHM07M1) and the SPN7 for 6-step motor control as a starting point and I've been able to get that working using the Atollic V9.2 IDE. I was using MCW and I was able to compile some of that code, but the MCW generates code primarily for FOC and I'm more interested in 6-step motor control, so I stopped using it. The MCW is still a good place to look at the parameters for various things, driver boards and motors.

Myself I would not advise our Community peers to rely on Atollic material. According STM communication such is going to be deprecated. Still in sync. with STM comments quite surprising to get better compile runtime if Atollic vs. CubeIDE because claiming they have done full Atollic material porting to CubeIDE. Sounds to me both are GCC based so ?

Yes, both are GCC based. I understand that Atollic is not recommended for new design, as that's right on their download page. And I mentioned, above, that ST's long term goal was to migrate to CubeIDE, but the are not quite there yet. I would prefer to be using CubeIDE, but the suggestion to use Atollic was based on recent experience and what worked for me. I tried CubeIDE for ten days, had issues getting it to work, switched to Atollic and was off and running. I didn't document the compile times, but that was my first impression, that Atollic was compiling the same application from scratch faster that CubeIDE. So I'm just relaying my recent experience. Do your own comparison. I'd rather be working on my application than on getting the tool to work.

The question has been set only to the "STM32 Motor Control" topic (the question is only about the STM32 MC SDK). 

Best regards