Difference between revisions of "PineTime"

From PINE64
Jump to navigation Jump to search
(Update Amazfish links)
 
(148 intermediate revisions by 46 users not shown)
Line 1: Line 1:
== Frequently asked questions ==
[[File:Pinetime.png|400px|thumb|right|The PineTime]]
 
The '''PineTime''' is a free and open source smartwatch capable of running custom-built open operating systems. Some of the notable features include a heart rate monitor, a week-long battery, and a capacitive touch IPS display that is legible in direct sunlight. It is a fully community driven side-project which anyone can contribute to, allowing you to keep control of your device.
 
== Getting started ==


'''Read these first!'''
'''Read these first!'''


* [https://wiki.pine64.org/index.php/Frequently_asked_questions_about_the_PineTime Frequently asked questions about the devkit]
* [[Upgrade PineTime to InfiniTime 1.0.0|Upgrading your new PineTime to InfiniTime 1.0.0]]
* [https://wiki.pine64.org/index.php/Reprogramming_the_PineTime Programming the PineTime]
* [[PineTime Devkit Wiring]]
* [https://wiki.pine64.org/index.php/Lup_Yuen_Lee_Q%26A_about_PineTime Q&A about Rust and MyNewt for PineTime by Lup Yuen Lee]
* [[Reprogramming the PineTime|Reprogramming the PineTime (development kit)]]
* [[Switching your PineTime between InfiniTime and Wasp-os]]
 
The frequently asked question can be found in the article [[PineTime FAQ]].
 
== Default OS ==
 
The current default operating system on the PineTime is called [[InfiniTime]], you can find more information about the firmware on its GitHub page. First devkits shipped with a proprietary custom firmware.
 
You can find a list of available firmware and other software here: [[PineTime Development]]
 
== Companion Apps ==
 
PineTime/InfiniTime needs a companion app to e.g. upload a firmware, get notifications from a phone, or just get the date/time. 
Here are some companion apps:
 
* [https://www.gadgetbridge.org Gadgetbridge] (Android >= 4.4) - Companion mobile app, supports updating firmware/bootloader, send notifications, etc.
* [https://github.com/piggz/harbour-amazfish/ Amazfish] ([https://sailfishos-chum.github.io/apps/harbour-amazfish/ SailfishOS], [https://open-store.io/app/uk.co.piggz.amazfish Ubuntu Touch] and [https://flathub.org/apps/uk.co.piggz.amazfish Linux]) - Companion mobile and desktop app, supports updating firmware/bootloader, send notifications, etc.
* [https://github.com/alexr4535/siglo Siglo] (Linux) - Companion desktop app.
* [https://github.com/ZephyrLabs/PinetimeFlasher PinetimeFlasher] (Windows) - Companion desktop app, only supports flashing firmware.
* [https://apps.apple.com/us/app/nrf-connect-for-mobile/id1054362403 nRFConnect] (iOS) - Only supports flashing firmware. The app is closed source and versions after 4.24.3 don't work for the PineTime anymore
* [https://github.com/xan-m/InfiniLink InfiniLink] (iOS) - Companion mobile app in development. Supports updating firmware/bootloader, setting date and time, Apple Music controls, and battery and heart rate data.
* [https://gitea.elara.ws/Elara6331/itd ITD] (Linux)


== Specifications ==
== Specifications ==
'''Dimensions:''' 37.5 x 40 x 11mm <br>
* '''Dimensions:''' 37.5 x 40 x 11mm
'''Weight:''' 38 grams <br>
* '''Weight:''' 38 grams
'''IP Rating:''' IP67 (waterproof to 1 meter) <br>
* '''IP Rating:''' IP67 (waterproof to 1 meter (sealed edition!))
'''Display:'''
* '''Display:'''
: '''Size:''' 1.3 inches (33mm) diagonal
** '''Size:''' 1.3 inches (33mm) diagonal
: '''Type:''' IPS capacitive touchscreen, RGB 65K colors
** '''Type:''' IPS capacitive touchscreen, RGB 65K colors
: '''Display Controller:''' ST7789
** '''Display Controller:''' ST7789
: '''Resolution:''' 240x240 pixels <br>
** '''Resolution:''' 240x240 pixels
'''System on Chip:''' Nordic Semiconductor nRF52832 <br>
* '''System on Chip:''' Nordic Semiconductor nRF52832
'''Flash:''' 512KB with additional 4MB SPI NOR <br>
* '''Flash:''' 512KB with additional 4MB SPI NOR
'''RAM:''' 64KB <br>
* '''RAM:''' 64KB
'''Bluetooth:''' 5.0 (including Bluetooth Low Energy) <br>
* '''Bluetooth:''' [[PineTime_Bluetooth|5.0 (including Bluetooth Low Energy)]]
'''Sensors:''' Accelerometer, Heart rate sensor <br>
* '''Sensors:''' Accelerometer, Heart rate sensor
'''Feedback:''' Vibration motor <br>
* '''Feedback:''' Vibration motor
'''Battery:''' 170-180mAh LiPo
* '''Battery:''' 170-180mAh 3.8V LiPo


== SWD Pinout ==
== Community ==
The devkits have exposed SWD pins for flashing and debugging.


Only a few devs have soldered to these pins, most just use friction to make contact with the programming cable.
=== Forum ===
* [https://forum.pine64.org/forumdisplay.php?fid=134 PineTime forum]


The pinout is:
=== Chat ===
* [https://matrix.to/#/#pinetime:matrix.org Matrix Channel] (No login required to read)
* IRC Server: [ircs://irc.pine64.org#pinetime irc.pine64.org] Channel: PineTime
* [https://t.me/pinetime Telegram group]
* [https://discordapp.com/invite/DgB7kzr Discord server invite link]


Developers and coding:
* [https://matrix.to/#/#pinetime-dev:matrix.org Matrix Channel] (No login required to read)
* [https://t.me/pinetime_dev Telegram group]
* [https://discordapp.com/invite/DgB7kzr Discord server invite link]
=== Development efforts ===
To read more about development on the PineTime, the projects available and more technical details, check out [[PineTime Development]]


[[File:PineTime_SWD_location.jpg]]
=== Useful articles and blog posts ===


== Driving the peripherals ==
If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.
 
* [https://www.ncartron.org/one-week-with-my-pinetime---a-feedback.html Using the PineTime in production (January 2021)]
* [https://lupyuen.github.io/articles/sneak-peek-of-pinetime-smart-watch-and-why-its-perfect-for-teaching-iot Sneak Peek of PineTime Smart Watch… And why it’s perfect for teaching IoT]
* [https://lupyuen.github.io/articles/building-a-rust-driver-for-pinetimes-touch-controller Building a Rust Driver for PineTime’s Touch Controller]
* [https://lupyuen.github.io/articles/porting-druid-rust-widgets-to-pinetime-smart-watch Porting (druid) Rust Widgets to PineTime Smart Watch]
* [https://lupyuen.github.io/articles/optimising-pinetimes-display-driver-with-rust-and-mynewt Optimising PineTime’s Display Driver with Rust and Mynewt]
* [https://electronut.in/getting-started-with-zephyr-rtos-on-nordic-nrf52832-hackable/ Getting Started with Zephyr RTOS on Nordic nRF52832 hackaBLE]
* [https://blog.aegrel.ee/absniffer-cmsis-dap-sniffer.html Removing the lock and installing another firmware on the nRF52832 using CMSIS-DAP dongle on Linux]
* [https://github.com/JF002/nrf52-baseproject/wiki/Build,-program-and-debug-NRF52-project-with-JLink,-CMake-and-CLion Build, program and debug NRF52 project with JLink, CMake and CLion]
* [https://www.nrbtech.io/blog/2020/1/4/using-clion-for-nordic-nrf52-projects Using CLion for Nordic nRF52 projects]
* [https://dev.to/aaronc81/flashing-your-pinetime-using-an-st-link-and-openocd-54dd Flashing your PineTime using an ST-Link and OpenOCD]
* [https://zephyrlabs.github.io/Watchfaces/ Zephyrlabs: just a bunch of watchfaces made for the pinetime]
* [https://pankajraghav.com/2021/04/03/PINETIME-STOPCLOCK.html Creating a stopwatch in Pinetime (with Infinitime)]
* [https://kj7rrv.com/fixing-a-pinetime-charging-cradle Fixing a broken charging cradle]
* [[PineTime Custom Watchface Tutorial]]
* [[PineTimeStyle]]
 
== Hardware ==


=== Display ===
=== Display ===
Line 54: Line 110:
|-
|-
| LCD_RS (P0.18)
| LCD_RS (P0.18)
| Clock/data pin (CD)
| Command/Data pin (CD)
|-
|-
| LCD_CS (P0.25)
| LCD_CS (P0.25)
Line 70: Line 126:
* Chip select must be held low while driving the display. It must be high when using other SPI devices on the same bus (such as external flash storage) so that the display controller won't respond to the wrong commands.
* Chip select must be held low while driving the display. It must be high when using other SPI devices on the same bus (such as external flash storage) so that the display controller won't respond to the wrong commands.
* SPI must be used in mode 3. Mode 0 (the default) won't work.
* SPI must be used in mode 3. Mode 0 (the default) won't work.
* LCD_DISPLAY_* is used to enable the backlight. Set at least one to low to see anything on the screen.
* LCD_BACKLIGHT_* is used to enable the backlight. Set at least one to low to see anything on the screen.
* Use SPI at 8MHz (the fastest clock available on the nRF52832) because otherwise refreshing will be super slow.
* Use SPI at 8MHz (the fastest clock available on the nRF52832) because otherwise refreshing will be super slow.


Line 95: Line 151:


Converting this voltage to an estimated capacity in percent requires a more complicated algorithm, because Lithium-ion batteries have a non-linear discharge curve.
Converting this voltage to an estimated capacity in percent requires a more complicated algorithm, because Lithium-ion batteries have a non-linear discharge curve.
=== How to write battery friendly software? ===
The key to save battery is to enable only what you need when you need it. NRF52832 has a lot of functionalities allowing you to draw as little current as possible. Here are some tips and tricks:
* Disable / shutdown / put in sleep mode '''all devices around the MCU''' (display controller, touch controller, external memory,...).
* Disable all '''peripheral inside the MCU''' when you don't need them (SPI, TWI(I²C),...). The power management of the NRF52832 is very smart and will completely shut down (power off and disable the clock) the peripheral when the software disables it.
* Put the MCU to sleep as soon and as often as possible. If you are not using a RTOS, this is done by calling ''WFE'' (wait for event) instruction. Most of the time, RTOS implement this functionality. For example, FreeRTOS calls it the ''tickless mode'' : it puts the CPU in sleep mode when no task is planned for execution for more than a specified time, and wakes up as soon as an event is detected or when a task is ready to run.
* Do not use logging (JLink RTT, SWO, semihosting,...), it uses a lot of power.
* Ensure that the debug circuitry of the MCU is not enabled when you measuring the battery life. The debug peripheral is enabled as soon as you connect a debugger to the device, and '''is not automatically disabled''', even if you disconnect the debugger you will have to wait for the battery to go flat to disable to port. The software running in the NRF52832 cannot disable the debug peripheral. How to disable the debug circuitry:
  - using ''nrfjprog --reset''
  - using JLinkExe : issue the command ''writeDP 1 0''
  or with OpenOCD
  - issue the command ''halt''
  - issue the command ''flash fillw 0x10001208 0xFFFFFF00 0x01''
  - issue the command ''reset''
  you can check if the debug port is enabled using the following code
  DWT->CYCCNT ? "NO":"YES"
* Read [https://infocenter.nordicsemi.com/pdf/nRF52832_Rev_2_Errata_v1.1.pdf the errata sheet of the MCU] and apply workarounds if they apply to your software.


=== Button ===
=== Button ===
Line 122: Line 157:


While enabled, the button in pin (P0.13) will be high when the button is pressed, and low when it is not pressed.
While enabled, the button in pin (P0.13) will be high when the button is pressed, and low when it is not pressed.
Note that the button consumes around 34µA when P0.15 is left high. To reduce current consumption, set it to low most of the time and only set it to high shortly before reading it. The button needs a short time to give good outputs though, setting P0.15 high at least four times in a row seems to result in enough delay that P0.13 has a stable output.


=== Touch panel ===
=== Touch panel ===
Line 139: Line 176:
* Frequency : from 10Khz to 400Khz
* Frequency : from 10Khz to 400Khz


'''NOTE : ''' The controller go to sleep when no event is detected. In sleep mode, the controller does not communicate on the I²C bus (it appears disconnected). So, for the communication to work, you need to tap on the screen so that the chip wakes-up.
'''NOTE: ''' The controller goes to sleep when no event is detected. In sleep mode, the controller does not communicate on the I²C bus (it appears disconnected). So, for the communication to work, you need to tap on the screen so that the chip wakes-up.
 
'''NOTE: ''' The I²C bus, also known as TWI bus, has known issues, make sure to write your TWI driver with timeouts.


==== Touch events ====
==== Touch events ====


Touch informations are available in the 63 first registers of the controller. Remember : the device is in sleep mode when no touch event is detected. It means that you can read the register only when the touch controller detected an event. You can use the ''Interrupt'' pin to detect such event in the software.  
Touch information is available from the 63 first registers of the controller. Remember: the device is in sleep mode when no touch event is detected. It means that you can read the register only when the touch controller detected an event. You can use the ''Interrupt'' pin to detect such event in the software.  


These 63 bytes contain up to 10 touch point (X, Y, event type, pressure,...) :  
These 63 bytes contain up to 10 touch point (X, Y, event type, pressure,...) :  
Line 290: Line 329:
'''WARNING : ''' <del>Writing the SLEEP command (write 0x05 in HYN_REG_POWER_MODE) seems to freeze the controller (it returns only static values) until the battery is totally drained and the whole system reset. Analysis and debugging is more than welcome!</del>
'''WARNING : ''' <del>Writing the SLEEP command (write 0x05 in HYN_REG_POWER_MODE) seems to freeze the controller (it returns only static values) until the battery is totally drained and the whole system reset. Analysis and debugging is more than welcome!</del>


== Manual / Articles ==
=== Accelerometer ===
The on board accelerometer in devices shipped before July 2021 is a Bosch BMA421, connected to the I2C bus.
Devices shipped after July 2021 use a Bosch BMA425 accelerometer.


* [https://github.com/najnesnaj/pinetime-zephyr Beginner manual explained how you to programs and install zephyr on PineTime Dev Kit, big thanks to najnesnaj :-)]
==== Pins ====


* [https://medium.com/swlh/sneak-peek-of-pinetime-smart-watch-and-why-its-perfect-for-teaching-iot-81b74161c159 Sneak Peek of PineTime Smart Watch… And why it’s perfect for teaching IoT]
* P0.06 : I²C SDA
 
* P0.07 : I²C SCL
* [https://medium.com/@ly.lee/building-a-rust-driver-for-pinetimes-touch-controller-cbc1a5d5d3e9 Building a Rust Driver for PineTime’s Touch Controller]
* P0.08 : Interrupt
 
* [https://medium.com/@ly.lee/porting-druid-rust-widgets-to-pinetime-smart-watch-7e1d5a5d977a Porting (druid) Rust Widgets to PineTime Smart Watch]
 
* [https://medium.com/@ly.lee/optimising-pinetimes-display-driver-with-rust-and-mynewt-3ba269ea2f5c Optimising PineTime’s Display Driver with Rust and Mynewt]


* [https://www.zephyrproject.org/getting-started-with-zephyr-rtos-on-nordic-nrf52832-hackable/ Getting Started with Zephyr RTOS on Nordic nRF52832 hackaBLE]
I2C Device address : 0x18


* [https://blog.aegrel.ee/absniffer-cmsis-dap-sniffer.html Removing the lock and installing another firmware on the nRF52832 using CMSIS-DAP dongle on Linux]
=== Reducing power consumption ===


* [https://github.com/JF002/nrf52-baseproject/wiki/Build,-program-and-debug-NRF52-project-with-JLink,-CMake-and-CLion Build, program and debug NRF52 project with JLink, CMake and CLion]
The PineTime appears to be able to sleep with a current consumption of [https://github.com/InfiniTimeOrg/InfiniTime/issues/53#issuecomment-783654321 only 66µA].


* [https://www.nrbtech.io/blog/2020/1/4/using-clion-for-nordic-nrf52-projects Using CLion for Nordic nRF52 projects]
To investigate current consumption, it's a good idea to disable everything possible to get the lowest current consumption possible, and then re-enable things one by one. Here is one way to get a baseline current consumption of 60µA, as measured from the 3.3V pin with the battery disconnected:


* [https://dev.to/aaronc81/flashing-your-pinetime-using-an-st-link-and-openocd-54dd Flashing your PineTime using an ST-Link and OpenOCD]
* Enable the DC/DC regulator. This doesn't affect the current consumption while sleeping, but almost halves the runtime current consumption.
* Use the low-frequency (32.768kHz) oscillator.
* Leave all pins in their default state, except for P0.05 (SPI CS) and P0.25 (LCD CS) which should be configured as an output and set to high.
* Put the heart rate sensor in sleep mode by setting the PDRIVER (0x0C) register to 0, see [https://files.pine64.org/doc/datasheet/pinetime/HRS3300%20Heart%20Rate%20Sensor.pdf#page=12 the HRS3300 datasheet for details].
* Put the SPI flash in [https://datasheet.lcsc.com/szlcsc/2005251035_XTX-XT25F32BSOIGU-S_C558851.pdf#page=38 deep power-down mode] by setting flash CS high, then low, then writing the byte 0xb9 on the SPI bus, and then setting flash CS high again.
* Sleep in a loop, using WFE or WFI (if you're using the Nordic SoftDevice, call <code>sd_app_evt_wait</code> instead).


== Development efforts ==
Here are some current consumption statistics (current consumed in addition to the baseline power), roughly ordered from large to small:


{| class="wikitable"
{| class="wikitable"
!
!Source
! Project Homepage
!Current
! Project Source
!Notes
! PineTime Implementations
|-
 
|SWD
|3.05mA
|Power cycle the chip after programming to avoid this, it can hide other inefficiencies.
|-
|LCD
|5.61mA
|Set the LCD to sleep mode when not used, using SLPIN.
|-
|Backlight high
|12.27mA
|-
|Backlight mid
|5.51mA
|-
|Backlight low
|1.83mA
|-
|-
! FreeRTOS
|ADC left enabled
|https://www.freertos.org
|1.3mA
| https://sourceforge.net/projects/freertos/
|Stopping SAADC brings the current back to the baseline. It seems that it doesn't need to be disabled entirely.
|
{|
|[https://github.com/JF002/Pinetime JF002/Pinetime]
|-
|-
|[https://github.com/kaythe/pinetime-os kaythe/pinetime-os]
|UART left enabled
|}
|1.25mA
 
|Some bootloaders might leave the UART enabled after they start the application, leading to high current consumption.
|-
|-
! Zephyr
|Edge triggered pin interrupts
| https://www.zephyrproject.org
|0-0.47mA?
| https://github.com/zephyrproject-rtos/zephyr
|It appears that under some configurations, edge triggered interrupts result in a large power drain. One way to avoid this is by using the pin sense mechanism.
|
{|
|[https://github.com/najnesnaj/pinetime-zephyr najnesnaj/pinetime-zephyr]
|-
|[https://github.com/SuperPrower/pinetime_zephyr_sample_fw SuperPrower/pinetime_zephyr_sample_fw]
|-
|-
|[https://github.com/Dejvino/pinetime-hermes-firmware Dejvino/pinetime-hermes-firmware]
|Accelerometer
|0.15mA
|151µA in performance mode, 99µA with performance mode disabled but power saving disabled, 50µA while polling on a high interval (100Hz, average 4 samples), 14µA when running at the lowest possible setting that still counts steps (50Hz, no averaging).
|-
|-
|[https://github.com/endian-albin/pinetime-hypnos endian-albin/pinetime-hypnos]
|HRS sensor is enabled
|}
|0.1mA
 
|The HRS3300 sensor is enabled on power on. Write byte 0x00 to the PDRIVER register (0x0C) to set it in sleep mode.
|-
|-
! mynewt
|BUTTON_OUT left high
| https://mynewt.apache.org/about/
|0.04mA
| https://github.com/apache/mynewt-core
|See [[#Button|Button]] for how to avoid this.
| [https://github.com/lupyuen/pinetime-rust-mynewt lupyuen/pinetime-rust-mynewt]
 
|-
|-
! MbedOS
|SPI flash sleep mode
| https://os.mbed.com
|0.014mA
| https://github.com/ARMmbed/mbed-os
|Sleep mode still consumes power. Put it in [https://datasheet.lcsc.com/szlcsc/2005251035_XTX-XT25F32BSOIGU-S_C558851.pdf#page=38 deep power down mode] to avoid this.
|
{|
|[https://github.com/sethitow/awesome-pinetime sethitow/mbed-pinetime]
|-
|-
|[https://github.com/geoffrey-vl/mbed-pinetime geoffrey.vl/mbed-pinetime]
|SPI, I2C
|(negligible)
|SPI and I2C appear to consume very little power when idle, around 1µA or less.
|}
|}


|-
== Accessory ==
! RIOT
 
| http://riot-os.org/
The following accessory is compatible with the PineTime.
| https://github.com/RIOT-OS/RIOT/
 
| [https://github.com/bosmoment/PineTime-apps bosmoment/PineTime-apps]
=== Watch band ===
 
The PineTime uses a standard 20mm watch band / strap. There is a [https://forum.pine64.org/showthread.php?tid=9392&pid=81902 thread] in the forum discussing this.
 
Due to the watches design. Retention for the spring bars are recessed into the watch. Not all 20mm bands / straps work. This is especially the case for Nato style bands / straps being too thick.
 


|-
Known working bands:
! TinyGo
| https://tinygo.org
| https://github.com/tinygo-org/tinygo
| [https://github.com/aykevl/go-smartwatch aykevl/go-smartwatch]


|-
* [https://www.bisonstrap.com/products/bisonstrap-waterproof-sport-silicone-watch-bands-black?variant=40103305543773 BISONSTRAP 20mm Quick Release Silicone Watch Band] / [https://www.amazon.com/dp/B08XTNKQSJ Amazon US]
! wasp-os (MicroPython)
* DMVEIMAL 20mm Quick Release Watch Band Metal Strap / [https://www.amazon.com/gp/product/B0BGJC8CXG Amazon US]
| https://micropython.org/
* Morsey 20mm Quick Release Watch Band / [https://www.amazon.com/dp/B08DD57SHV Amazon US]
| https://github.com/micropython/micropython
* langley Milanese Watch Band Stainless Steel Wristband Replacement Strap Width 20mm / [https://www.aliexpress.com/item/4000935646261.html Aliexpress] Be sure to select 20mm!
| [https://github.com/daniel-thompson/wasp-os daniel-thompson/wasp-os]
* [https://www.horlogebanden.com/milanaise-mesh-horlogeband-staal/?classid=20+mm Milanese Horlogebandje Fijn Geweven Mesh Staal at horlogebanden.com] Ships to Netherlands and Belgium.


|-
=== Cases ===
! Rust + RTFM
There are no cases for PineTime yet, but some cases for Fitbit are suitable for it. Cases for Fitbit have one microphone hole, which is unnecessary for the PineTime, but otherwise they fit perfectly.
| https://rtfm.rs/
| [https://github.com/rtfm-rs/cortex-m-rtfm rtfm-rs/cortex-m-rtfm]
| https://github.com/dbrgn/pinetime-rtfm/


|-
* [https://www.aliexpress.com/item/1005003150606521.html Soft TPU case for Fitbit Versa 2/Versa Lite from AliExpress]
! Bare Metal
* [https://www.aliexpress.com/item/1005003329398933.html Screen Protector Soft Cover for Fitbit Versa 2 from AliExpress] rather loose fit and collects shower water under it. Also lets dust in, but protects against scratches.
|
|
{|
|https://github.com/xriss/timecake
|-
|https://github.com/Arc13/Pyrus
|}
|
{|
|[https://github.com/xriss/timecake xriss/timecake]
|-
|[https://github.com/Arc13/Pyrus Arc13/Pyrus]
|}
|-
! AdaFruit bootloader
|
| https://github.com/adafruit/Adafruit_nRF52_Bootloader
| [https://github.com/daniel-thompson/wasp-bootloader daniel-thompson/wasp-bootloader]
|-
! Useful drivers
|
| https://github.com/sethitow/mbed-pinetime
| [https://github.com/sethitow/mbed-pinetime/tree/master/drivers https://github.com/sethitow/mbed-pinetime]


|-
The community designed the following cases:
! UI concepts and drawings
* [https://www.thingiverse.com/thing:4172849 PineTime Smart Watch case by dara0s at thingiverse]
|
* [https://www.thingiverse.com/thing:4651462 PineTime dev kit back fix by joaquimorg at thingiverse]
|
* [https://www.thingiverse.com/thing:4763267 PineTime dev kit charging holder v4 by zevix81 at thingiverse]
| [https://gitlab.com/arteeh/pinetimeos arteeh/pinetimeos]
* [https://www.prusaprinters.org/prints/88913-pinetime-charger-case PineTime Charger Travel Case by brett at PrusaPrinters]
|-
! Arduino
| https://youtu.be/4aFDjymXjOw
| https://github.com/atc1441/ATCwatch
| https://github.com/atc1441/ATCwatch
|-
! OTA Update Flasher / DaFlasher
| https://youtu.be/gUVEz-pxhgg
| https://github.com/atc1441/DaFlasherFiles
| https://github.com/atc1441/DaFlasherFiles
|-
|}


== Datasheets and Schematics ==
== Datasheets, Schematics and Certifications ==


=== Schematics ===
=== Schematics ===
* [http://files.pine64.org/doc/PineTime/PineTime%20Schematic-V1.0a-20191103.pdf PineTime Schematic ver1.0a]
* [https://files.pine64.org/doc/PineTime/PineTime%20Schematic-V1.0a-20191103.pdf PineTime Schematic ver1.0a]
* [http://files.pine64.org/doc/PineTime/PineTime%20Port%20Assignment%20rev1.0.pdf PineTime GPIO Port Assignment ver1.0]
* [https://files.pine64.org/doc/PineTime/PineTime%20Port%20Assignment%20rev1.0.pdf PineTime GPIO Port Assignment ver1.0]


Note: The part number for the SPI FLASH in the schematic diagram is not correct, the PineTime features a larger external FLASH device, see below.
Note: The part number for the SPI FLASH in the schematic diagram is not correct, the PineTime features a larger external FLASH device, see below.


=== Chip Datasheets ===
=== Chip Datasheets ===
* NORDIC nRF52832 information:
 
** [http://files.pine64.org/doc/datasheet/pinetime/nRF52832%20product%20brief.pdf nRF52832 Product Brief]
NORDIC nRF52832 information:
** [https://infocenter.nordicsemi.com/pdf/nRF52832_PS_v1.1.pdf nRF52832 Product Specification v1.1]
* [https://files.pine64.org/doc/datasheet/pinetime/nRF52832%20product%20brief.pdf nRF52832 Product Brief]
* ARMv7-M information:
* [https://infocenter.nordicsemi.com/pdf/nRF52832_PS_v1.4.pdf nRF52832 Product Specification v1.4]
** [https://static.docs.arm.com/ddi0403/eb/DDI0403E_B_armv7m_arm.pdf ARMv7-M Architecture Reference Manual]
 
ARMv7-M information:
* [https://developer.arm.com/documentation/ddi0403/ee/?lang=en ARMv7-M Architecture Reference Manual]


=== Component Datasheets ===
=== Component Datasheets ===
* PMU (Power Management Unit) information:
** [http://files.pine64.org/doc/datasheet/pinetime/SGM40561.pdf SGMicro SGM40561 Single Cell Charger Datasheet]
** [http://files.pine64.org/doc/datasheet/pinetime/SGMICRO-SGM2036.pdf SGMicro SGM2036 3.3V Low Power Low Dropout RF Linear Regulator Datasheet]
* SPI Flash information:
** [https://www.elnec.com/en/device/XTX/XT25F32B+%28QuadSPI%29+%5BSOP8-200%5D/ XTX XT25F32B 32Mb(4MB) SPI NOR Flash] (data sheets for this part are hard to find but it acts similar to other QuadSPI SPI NOR Flash such as [https://www.macronix.com/Lists/Datasheet/Attachments/7426/MX25L3233F,%203V,%2032Mb,%20v1.6.pdf Macronix 32Mb(4MB) SPI NOR Flash])
** IDs for XT25F32B are: manufacturer (0x0b), device (0x15), memory type (0x40), density (0x16)
* LCD Panel:
** [http://files.pine64.org/doc/datasheet/pinetime/PineTime%20LCD%20Panel.jpg 1.3" 240x240 IPS LCD Panel Specification for PineTime]
** [https://wiki.pine64.org/images/5/54/ST7789V_v1.6.pdf 11.6" Sitronix LCD Driver/Controller Datasheet]
* Touchpad information:
** [http://files.pine64.org/doc/datasheet/pinetime/PineTime%20Touch%20Panel.jpg Touchpad Specification for PineTimel]
** [http://files.pine64.org/doc/datasheet/pinetime/CST816S数据手册V1.1.pdf 11.6" Hynitron CST816S Capacitive Touch Controller Datasheet in Chinese]
*** [https://wiki.pine64.org/images/5/51/CST816S%E6%95%B0%E6%8D%AE%E6%89%8B%E5%86%8CV1.1.en.pdf English Translation]
* Sensor:
** [http://files.pine64.org/doc/datasheet/pinetime/BST-BMA421-FL000.pdf BOSCH BMA421 Triaxial VAcceleration Sensor Product Brief]
** [https://wiki.pine64.org/images/c/cc/Bst-bma400-ds000.pdf BOSCH BMA400 3-axes ultra-low power accelerometer datasheet]
** [http://files.pine64.org/doc/datasheet/pinetime/HRS3300%20Heart%20Rate%20Sensor.pdf TianYiHeXin HRS3300 PPG Heart Rate Sensor Data Sheet]


= Community =
PMU (Power Management Unit) information:
* [https://forum.pine64.org/forumdisplay.php?fid=134 PineTime forum]
* [https://files.pine64.org/doc/datasheet/pinetime/SGM40561.pdf SGMicro SGM40561 Single Cell Charger Datasheet]
* [https://riot.im/app/#/room/#pinetime64:matrix.org Matrix Channel] (No login required to read)
* [https://files.pine64.org/doc/datasheet/pinetime/SGMICRO-SGM2036.pdf SGMicro SGM2036 3.3V Low Power Low Dropout RF Linear Regulator Datasheet]
* IRC Server: irc.pine64.org Channel: PineTime
 
* [https://t.me/pinetime Telegram group]
SPI Flash information:
* [https://discordapp.com/invite/DgB7kzr Discord server invite link]
* [https://www.elnec.com/en/device/XTX/XT25F32B+%28QuadSPI%29+%5BSOP8-200%5D/ XTX XT25F32B 32Mb(4MB) SPI NOR Flash] (data sheets for this part are hard to find but it acts similar to other QuadSPI SPI NOR Flash such as [https://www.macronix.com/Lists/Datasheet/Attachments/7426/MX25L3233F,%203V,%2032Mb,%20v1.6.pdf Macronix 32Mb(4MB) SPI NOR Flash])
* [https://datasheet.lcsc.com/szlcsc/2005251035_XTX-XT25F32BSOIGU-S_C558851.pdf XTX XT25F32B]
* IDs for XT25F32B are: manufacturer (0x0b), device (0x15), memory type (0x40), density (0x16)
 
LCD Panel:
* [https://files.pine64.org/doc/datasheet/pinetime/PineTime%20LCD%20Panel.jpg 1.3" 240x240 IPS LCD Panel Specification for PineTime]
* [https://wiki.pine64.org/images/5/54/ST7789V_v1.6.pdf 11.6" Sitronix LCD Driver/Controller Datasheet]
 
Touchpad information:
* [https://files.pine64.org/doc/datasheet/pinetime/PineTime%20Touch%20Panel.jpg Touchpad Specification for PineTimel]
* [https://files.pine64.org/doc/datasheet/pinetime/CST816S数据手册V1.1.pdf 11.6" Hynitron CST816S Capacitive Touch Controller Datasheet in Chinese]
* [https://wiki.pine64.org/images/2/2f/CST816S.zip Touch Controller Datasheet en]
 
Sensor:
* [https://datasheet.lcsc.com/lcsc/1912111437_Bosch-Sensortec-BMA425_C437656.pdf BOSCH BMA425 Triaxial Acceleration Sensor Datasheet on current PineTime device]
* [https://files.pine64.org/doc/datasheet/pinetime/BST-BMA421-FL000.pdf BOSCH BMA421 Triaxial Acceleration Sensor Product Brief on early PineTime device]
* [https://files.pine64.org/doc/datasheet/pinetime/HRS3300%20Heart%20Rate%20Sensor.pdf TianYiHeXin HRS3300 PPG Heart Rate Sensor Data Sheet]
 
=== Certificates ===
* [https://files.pine64.org/doc/cert/FCC_Grant_PineTime_2AWAG-PINETIME_DTS.pdf PineTime FCC Certificate]
* [https://files.pine64.org/doc/cert/CTL2203033031-W%20RED%20Certificate.pdf PineTime CE Certificate]
 
=== Manuals ===
* [[:File:PineTime Quick Start Guide.pdf|PineTime Quick Start Guide]]
 
[[Category:PineTime]]

Latest revision as of 05:40, 19 September 2024

The PineTime

The PineTime is a free and open source smartwatch capable of running custom-built open operating systems. Some of the notable features include a heart rate monitor, a week-long battery, and a capacitive touch IPS display that is legible in direct sunlight. It is a fully community driven side-project which anyone can contribute to, allowing you to keep control of your device.

Getting started

Read these first!

The frequently asked question can be found in the article PineTime FAQ.

Default OS

The current default operating system on the PineTime is called InfiniTime, you can find more information about the firmware on its GitHub page. First devkits shipped with a proprietary custom firmware.

You can find a list of available firmware and other software here: PineTime Development

Companion Apps

PineTime/InfiniTime needs a companion app to e.g. upload a firmware, get notifications from a phone, or just get the date/time. Here are some companion apps:

  • Gadgetbridge (Android >= 4.4) - Companion mobile app, supports updating firmware/bootloader, send notifications, etc.
  • Amazfish (SailfishOS, Ubuntu Touch and Linux) - Companion mobile and desktop app, supports updating firmware/bootloader, send notifications, etc.
  • Siglo (Linux) - Companion desktop app.
  • PinetimeFlasher (Windows) - Companion desktop app, only supports flashing firmware.
  • nRFConnect (iOS) - Only supports flashing firmware. The app is closed source and versions after 4.24.3 don't work for the PineTime anymore
  • InfiniLink (iOS) - Companion mobile app in development. Supports updating firmware/bootloader, setting date and time, Apple Music controls, and battery and heart rate data.
  • ITD (Linux)

Specifications

  • Dimensions: 37.5 x 40 x 11mm
  • Weight: 38 grams
  • IP Rating: IP67 (waterproof to 1 meter (sealed edition!))
  • Display:
    • Size: 1.3 inches (33mm) diagonal
    • Type: IPS capacitive touchscreen, RGB 65K colors
    • Display Controller: ST7789
    • Resolution: 240x240 pixels
  • System on Chip: Nordic Semiconductor nRF52832
  • Flash: 512KB with additional 4MB SPI NOR
  • RAM: 64KB
  • Bluetooth: 5.0 (including Bluetooth Low Energy)
  • Sensors: Accelerometer, Heart rate sensor
  • Feedback: Vibration motor
  • Battery: 170-180mAh 3.8V LiPo

Community

Forum

Chat

Developers and coding:

Development efforts

To read more about development on the PineTime, the projects available and more technical details, check out PineTime Development

Useful articles and blog posts

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

Hardware

Display

Note: The factory-default software on the PineTime does not auto-detect the display being disconnected when it has already booted. That can cause garbled output, to fix it just restart the PineTime.

The display is driven using the ST7789 display controller. Use the following pins to drive the screen:

PineTime pin ST7789 pin
LCD_SCK (P0.02) SPI clock
LCD_SDI (P0.03) SPI MOSI
LCD_RS (P0.18) Command/Data pin (CD)
LCD_CS (P0.25) Chip select
LCD_RESET (P0.26) Display reset
LCD_BACKLIGHT_{LOW,MID,HIGH} Backlight (active low)

Notes:

  • Chip select must be held low while driving the display. It must be high when using other SPI devices on the same bus (such as external flash storage) so that the display controller won't respond to the wrong commands.
  • SPI must be used in mode 3. Mode 0 (the default) won't work.
  • LCD_BACKLIGHT_* is used to enable the backlight. Set at least one to low to see anything on the screen.
  • Use SPI at 8MHz (the fastest clock available on the nRF52832) because otherwise refreshing will be super slow.

References:

Adafruit ST7789 driver in cpp

Battery measurement

Reading whether the PineTime has power attached is easy: simply read the charge indication pin (P0.12). When it is high it is running on battery, when it is low it is charging.

Reading the battery voltage is a bit harder. For that you can use the battery voltage pin on P0.31 (AIN7). The returned value is 12 bits, which means it is 0..4095. You can get the measured voltage with the following formula, assuming a reference voltage of 3.3V (this is configurable in the ADC):

adcVoltage = adcValue / (4095 / 3.3)

The measured voltage is actually half of the actual battery voltage, because the ADC is connected between a voltage divider where both resistors are 1MΩ. This can be corrected by multiplying the value:

batteryVoltage = adcValue * 2 / (4095 / 3.3)

It's often better to avoid floating point values on embedded systems and in this case there is no reason to use float at all, we can just represent the value in millivolts. Therefore the formula can be simplified to:

batteryVoltage = adcValue * 2000 / (4095 / 3.3)
batteryVoltage = adcValue * 2000 / 1241

Converting this voltage to an estimated capacity in percent requires a more complicated algorithm, because Lithium-ion batteries have a non-linear discharge curve.

Button

The button on the side of the PineTime is disabled by default. To enable it, drive the button out pin (P0.15) high.

While enabled, the button in pin (P0.13) will be high when the button is pressed, and low when it is not pressed.

Note that the button consumes around 34µA when P0.15 is left high. To reduce current consumption, set it to low most of the time and only set it to high shortly before reading it. The button needs a short time to give good outputs though, setting P0.15 high at least four times in a row seems to result in enough delay that P0.13 has a stable output.

Touch panel

The touch panel is controlled by a Hynitron CST816S chips. Unfortunately, there is not much information about this chip on the internet apart from the datasheet below and a reference driver. This is enough to implement a basic driver, but crucial information needed to implement advanced functionalities are missing (I²C protocol and registers, timings, power modes,...).

Pins

  • P0.10 : Reset
  • P0.28 : Interrupt (signal to the CPU when a touch event is detected)
  • P0.06 : I²C SDA
  • P0.07 : I²C SCL

I²C

  • Device address : 0x15
  • Frequency : from 10Khz to 400Khz

NOTE: The controller goes to sleep when no event is detected. In sleep mode, the controller does not communicate on the I²C bus (it appears disconnected). So, for the communication to work, you need to tap on the screen so that the chip wakes-up.

NOTE: The I²C bus, also known as TWI bus, has known issues, make sure to write your TWI driver with timeouts.

Touch events

Touch information is available from the 63 first registers of the controller. Remember: the device is in sleep mode when no touch event is detected. It means that you can read the register only when the touch controller detected an event. You can use the Interrupt pin to detect such event in the software.

These 63 bytes contain up to 10 touch point (X, Y, event type, pressure,...) :

Byte Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
0 ?
1 GestureID : (Gesture code ,

0x00: no gesture,

0x01: Slide down,

0x02: Slide up,

0x03: Slide left,

0x04: Slide right,

0x05: Single click,

0x0B: Double click,

0x0C: Long press)

2 ? Number of touch points
3 Event (0 = Down, 1 = Up, 2 = Contact) ? X (MSB) coordinate
4 X (LSB) coordinate
5 ? Touch ID Y (MSB) coordinate
6 Y (LSB) coordinate
7 Pressure (?)
8 Miscellaneous (?)

Bytes 3 to 8 are repeated 10 times (10*6 + 3 = 63 bytes).

NOTES

  • The touch controller seems to report only 1 touch point
  • Fields X, Y, Number of touch points and touch ID are updated. The others are always 0.

Registers

The reference driver specifies some registers and value, but there is no information about them:

Register Address Description
HYN_REG_INT_CNT 0x8F
HYN_REG_FLOW_WORK_CNT 0x91
HYN_REG_WORKMODE 0x00 0 = WORK, 0x40 = FACTORY
HYN_REG_CHIP_ID 0xA3
HYN_REG_CHIP_ID2 0x9F
HYN_REG_POWER_MODE 0xA5 0x03 = SLEEP (reset the touchpanel using the reset pin before using this register : pin_low, delay 5ms, pin_high, delay 50ms then write 3 to register 0xA5)
HYN_REG_FW_VER 0xA6
HYN_REG_VENDOR_ID 0xA8
HYN_REG_LCD_BUSY_NUM 0xAB
HYN_REG_FACE_DEC_MODE_EN 0xB0
HYN_REG_GLOVE_MODE_EN 0xC0
HYN_REG_COVER_MODE_EN 0xC1
HYN_REG_CHARGER_MODE_EN 0x8B
HYN_REG_GESTURE_EN 0xD0
HYN_REG_GESTURE_OUTPUT_ADDRESS 0xD3
HYN_REG_ESD_SATURATE 0xED 0xED

WARNING : Writing the SLEEP command (write 0x05 in HYN_REG_POWER_MODE) seems to freeze the controller (it returns only static values) until the battery is totally drained and the whole system reset. Analysis and debugging is more than welcome!

Accelerometer

The on board accelerometer in devices shipped before July 2021 is a Bosch BMA421, connected to the I2C bus. Devices shipped after July 2021 use a Bosch BMA425 accelerometer.

Pins

  • P0.06 : I²C SDA
  • P0.07 : I²C SCL
  • P0.08 : Interrupt

I2C Device address : 0x18

Reducing power consumption

The PineTime appears to be able to sleep with a current consumption of only 66µA.

To investigate current consumption, it's a good idea to disable everything possible to get the lowest current consumption possible, and then re-enable things one by one. Here is one way to get a baseline current consumption of 60µA, as measured from the 3.3V pin with the battery disconnected:

  • Enable the DC/DC regulator. This doesn't affect the current consumption while sleeping, but almost halves the runtime current consumption.
  • Use the low-frequency (32.768kHz) oscillator.
  • Leave all pins in their default state, except for P0.05 (SPI CS) and P0.25 (LCD CS) which should be configured as an output and set to high.
  • Put the heart rate sensor in sleep mode by setting the PDRIVER (0x0C) register to 0, see the HRS3300 datasheet for details.
  • Put the SPI flash in deep power-down mode by setting flash CS high, then low, then writing the byte 0xb9 on the SPI bus, and then setting flash CS high again.
  • Sleep in a loop, using WFE or WFI (if you're using the Nordic SoftDevice, call sd_app_evt_wait instead).

Here are some current consumption statistics (current consumed in addition to the baseline power), roughly ordered from large to small:

Source Current Notes
SWD 3.05mA Power cycle the chip after programming to avoid this, it can hide other inefficiencies.
LCD 5.61mA Set the LCD to sleep mode when not used, using SLPIN.
Backlight high 12.27mA
Backlight mid 5.51mA
Backlight low 1.83mA
ADC left enabled 1.3mA Stopping SAADC brings the current back to the baseline. It seems that it doesn't need to be disabled entirely.
UART left enabled 1.25mA Some bootloaders might leave the UART enabled after they start the application, leading to high current consumption.
Edge triggered pin interrupts 0-0.47mA? It appears that under some configurations, edge triggered interrupts result in a large power drain. One way to avoid this is by using the pin sense mechanism.
Accelerometer 0.15mA 151µA in performance mode, 99µA with performance mode disabled but power saving disabled, 50µA while polling on a high interval (100Hz, average 4 samples), 14µA when running at the lowest possible setting that still counts steps (50Hz, no averaging).
HRS sensor is enabled 0.1mA The HRS3300 sensor is enabled on power on. Write byte 0x00 to the PDRIVER register (0x0C) to set it in sleep mode.
BUTTON_OUT left high 0.04mA See Button for how to avoid this.
SPI flash sleep mode 0.014mA Sleep mode still consumes power. Put it in deep power down mode to avoid this.
SPI, I2C (negligible) SPI and I2C appear to consume very little power when idle, around 1µA or less.

Accessory

The following accessory is compatible with the PineTime.

Watch band

The PineTime uses a standard 20mm watch band / strap. There is a thread in the forum discussing this.

Due to the watches design. Retention for the spring bars are recessed into the watch. Not all 20mm bands / straps work. This is especially the case for Nato style bands / straps being too thick.


Known working bands:

Cases

There are no cases for PineTime yet, but some cases for Fitbit are suitable for it. Cases for Fitbit have one microphone hole, which is unnecessary for the PineTime, but otherwise they fit perfectly.

The community designed the following cases:

Datasheets, Schematics and Certifications

Schematics

Note: The part number for the SPI FLASH in the schematic diagram is not correct, the PineTime features a larger external FLASH device, see below.

Chip Datasheets

NORDIC nRF52832 information:

ARMv7-M information:

Component Datasheets

PMU (Power Management Unit) information:

SPI Flash information:

LCD Panel:

Touchpad information:

Sensor:

Certificates

Manuals