PineTime SD MCUBoot - Revision history

Abcde: added category

2020-10-17T20:43:42Z

added category

← Older revision		Revision as of 20:43, 17 October 2020
Line 66:		Line 66:

	To be used to install SoftDevice from mcuboot it would need linker scripts for mcuboot (to ensure the reloader sits high enough in flash to avoid a self-overwrite). To install mcuboot we need an Intel HEX file of the mcuboot payload and InfiniTime (we have to write it in one shot to keep BLE updates working after switching bootloaders). This may need custom linker scripts depending on how big the Infinitime binaries are.		To be used to install SoftDevice from mcuboot it would need linker scripts for mcuboot (to ensure the reloader sits high enough in flash to avoid a self-overwrite). To install mcuboot we need an Intel HEX file of the mcuboot payload and InfiniTime (we have to write it in one shot to keep BLE updates working after switching bootloaders). This may need custom linker scripts depending on how big the Infinitime binaries are.

			[[Category:PineTime]]

Avamander: /* Dual Bootloader Modes */

2020-08-13T22:43:42Z

Dual Bootloader Modes

← Older revision		Revision as of 22:43, 13 August 2020
Line 11:		Line 11:

	=== Dual Bootloader Modes ===		=== Dual Bootloader Modes ===

			==== Process ====

	- PineTime will support 2 Bootloader Modes: [https://github.com/JuulLabs-OSS/mcuboot/wiki MCUBoot] and SoftDevice. Default is MCUBoot Mode.		- PineTime will support 2 Bootloader Modes: [https://github.com/JuulLabs-OSS/mcuboot/wiki MCUBoot] and SoftDevice. Default is MCUBoot Mode.

Danielt: /* External resources about custom MBR */

2020-08-11T08:15:50Z

External resources about custom MBR

← Older revision		Revision as of 08:15, 11 August 2020
Line 54:		Line 54:

	* https://devzone.nordicsemi.com/f/nordic-q-a/27599/boot-sequence-for-nrf52832		* https://devzone.nordicsemi.com/f/nordic-q-a/27599/boot-sequence-for-nrf52832
			* https://aykevl.nl/2018/01/mbr-softdevice-internals
	* https://forum.pine64.org/showthread.php?tid=9779&pid=65203#pid65203		* https://forum.pine64.org/showthread.php?tid=9779&pid=65203#pid65203

Danielt at 08:14, 11 August 2020

2020-08-11T08:14:41Z

← Older revision		Revision as of 08:14, 11 August 2020
Line 7:		Line 7:
	- But some firmware (wasp-os, ATCwatch) require Nordic SoftDevice to be installed to support the BLE and DFU functions		- But some firmware (wasp-os, ATCwatch) require Nordic SoftDevice to be installed to support the BLE and DFU functions

	- [[InfiniTime]] Firmware does not support flashing of SoftDevice as firmware update, because SoftDevice is usually flashed at address 0x1000, which is used by the MCUBoot Bootloader		- [[InfiniTime]] Firmware does not support flashing of SoftDevice as firmware update, because SoftDevice is usually flashed at address 0x1000 (plus a 4k MBR at 0 to switch between the bootloader and the softdevice), which is used by the MCUBoot Bootloader

	== How do we allow SoftDevice-based firmware to be flashed to PineTime via DFU? ==		== How do we allow SoftDevice-based firmware to be flashed to PineTime via DFU? ==

Danielt at 08:13, 11 August 2020

2020-08-11T08:13:49Z

← Older revision		Revision as of 08:13, 11 August 2020
Line 7:		Line 7:
	- But some firmware (wasp-os, ATCwatch) require Nordic SoftDevice to be installed to support the BLE and DFU functions		- But some firmware (wasp-os, ATCwatch) require Nordic SoftDevice to be installed to support the BLE and DFU functions

	- [[InfiniTime]] Firmware does not support flashing of SoftDevice as firmware update, because SoftDevice is usually flashed at address ~~0x0~~, which is used by the MCUBoot Bootloader		- [[InfiniTime]] Firmware does not support flashing of SoftDevice as firmware update, because SoftDevice is usually flashed at address 0x1000, which is used by the MCUBoot Bootloader

	== How do we allow SoftDevice-based firmware to be flashed to PineTime via DFU? ==		== How do we allow SoftDevice-based firmware to be flashed to PineTime via DFU? ==

Avamander: /* Custom MBR */

2020-08-10T18:46:35Z

Custom MBR

← Older revision		Revision as of 18:46, 10 August 2020
Line 41:		Line 41:

	It's possible to customise (SoftDevice's) MBR so that it can coexist with MCUBoot.		It's possible to customise (SoftDevice's) MBR so that it can coexist with MCUBoot.


	'''Pros:'''		'''Pros:'''
Line 50:		Line 49:

	* Technically more complex - documentation isn't the best, SoftDevice's future support for custom MBR might be unknown		* Technically more complex - documentation isn't the best, SoftDevice's future support for custom MBR might be unknown

			Should be explored further.

	==== External resources about custom MBR ====		==== External resources about custom MBR ====

