Merge remote-tracking branch 'upstream/develop' into pts-settings
@ -0,0 +1,14 @@
|
|||||||
|
# How to flash InfiniTime using the SWD interface
|
||||||
|
Download the files **bootloader.bin**, **image-x.y.z.bin** and **pinetime-graphics-x.y.z.bin** from the release page:
|
||||||
|
|
||||||
|
![Image file](imageFile.png)
|
||||||
|
|
||||||
|
The bootloader reads a boot logo from the external SPI flash memory. The first step consists of flashing a tool in the MCU that will flash the boot logo into this SPI flash memory. This first step is optional but recommended (the bootloader will display garbage on screen for a few second if you don't do it).
|
||||||
|
Using your SWD tool, flash **pinetime-graphics-x.y.z.bin** at offset **0x0000**. Reset the MCU and wait for a few second, until the logo is completely drawn on the display.
|
||||||
|
|
||||||
|
Then, using your SWD tool, flash those file at specific offset:
|
||||||
|
|
||||||
|
- bootloader.bin : **0x0000**
|
||||||
|
- image-x.y.z.bin : **0x8000**
|
||||||
|
|
||||||
|
Reset and voilà, you're running InfiniTime on your PineTime!
|
Before Width: | Height: | Size: 187 KiB After Width: | Height: | Size: 187 KiB |
Before Width: | Height: | Size: 208 KiB After Width: | Height: | Size: 208 KiB |
Before Width: | Height: | Size: 176 KiB After Width: | Height: | Size: 176 KiB |
@ -0,0 +1,41 @@
|
|||||||
|
# Coding convention
|
||||||
|
|
||||||
|
## Language
|
||||||
|
|
||||||
|
The language of this project is **C++**, and all new code must be written in C++. (Modern) C++ provides a lot of useful tools and functionalities that are beneficial for embedded software development like `constexpr`, `template` and anything that provides zero-cost abstraction.
|
||||||
|
|
||||||
|
C code is accepted if it comes from another library like FreeRTOS, NimBLE, LVGL or the NRF-SDK.
|
||||||
|
|
||||||
|
## Coding style
|
||||||
|
|
||||||
|
The most important rule to follow is to try to keep the code as easy to read and maintain as possible.
|
||||||
|
|
||||||
|
Using an autoformatter is highly recommended, but make sure it's configured properly.
|
||||||
|
|
||||||
|
There are preconfigured autoformatter rules for:
|
||||||
|
|
||||||
|
* CLion (IntelliJ) in [.idea/codeStyles/Project.xml](/.idea/codeStyles/Project.xml)
|
||||||
|
* `clang-format`
|
||||||
|
|
||||||
|
Also use `clang-tidy` to check the code for other issues.
|
||||||
|
|
||||||
|
If there are no preconfigured rules for your IDE, you can use one of the existing ones to configure your IDE.
|
||||||
|
|
||||||
|
- **Indentation** : 2 spaces, no tabulation
|
||||||
|
- **Opening brace** at the end of the line
|
||||||
|
- **Naming** : Choose self-describing variable name
|
||||||
|
- **class** : PascalCase
|
||||||
|
- **namespace** : PascalCase
|
||||||
|
- **variable** : camelCase, **no** prefix/suffix ('_', 'm_',...) for class members
|
||||||
|
- **Include guard** : `#pragma once` (no `#ifdef __MODULE__ / #define __MODULE__ / #endif`)
|
||||||
|
- **Includes** :
|
||||||
|
- files from the project : `#include "relative/path/to/the/file.h"`
|
||||||
|
- external files and std : `#include <file.h>`
|
||||||
|
- use includes relative to included directories like `src`, not relative to the current file. Don't do: `#include "../file.h"`
|
||||||
|
- Only use [primary spellings for operators and tokens](https://en.cppreference.com/w/cpp/language/operator_alternative)
|
||||||
|
- Use auto sparingly. Don't use auto for [fundamental/built-in types](https://en.cppreference.com/w/cpp/language/types) and [fixed width integer types](https://en.cppreference.com/w/cpp/types/integer), except when initializing with a cast to avoid duplicating the type name.
|
||||||
|
- Examples:
|
||||||
|
- `auto* app = static_cast<DisplayApp*>(instance);`
|
||||||
|
- `auto number = static_cast<uint8_t>(variable);`
|
||||||
|
- `uint8_t returnValue = MyFunction();`
|
||||||
|
- Use nullptr instead of NULL
|
@ -1,16 +0,0 @@
|
|||||||
# Amazfish
|
|
||||||
[Amazfish](https://openrepos.net/content/piggz/amazfish) is a companion app that supports many smartwatches and activity trackers running on [SailfishOS](https://sailfishos.org/).
|
|
||||||
|
|
||||||
## Features
|
|
||||||
The following features are implemented:
|
|
||||||
- Scanning & detection of Pinetime-JF / InfiniTime
|
|
||||||
- Connection / disconnection
|
|
||||||
- Time synchronization
|
|
||||||
- Notifications
|
|
||||||
- Music control
|
|
||||||
- Navigation with Puremaps
|
|
||||||
|
|
||||||
## Demo
|
|
||||||
[This video](https://seafile.codingfield.com/f/21c5d023452740279e36/) shows how to connect to the Pinetime and control the playback of the music on the phone.
|
|
||||||
Amazfish and Sailfish OS are running on the [Pinephone](https://www.pine64.org/pinephone/), another awesome device from Pine64.
|
|
||||||
|
|
@ -1,13 +0,0 @@
|
|||||||
# Integration with Gadgetbridge
|
|
||||||
[Gadgetbridge](https://gadgetbridge.org/) is an Android application that supports many smartwatches and fitness trackers.
|
|
||||||
|
|
||||||
The integration of InfiniTime (previously Pinetime-JF) is now merged into the master branch (https://codeberg.org/Freeyourgadget/Gadgetbridge/) and initial support is available [starting with version 0.47](https://codeberg.org/Freeyourgadget/Gadgetbridge/src/branch/master/CHANGELOG.md). Note that the official version is only available on F-Droid (as of May 2021), and the unofficial fork available on the Play Store is outdated and does not support Infinitime.
|
|
||||||
|
|
||||||
## Features
|
|
||||||
The following features are implemented:
|
|
||||||
- Scanning & detection of Pinetime-JF / InfiniTime
|
|
||||||
- Connection / disconnection
|
|
||||||
- Notifications
|
|
||||||
|
|
||||||
## Demo
|
|
||||||
[This video](https://seafile.codingfield.com/f/0a2920b9d765462385e4/) shows how to scan, connect, send notification (using the debug screen) and disconnect from the Pinetime.
|
|
@ -1,12 +0,0 @@
|
|||||||
# OTA using NRFConnect
|
|
||||||
[NRFConnect](https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Connect-for-mobile) is a powerful application (running on Android and iOS) which allows to scan and connect to BLE devices.
|
|
||||||
|
|
||||||
## Features
|
|
||||||
- Scanning, connect, disconnect
|
|
||||||
- Time synchronization
|
|
||||||
- OTA
|
|
||||||
|
|
||||||
InfiniTime implements the Nordic DFU protocol for the OTA functionality. NRFConnect also supports this protocol.
|
|
||||||
|
|
||||||
# Demo
|
|
||||||
[This video](https://seafile.codingfield.com/f/a52b69683a05472a90c7/) shows how to use NRFConnect to update the firmware running on the Pinetime.
|
|
@ -0,0 +1,26 @@
|
|||||||
|
# Firmware, InfiniTime, Bootloader, Recovery firmware, OTA, DFU... What is it?
|
||||||
|
|
||||||
|
You may have already encountered these words by reading the announcement, release notes, or [the wiki guide](https://wiki.pine64.org/wiki/Upgrade_PineTime_to_InfiniTime_1.0.0) and you may find them confusing if you're not familiar with the project.
|
||||||
|
|
||||||
|
A **firmware** is software running on the embedded hardware of a device.
|
||||||
|
|
||||||
|
InfiniTime has three distinct firmwares:
|
||||||
|
|
||||||
|
- **[InfiniTime](https://github.com/InfiniTimeOrg/InfiniTime)** is the operating system.
|
||||||
|
- **[The bootloader](https://github.com/JF002/pinetime-mcuboot-bootloader)** is responsible for safely applying firmware updates and runs before booting into InfiniTime.
|
||||||
|
- **The recovery firmware** is a special *application firmware* than can be loaded by the bootloader on user request. This firmware can be useful in case of serious issue, when the main application firmware cannot perform an OTA update correctly.
|
||||||
|
|
||||||
|
**OTA** (**O**ver **T**he **A**ir) refers to updating of the firmware over BLE (**B**luetooth **L**ow **E**nergy). This is a functionality that allows the user to update the firmware on their device wirelessly.
|
||||||
|
|
||||||
|
**DFU** (**D**evice **F**irmware **U**pdate) is the file format and protocol used to send the update of the firmware to the watch over-the-air. InfiniTime implement the (legacy) DFU protocol from Nordic Semiconductor (NRF).
|
||||||
|
|
||||||
|
## Bootloader
|
||||||
|
|
||||||
|
Most of the time, the bootloader just runs without your intervention (update and load the firmware).
|
||||||
|
|
||||||
|
However, you can enable 2 functionalities using the push button:
|
||||||
|
|
||||||
|
- Push the button until the pine cone is drawn in **blue** to force the rollback of the previous version of the firmware, even if you've already validated the updated one
|
||||||
|
- Push the button until the pine cone is drawn in **red** to load the recovery firmware. This recovery firmware only provides BLE connectivity and OTA functionality.
|
||||||
|
|
||||||
|
More info about the bootloader in [its project page](https://github.com/JF002/pinetime-mcuboot-bootloader/blob/master/README.md).
|
Before Width: | Height: | Size: 107 KiB |
Before Width: | Height: | Size: 118 KiB |
Before Width: | Height: | Size: 156 KiB After Width: | Height: | Size: 72 KiB |
@ -1,119 +1,57 @@
|
|||||||
# Getting started with InfiniTime 1.0
|
# Getting started with InfiniTime
|
||||||
|
|
||||||
On April 22 2021, InfiniTime and Pine64 [announced the release of InfiniTime 1.0](https://www.pine64.org/2021/04/22/its-time-infinitime-1-0/) and the availability of PineTime smartwatches as *enthusiast grade end-user product*. This page aims to guide you with your first step with your new PineTime.
|
On April 22 2021, InfiniTime and Pine64 [announced the release of InfiniTime 1.0.0](https://www.pine64.org/2021/04/22/its-time-infinitime-1-0/) and the availability of PineTime smartwatches as an *enthusiast grade end-user product*. This page aims to guide you with your first step with your new PineTime.
|
||||||
|
|
||||||
## Firmware, InfiniTime, Bootloader, Recovery firmware, OTA, DFU... What is it?
|
It is highly recommended to update the firmware to the latest version when you receive your watch and when a new InfiniTime version is released. More information on updating the firmware [here](/doc/gettingStarted/updating-software.md).
|
||||||
|
|
||||||
You might have already seen these words by reading the announcement, release notes, or [the wiki guide](https://wiki.pine64.org/wiki/Upgrade_PineTime_to_InfiniTime_1.0.0) and, you may find them misleading if you're not familiar with the project.
|
## InfiniTime quick user guide
|
||||||
|
|
||||||
Basically, a **firmware** is just a software running on the embedded hardware of a device, the PineTime in this case.
|
|
||||||
**InfiniTime** is based on 3 distinct **firmwares**:
|
|
||||||
- **[InfiniTime](https://github.com/InfiniTimeOrg/InfiniTime)** itself, this is the *application firmware* running on the PineTime. This is the main firmware which provides most of the functionalities you'll use on a daily basis : bluetooth low-energy (BLE) connectivity, applications, watchfaces,...
|
|
||||||
- **[The bootloader](https://github.com/JF002/pinetime-mcuboot-bootloader)** is responsible for safely applying **updates** of the *application firmware*, reverting them in case of issues and load the recovery firmware when requested.
|
|
||||||
- **The recovery firmware** is a specific *application firmware* than can be loaded by the bootloader on user request. This firmware can be useful in case of serious issue, when the main application firmware cannot perform an OTA update correctly. Currently, this recovery firmware is based on [InfiniTime 0.14.1](https://github.com/InfiniTimeOrg/InfiniTime/releases/tag/0.14.1).
|
|
||||||
|
|
||||||
**OTA** and **DFU** refer to the update of the firmware over BLE (**B**luetooth **L**ow **E**nergy). **OTA** means **O**ver **T**he **A**ir, this is a functionality that allows the user to update the firmware how their device using a wireless communication like BLE. When we talk about **DFU** (**D**evice **F**irmware **U**pdate), we refer to the file format and protocol used to send the update of the firmware to the watch over-the-air. InfiniTime implement the (legacy) DFU protocol from Nordic Semiconductor (NRF).
|
|
||||||
|
|
||||||
## How to check the version of InfiniTime and the bootloader?
|
|
||||||
|
|
||||||
Since September 2020, all PineTimes (devkits or sealed) are flashed using the **[first iteration of the bootloader](https://github.com/lupyuen/pinetime-rust-mynewt/releases/tag/v4.1.7)** and **[InfiniTime 0.7.1](https://github.com/InfiniTimeOrg/InfiniTime/releases/tag/0.7.1)**. There was no recovery firmware at that time.
|
|
||||||
|
|
||||||
The bootloader only runs when the watch starts (from an empty battery, for example) or after a reset (after a successful OTA or a manual reset - long push on the button).
|
|
||||||
|
|
||||||
You can recognize this first iteration of the bootloader with it greenish **PINETIME** logo.
|
|
||||||
|
|
||||||
![Old bootloader logo](oldbootloaderlogo.jpg)
|
|
||||||
|
|
||||||
You can check the version of InfiniTime by opening the app *SystemInfo*. For version < 1.0:
|
|
||||||
|
|
||||||
![InfiniTime 0.7.1 Application menu](appmenu-071.jpg)
|
|
||||||
![InfiniTime 0.7.1 version](version-071.jpg)
|
|
||||||
|
|
||||||
And for version >= 1.0 :
|
|
||||||
|
|
||||||
![InfiniTime 1.0 version](version-1.0.jpg)
|
|
||||||
|
|
||||||
PineTime shipped from June 2021 (to be confirmed) will be flashed with the [new version of the bootloader](https://github.com/JF002/pinetime-mcuboot-bootloader/releases/tag/1.0.0), the [recovery firmware](https://github.com/InfiniTimeOrg/InfiniTime/releases/tag/0.14.1) and [InfiniTime 1.0](https://github.com/InfiniTimeOrg/InfiniTime/releases/tag/1.0.0).
|
|
||||||
|
|
||||||
The bootloader is easily recognizable with it white pine cone that is progressively drawn in green. It also displays its own version on the bottom (1.0.0 as of now).
|
|
||||||
|
|
||||||
![Bootloader 1.0](bootloader-1.0.jpg)
|
|
||||||
|
|
||||||
## How to update your PineTime?
|
|
||||||
|
|
||||||
To update your PineTime, you can use one of the compatible companion applications. Here are the main ones:
|
|
||||||
|
|
||||||
- **[Amazfish](https://github.com/piggz/harbour-amazfish)** (Desktop Linux, mobile Linux, SailfishOS, runs on the PinebookPro and the Pinephone)
|
|
||||||
- **[Gadgetbridge](https://www.gadgetbridge.org/)** (Android)
|
|
||||||
- **[Siglo](https://github.com/alexr4535/siglo)** (Linux, GTK based)
|
|
||||||
- **NRFConnect** (closed source, Android & iOS).
|
|
||||||
|
|
||||||
See [this page](ota-gadgetbridge-nrfconnect.md) for more info about the OTA procedure using Gadgetbridge and NRFConnect.
|
|
||||||
|
|
||||||
### From InfiniTime 0.7.1 / old bootloader
|
|
||||||
|
|
||||||
If your PineTime is currently running InfiniTime 0.7.1 and the old bootloader, we strongly recommend you update them to more recent version (Bootloader 1.0.0 and InfiniTime 1.0.0 as of now). We also recommend you install the recovery firmware once the bootloader is up-do-date.
|
|
||||||
|
|
||||||
Using the companion app of your choice, you'll need to apply the OTA procedure for these 3 firmwares in this sequence (failing to follow this specific order might temporarily or permanently brick your device):
|
|
||||||
|
|
||||||
1. Flash the latest version of InfiniTime. The file to upload is named **pinetime-mcuboot-app-dfu-x.y.z.zip**. Here is the link to [InfiniTime 1.0](https://github.com/InfiniTimeOrg/InfiniTime/releases/download/1.0.0/pinetime-mcuboot-app-dfu-1.0.0.zip).
|
|
||||||
2. Update the bootloader by applying the OTA procedure with the file named [**reloader-mcuboot.zip** from the repo of the bootloader](https://github.com/JF002/pinetime-mcuboot-bootloader/releases/download/1.0.0/reloader-mcuboot.zip).
|
|
||||||
3. Install the recovery firmware by applying the OTA procedure with the file named [**pinetime-mcuboot-recovery-loader-dfu-0.14.1.zip** from the version 0.14.1 of InfiniTime](https://github.com/InfiniTimeOrg/InfiniTime/releases/download/0.14.1/pinetime-mcuboot-recovery-loader-dfu-0.14.1.zip).
|
|
||||||
|
|
||||||
You'll find more info about this process in [this wiki page](https://wiki.pine64.org/wiki/Upgrade_PineTime_to_InfiniTime_1.0.0). You can also see the procedure in video [here](https://video.codingfield.com/videos/watch/831077c5-16f3-47b4-9b2b-c4bbfecc6529) and [here (from Amazfish)](https://video.codingfield.com/videos/watch/f7bffb3d-a6a1-43c4-8f01-f4aeff4adf9e)
|
|
||||||
|
|
||||||
### From version > 1.0
|
|
||||||
|
|
||||||
If you are already running the new "1.0.0" bootloader, all you have to do is update your version of InfiniTime when it'll be available. We'll write specific instructions when (if) we release a new version of the bootloader.
|
|
||||||
|
|
||||||
### Firmware validation
|
|
||||||
|
|
||||||
The bootloader requires a (manual) validation of the firmware. If the watch reset with an updated firmware that was not validated, the bootloader will consider it as non-functioning and will revert to the previous version of the firmware. This is a safety feature to prevent bricking your device with a faulty firmware.
|
|
||||||
|
|
||||||
You can validate your updated firmware on InfiniTime >= 1.0 by following this simple procedure:
|
|
||||||
|
|
||||||
- From the watchface, swipe **right** to display the *Quick Actions menu*
|
|
||||||
- Open the **Settings** app by tapping the *gear* icon on the bottom right
|
|
||||||
- Swipe down and tap on the entry named **Firmware**
|
|
||||||
- This app shows the version that is currently running. If it's not validated yet, it displays 2 buttons:
|
|
||||||
- **Validate** to validate your firmware
|
|
||||||
- **Reset** to reset the watch and revert to the previously running version of the firmware
|
|
||||||
|
|
||||||
## InfiniTime 1.0 quick user guide
|
|
||||||
|
|
||||||
### Setting the time
|
### Setting the time
|
||||||
|
|
||||||
By default, InfiniTime starts on the digital watchface. It'll probably display the epoch time (1 Jan 1970, 00:00). The time will be automatically synchronized once you connect on of the companion app to your PineTime using BLE connectivity. InfiniTime does not provide any way to manually set the time for now.
|
By default, InfiniTime starts on the digital watchface. It'll probably display the epoch time (1 Jan 1970, 00:00).
|
||||||
|
|
||||||
|
You can sync the time using companion apps.
|
||||||
|
|
||||||
|
- Gadgetbridge automatically synchronizes the time when you connect it to your watch. More information on Gadgetbridge [here](/doc/gettingStarted/ota-gadgetbridge.md)
|
||||||
|
- [Sync the time with NRFConnect](/doc/gettingStarted/time-nrfconnect.md)
|
||||||
|
- Sync the time with your browser https://hubmartin.github.io/WebBLEWatch/
|
||||||
|
|
||||||
|
You can also set the time in the settings without a companion app. (version >1.7.0)
|
||||||
|
|
||||||
|
InfiniTime doesn't handle daylight savings automatically, so make sure to set the correct the time or sync it with a companion app
|
||||||
|
|
||||||
|
### Digital watch face
|
||||||
|
|
||||||
|
![Digital watch face](ui/watchface.jpg)
|
||||||
|
|
||||||
|
This is what the default digital watch face looks like. You can change watch faces in the settings.
|
||||||
|
|
||||||
|
The indicator on the top left is visible if you have unread notifications
|
||||||
|
|
||||||
|
On the top right there are status icons
|
||||||
|
|
||||||
|
- The battery icon shows roughly how much charge is remaining
|
||||||
|
- The Bluetooth icon is visible when the watch is connected to a companion app
|
||||||
|
- A plug icon is shown when the watch is plugged into a charger.
|
||||||
|
|
||||||
|
On the bottom left you can see your heart rate if you have the measurement enabled in the heart rate app.
|
||||||
|
|
||||||
|
On the bottom right you can see how many steps you have taken today.
|
||||||
|
|
||||||
### Navigation in the menu
|
### Navigation in the menu
|
||||||
|
|
||||||
![Quick actions](quickactions.jpg)
|
![Application menu](ui/applist.jpg)
|
||||||
![Settings](settings.jpg)
|
![Notifications](ui/notifications.jpg)
|
||||||
![Application menu](appmenu.jpg)
|
![Quick actions](ui/quicksettings.jpg)
|
||||||
|
![Settings](ui/settings.jpg)
|
||||||
|
|
||||||
- Swipe **down** to display the notification panel. Notification sent by your companion app will be displayed in this panel.
|
|
||||||
- Swipe **up** to display the application menus. Apps (stopwatch, music, step, games,...) can be started from this menu.
|
- Swipe **up** to display the application menus. Apps (stopwatch, music, step, games,...) can be started from this menu.
|
||||||
|
- Swipe **down** to display the notification panel. Notification sent by your companion app will be displayed here.
|
||||||
- Swipe **right** to display the Quick Actions menu. This menu allows you to
|
- Swipe **right** to display the Quick Actions menu. This menu allows you to
|
||||||
- Set the brightness of the display
|
- Set the brightness of the display
|
||||||
- Start the **flashlight** app
|
- Start the **flashlight** app
|
||||||
- Enable/disable vibrations on notifications (Do Not Disturb mode)
|
- Enable/disable notifications (Do Not Disturb mode)
|
||||||
- Enter the **settings** menu
|
- Enter the **settings** menu
|
||||||
- Settings
|
- Swipe up and down to see all options
|
||||||
- Display timeout
|
- Click the button to go back a screen.
|
||||||
- Wake up event (Tap, wrist rotation)
|
- You can hold the button for a short time to return to the watch face. (version >1.7.0)
|
||||||
- Time format (12/24H)
|
|
||||||
- Default watchface (digital / analog)
|
|
||||||
- Battery info
|
|
||||||
- Firmware validation
|
|
||||||
- About (system info, firmware version,...)
|
|
||||||
|
|
||||||
### Bootloader
|
|
||||||
|
|
||||||
Most of the time, the bootloader just runs without your intervention (update and load the firmware).
|
|
||||||
|
|
||||||
However, you can enable 2 functionalities using the push button:
|
|
||||||
|
|
||||||
- Push the button until the pine cone is drawn in **blue** to force the rollback of the previous version of the firmware, even if you've already validated the updated one
|
|
||||||
- Push the button until the pine cone is drawn in **red** to load the recovery firmware. This recovery firmware only provides BLE connectivity and OTA functionality.
|
|
||||||
|
|
||||||
More info about the bootloader in [its project page](https://github.com/JF002/pinetime-mcuboot-bootloader/blob/master/README.md).
|
|
||||||
|
Before Width: | Height: | Size: 114 KiB |
@ -1,109 +0,0 @@
|
|||||||
# Flash and upgrade InfiniTime
|
|
||||||
If you just want to flash or upgrade InfiniTime on your PineTime, this page is for you!
|
|
||||||
|
|
||||||
- [InfiniTime releases and versions](#infinitime-releases-and-versions)
|
|
||||||
- [How to upgrade Over-The-Air (OTA)](#how-to-upgrade-over-the-air-ota)
|
|
||||||
- [Using Gadgetbridge](#using-gadgetbridge)
|
|
||||||
- [Using NRFConnect](#Using-nrfconnect)
|
|
||||||
- [How to flash InfiniTime using the SWD interface](#how-to-flash-infinitime-using-the-swd-interface)
|
|
||||||
|
|
||||||
## InfiniTime releases and versions
|
|
||||||
All releases of InfiniTime are available on the [release page of the GitHub repo](https://github.com/InfiniTimeOrg/InfiniTime/releases).
|
|
||||||
|
|
||||||
Versions that are tagged as **RELEASE CANDIDATE** are pre-release versions, that are available for testing before actually releasing a new stable version. If you want to help us debug the project and provide stable versions to other user, you can use them. If you want stable and tested version, you should not flash these release candidate version.
|
|
||||||
|
|
||||||
Release files are available under the *Assets* button.
|
|
||||||
|
|
||||||
## How to upgrade Over-The-Air (OTA)
|
|
||||||
OTA is the easiest method to upgrade InfiniTime. Note that it's only possible is your PineTime is already running InfiniTime (>= 0.7.1).
|
|
||||||
|
|
||||||
2 companion apps provide support for OTA :
|
|
||||||
- [Gadgetbridge](https://gadgetbridge.org/) (open source, runs on Android, [available on F-Droid](https://f-droid.org/packages/nodomain.freeyourgadget.gadgetbridge/)).
|
|
||||||
- [NRFConnect](https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Connect-for-mobile) (close source, runs on Android and iOS).
|
|
||||||
|
|
||||||
Both applications need you to download the **DFU file** of InfiniTime. This file contains the new version of InfiniTime that will be flashed into your device. It's called **dfu-x.y.z.zip** (ex: dfu-0.9.0.zip) in the release note.
|
|
||||||
![Dfu file](dfuFile.png )
|
|
||||||
|
|
||||||
### Using Gadgetbridge
|
|
||||||
Launch Gadgetbridge and tap on the **"+"** button on the bottom right to add a new device:
|
|
||||||
|
|
||||||
![Gadgetbridge 0](gadgetbridge0.jpg)
|
|
||||||
|
|
||||||
Wait for the scan to complete, your PineTime should be detected:
|
|
||||||
|
|
||||||
![Gadgetbridge 1](gadgetbridge1.jpg)
|
|
||||||
|
|
||||||
Tap on it. Gadgdetbridge will pair and connect to your device:
|
|
||||||
|
|
||||||
![Gadgetbridge 2](gadgetbridge2.jpg)
|
|
||||||
|
|
||||||
Now that Gadgetbridge is connected to your PineTime, use a file browser application (I'm using Seafile to browse my NAS) and browse to the DFU file (image-xxx.zip) you downloaded previously. Tap on it and open it using the Gadgetbridge application/firmware installer:
|
|
||||||
|
|
||||||
![Gadgetbridge 3](gadgetbridge3.jpg)
|
|
||||||
|
|
||||||
Read carefully the warning and tap **Install**:
|
|
||||||
|
|
||||||
![Gadgetbridge 4](gadgetbridge4.jpg)
|
|
||||||
|
|
||||||
Wait for the transfer to finish. Your PineTime should reset and reboot with the new version of InfiniTime!
|
|
||||||
|
|
||||||
Don't forget to **validate** your firmware. In the InfiniTime go to the settings (swipe right, select gear icon) and Firmware option and click **validate**. Otherwise after reboot the previous firmware will be used.
|
|
||||||
|
|
||||||
![Gadgetbridge 5](gadgetbridge5.jpg)
|
|
||||||
|
|
||||||
### Using NRFConnect
|
|
||||||
Open NRFConnect. Swipe down in the *Scanner* tab and wait for your device to appear:
|
|
||||||
|
|
||||||
![NRFConnect 0](nrfconnect0.jpg)
|
|
||||||
|
|
||||||
Tap on the *Connect* button on the right of your device. NRFConnect will connect to your PineTime and discover its characteristics. Tap on the **DFU** button on the top right:
|
|
||||||
|
|
||||||
![NRFConnect 1](nrfconnect1.jpg)
|
|
||||||
|
|
||||||
Select **Distribution packet (ZIP)**:
|
|
||||||
|
|
||||||
![NRFConnect 2](nrfconnect2.jpg)
|
|
||||||
|
|
||||||
Browse to the DFU file you downloaded previously, the DFU transfer will start automatically. When the transfer is finished, your PineTime will reset and restart on the new version of InfiniTime!
|
|
||||||
|
|
||||||
Don't forget to **validate** your firmware. In the InfiniTime go to the settings (swipe right, select gear icon) and Firmware option and click **validate**. Otherwise after reboot the previous firmware will be used.
|
|
||||||
|
|
||||||
![NRFConnect 3](nrfconnect3.jpg)
|
|
||||||
|
|
||||||
## How to flash InfiniTime using the SWD interface
|
|
||||||
Download the files **bootloader.bin**, **image-x.y.z.bin** and **pinetime-graphics-x.y.z.bin** from the release page:
|
|
||||||
|
|
||||||
![Image file](imageFile.png )
|
|
||||||
|
|
||||||
The bootloader reads a boot logo from the external SPI flash memory. The first step consists in flashing a tool in the MCU that will flash the boot logo into this SPI flash memory. This first step is optional but recommanded (the bootloader will display garbage on screen for a few second if you don't do it).
|
|
||||||
Using your SWD tool, flash **pinetime-graphics-x.y.z.bin** at offset **0x0000**. Reset the MCU and wait for a few second, until the logo is completely drawn on the display.
|
|
||||||
|
|
||||||
Then, using your SWD tool, flash those file at specific offset:
|
|
||||||
|
|
||||||
- bootloader.bin : **0x0000**
|
|
||||||
- image-x.y.z.bin : **0x8000**
|
|
||||||
|
|
||||||
Reset and voilà, you're running InfiniTime on your PineTime!
|
|
||||||
|
|
||||||
If you are using OpenOCD with a STLinkV2, you can find more info [on this page](../openOCD.md).
|
|
||||||
|
|
||||||
## How to synchronize the time
|
|
||||||
|
|
||||||
### Using Gadgetbridge
|
|
||||||
Good news! Gadgetbridge **automatically** synchronizes the time when connecting to your PineTime!
|
|
||||||
|
|
||||||
### Using any Chromium-based web browser
|
|
||||||
You can use it from your PC, Mac, Android. Browsers now have BLE support.
|
|
||||||
https://hubmartin.github.io/WebBLEWatch/
|
|
||||||
|
|
||||||
### Using NRFConnect
|
|
||||||
You must enable the **CTS** *GATT server* into NRFConnect so that InfiniTime can synchronize the time with your smartphone.
|
|
||||||
|
|
||||||
Launch NRFConnect, tap the sandwich button on the top left and select *Configure GATT server*:
|
|
||||||
|
|
||||||
![NRFConnect CTS 0](nrfconnectcts0.jpg)
|
|
||||||
|
|
||||||
|
|
||||||
Tap *Add service* and select the server configuration *Current Time service*. Tap OK and connect to your PineTime, it should automcatically sync the time once the connection is established!
|
|
||||||
|
|
||||||
![NRFConnect CTS 1](nrfconnectcts1.jpg)
|
|
@ -0,0 +1,29 @@
|
|||||||
|
# Connecting to Gadgetbridge
|
||||||
|
|
||||||
|
Launch Gadgetbridge and tap on the **"+"** button on the bottom right to add a new device:
|
||||||
|
|
||||||
|
![Gadgetbridge 0](gadgetbridge0.jpg)
|
||||||
|
|
||||||
|
Wait for the scan to complete, your PineTime should be detected:
|
||||||
|
|
||||||
|
![Gadgetbridge 1](gadgetbridge1.jpg)
|
||||||
|
|
||||||
|
Tap on it. Gadgdetbridge will pair and connect to your device:
|
||||||
|
|
||||||
|
![Gadgetbridge 2](gadgetbridge2.jpg)
|
||||||
|
|
||||||
|
# Updating with Gadgetbridge
|
||||||
|
|
||||||
|
Now that Gadgetbridge is connected to your PineTime, use a file browser application and find the DFU file (`pinetime-mcuboot-app-dfu-x.x.x.zip`) you downloaded previously. Tap on it and open it using the Gadgetbridge application/firmware installer:
|
||||||
|
|
||||||
|
![Gadgetbridge 3](gadgetbridge3.jpg)
|
||||||
|
|
||||||
|
Read carefully the warning and tap **Install**:
|
||||||
|
|
||||||
|
![Gadgetbridge 4](gadgetbridge4.jpg)
|
||||||
|
|
||||||
|
Wait for the transfer to finish. Your PineTime should reset and reboot with the new version of InfiniTime!
|
||||||
|
|
||||||
|
Don't forget to **validate** your firmware. In the InfiniTime go to the settings (swipe right, select gear icon) and Firmware option and click **validate**. Otherwise after reboot the previous firmware will be used.
|
||||||
|
|
||||||
|
![Gadgetbridge 5](gadgetbridge5.jpg)
|
@ -0,0 +1,22 @@
|
|||||||
|
# Updating with NRFConnect
|
||||||
|
|
||||||
|
Open NRFConnect. Swipe down in the *Scanner* tab and wait for your device to appear:
|
||||||
|
|
||||||
|
![NRFConnect 0](nrfconnect0.jpg)
|
||||||
|
|
||||||
|
Tap on the *Connect* button on the right of your device. NRFConnect will connect to your PineTime and discover its characteristics. Tap on the **DFU** button on the top right:
|
||||||
|
|
||||||
|
![NRFConnect 1](nrfconnect1.jpg)
|
||||||
|
|
||||||
|
Select **Distribution packet (ZIP)**:
|
||||||
|
|
||||||
|
![NRFConnect 2](nrfconnect2.jpg)
|
||||||
|
|
||||||
|
Find the DFU file (`pinetime-mcuboot-app-dfu-x.x.x.zip`) you downloaded previously, the DFU transfer will start automatically. When the transfer is finished, your PineTime will reset and restart on the new version of InfiniTime!
|
||||||
|
|
||||||
|
Don't forget to **validate** your firmware. In the InfiniTime go to the settings (swipe right, select gear icon) and Firmware option and click **validate**. Otherwise after reboot the previous firmware will be used.
|
||||||
|
|
||||||
|
![NRFConnect 3](nrfconnect3.jpg)
|
||||||
|
|
||||||
|
# Demo
|
||||||
|
[This video](https://seafile.codingfield.com/f/a52b69683a05472a90c7/) shows how to use NRFConnect to update the firmware running on the Pinetime.
|
Before Width: | Height: | Size: 112 KiB |
Before Width: | Height: | Size: 127 KiB |
@ -0,0 +1,11 @@
|
|||||||
|
### Syncing time
|
||||||
|
|
||||||
|
You must enable the **CTS** *GATT server* in NRFConnect so that InfiniTime can synchronize the time with your smartphone.
|
||||||
|
|
||||||
|
Launch NRFConnect, tap the sandwich button on the top left and select *Configure GATT server*:
|
||||||
|
|
||||||
|
![NRFConnect CTS 0](nrfconnectcts0.jpg)
|
||||||
|
|
||||||
|
Tap *Add service* and select the server configuration *Current Time service*. Tap OK and connect to your PineTime, it should automcatically sync the time once the connection is established!
|
||||||
|
|
||||||
|
![NRFConnect CTS 1](nrfconnectcts1.jpg)
|
After Width: | Height: | Size: 130 KiB |
After Width: | Height: | Size: 182 KiB |
After Width: | Height: | Size: 132 KiB |
After Width: | Height: | Size: 135 KiB |
After Width: | Height: | Size: 101 KiB |
@ -0,0 +1,41 @@
|
|||||||
|
# Updating InfiniTime
|
||||||
|
|
||||||
|
If you just want to flash or upgrade InfiniTime on your PineTime, this page is for you! If you want more information about the software and the update procedure, check out [this](/doc/gettingStarted/about-software.md) page.
|
||||||
|
|
||||||
|
## Checking the version of InfiniTime
|
||||||
|
|
||||||
|
You can check the InfiniTime version by first swiping right on the watchface to open quick settings, tapping the cogwheel to open settings, swipe up until you find an entry named "About" and tap on it.
|
||||||
|
|
||||||
|
![InfiniTime 1.0 version](version-1.0.jpg)
|
||||||
|
|
||||||
|
PineTimes shipped after June 2021 will ship with the latest version of [the bootloader](https://github.com/JF002/pinetime-mcuboot-bootloader/releases/tag/1.0.0) and [recovery firmware](https://github.com/InfiniTimeOrg/InfiniTime/releases/tag/0.14.1)
|
||||||
|
|
||||||
|
The bootloader is run right before booting into InfiniTime. It is easily recognizable with its white pine cone that is progressively drawn in green. It also displays its own version on the bottom (1.0.0 as of now).
|
||||||
|
|
||||||
|
![Bootloader 1.0](bootloader-1.0.jpg)
|
||||||
|
|
||||||
|
## Updating with companion apps
|
||||||
|
|
||||||
|
To update your PineTime, you can use one of the [compatible companion applications](/README.md#companion-apps).
|
||||||
|
|
||||||
|
The updating process differs slightly on every companion app, so you'll need to familiarize yourself with the companion app of your choice.
|
||||||
|
|
||||||
|
All releases of InfiniTime are available on the [release page of the GitHub repo](https://github.com/InfiniTimeOrg/InfiniTime/releases) under assets.
|
||||||
|
|
||||||
|
To update the firmware, you need to download the DFU of the firmware version that you'd like to install, for example `pinetime-mcuboot-app-dfu-1.6.0.zip`, and flash it with your companion app.
|
||||||
|
|
||||||
|
We have prepared instructions for flashing InfiniTime with Gadgetbridge and NRFConnect.
|
||||||
|
|
||||||
|
- [Updating with Gadgetbridge](/doc/gettingStarted/ota-gadgetbridge.md)
|
||||||
|
- [Updating with NRFConnect](/doc/gettingStarted/ota-nrfconnect.md)
|
||||||
|
|
||||||
|
## Firmware validation
|
||||||
|
|
||||||
|
Firmware updates must be manually validated. If the firmware isn't validated and the watch resets, the watch will revert to the previous firmware. This is a safety feature to prevent bricking your device with faulty firmware.
|
||||||
|
|
||||||
|
You can validate your updated firmware on InfiniTime >= 1.0 by following this simple procedure:
|
||||||
|
|
||||||
|
- From the watchface, swipe **right** to display the *quick settings menu*
|
||||||
|
- Open settings by tapping the cogwheel on the bottom right
|
||||||
|
- Swipe up until you find an entry named **Firmware** and tap on it
|
||||||
|
- If the firmware is not validated yet, you can either validate the running firmware, or reset and revert to the previous firmware version
|
Before Width: | Height: | Size: 109 KiB |
Before Width: | Height: | Size: 114 KiB After Width: | Height: | Size: 55 KiB |
@ -1,6 +1,6 @@
|
|||||||
# Versioning
|
# Versioning
|
||||||
The versioning of this project is based on [Semantic versionning](https://semver.org/) :
|
The versioning of this project is based on [Semantic versioning](https://semver.org/):
|
||||||
|
|
||||||
- The **patch** is incremented when we fix a bug on a **released** version (most of the time using a **hotfix** branch).
|
- The **patch** is incremented when a bug is fixed on a **released** version (most of the time using a **hotfix** branch).
|
||||||
- The **minor** is incremented when we release a new version with new features. It corresponds to a merge of **develop** into **master**.
|
- The **minor** is incremented when a new version with new features is released. It corresponds to a merge of **develop** into **master**.
|
||||||
- The **major** should be incremented when a breaking change is made to the application. We still have to define what is a breaking change in the context of this project. For now, I suggest that it stays **0** until we have a fully functioning firmware suited for the final user.
|
- The **major** should be incremented when a breaking change is made to the application. We still have to define what is a breaking change in the context of this project.
|
||||||
|
Before Width: | Height: | Size: 37 KiB |
After Width: | Height: | Size: 31 KiB |