Posted by michaelsander on 2015-09-03 19:27

Thanks for creating your step by step process! I followed it successfully and have a few comments.

1) For whatever reasons, a lot of the peripherals you listed were presented by STMCubeMX as unavailable, Some of the pins were red and I couldn’t select them. I thought, based on similar tools, that they would become available as I deselected other peripherals, like it was a pin-mux issue, but they stayed red.

In the end I didn’t need any of the peripherals that were red, so I left them out. That meant that the main.c file contained initialization for devices that I didn’t have code for, so I commented the undefined initialization code out.

2) STMCubeMX downloaded a package during the process, and put it in a default location. When I got to steps 12 and 14, I had to find where that was. For me it was,
C:\users\Michael\STM32Cube\Repository\STM32Cube_FW_F4_V1.5.0...

3) Between step 17, items ‘i’ and ‘j’, I had to manually add to the “Debug Configurations” dialog, “Main” tab, “C/C++ Application” field the location of the FreeRTOS.elf file. \SW4STM32\FreeRTOS\Debug\FreeRTOS.elf

4) I ran into a series of error messages once I clicked “Debug”.

The final ones were:

Error message from debugger back end:
localhost:3333: The system tried to join a drive to a directory on a joined drive.
localhost:3333: The system tried to join a drive to a directory on a joined drive.

After trying many things, I got it going by reinstalling the ST-Link Utility software. That gave me the correct windows drivers for OpenOCD to talk to the on-board ST-Link V2.