Add Blackmagic (BMP) support for Generic F103

[evark]

A small addition to boards/platform files to support Blackmagic probe as uploading method for Generic F103 devices.

[fpistm]

Thansk for this PR.
I assume you have tested with bmp_upload provided with Arduino_Tools?
Could you test with the compiler path and update your PR. I do not have BMP to do the test.
Thanks in advance

[fpistm]

I think you should use
tools.bmp_upload.path={compiler.path}

which is set on top of platform.txt
compiler.path={runtime.tools.arm-none-eabi-gcc-6-2017-q2-update.path}/bin/
This will avoid any issue if compiler version change

[sabas1080]

I can try in a few days with my BMP

[RickKimball]

It looks like you are using the original version of the BMP command line I wrote a long time ago. I've since simplified the parameters so that it isn't doing a lot of extra work. You might look at doing something like this:

# blackmagic probe upload
...
tools.bmp_upload.upload.pattern="{path}{cmd}" -cd={build.path} -ex "file {build.project_name}.elf" -nh -b {upload.speed} {upload.verbose} -ex "target extended-remote {serial.port}" -ex "monitor swdp_scan" -ex "attach 1" -ex "stop" -ex "mon erase_mass" -ex "load"

I started a post a while back http://www.stm32duino.com/viewtopic.php?f=37&t=2802 but I don't think it went anywhere.

Seeing as you are adding something new to this core, you might think about how to select the debug BMP port a different way so you can still use the serial console without having to switch the port between the debug port and the virtual com port. I had some ideas in that post thread.

[evark]

I tried the path
tools.bmp_upload.path={compiler.path}

but it seems that this is not evaluated correctly (why?), so I have to define the compiler path again

tools.bmp_upload.path={runtime.tools.arm-none-eabi-gcc-6-2017-q2-update.path}/bin/

The command line of gdb can be simplified, according blackmagic wiki and looking how the gdb is used in platformio as

tools.bmp_upload.upload.pattern="{path}{cmd}" -nx --batch -ex "set confirm off" -ex "target extended-remote {serial.port}" -ex "monitor swdp_scan" -ex "attach 1" -ex "load" -ex "compare-sections" -ex "kill" "{build.path}/{build.project_name}.elf"

There is no need to full erase the chip on every download.

[fpistm]

Seeing as you are adding something new to this core, you might think about how to select the debug BMP port a different way so you can still use the serial console without having to switch the port between the debug port and the virtual com port. I had some ideas in that post thread.

@RickKimball , I see your point. The only way I see is to add script file to perform this but as I cannot perform any test it will be too risky and bring several support I guess

Edit:
One request has been submitted to add programmer serial port menu:
arduino/Arduino#5554

[fpistm]

There are some extra space btw:
{serial.port}" -ex "monitor swdp_scan
and
-ex "monitor swdp_scan" -ex "attach 1"

[fpistm]

upload speed is not used in the cmd? It should be fine to add it, no?
-b {upload.speed}

[RickKimball]

It is really a USB CDCACM so it doesn't really matter. It is going to go USB speed. But you can add it without issue

[fpistm]

I've tested under windows, it seems it could not expand properly {runtime.tools.arm-none-eabi-gcc-6-2017-q2-update.path} at upload step.... I need to investigate this. You use it under Linux?
Update:
only {runtime.tools.arm-none-eabi-gcc.path} is really expanded... but when Arduino Due is installed, this is the arm gdb 4.8.3 which is used. :(

[fpistm]

I've opened an issue at Arduino side:
arduino/Arduino#7616

[fpistm]

Based on @facchinm comment in arduino/Arduino#7616 (comment)
{runtime.tools.arm-none-eabi-gcc} will be used by default in git repo.
I will update path when releasing the package to set the gcc version as it is done for other upload tools.

[fpistm]

Thanks @evark
It is merged with small fix.