2023-10-24 01:13 AM
[VERSION]: MCSDK 6.2.0,STM32CubeMX 6.9.2
[TOOL]: MotorControl Workbench 6.2.0
[DETAILS]: I want to add my custom control board,but it say "Unable to generate ioc file due to: The following has evaluated to null or missing".
My custom control board is STM32F405RGT6, but my attempt failed. Then I try STM32F401RDTx, it is same.
1.create mcu json (STM32F401RDTx), copy from STM32F401RETx.json.
I have to add an MCU that is not in the list, otherwise my custom control board will not be displayed correctly.
Then in this STM32F401RDTx.json file, I replace "STM32F401RETx" with "STM32F401RDTx" , and change the flash size to "flash" : 384. The two are just different in flash size, I think it works fine.
2.Create new board using Board Manager. Clone from NUCLEO-F401RE.
Then change the mcu name.
3.Create new project
STM32F401RD+IHM17M1
Then generate the project.
I want to know how to solve this problem.
Solved! Go to Solution.
2023-10-24 02:47 AM
Hello @gtop.1 ,
Thank you for your post.
Allowing the users to custom their boards is limited to the boards. The production of the mcu definitions from the user is not something we support. In the 6.2.0 release, we did a huge effort to support all the parts number of few series : STM32F0, STM32F3, STM32G0, STM32G4, STM32H5, STM32C0. Unfortunately, it is not the case yet for STM32F4. It is why the json definitions of STM32F4 are still limited to few MCUs.
In your case, as it is just a matter of flash size. I strongly advise you to stay with the supported MCU, it will not hurt the binary generation and download into the target.
Regards
Cedric
2023-10-24 02:47 AM
Hello @gtop.1 ,
Thank you for your post.
Allowing the users to custom their boards is limited to the boards. The production of the mcu definitions from the user is not something we support. In the 6.2.0 release, we did a huge effort to support all the parts number of few series : STM32F0, STM32F3, STM32G0, STM32G4, STM32H5, STM32C0. Unfortunately, it is not the case yet for STM32F4. It is why the json definitions of STM32F4 are still limited to few MCUs.
In your case, as it is just a matter of flash size. I strongly advise you to stay with the supported MCU, it will not hurt the binary generation and download into the target.
Regards
Cedric
2023-10-25 06:44 PM
I‘m so sad. Then I will use STM32F407 first.