Reprogramming the PineTime - Revision history

Fxc: fix

2023-03-16T03:02:26Z

fix

← Older revision		Revision as of 03:02, 16 March 2023
Line 3:		Line 3:
	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.		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 [[PineTime ~~devkit wiring~~\|wire up your pinetime]]. Heavily recommended you read this first!'''		'''Before you can use your debugger/programmer, you probably have to [[PineTime Devkit Wiring\|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:		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:
Line 17:		Line 17:
	== SWD Pinout ==		== SWD Pinout ==

	See [[PineTime ~~devkit wiring\|PineTime devkit wiring~~]]		See [[PineTime Devkit Wiring]]

	== nrfjprog (for Segger JLink) ==		== nrfjprog (for Segger JLink) ==

Fxc: Fixes

2023-03-16T00:54:31Z

Fixes

← Older revision		Revision as of 00:54, 16 March 2023
Line 1:		Line 1:
	= Introduction =		== Introduction ==

	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.		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.
Line 15:		Line 15:
	Unlocking the device is a one-time action that is needed to enable the debug port and provide full access to the device. Unlocking the device will erase all existing software from the internal flash.		Unlocking the device is a one-time action that is needed to enable the debug port and provide full access to the device. Unlocking the device will erase all existing software from the internal flash.

	= SWD Pinout =		== SWD Pinout ==

	See [[PineTime devkit wiring\|PineTime devkit wiring]]		See [[PineTime devkit wiring\|PineTime devkit wiring]]

	= nrfjprog (for Segger JLink) =		== nrfjprog (for Segger JLink) ==

	The following steps have been tested with the Segger JLink embedded in the [https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF52-DK NRF52-DK development board].		The following steps have been tested with the Segger JLink embedded in the [https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF52-DK NRF52-DK development board].
Line 66:		Line 66:
	nrfjprog -f NRF52 --reset		nrfjprog -f NRF52 --reset

	= OpenOCD =		== OpenOCD ==

	OpenOCD, the Open On-Chip Debugger supports multiple different adapters. You can read more about it here: http://openocd.org/		OpenOCD, the Open On-Chip Debugger supports multiple different adapters. You can read more about it here: http://openocd.org/

	== Adapters ==		=== Adapters ===

	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''.		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''.
Line 78:		Line 78:
	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'').		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'').

	=== CMSIS-DAP ===		==== CMSIS-DAP ====

	This is a generic specification that is supported by a bunch of different hardware, things such as DAPLink also use it.		This is a generic specification that is supported by a bunch of different hardware, things such as DAPLink also use it.
Line 91:		Line 91:
	-c 'init'		-c 'init'

	=== JLink ===		==== JLink ====

	Start OpenOCD:		Start OpenOCD:
Line 102:		Line 102:
	-c 'init'		-c 'init'

	=== Raspberry Pi ===		==== Raspberry Pi ====

	openocd \		openocd \
Line 110:		Line 110:
	-c 'init'		-c 'init'

	=== STLink ===		==== STLink ====

	Connect PineTime SWD Pins to ST-Link v2 as follows:		Connect PineTime SWD Pins to ST-Link v2 as follows:
Line 139:		Line 139:
	[[PineTime FAQ\|'''ST-Link can't be used to remove nRF52 flash protection''']]		[[PineTime FAQ\|'''ST-Link can't be used to remove nRF52 flash protection''']]

	== Unlocking the device ==		=== Unlocking the device ===

	If you need to disable access port protection then you can do this using the following commands below.		If you need to disable access port protection then you can do this using the following commands below.
Line 166:		Line 166:
	(If the ''nrf52.dap'' command cannot be found, try just ''dap'' instead.)		(If the ''nrf52.dap'' command cannot be found, try just ''dap'' instead.)

	== Uploading new software ==		=== Uploading new software ===

	Just issue this command, replace ''code.hex'' with your own (and cmsis-dap.cfg with an appropriate adapter).		Just issue this command, replace ''code.hex'' with your own (and cmsis-dap.cfg with an appropriate adapter).
