MX 4.7.1 code generation bug

hbarta · ‎2015-05-10

Posted on May 10, 2015 at 14:29

Hi folks,

I used MX to generate code for a project based on the STM32F429I-DISCO board pretty much for the default I/O configuration. (IIRC I made no changes)

MX_FMC_Init() was declared but not defined.

Project Settings -> Project:

Toolchain: SW4STM32

Project Settings -> Code Generation:

- Add Necessary Library Files

- Keep user code ... and delete previously ... both checked

.ioc file attached.

Thanks!

hank

Rob.Riggs · ‎2015-05-12

Posted on May 12, 2015 at 14:56

What operating system are you using?

chrif · ‎2015-05-14

Posted on May 14, 2015 at 17:39

Hi,

I used MX to generate code for a project based on the STM32F429I-DISCO board with default configuration and toolchain SW4STM32, and MX_FMC_Init() was declared and defined.

Besides, I have loaded the .ioc in attachement, I generated code and MX_FMC_Init() is declared and defined. Also, It seems that sent project does not contain the default configuration.

hbarta2 · ‎2015-05-14

Posted on May 14, 2015 at 18:08

Linux

Rob.Riggs · ‎2015-05-17

Posted on May 18, 2015 at 04:41

That's a known issue. STM does not test its tools on case-sensitive file systems. As a work-around, mount up a VFAT or NTFS loopback filesystem and export the code there. It will be fine.

hbarta · ‎2015-05-20

Posted on May 20, 2015 at 13:12

Thanks for the tip, Rob. Is this necessary only for the project directory or does the repository that MX uses also need to be VFAT/NTFS?

thanks,

hank

Rob.Riggs · ‎2015-05-23

Posted on May 24, 2015 at 04:31

Just the project directory based on my experience to date.

stm32cube-t · ‎2015-12-01

Posted on December 01, 2015 at 12:44

Dear users,

this issue will be solved in STM32CubeMX 4.12.0 release.