Using Mbed, when I try to upload I get following output.
[env:nucleo_f401re]
platform = ststm32
board = nucleo_f401re
framework = mbed
upload_protocol = stlink
Bug report to https://github.com/platformio/platform-ststm32/issues please for @valeros.
See @Copperbot, he also recently posted about this
Hello @sstaub
This seems to be related to MBED 6.6 and stlink/jlink issue, can you please check this solution ?
After editing your MBED framework, you may need to keep “reset” button pushed on your Nucleo before uploading the new program to get stlink upload protocol working (or switch to upload_protocol = mbed once before working with stlink again).
It seems this is not a Mbed problem, I have the same issue when using the Arduino framework. On Mbed Studio I have no upload problem.
It is really annoying that PlatformIO becomes more and more a problem rather than a solution.
Well the question is whether OpenOCD returns a non-zero error code because it failed or if PlatformIO cannot interpret the output or return code directly.
Can you please do a “Verbose Build” and copy the OpenOCD invocation like. Then open a PIO CLI and copy-paste that line, but prefix it with the folder path of the openocd binary. E.g. the output might look something like
openocd -d2 -s C:\Users\Max.platformio\packages\tool-openocd/scripts -f interface/stlink.cfg -c “transport select hla_swd” -f target/stm32f1x.cfg -c “program {.pio\build\genericSTM32F103RC\firmware.elf} verify reset; shutdown;”
And then I would prefix that with
C:\Users\Max.platformio\packages\tool-openocd\bin\
so make it a valid command. For Mac users, the path should look something like /Users/<user>/.platformio/packages/tool-openocd/bin.
Then post that output.