Difference between revisions of "Programming nRF51822 with STlink on Windows"
| Line 14: | Line 14: | ||
==References== | ==References== | ||
| − | + | * [http://andybrown.me.uk/2014/09/09/stlinkv2/ STLINK V2 One programmer for all STM devices] | |
| + | * [http://electronut.in/nrf51-adc-test/ nRF51822 Begins - nRF-DK, GCC, ADC, UART/BLE] | ||
| + | * [https://github.com/RIOT-OS/RIOT/wiki/Board:-yunjia-nrf51822 Board: yunjia nrf51822] | ||
[[File:k.png|600x600px]] | [[File:k.png|600x600px]] | ||
Revision as of 11:08, 30 September 2015
Sandeep (talk) and Vaibhav Katkar (talk) 17:43, 10 September 2015 (IST)
Getting STlink v1 working with openOCD is a pain. The USB driver implementation has flaws. The PC picks different drivers for the same device depending on its mood! Initially I got it working on my computer and to check I asked Vaibhav to try on his computer. He too wanted to use it to debug the LPC1114 MCU that he is working on for a last few weeks. It did not work, even after following the exact same steps. So we debugged and found out what the issue was.
Contents
Configuring Open OCD
Connecting STlink with nRF51822
Reassigning WinUSB for stlink
Using Open OCD
Open OCD as debugger
Open OCD as programmer/flasher
References
- STLINK V2 One programmer for all STM devices
- nRF51822 Begins - nRF-DK, GCC, ADC, UART/BLE
- Board: yunjia nrf51822