Line 181:		Line 181:
	-c 'exit'		-c 'exit'

	= Black Magic Probe =		== 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 [https://github.com/blacksphere/blackmagic/wiki wiki].		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 [https://github.com/blacksphere/blackmagic/wiki wiki].
Line 213:		Line 213:
	Then, proceed with debugging as normal.		Then, proceed with debugging as normal.

			== External links and additional tutorials ==
	= External links and additional tutorials =

	* https://github.com/jlukanc1/pinetime-boot-flasher		* https://github.com/jlukanc1/pinetime-boot-flasher

Avamander: /* CMSIS-DAP */

2021-12-17T14:13:51Z

CMSIS-DAP

← Older revision		Revision as of 14:13, 17 December 2021
Line 79:		Line 79:

	=== CMSIS-DAP ===		=== CMSIS-DAP ===

			This is a generic specification that is supported by a bunch of different hardware, things such as DAPLink also use it.

	Issue this command to initialize a connection to the devkit:		Issue this command to initialize a connection to the devkit:

Avamander: /* Uploading new software */

2021-07-28T21:00:10Z

Uploading new software

← Older revision		Revision as of 21:00, 28 July 2021
Line 173:		Line 173:
	-c 'source [find target/nrf52.cfg]' \		-c 'source [find target/nrf52.cfg]' \
	-c 'init' \		-c 'init' \
			-c 'halt' \
	-c 'nrf5 mass_erase' \		-c 'nrf5 mass_erase' \
	-c 'program code.hex verify' \		-c 'program code.hex verify' \

Guenter: Typo

2021-04-10T15:38:05Z

Typo

← Older revision		Revision as of 15:38, 10 April 2021
Line 13:		Line 13:
	All of these are described in this article.		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.		Unlocking the device is a one-time action that is needed to enable the debug port and provide full access to the device. Unlocking the device will erase all existing software from the internal flash.

	= SWD Pinout =		= SWD Pinout =

Avamander: Minor copy from lupyuen/openocd-spi

2021-03-04T19:27:36Z

Minor copy from lupyuen/openocd-spi

← Older revision		Revision as of 19:27, 4 March 2021
Line 103:		Line 103:

	openocd \		openocd \
	-c 'source ~~[find interface/~~bcm2835spi~~.cfg]~~' \		-c 'source bcm2835spi' \
	-c 'bcm2835spi_speed 31200' \		-c 'bcm2835spi_speed 31200' \
	-c 'source [find target/nrf52.cfg]' \		-c 'source [find target/nrf52.cfg]' \

Fxc: link fix

2021-01-15T02:03:13Z

link fix

← Older revision		Revision as of 02:03, 15 January 2021
Line 135:		Line 135:
	To flash PineTime with ST-Link on Linux and macOS, use [https://github.com/lupyuen/pinetime-updater/blob/master/README.md PineTime Updater]		To flash PineTime with ST-Link on Linux and macOS, use [https://github.com/lupyuen/pinetime-updater/blob/master/README.md PineTime Updater]

	[[~~Frequently_asked_questions_about_the_PineTime~~\|'''ST-Link can't be used to remove nRF52 flash protection''']]		[[PineTime FAQ\|'''ST-Link can't be used to remove nRF52 flash protection''']]

	== Unlocking the device ==		== Unlocking the device ==

Avamander: /* Introduction */

2020-10-25T15:16:20Z

Introduction

← Older revision		Revision as of 15:16, 25 October 2020
Line 3:		Line 3:
	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.		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 [[PineTime devkit wiring\|wire up your pinetime]].'''		'''Before you can use your debugger/programmer, you probably have to [[PineTime devkit wiring\|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:		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:

	* ~~Unlock~~ the device ~~(if you have an older devkit)~~		* Unlocking the device '''Note: PineTime watches shipped after 20 Sep 2020 do not require unlocking. They are shipped unlocked.'''
	* ~~Upload~~ new software		* Uploading new software
	* ~~Run~~ a debugger		* 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.		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.

	~~'''Note: PineTime watches shipped after 20 Sep 2020 do not require unlocking. They are shipped unlocked.'''~~

	= SWD Pinout =		= SWD Pinout =

Avamander: /* Introduction */

2020-10-22T20:43:47Z

Introduction

← Older revision		Revision as of 20:43, 22 October 2020
Line 7:		Line 7:
	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:		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:

	* Unlock the device		* Unlock the device (if you have an older devkit)
	* Upload new software		* Upload new software
	* Run a debugger		* Run a debugger

Abcde: image fix

2020-10-18T23:05:40Z

image fix

← Older revision		Revision as of 23:05, 18 October 2020
Line 129:		Line 129:
	\|}		\|}

	[[File:~~pinetime_stlink~~.jpg\|400px]]		[[File:pinetime-stlink.jpg\|400px]]

	Note that only the bottom row of pins on ST-Link are used.		Note that only the bottom row of pins on ST-Link are used.