The ST Nucleo-F412ZG is in the supported targets list but isn't actually supported for debug.

Having said that, it would be really nice if ST stepped up and added the necessary support in ST-Link.

Hi Philllip,

Have you upgraded the firmware yet?

https://os.mbed.com/teams/ST/wiki/ST-Link-Driver

Thanks, Desmond

I had the same issue with the u-blox C030-U201 board. The issue that I found is some of the information in the C:\Users\[username]\AppData\Local\Mbed Studio\api-targets.json file isn't correct. For example, the "device_name" for the "ublox_c030_u201" is set to null instead of "STM32F437VG". If you modify that file and restart Mbed Studio, it just get overwritten again because it pulls the latest info from https://os.mbed.com/api/v4/targets and that has the incorrect values as well. Here is what worked for me.

1. Close Mbed Studio
2. Modify the file C:\Users\[username]\AppData\Local\Mbed Studio\api-targets.json file so that it has the correct values for your platform. Most likely, the "device_name" needs to have the correct MCU part number. “[username]” is not a literal value, you need to replace it with your actual username. For example, my file is located at “C:\Users\kyleh\AppData\Local\Mbed Studio\api-targets.json”.
3. Disconnect from the internet.
4. Open Mbed Studio and wait for it to be fully up and running
5. Only after Mbed Studio has fully started can you reconnect to the internet. It looks like it only tries to update the api-targets.json file when it starts up and then doesn’t update it again while running, but I could be wrong.
6. If you have the board connected, you should be able to debug it without any issues.

Keep in mind that if you do this and then later start Mbed Studio while connected to the internet then you’ll need to do it over again.

Kyle