Using stm32 disco board for flashing a custom nrf52832 chip with keil

[MikeLemon]

Hello there,

I'm trying to flash my custom nrf52832 pcbs(untill I get my DKs in the tech tour with a reconfigured stm32 disco board's SWD port with keil uVision using the blinky blank example in SDK 14.0 (Already have S132 of those chips and I know the SWD port works sins I was able to flash some stuff to it with arduino but with the ST link V2 dongle which is not supported by keil(what a shame)).

now when I try to download the build example from keil I get this error message:

and here is what the PC sees when connecting ST link to the pc:

Thanks for helping.

[endnode]

Yes, SEGGER don't provide you full version of J-Link OB for free, it releases it for cheap boards like STM32 Dev Kits or nRF5x DK boards but implements internal check of the target and limits it only to the brand of Dev Kit. If you get nRF5x DK and upgrade to latest SEGGER J-Link OB firmware you will get the same error when trying to flash/debug targets from other vendors then Nordic. However this feature is fairly recent so if you find some >1 year old SEGGER J-Link OB firmware for your STM32 board it might work without this internal lock to ST Micro targets. Good luck.

[endnode]

(btw. this rises question how you were able to use Arduino IDE to flash something else on nRF5x target through this STM32 J-Link board... it might bypass some things but I believe that these lock downs are implemented in J-Link FW itself or it's combination of FW and J-Link DLL. Smells fishy that you have really succeeded with that set-up before...)

[MikeLemon]

actually I've used an st link V2 dongle for that along with an extention for arduino ide..

anyway if this doesn't work how do you suggest I flash my boards with the dongle or the stm32 disco? why can't nordic add support to it and make it so difficult to work of their products? I'm loosing faith in this company and this just increases my chances in moving my developments to another(maybe a bit more bulky because of the NFC) SOC BLE MCU...

[endnode]

I want to feel for you but honestly I believe that spending $100 for J-link EDU or $40 for any nRF5x DK must solve all your problems and you would suddenly praise how easy it is to work with Nordic products... and unfortunately I don't buy the argument that nothing from that is available in Israel (I can even package one here in EU and send it by post to you but as you will get yours from Nordic next week I guess it's not worth it...)

[endnode]

(also how would Nordic make JTAG/SWD firmwares for Dev Kits of other companies - like ST Micro which is kind of a competitor! - when they license external supplier - SEGGER - even for their own dev kits? Doesn't make sense to me at all...)

[endnode]

Also OpenOCD works with ST-Link with nRF51 target (I've used it long time ago) so if you really really insist on that set-up you should go that way... (but we have spent few months by various Q&S on this topic already and it doesn't look we agree on the view and solution)