Profiles for STEVAL-ETH001V1

[MWiel.1]

Hello,

I'm evaluating the STEVAL-ETH001V1 and wanted to create a project in MC Workbench for that board. Unfortunately this is not listed as an option and I also can't find a Workbench project or profile file or an STM32CubeIDE project.

Is there anything that can help me configure this board in MC Workbench

[GMA]

Hello,

You are right, this board is not available through the MC workbench. An associated STM32CubeIDE project is available here.

[MWiel.1]

Thanks for your reply but I already found that software package and until today it only contains the project files for the IAR embedded workbench. I couldn't even find a project file for the MC-SDK in there.

As we are also going to use motors that are also not listed, it would be a good starting point to have example projects.

[Rajeswari]

have you found out a solution to customize the board using MC-SDK

[Rajeswari]

In the firmware manual it says, " firmware developed using IAR workbench, and is compliant with STM32 cube framework" . I want to know how you did the firmware customization for your motor.

[MWiel.1]

I haven't.

Though I started to create a Cube IDE project manually by going throught the IAR project sources and what they configured, I aborted this route as it was too much at that point to figure out which headers and sources of MC-SDK I had to copy.

I also tried to clone the board description of boards that seemed close but that wouldn't work as well because Motorbench does not display any board that contains errors in the board description. Unfortunately those errors include the tag 26_crystal instead of 24_crystal or 8_crystal or even the MCU used on the STEVAL-ETH001V1.

Somewhere here in the forum I found that someone else had a similar issue and was linked to https://community.st.com/t5/stm32-mcus/mcu1-to-mcu2-migration-option-within-stm32cubeide/ta-p/49650 where the migration process for CubeMX projects is described. So the closest I came to configure motor parameters for this board was creating a workbench project with EVALSTDRIVE101 as power board and  a nucleo-F746 as control board and then migrating the CubeMX to the STM32F767. And I still had to check which pins were used and re-route themwithin CubeMX of CubeIDE.

We decided to switch to another controller though and also bought a matching power board by now.

[Rajeswari]

Thank you for your response. 

I was going to purchase the board without knowing this issue. Now we just found out another board for our purpose. Thank you for sharing these insights.

[GMA]

Hello,
Just to inform you that we are investigating your point, and we will come back to you soon.