FreeRTOS running, SUCCESS!
I will address your input from what I have learned (which is not much)
1) After much experimentation with STM32CubMX and System Workbench, I am able to get most of the STM32F4-Discovery pins to go green. When I do this, the STM32CubeMX F4 code that is generated has the requisite support fo these peripherals in it, for intialization and use. I initally commented out a lot or simply deleted to get a working compile.
2) The STM32CubeMX may decide the default install location to be whatever it likes. In any event, one can find it by using the STM32CubeMX Help menu.
3) I suspect that System Workbench is still a work in progress and there are some anomalous happendings every now and then. Sometimes, it has created and filled in the correct information for Debug for me and other times I have to fill it in.
4) I had those same error messages yesterday and was struck by not being able to rid myself of them. I exited System Workbench and restarted, I tried other stuff and then, I unplugged and replugged the USB into my computer and it worked again. I am theorizing that the USB stuff in Windows go confused and that OpenOCD could not figure things out for itself.
Recently, I updated System Workbench, updated the F4 libraries to V1.8.0 and then rebuilt the code with FreeRTOS and VCP with success. And yes, I still had to do all the jumping through hoops to get it going.
If I had the money, I’d own a commercial package in a heartbeat.
;){kind=link}