boards/calliope-mini: rework programmer config (openocd and pyocd)

[aabadie]

Contribution description

This PR is changing the programmer options for the calliope-mini board. After #11404 was opened, I checked and apparently this board provides a CMSIS-DAP programmer interface by default, which is compatible with openocd and pyocd.

For example, they use this openocd configuration in there sample projects.

I'm wondering why jlink adapter was selected as the default. There's no documentation about that.

Testing procedure

Try to flash a calliope-mini with PROGRAMMER=openocd or PROGRAMMER=pyocd, it should work.

Issues/PRs references

Noticed while looking at #11404

[miri64]

Works for openocd but not for pyocd (though I don't get en error returned):

$ BOARD=calliope-mini PROGRAMMER=pyocd make -C examples/hello-world/ --no-print-directory flash
Building application "hello-world" for "calliope-mini" with MCU "nrf51".

[…]
   text	   data	    bss	    dec	    hex	filename
   8000	    136	   2604	  10740	   29f4	/home/mlenders/Repositories/RIOT-OS/RIOT/examples/hello-world/bin/calliope-mini/hello-world.elf
/home/mlenders/Repositories/RIOT-OS/RIOT/dist/tools/pyocd/pyocd.sh flash /home/mlenders/Repositories/RIOT-OS/RIOT/examples/hello-world/bin/calliope-mini/hello-world.hex
### Flashing Target ###
0000194:WARNING:mbed_board:Board ID 12A0 is not recognized; you will be able to use pyOCD but not program flash.
0000261:INFO:rom_table:AP#0 ROM table #0 @ 0xf0000000 (designer=244 part=001)
0000268:INFO:rom_table:[0]<e00ff000:ROM class=1 designer=43b part=471>
0000268:INFO:rom_table:  AP#0 ROM table #1 @ 0xe00ff000 (designer=43b part=471)
0000275:INFO:rom_table:  [0]<e000e000:SCS-M0+ class=14 designer=43b part=008>
0000280:INFO:rom_table:  [1]<e0001000:DWT-M0+ class=14 designer=43b part=00a>
0000285:INFO:rom_table:  [2]<e0002000:BPU class=14 designer=43b part=00b>
0000291:INFO:rom_table:[1]<f0002000:??? class=9 designer=43b part=9a3 devtype=13 archid=0000 devid=0:0:0>
0000317:WARNING:loader:Failed to add data chunk: no memory region defined for address 0x00000000
0000317:INFO:loader:Erased 0 bytes (0 sectors), programmed 0 bytes (0 pages), skipped 0 bytes (0 pages) at 0.00 kB/s
Done flashing

[miri64]

So suggestion: remove pyocd config for now. Without it, this would be an insta-merge ;-)

[aabadie]

For the pyocd change, I'm sure this is possible. Maybe one needs to add an extra configuration in Makefile.include: can you try to add export FLASH_TARGET_TYPE ?= -t nrf51 before include $(RIOTMAKE)/tools/pyocd.inc.mk ?

[miri64]

For the pyocd change, I'm sure this is possible.

Me as well, I just don't think those configurations should be one commit TBH ;-). I'll try what you proposed anyway.

[aabadie]

No problem, I totally agree with the split in 2 commits :)

[miri64]

can you try to add export FLASH_TARGET_TYPE ?= -t nrf51 before include $(RIOTMAKE)/tools/pyocd.inc.mk ?

It works with that.

[aabadie]

Thanks for testing @miri64!

I split the PR in 2 commits and adapted the PyOCD part with the target type variable.

[miri64]

ACK. Both flashing with openocd and pyocd still works. Flashing with fscopy also still works.