Avamander: /* Custom MBR */

2020-08-10T18:46:00Z

Custom MBR

← Older revision		Revision as of 18:46, 10 August 2020
Line 40:		Line 40:
	=== Custom MBR ===		=== Custom MBR ===

	- It's possible to customise SoftDevice MBR so that it ~~coexists~~ with MCUBoot.		It's possible to customise (SoftDevice's) MBR so that it can coexist with MCUBoot.

	- ~~However~~ the ~~team feels this may be a technical risk as it~~'s ~~not very well-documented and may not~~ be ~~supported in future versions of SoftDevice~~
			'''Pros:'''

			* Seamless switching between the two different boot modes. Both MCUBoot and SD can be used.

			'''Cons:'''

			* Technically more complex - documentation isn't the best, SoftDevice's future support for custom MBR might be unknown

	==== External resources about custom MBR ====		==== External resources about custom MBR ====

Avamander: /* How do we allow SoftDevice-based firmware to be flashed to PineTime via DFU? */

2020-08-10T17:16:27Z

How do we allow SoftDevice-based firmware to be flashed to PineTime via DFU?

← Older revision		Revision as of 17:16, 10 August 2020
Line 13:		Line 13:
	=== Dual Bootloader Modes ===		=== Dual Bootloader Modes ===

	- PineTime will support 2 Bootloader Modes: [[https://github.com/JuulLabs-OSS/mcuboot/wiki\|MCUBoot]] and SoftDevice. Default is MCUBoot Mode.		- PineTime will support 2 Bootloader Modes: [https://github.com/JuulLabs-OSS/mcuboot/wiki MCUBoot] and SoftDevice. Default is MCUBoot Mode.

	- The two bootloaders will not coexist, they will be mutually exclusive. This allows a different flash ROM map for each bootloader.		- The two bootloaders will not coexist, they will be mutually exclusive. This allows a different flash ROM map for each bootloader.

Avamander: /* Dual Bootloader Modes */

2020-08-10T17:15:40Z

Dual Bootloader Modes

← Older revision		Revision as of 17:15, 10 August 2020
Line 13:		Line 13:
	=== Dual Bootloader Modes ===		=== Dual Bootloader Modes ===

	- PineTime will support 2 Bootloader Modes: MCUBoot and SoftDevice. Default is MCUBoot Mode.		- PineTime will support 2 Bootloader Modes: [[https://github.com/JuulLabs-OSS/mcuboot/wiki\|MCUBoot]] and SoftDevice. Default is MCUBoot Mode.

	- The two bootloaders will not coexist, they will be mutually exclusive. This allows a different flash ROM map for each bootloader.		- The two bootloaders will not coexist, they will be mutually exclusive. This allows a different flash ROM map for each bootloader.

Avamander at 17:14, 10 August 2020

2020-08-10T17:14:42Z

← Older revision		Revision as of 17:14, 10 August 2020
Line 1:		Line 1:
	== The Problem ==		== The Problem ==

	- PineTime ships with the MCUBoot bootloader which boots to the InfiniTime Firmware		- PineTime ships with the MCUBoot bootloader which boots to the [[InfiniTime]] Firmware

	- This assumes that the firmware (InfiniTime, Mynewt, Zephyr, ...) has its own Bluetooth LE (BLE) stack and can handle firmware updates (DFU)		- This assumes that the firmware ([[InfiniTime]], Mynewt, Zephyr, ...) has its own Bluetooth LE (BLE) stack and can handle firmware updates (DFU)

	- But some firmware (wasp-os, ATCwatch) require Nordic SoftDevice to be installed to support the BLE and DFU functions		- But some firmware (wasp-os, ATCwatch) require Nordic SoftDevice to be installed to support the BLE and DFU functions

	- InfiniTime Firmware does not support flashing of SoftDevice as firmware update, because SoftDevice is usually flashed at address 0x0, which is used by the MCUBoot Bootloader		- [[InfiniTime]] Firmware does not support flashing of SoftDevice as firmware update, because SoftDevice is usually flashed at address 0x0, which is used by the MCUBoot Bootloader

	== How do we allow SoftDevice-based firmware to be flashed to PineTime via DFU? ==		== How do we allow SoftDevice-based firmware to be flashed to PineTime via DFU? ==
Line 34:		Line 34:
	==== Switching modes with Companion App ====		==== Switching modes with Companion App ====

	- The PineTime Companion App (e.g. ~~GadgetBridge~~) will switch modes automatically depending on the firmware to be flashed. So PineTime Owners will never have to switch modes themselves.		- The PineTime Companion App (e.g. Gadgetbridge) will switch modes automatically depending on the firmware to be flashed. So PineTime Owners will never have to switch modes themselves.

	- For SoftDevice-based firmware, the Companion App will also know which SoftDevice version is needed by the firmware, and load the right SoftDevice version.		- For SoftDevice-based firmware, the Companion App will also know which SoftDevice version is needed by the firmware, and load the right SoftDevice version.