Reprogramming the PineTime
- 1 Introduction
- 2 SWD Pinout
- 3 nrfjprog (for Segger JLink)
- 4 OpenOCD
- 5 Black Magic Probe
- 6 External links and additional tutorials
The PineTime Dev Kit comes with the back not glued down to allow it to be easily reprogrammed, however the kit does not include an hardware programmer/debugger.
Before you can use your debugger/programmer, you probably have to wire up your pinetime. Heavily recommended you read this first!
There is a bewildering variety of different hardware programmers available but whatever programmer you have there are only a few tasks you will have to learn about:
- Unlocking the device Note: PineTime watches shipped after 20 Sep 2020 do not require unlocking. They are shipped unlocked.
- Uploading new software
- Running a debugger
All of these are described in this article.
Unlocking the device is a one-time action that is needed to enable to debug port and provide full access to the device. Unlocking the device will erase all existing software from the internal flash.
nrfjprog (for Segger JLink)
The following steps have been tested with the Segger JLink embedded in the NRF52-DK development board.
Connect the Pinetime SWD pins to the debugger (P20 on NRF52-DK)
|VCC (3.3V)||VTG (target detect)|
Unlocking the FLASH
Unlocking the device and erase the memory.
You need to execute this step only once, to remove the read protection on the memory. Note that it will erase the whole flash memory of the MCU! :
nrfjprog -f NRF52 --recover
Uploading new software
1. Program the BLE softdevice (if needed by the firmware). Replace PATH_TO_NRF_SDK by the path where you unzipped the NRF52 SDK :
nrfjprog -f NRF52 --program /PATH_TO_NRF_SDK/components/softdevice/s132/hex/s132_nrf52_6.1.1_softdevice.hex --sectorerase
2. Program the firmware (replace firmware.hex by the actual filename of the firmware):
nrfjprog -f NRF52 --program firmware.hex --sectorerase
3. Reset and run the new firmware:
nrfjprog -f NRF52 --reset
OpenOCD, the Open On-Chip Debugger supports multiple different adapters. You can read more about it here: http://openocd.org/
These examples allow you to use telnet to issue futher commands to the devkit. Using them you can connect to 127.0.0.1 (localhost) port 4444 using telnet and invoke OpenOCD commands. GDB should also be available on port 3333.
You can simplify your life by creating a configuration file that contains the interface, transport, target and speed configuration. Things like CLion also need one to work properly.
If you aren't using the latest version of OpenOCD, you might need to substitute things in these examples with older syntax (e.g. instead of adapter speed it's adapter_khz).
Issue this command to initialize a connection to the devkit:
openocd \ -c 'source [find interface/cmsis-dap.cfg]' \ -c 'transport select swd' \ -c 'source [find target/nrf52.cfg]' \ -c 'adapter speed 8000' \ -c 'init'
openocd \ -c 'source [find interface/jlink.cfg]' \ -c 'transport select swd' \ -c 'source [find target/nrf52.cfg]' \ -c 'adapter speed 8000' \ -c 'init'
openocd \ -c 'source [find interface/bcm2835spi.cfg]' \ -c 'bcm2835spi_speed 31200' \ -c 'source [find target/nrf52.cfg]' \ -c 'init'
Connect PineTime SWD Pins to ST-Link v2 as follows:
Note that only the bottom row of pins on ST-Link are used.
To flash PineTime with ST-Link on Linux and macOS, use PineTime Updater
Unlocking the device
If you need to disable access port protection then you can do this using the following commands below.
This can be done in two ways:
Appending this to OpenOCD command line:
-c 'nrf52.dap apreg 1 0x04' -c 'nrf52.dap apreg 1 0x04 0x01' -c 'nrf52.dap apreg 1 0x04'
Or by using the telnet connection, just type in telnet localhost 4444 and then you can issue commands to OpenOCD:
Note: Unlocking the device to remove access port protection will erase the contents of flash.
telnet localhost 4444 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Open On-Chip Debugger > nrf52.dap apreg 1 0x04 0x00000000 > nrf52.dap apreg 1 0x04 0x01 > nrf52.dap apreg 1 0x04 0x00000001
(If the nrf52.dap command cannot be found, try just dap instead.)
Uploading new software
Just issue this command, replace code.hex with your own (and cmsis-dap.cfg with an appropriate adapter).
openocd \ -c 'source [find interface/cmsis-dap.cfg]' \ -c 'transport select swd' \ -c 'source [find target/nrf52.cfg]' \ -c 'init' \ -c 'nrf5 mass_erase' \ -c 'program code.hex verify' \ -c 'reset' \ -c 'exit'
Black Magic Probe
BlackMagic Probe is an JTAG/SWD adapter with open-source firmware, allowing for it to be ported to a multitude of different boards. One of it's defining features is lack of need for intermediate software such as OpenOCD - one would just need to connect to the GDB server running on the chip and proceed with debugging. For more information, refer to wiki.
The native adapters are the official Black Magic family of debug adapters, including the original Black Magic Probe and the Black Magic Probe Mini. By buying the official hardware you are supporting the continued development of the Black Magic Probe software.
Providing your native adapter is running up-to-date firmware then it can be used to program your PineTime.
STM32 (Blue Pill)
It is possible to flash a popular development board based on STM32F103C8T6 microcontroller, known as Blue Pill, to make a BlackMagic Probe device. For example, one may follow instructions in forum post or gist (mac os). Also, it is possible to use SWD pins on the board to flash other devices, instead using arbitrary pins on the board itself. See this link for more detals.
The Black Magic Probe firmware can be run on a variety of host devices. See BMP Debugger Hardware for more information.
Using the BMP to flash the PineTime
Refer to the BMP wiki for the full description of commands. Overall, the process on Linux is like following. (/dev/ttyBmpGdb is a symlink created by the udev rule). It's useful to create a gdb script file (or .gdbinit) with following commands:
target extended-remote /dev/ttyBmpGdb monitor swdp_scan attach 1 file %firmware file%
Then one may use load command to flash the firmware, compare-sections to verify the upload, or monitor erase_mass to erase the firmware.
Then, proceed with debugging as normal.