https://wiki.pine64.org/api.php?action=feedcontributions&feedformat=atom&user=Avamander 2026-04-06T09:09:04Z User contributions MediaWiki 1.37.1 https://wiki.pine64.org/index.php?title=PineTime_Hardware_Wishlist&diff=15585 2023-01-15T14:42:54Z

<p>Avamander: </p> <hr /> <div>This page contains a list of things people wish PineTime did differently<br /> <br /> === Hardware ===<br /> <br /> * Other display technology could be explored.<br /> ** E-ink<br /> *** Still images require no power to maintain<br /> **[//en.Wikipedia.org/wiki/Transflective_liquid-crystal_display A transflective LCD]<br /> *** Increased readability in bright daylight<br /> **[//en.wikipedia.org/wiki/OLED OLED]<br /> *** Self-emissive display (pixels emit their own light)<br /> *** Allows for lower power usage with mostly black screens<br /> *** Allows for low power visual notifications (imagine an always-on small red square in the corner to indicate a notification)<br /> * Touchscreen with configurable sensitivity<br /> ** Ideal for gloved fingers and water droplet resistance<br /> ** Preferably it should remain capacitive, as a resistive touchscreen would have too many trade-offs.<br /> * A slightly bigger 256×256 pixel display<br /> ** This resolution is preferable for its binary alignment for low-level simplicity<br /> ** It has the property that its X and Y coordinates are each addressable with a single byte, with no bounds checking<br /> ** Its total number of pixels is a power of 2 (65536), and each pixel is addressable with exactly 2 bytes.<br /> ** The [http://Pelulamu.net/ibniz IBNIZ (Ideally Bare Numeric Impression giZmo) virtual machine], designed for minimalist demoscene graphics, has chosen 256×256 for its virtual display specifically for code efficiency.<br /> *** If PineTime also chose 256×256 then it would be a target platform for unclipped IBNIZ demoscene programmes, which would be really fun to play around with on one's wrist!<br /> * Full screen refresh is very slow<br /> ** A full 16-bit redraw on the display takes at worst 120ms, which is 8Hz<br /> ** Modest optimization is possible by adopting 12-bit color<br /> ** A smooth scrolling/usage/animation experience would be 30Hz minimum, preferably 60hz<br /> ** Display redraw is currently bottlenecked by the nRF52832 maximum SPI clock (8MHz).<br /> ** The nRF528(33/40) has one high speed SPI master which supports 32MHz, still well below the ST7789 maximum<br /> ** Parallel data transfer could be an option, but using more GPIOs (which don't look available)<br /> * Some sort of scroll wheel (and possibly button combination) would be nice as an additional input method<br /> * Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)<br /> * Wireless charging, or Qi Charging capability<br /> * Different MCU with more RAM and ROM, higher clock<br /> ** nRF5840 update<br /> *** 32MHz HS SPI, QuadSPI<br /> *** CryptoCell + Secure Key Storage<br /> *** More RAM, a coprocessor<br /> *** The possibility to expose USB through power pins<br /> ** Ox64/BL808<br /> *** Open hardware RISC-V based MCU<br /> *** Significant jump in performance<br /> *** Significant jump in memory and storage, allowing for more features and better UI's<br /> ** Possibly a pre-certified MCU module with a ceramic antenna<br /> * Version without sensors but maybe bigger battery<br /> * Pins on the programmer connector to allow UART while developing (currently there is a TX test point on PCB). (Note: There's ARM SemiHosting, ITM and Segger RTT that fulfil this purpose for most)<br /> * Connect SDO of ST7889 LCD controller to MCU<br /> ** Allows MCU to execute READ commands<br /> ** Possibility of leveraging ST7889 RAM to save MCU RAM?<br /> * LCD must be centered on case. Currently is not and watchfaces seems different when clock is put on the other wrist.<br /> * A NFC antenna around the case, connected to the NFC pins.<br /> * Used sensors should be NDA-free and preferably also blob-free for easier development<br /> ** Possibly replace BMA421 accelerometer with a magnetometer + gyroscope + accelerometer combination<br /> *** The BMA421 doesn't have a public datasheet<br /> *** Special attention should be paid to advanced features, such as step counting integration or flick detection.<br /> * PineTime SoC could support USB or have a FTDI chip with the relevant pins exposed<br /> ** It could allow flashing a sealed device, just like Arduinos work.<br /> ** Alternatively, an USB-C port could be added that provides these features. <br /> * A bigger pulldown resistor for the power button<br /> ** 100k still leaks a noticeable amount of power when the button is always on.<br /> * Ceramic Bluetooth antenna for better signal reception<br /> * An external RTC circuit<br /> ** Allows the main MCU go to deep-sleep while retaining time.<br /> ** Allows time retention through MCU reset.<br /> * Ultra low quiescent current PMIC<br /> ** In theory could provide a hard reset capability based on button press<br /> ** Better deep sleep/shipping/storage/off lifetime<br /> *** A nano-power system timer IC could in theory provide a RTC, MOSFET-controlled deep sleep, watchdog timer and button-controlled reset<br /> ** Built-in &quot;fuel gauge&quot; for better estimation of battery capacity<br /> * Improved haptic or audible feedback<br /> ** E.g. small Piezo buzzer<br /> ** Use case would be for very short beeps (think old-school casio watch) as notification.<br /> ** Of course developers can PWM other frequency to make it sing, but piezos tend to be shrill.<br /> * A built-in microphone<br /> ** Would allow phone call functionality to be built into the watch.<br /> ** Could potentially allow for speech recognition for text input.<br /> ** Direct access to the external (flash) storage<br /> ** Only a small jump in price<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_Hardware_Wishlist&diff=15583 2023-01-15T14:07:23Z

<p>Avamander: </p> <hr /> <div>This page contains a list of things people wish PineTime did differently<br /> <br /> === Hardware ===<br /> <br /> * Other display technology could be explored.<br /> ** E-ink<br /> *** Still images require no power to maintain<br /> **[//en.Wikipedia.org/wiki/Transflective_liquid-crystal_display A transflective LCD]<br /> *** Increased readability in bright daylight<br /> **[//en.wikipedia.org/wiki/OLED OLED]<br /> *** Self-emissive display (pixels emit their own light)<br /> *** Allows for lower power usage with mostly black screens<br /> *** Allows for low power visual notifications (imagine an always-on small red square in the corner to indicate a notification)<br /> * Touchscreen with configurable sensitivity<br /> ** Ideal for gloved fingers and water droplet resistance<br /> ** Preferably it should remain capacitive, as a resistive touchscreen would have too many trade-offs.<br /> * A slightly bigger 256×256 pixel display<br /> ** This resolution is preferable for its binary alignment for low-level simplicity<br /> ** It has the property that its X and Y coordinates are each addressable with a single byte, with no bounds checking<br /> ** Its total number of pixels is a power of 2 (65536), and each pixel is addressable with exactly 2 bytes.<br /> ** The [http://Pelulamu.net/ibniz IBNIZ (Ideally Bare Numeric Impression giZmo) virtual machine], designed for minimalist demoscene graphics, has chosen 256×256 for its virtual display specifically for code efficiency.<br /> ** If PineTime also chose 256×256 then it would be a target platform for unclipped IBNIZ demoscene programmes, which would be really fun to play around with on one's wrist!<br /> * Full screen refresh is very slow<br /> ** A full 16-bit redraw on the display takes at worst 120ms, which is 8Hz<br /> ** Modest optimization is possible by adopting 12-bit color<br /> ** A smooth scrolling/usage/animation experience would be 30Hz minimum, preferably 60hz<br /> ** Display redraw is currently bottlenecked by the nRF52832 maximum SPI clock (8MHz).<br /> ** The nRF528(33/40) has one high speed SPI master which supports 32MHz, still well below the ST7789 maximum<br /> ** Parallel data transfer could be an option, but using more GPIOs (which don't look available)<br /> * Some sort of scroll wheel (and possibly button combination) would be nice as an additional input method<br /> * Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)<br /> * Wireless charging, or Qi Charging capability<br /> * Different MCU with more RAM and ROM, higher clock<br /> ** nRF5840 update<br /> *** 32MHz HS SPI, QuadSPI<br /> *** CryptoCell + Secure Key Storage<br /> *** More RAM, a coprocessor<br /> *** The possibility to expose USB through power pins<br /> ** Ox64/BL808<br /> *** Open hardware RISC-V based MCU<br /> *** Significant jump in performance<br /> *** Significant jump in memory and storage, allowing for more features and better UI's<br /> ** Possibly a pre-certified MCU module with a ceramic antenna<br /> * Version without sensors but maybe bigger battery<br /> * Pins on the programmer connector to allow UART while developing (currently there is a TX test point on PCB). (Note: There's ARM SemiHosting, ITM and Segger RTT that fulfil this purpose for most)<br /> * Connect SDO of ST7889 LCD controller to MCU<br /> ** Allows MCU to execute READ commands<br /> ** Possibility of leveraging ST7889 RAM to save MCU RAM?<br /> * LCD must be centered on case. Currently is not and watchfaces seems different when clock is put on the other wrist.<br /> * A NFC antenna around the case, connected to the NFC pins.<br /> * Used sensors should be NDA-free and preferably also blob-free for easier development<br /> ** Possibly replace BMA421 accelerometer with a magnetometer + gyroscope + accelerometer combination<br /> *** The BMA421 doesn't have a public datasheet<br /> *** Special attention should be paid to advanced features, such as step counting integration or flick detection.<br /> * PineTime SoC could support USB or have a FTDI chip with the relevant pins exposed<br /> ** It could allow flashing a sealed device, just like Arduinos work.<br /> ** Alternatively, an USB-C port could be added that provides these features. <br /> * A bigger pulldown resistor for the power button<br /> ** 100k still leaks a noticeable amount of power when the button is always on.<br /> * Ceramic Bluetooth antenna for better signal reception<br /> * An external RTC circuit<br /> ** Allows the main MCU go to deep-sleep while retaining time.<br /> ** Allows time retention through MCU reset.<br /> * Ultra low quiescent current PMIC<br /> ** In theory could provide a hard reset capability based on button press<br /> ** Better deep sleep/shipping/storage/off lifetime<br /> *** A nano-power system timer IC could in theory provide a RTC, MOSFET-controlled deep sleep, watchdog timer and button-controlled reset<br /> ** Built-in &quot;fuel gauge&quot; for better estimation of battery capacity<br /> * Improved haptic or audible feedback<br /> ** E.g. small Piezo buzzer<br /> ** Use case would be for very short beeps (think old-school casio watch) as notification.<br /> ** Of course developers can PWM other frequency to make it sing, but piezos tend to be shrill.<br /> * A built-in microphone<br /> ** Would allow phone call functionality to be built into the watch.<br /> ** Could potentially allow for speech recognition for text input.<br /> ** Direct access to the external (flash) storage<br /> ** Only a small jump in price<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_Hardware_Wishlist&diff=15582 2023-01-15T14:06:58Z

<p>Avamander: </p> <hr /> <div>This page contains a list of things people wish PineTime did differently<br /> <br /> === Hardware ===<br /> <br /> * Other display technology could be explored.<br /> ** E-ink<br /> *** Still images require no power to maintain<br /> **[//en.Wikipedia.org/wiki/Transflective_liquid-crystal_display A transflective LCD]<br /> *** Increased readability in bright daylight<br /> **[//en.wikipedia.org/wiki/OLED OLED]<br /> *** Self-emissive display (pixels emit their own light)<br /> *** Allows for lower power usage with mostly black screens<br /> *** Allows for low power visual notifications (imagine an always-on small red square in the corner to indicate a notification)<br /> * Touchscreen with configurable sensitivity<br /> ** Ideal for gloved fingers and water droplet resistance<br /> ** Preferably it should remain capacitive, as a resistive touchscreen would have too many trade-offs.<br /> * A slightly bigger 256×256 pixel display<br /> ** This resolution is preferable for its binary alignment for low-level simplicity<br /> ** It has the property that its X and Y coordinates are each addressable with a single byte, with no bounds checking<br /> ** Its total number of pixels is a power of 2 (65536), and each pixel is addressable with exactly 2 bytes.<br /> ** The [http://Pelulamu.net/ibniz IBNIZ (Ideally Bare Numeric Impression giZmo) virtual machine], designed for minimalist demoscene graphics, has chosen 256×256 for its virtual display specifically for code efficiency.<br /> ** If PineTime also chose 256×256 then it would be a target platform for unclipped IBNIZ demoscene programmes, which would be really fun to play around with on one's wrist!<br /> * Full screen refresh is very slow<br /> ** A full 16-bit redraw on the display takes at worst 120ms, which is 8Hz<br /> ** Modest optimization is possible by adopting 12-bit color<br /> ** A smooth scrolling/usage/animation experience would be 30Hz minimum, preferably 60hz<br /> ** Display redraw is currently bottlenecked by the nRF52832 maximum SPI clock (8MHz).<br /> ** The nRF528(33/40) has one high speed SPI master which supports 32MHz, still well below the ST7789 maximum<br /> ** Parallel data transfer could be an option, but using more GPIOs (which don't look available)<br /> * Some sort of scroll wheel (and possibly button combination) would be nice as an additional input method<br /> * Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)<br /> * Wireless charging, or Qi Charging capability<br /> * Different MCU with more RAM and ROM, higher clock<br /> ** nRF5840 update<br /> *** 32MHz HS SPI, QuadSPI<br /> *** CryptoCell + Secure Key Storage<br /> *** More RAM, a coprocessor<br /> *** The possibility to expose USB through power pins<br /> ** Ox64/BL808<br /> *** Open hardware RISC-V based MCU<br /> *** Significant jump in performance<br /> *** Significant jump in memory and storage, allowing for more features and better UI's<br /> * Preferably a pre-certified MCU module with a ceramic antenna<br /> * Version without sensors but maybe bigger battery<br /> * Pins on the programmer connector to allow UART while developing (currently there is a TX test point on PCB). (Note: There's ARM SemiHosting, ITM and Segger RTT that fulfil this purpose for most)<br /> * Connect SDO of ST7889 LCD controller to MCU<br /> ** Allows MCU to execute READ commands<br /> ** Possibility of leveraging ST7889 RAM to save MCU RAM?<br /> * LCD must be centered on case. Currently is not and watchfaces seems different when clock is put on the other wrist.<br /> * A NFC antenna around the case, connected to the NFC pins.<br /> * Used sensors should be NDA-free and preferably also blob-free for easier development<br /> ** Possibly replace BMA421 accelerometer with a magnetometer + gyroscope + accelerometer combination<br /> *** The BMA421 doesn't have a public datasheet<br /> *** Special attention should be paid to advanced features, such as step counting integration or flick detection.<br /> * PineTime SoC could support USB or have a FTDI chip with the relevant pins exposed<br /> ** It could allow flashing a sealed device, just like Arduinos work.<br /> ** Alternatively, an USB-C port could be added that provides these features. <br /> * A bigger pulldown resistor for the power button<br /> ** 100k still leaks a noticeable amount of power when the button is always on.<br /> * Ceramic Bluetooth antenna for better signal reception<br /> * An external RTC circuit<br /> ** Allows the main MCU go to deep-sleep while retaining time.<br /> ** Allows time retention through MCU reset.<br /> * Ultra low quiescent current PMIC<br /> ** In theory could provide a hard reset capability based on button press<br /> ** Better deep sleep/shipping/storage/off lifetime<br /> *** A nano-power system timer IC could in theory provide a RTC, MOSFET-controlled deep sleep, watchdog timer and button-controlled reset<br /> ** Built-in &quot;fuel gauge&quot; for better estimation of battery capacity<br /> * Improved haptic or audible feedback<br /> ** E.g. small Piezo buzzer<br /> ** Use case would be for very short beeps (think old-school casio watch) as notification.<br /> ** Of course developers can PWM other frequency to make it sing, but piezos tend to be shrill.<br /> * A built-in microphone<br /> ** Would allow phone call functionality to be built into the watch.<br /> ** Could potentially allow for speech recognition for text input.<br /> ** Direct access to the external (flash) storage<br /> ** Only a small jump in price<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_Hardware_Wishlist&diff=14705 2022-11-16T23:05:01Z

<p>Avamander: </p> <hr /> <div>This page contains a list of things people wish PineTime did differently<br /> <br /> === Hardware ===<br /> <br /> * Long pressing the button should power-cycle the watch without any software being involved<br /> * Other display technology could be explored.<br /> ** E-ink<br /> *** Still images require no power to maintain<br /> **[//en.Wikipedia.org/wiki/Transflective_liquid-crystal_display A transflective LCD]<br /> *** Increased readability in bright daylight<br /> **[//en.wikipedia.org/wiki/OLED OLED]<br /> *** Self-emissive display (pixels emit their own light)<br /> *** Allows for lower power usage with mostly black screens<br /> *** Allows for low power visual notifications (imagine an always-on small red square in the corner to indicate a notification)<br /> * Touchscreen with configurable sensitivity<br /> ** Ideal for gloved fingers and water droplet resistance<br /> ** Preferably it should remain capacitive, as a resistive touchscreen would have too many trade-offs.<br /> * A slightly bigger 256×256 pixel display<br /> ** This resolution is preferable for its binary alignment for low-level simplicity<br /> ** It has the property that its X and Y coordinates are each addressable with a single byte, with no bounds checking<br /> ** Its total number of pixels is a power of 2 (65536), and each pixel is addressable with exactly 2 bytes.<br /> ** The [http://Pelulamu.net/ibniz IBNIZ (Ideally Bare Numeric Impression giZmo) virtual machine], designed for minimalist demoscene graphics, has chosen 256×256 for its virtual display specifically for code efficiency.<br /> ** If PineTime also chose 256×256 then it would be a target platform for unclipped IBNIZ demoscene programmes, which would be really fun to play around with on one's wrist!<br /> * Full screen refresh is very slow<br /> ** A full 16-bit redraw on the display takes at worst 120ms, which is 8Hz<br /> ** Modest optimization is possible by adopting 12-bit color<br /> ** A smooth scrolling/usage/animation experience would be 30Hz minimum, preferably 60hz<br /> ** Display redraw is currently bottlenecked by the nRF52832 maximum SPI clock (8MHz).<br /> ** The nRF528(33/40) has one high speed SPI master which supports 32MHz, still well below the ST7789 maximum<br /> ** Parallel data transfer could be an option, but using more GPIOs (which don't look available)<br /> * Some sort of scroll wheel would be nice for convenience.<br /> * Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)<br /> * Wireless charging, or Qi Charging capability<br /> * Different MCU with more RAM and ROM, higher clock<br /> ** nRF5840 update<br /> *** 32MHz HS SPI, QuadSPI<br /> *** CryptoCell + Secure Key Storage<br /> *** More RAM, a coprocessor<br /> *** The possibility to expose USB through power pins<br /> ** Ox64/BL808<br /> *** Open hardware RISC-V based MCU<br /> *** Significant jump in performance<br /> *** Significant jump in memory and storage, allowing for more features and better UI's<br /> * Preferably a pre-certified MCU module with a ceramic antenna<br /> * Version without sensors but maybe bigger battery<br /> * Pins on the programmer connector to allow UART while developing (currently there is a TX test point on PCB). (Note: There's ARM SemiHosting, ITM and Segger RTT)<br /> * Connect SDO of ST7889 LCD controller to MCU.<br /> ** Allows MCU to execute READ commands<br /> ** Possibility of leveraging ST7889 RAM to save MCU RAM?<br /> * LCD must be centered on case. Currently is not and watchfaces seems different when clock is put on the other wrist.<br /> * A NFC antenna around the case, connected to the NFC pins.<br /> * Used sensors should be NDA-free and preferably also blob-free for easier development<br /> ** Possibly replace BMA421 accelerometer<br /> *** The BMA421 doesn't have a public datasheet<br /> *** Special attention should be paid to advanced features, such as step counting integration or flick detection.<br /> * PineTime SoC could support USB or have a FTDI chip with the relevant pins exposed.<br /> ** It could allow flashing a sealed device, just like Arduinos work.<br /> ** Alternatively, an USB-C port could be added that provides these features. <br /> * A bigger pulldown resistor for the power button<br /> ** 100k still leaks a noticeable amount of power when the button is always on.<br /> * Ceramic Bluetooth antenna for better signal reception<br /> * An external RTC circuit<br /> ** Allows the main MCU go to deep-sleep while retaining time.<br /> ** Allows time retention through MCU reset.<br /> * Ultra low quiescent current PMIC<br /> ** In theory could provide a hard reset capability based on button press<br /> ** Better deep sleep/shipping/storage/off lifetime<br /> *** A nano-power system timer IC could in theory provide a RTC, MOSFET-controlled deep sleep, watchdog timer and button-controlled reset<br /> ** Built-in &quot;fuel gauge&quot; for better estimation of battery capacity<br /> * Improved haptic or audible feedback<br /> ** E.g. small Piezo buzzer<br /> ** Use case would be for very short beeps (think old-school casio watch) as notification.<br /> ** Of course developers can PWM other frequency to make it sing, but piezos tend to be shrill.<br /> * A built-in microphone<br /> ** Would allow phone call functionality to be built into the watch.<br /> ** Could potentially allow for speech recognition for text input.<br /> ** Direct access to the external (flash) storage<br /> ** Only a small jump in price<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime&diff=12181 2022-01-05T22:51:58Z

<p>Avamander: /* Companion Apps */</p> <hr /> <div>[[File:Pinetime.png|400px|thumb|right|The PineTime]]<br /> <br /> 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.<br /> <br /> == Frequently asked questions / Getting started ==<br /> <br /> '''Read these first!'''<br /> <br /> * [[Upgrade PineTime to InfiniTime 1.0.0|Upgrading your new PineTime to InfiniTime 1.0.0]]<br /> * [[PineTime FAQ| Frequently Asked Questions about the PineTime]]<br /> * [[PineTime Devkit Wiring]]<br /> * [[Reprogramming the PineTime|Reprogramming the PineTime (development kit)]]<br /> * [[Switching your PineTime between InfiniTime and Wasp-os]]<br /> <br /> == Default OS ==<br /> <br /> 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.<br /> <br /> You can find a list of available firmware and other software here: [[PineTime Development]]<br /> <br /> == Companion Apps ==<br /> <br /> PineTime/InfiniTime needs a companion app to e.g. upload a firmware, get notifications from a phone, or just get the date/time. <br /> Here are some companion apps:<br /> <br /> * [https://www.gadgetbridge.org Gadgetbridge] (Android &gt;= 4.4) - Companion mobile app, supports updating firmware/bootloader, send notifications, etc.<br /> * [https://openrepos.net/content/piggz/amazfish Amazfish] (SailfishOS and Linux) - Companion mobile and desktop app, supports updating firmware/bootloader, send notifications, etc.<br /> * [https://github.com/alexr4535/siglo Siglo] (Linux) - Companion desktop app.<br /> * [https://github.com/ZephyrLabs/PinetimeFlasher PinetimeFlasher] (Windows) - Companion desktop app, only supports flashing firmware.<br /> * [https://apps.apple.com/us/app/nrf-connect-for-mobile/id1054362403 nRFConnect] (iOS) - Only supports flashing firmware.<br /> * [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.<br /> * [https://gitea.arsenm.dev/Arsen6331/itd itd] (Linux)<br /> <br /> == Short overview / Specifications ==<br /> '''Dimensions:''' 37.5 x 40 x 11mm &lt;br&gt;<br /> '''Weight:''' 38 grams &lt;br&gt;<br /> '''IP Rating:''' IP67 (waterproof to 1 meter (sealed edition!)) &lt;br&gt;<br /> '''Display:'''<br /> : '''Size:''' 1.3 inches (33mm) diagonal<br /> : '''Type:''' IPS capacitive touchscreen, RGB 65K colors<br /> : '''Display Controller:''' ST7789<br /> : '''Resolution:''' 240x240 pixels &lt;br&gt;<br /> '''System on Chip:''' Nordic Semiconductor nRF52832 &lt;br&gt;<br /> '''Flash:''' 512KB with additional 4MB SPI NOR &lt;br&gt;<br /> '''RAM:''' 64KB &lt;br&gt;<br /> '''Bluetooth:''' [[PineTime_Bluetooth|5.0 (including Bluetooth Low Energy)]] &lt;br&gt;<br /> '''Sensors:''' Accelerometer, Heart rate sensor &lt;br&gt;<br /> '''Feedback:''' Vibration motor &lt;br&gt;<br /> '''Battery:''' 170-180mAh 3.8V LiPo<br /> <br /> = Community =<br /> <br /> == Forum ==<br /> * [https://forum.pine64.org/forumdisplay.php?fid=134 PineTime forum]<br /> <br /> == Chat ==<br /> * [https://app.element.io/#/room/#pinetime:matrix.org Matrix Channel] (No login required to read)<br /> * IRC Server: [ircs://irc.pine64.org#pinetime irc.pine64.org] Channel: PineTime<br /> * [https://t.me/pinetime Telegram group]<br /> * [https://discordapp.com/invite/DgB7kzr Discord server invite link]<br /> <br /> === Developers and coding ===<br /> * [https://app.element.io/#/room/#pinetime-dev:matrix.org Matrix Channel] (No login required to read)<br /> * [https://t.me/pinetime_dev Telegram group]<br /> * [https://discordapp.com/invite/DgB7kzr Discord server invite link]<br /> <br /> == Development efforts ==<br /> <br /> To read more about development on the PineTime, the projects available and more technical details, check out [[PineTime Development]]<br /> <br /> == Useful articles and blog posts == <br /> <br /> 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.<br /> <br /> * [https://www.ncartron.org/one-week-with-my-pinetime---a-feedback.html Using the PineTime in production (January 2021)]<br /> * [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]<br /> * [https://lupyuen.github.io/articles/building-a-rust-driver-for-pinetimes-touch-controller Building a Rust Driver for PineTime’s Touch Controller]<br /> * [https://lupyuen.github.io/articles/porting-druid-rust-widgets-to-pinetime-smart-watch Porting (druid) Rust Widgets to PineTime Smart Watch]<br /> * [https://lupyuen.github.io/articles/optimising-pinetimes-display-driver-with-rust-and-mynewt Optimising PineTime’s Display Driver with Rust and Mynewt]<br /> * [https://electronut.in/getting-started-with-zephyr-rtos-on-nordic-nrf52832-hackable/ Getting Started with Zephyr RTOS on Nordic nRF52832 hackaBLE]<br /> * [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]<br /> * [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]<br /> * [https://www.nrbtech.io/blog/2020/1/4/using-clion-for-nordic-nrf52-projects Using CLion for Nordic nRF52 projects]<br /> * [https://dev.to/aaronc81/flashing-your-pinetime-using-an-st-link-and-openocd-54dd Flashing your PineTime using an ST-Link and OpenOCD]<br /> * [https://zephyrlabs.github.io/Watchfaces/ Zephyrlabs: just a bunch of watchfaces made for the pinetime]<br /> * [https://pankajraghav.com/2021/04/03/PINETIME-STOPCLOCK.html Creating a stopwatch in Pinetime (with Infinitime)]<br /> <br /> = Hardware =<br /> <br /> == Display ==<br /> <br /> 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.<br /> <br /> The display is driven using the ST7789 display controller. Use the following pins to drive the screen:<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! PineTime pin<br /> ! ST7789 pin<br /> |-<br /> | LCD_SCK (P0.02)<br /> | SPI clock<br /> |-<br /> | LCD_SDI (P0.03)<br /> | SPI MOSI<br /> |-<br /> | LCD_RS (P0.18)<br /> | Command/Data pin (CD)<br /> |-<br /> | LCD_CS (P0.25)<br /> | Chip select<br /> |-<br /> | LCD_RESET (P0.26)<br /> | Display reset<br /> |-<br /> | LCD_BACKLIGHT_{LOW,MID,HIGH}<br /> | Backlight (active low)<br /> |}<br /> <br /> Notes:<br /> <br /> * 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.<br /> * SPI must be used in mode 3. Mode 0 (the default) won't work.<br /> * LCD_DISPLAY_* is used to enable the backlight. Set at least one to low to see anything on the screen.<br /> * Use SPI at 8MHz (the fastest clock available on the nRF52832) because otherwise refreshing will be super slow.<br /> <br /> '''References''':<br /> <br /> [https://github.com/adafruit/Adafruit-ST7735-Library/ Adafruit ST7789 driver in cpp]<br /> <br /> == Battery measurement ==<br /> <br /> 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.<br /> <br /> 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):<br /> <br /> adcVoltage = adcValue / (4095 / 3.3)<br /> <br /> 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:<br /> <br /> batteryVoltage = adcValue * 2 / (4095 / 3.3)<br /> <br /> 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:<br /> <br /> batteryVoltage = adcValue * 2000 / (4095 / 3.3)<br /> batteryVoltage = adcValue * 2000 / 1241<br /> <br /> Converting this voltage to an estimated capacity in percent requires a more complicated algorithm, because Lithium-ion batteries have a non-linear discharge curve.<br /> <br /> == Button ==<br /> <br /> The button on the side of the PineTime is disabled by default. To enable it, drive the button out pin (P0.15) high.<br /> <br /> While enabled, the button in pin (P0.13) will be high when the button is pressed, and low when it is not pressed.<br /> <br /> == Touch panel ==<br /> <br /> 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 [https://github.com/lupyuen/hynitron_i2c_cst0xxse/ 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,...).<br /> <br /> === Pins ===<br /> <br /> * P0.10 : Reset<br /> * P0.28 : Interrupt (signal to the CPU when a touch event is detected)<br /> * P0.06 : I²C SDA<br /> * P0.07 : I²C SCL<br /> <br /> === I²C ===<br /> <br /> * Device address : 0x15<br /> * Frequency : from 10Khz to 400Khz<br /> <br /> '''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.<br /> <br /> '''NOTE: ''' The I²C bus, also known as TWI bus has known issues, make sure to write your TWI driver with timeouts.<br /> <br /> === Touch events ===<br /> <br /> 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. <br /> <br /> These 63 bytes contain up to 10 touch point (X, Y, event type, pressure,...) : <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Byte<br /> ! Bit7<br /> ! Bit6<br /> ! Bit5<br /> ! Bit4<br /> ! Bit3<br /> ! Bit2<br /> ! Bit1<br /> ! Bit0<br /> |-<br /> |0<br /> |colspan=&quot;8&quot;|?<br /> |-<br /> |1<br /> |colspan=&quot;8&quot;|GestureID : (Gesture code ,<br /> <br /> 0x00: no gesture,<br /> <br /> 0x01: Slide down,<br /> <br /> 0x02: Slide up,<br /> <br /> 0x03: Slide left,<br /> <br /> 0x04: Slide right,<br /> <br /> 0x05: Single click,<br /> <br /> 0x0B: Double click,<br /> <br /> 0x0C: Long press) <br /> |-<br /> |2<br /> |colspan=&quot;4&quot;|? <br /> |colspan=&quot;4&quot;|Number of touch points <br /> |-<br /> |3<br /> |colspan=&quot;2&quot;|Event (0 = Down, 1 = Up, 2 = Contact)<br /> |colspan=&quot;2&quot;|?<br /> |colspan=&quot;4&quot;|X (MSB) coordinate<br /> |-<br /> |4<br /> |colspan=&quot;8&quot;|X (LSB) coordinate<br /> |-<br /> |5<br /> |colspan=&quot;2&quot;|?<br /> |colspan=&quot;2&quot;|Touch ID<br /> |colspan=&quot;4&quot;|Y (MSB) coordinate<br /> |-<br /> |6<br /> |colspan=&quot;8&quot;|Y (LSB) coordinate<br /> |-<br /> |7<br /> |colspan=&quot;8&quot;|Pressure (?)<br /> |-<br /> |8<br /> |colspan=&quot;8&quot;|Miscellaneous (?)<br /> |}<br /> <br /> Bytes 3 to 8 are repeated 10 times (10*6 + 3 = 63 bytes).<br /> <br /> '''NOTES'''<br /> <br /> * The touch controller seems to report only 1 touch point<br /> * Fields X, Y, Number of touch points and touch ID are updated. The others are always 0.<br /> <br /> === Registers ===<br /> <br /> The reference driver specifies some registers and value, but there is no information about them: <br /> <br /> {| class=&quot;wikitable&quot;<br /> <br /> !Register<br /> !Address<br /> !Description<br /> |-<br /> |HYN_REG_INT_CNT<br /> |0x8F<br /> |<br /> |-<br /> |HYN_REG_FLOW_WORK_CNT<br /> |0x91<br /> |<br /> |-<br /> |HYN_REG_WORKMODE <br /> |0x00<br /> |0 = WORK, 0x40 = FACTORY<br /> |-<br /> |HYN_REG_CHIP_ID<br /> |0xA3<br /> |<br /> |-<br /> |HYN_REG_CHIP_ID2<br /> |0x9F<br /> |-<br /> |HYN_REG_POWER_MODE<br /> |0xA5<br /> |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)<br /> |-<br /> |HYN_REG_FW_VER<br /> |0xA6<br /> |<br /> |-<br /> |HYN_REG_VENDOR_ID<br /> |0xA8<br /> |<br /> |-<br /> |HYN_REG_LCD_BUSY_NUM<br /> |0xAB<br /> |<br /> |-<br /> |HYN_REG_FACE_DEC_MODE_EN<br /> |0xB0<br /> |<br /> |-<br /> |HYN_REG_GLOVE_MODE_EN<br /> |0xC0<br /> |<br /> |-<br /> |HYN_REG_COVER_MODE_EN<br /> |0xC1<br /> |<br /> |-<br /> |HYN_REG_CHARGER_MODE_EN<br /> |0x8B<br /> |<br /> |-<br /> |HYN_REG_GESTURE_EN<br /> |0xD0<br /> |<br /> |-<br /> |HYN_REG_GESTURE_OUTPUT_ADDRESS<br /> |0xD3<br /> |<br /> |-<br /> |HYN_REG_ESD_SATURATE 0xED<br /> |0xED<br /> |<br /> |}<br /> <br /> '''WARNING : ''' &lt;del&gt;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!&lt;/del&gt;<br /> <br /> ==Accelerometer==<br /> The on board accelerometer in devices shipped before July 2021 is a Bosch BMA421, connected to the I2C bus.<br /> Devices shipped after July 2021 use a Bosch BMA425 accelerometer.<br /> <br /> === Pins ===<br /> <br /> * P0.06 : I²C SDA<br /> * P0.07 : I²C SCL<br /> * P0.08 : Interrupt<br /> <br /> I2C Device address : 0x18<br /> <br /> = Datasheets and Schematics =<br /> <br /> == Schematics ==<br /> * [https://files.pine64.org/doc/PineTime/PineTime%20Schematic-V1.0a-20191103.pdf PineTime Schematic ver1.0a]<br /> * [https://files.pine64.org/doc/PineTime/PineTime%20Port%20Assignment%20rev1.0.pdf PineTime GPIO Port Assignment ver1.0]<br /> <br /> 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.<br /> <br /> == Chip Datasheets ==<br /> * NORDIC nRF52832 information:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/nRF52832%20product%20brief.pdf nRF52832 Product Brief]<br /> ** [https://infocenter.nordicsemi.com/pdf/nRF52832_PS_v1.4.pdf nRF52832 Product Specification v1.4]<br /> * ARMv7-M information:<br /> ** [https://static.docs.arm.com/ddi0403/eb/DDI0403E_B_armv7m_arm.pdf ARMv7-M Architecture Reference Manual]<br /> <br /> == Component Datasheets ==<br /> * PMU (Power Management Unit) information:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/SGM40561.pdf SGMicro SGM40561 Single Cell Charger Datasheet]<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/SGMICRO-SGM2036.pdf SGMicro SGM2036 3.3V Low Power Low Dropout RF Linear Regulator Datasheet]<br /> * SPI Flash information:<br /> ** [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])<br /> ** [https://datasheet.lcsc.com/szlcsc/2005251035_XTX-XT25F32BSOIGU-S_C558851.pdf XTX XT25F32B]<br /> ** IDs for XT25F32B are: manufacturer (0x0b), device (0x15), memory type (0x40), density (0x16)<br /> * LCD Panel:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/PineTime%20LCD%20Panel.jpg 1.3&quot; 240x240 IPS LCD Panel Specification for PineTime]<br /> ** [https://wiki.pine64.org/images/5/54/ST7789V_v1.6.pdf 11.6&quot; Sitronix LCD Driver/Controller Datasheet]<br /> * Touchpad information:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/PineTime%20Touch%20Panel.jpg Touchpad Specification for PineTimel]<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/CST816S数据手册V1.1.pdf 11.6&quot; Hynitron CST816S Capacitive Touch Controller Datasheet in Chinese]<br /> ** [https://wiki.pine64.org/images/2/2f/CST816S.zip Touch Controller Datasheet en]<br /> * Sensor:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/BST-BMA421-FL000.pdf BOSCH BMA421 Triaxial VAcceleration Sensor Product Brief]<br /> ** [https://wiki.pine64.org/images/c/cc/Bst-bma400-ds000.pdf BOSCH BMA400 3-axes ultra-low power accelerometer datasheet]<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/HRS3300%20Heart%20Rate%20Sensor.pdf TianYiHeXin HRS3300 PPG Heart Rate Sensor Data Sheet]<br /> <br /> = Community case design =<br /> <br /> * [https://www.thingiverse.com/thing:4172849 PineTime Smart Watch case by dara0s at thingiverse]<br /> * [https://www.thingiverse.com/thing:4651462 PineTime dev kit back fix by joaquimorg at thingiverse]<br /> * [https://www.thingiverse.com/thing:4763267 PineTime dev kit charging holder v4 by zevix81 at thingiverse]<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=InfiniTime&diff=12122 2021-12-29T21:27:21Z

<p>Avamander: /* Version 1.3.0 &quot;Purple Fig&quot; */</p> <hr /> <div>== InfiniTime ==<br /> InfiniTime (also known as JF's project, FreeRTOS firmware or Pinetime-JF) is an open source (GPLv3) firmware written in C++ and based on FreeRTOS, LVGL and NimBLE. This firmware (version 0.7.1) is preloaded at the factory since the new batch of PineTime devkits and sealed PineTimes of end of September 2020. '''This page contains general information about the project. Actual project documentation and nuances are documented in the repository'''<br /> <br /> * GitHub repo : https://github.com/JF002/InfiniTime<br /> * Official website : https://infinitime.io/<br /> <br /> == Read this first! ==<br /> * InfiniTime and the bootloader are still in heavy development, and some features might not work as expected. Any issues should be reported on GitHub.<br /> * Do not use a sealed PineTime as a development device, there is a fair amount of chances that you'll brick it with very experimental firmware.<br /> * OTA is relatively stable, but when you're on an outdated bootloader version it can freeze which will require you to wait for the battery to run out.<br /> <br /> == Known issues ==<br /> {{warning|1=Please read this section carefully before upgrading the firmware on your PineTime, especially if you are using a sealed device!}}<br /> === Black screen after a reset in sleep mode ===<br /> ==== Description ====<br /> This issue occurs if you are using the original bootloader (from InfiniTime 0.7.1), upgraded from InfiniTime 0.7.1 to 0.8.2 and the watch resets while the display is OFF : the watch is stuck on a black screen and does not respond to touch, button press or BLE.<br /> <br /> The reset can be triggered by the watchdog or manually by long pressing the button. If that doesn't work, wait for the battery to run out, it'll reboot then.<br /> <br /> This issue is caused by InfiniTime 0.8.2 that put the external SPI flash memory to sleep before switching the display off and by the bootloader that cannot wake the memory chip up. The bootloader is stuck in an infinite loop.<br /> <br /> More info : https://github.com/lupyuen/pinetime-rust-mynewt/issues/24 and https://github.com/JF002/InfiniTime/issues/60<br /> <br /> ==== Workaround ====<br /> On a development kit, a simple reset via SWD is needed to unlock the bootloader.<br /> <br /> On a sealed device, the only way to work around this issue is to wait for the battery to drain completely before trying again.<br /> <br /> This issue can be avoided by ensuring that the display is ON when manually resetting the device (long push on the button).<br /> <br /> ==== Fixed version ====<br /> This issues is fixed in [https://github.com/JF002/InfiniTime/releases/tag/0.8.3 InfiniTime 0.8.3]<br /> <br /> == Releases == <br /> <br /> In the order of oldest first.<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.7.1 Version 0.7.1] ===<br /> This is the version that ships with PineTime devkits and sealed PineTime as of September 2020.<br /> * Time synchronization over BLE<br /> * Display brightness setting<br /> * Notifications over BLE<br /> * Integration with AmazFish (SailFishOS) and Gadgetbridge (Android)<br /> * OTA using NRFConnect<br /> <br /> Bootloader : https://github.com/lupyuen/pinetime-rust-mynewt/releases/tag/v4.1.7<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.8.2 Version 0.8.2] ===<br /> * Music control app<br /> * Paint app<br /> * Manual image validation after OTA<br /> <br /> Bootloader : https://github.com/lupyuen/pinetime-rust-mynewt/releases/tag/v5.0.4.<br /> <br /> This new version of the bootloader fixes [[#Black_screen_after_a_reset_in_sleep_mode]] and enables the watchdog before launching the firmware.<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.8.3 Version 0.8.3] ===<br /> * Fixes the &quot;bootloader stuck after a reset&quot; mentioned in 0.8.2 above<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.9.0 Version 0.9.0] ===<br /> * Touch panel fixed (no more freezing)<br /> * Improved music application (possibility to control both volumes and browsing, display the song progression)<br /> * Notification UI rewritten: can now display up to 100 characters<br /> * Improved BLE connectivity<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.10.0 Version 0.10.0] ===<br /> * 2 new games: Pong and 2048<br /> * Fixed display glitches and improved needed time to turn on the display<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.11.0 Version 0.11.0] ===<br /> * Heart-rate sensor application:<br /> * Displays the current value, and when running, this value is also displayed on the clock face<br /> * Value exposed over BLE, meaning other applications can read it (e.g. companion app such as Amazfish)<br /> * Navigation app: InfiNav - works e.g. with PureMaps on SailfishOS<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.12.0 Version 0.12.0] ===<br /> * Improved BLE connection<br /> * OTA updates much more reliable<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.13.0 Version 0.13.0] ===<br /> * Vibration<br /> * Call notification: it is possible to accept/ignore/reject a call from the PineTime<br /> * Music app got nicer icons<br /> * BLE connectivity improved a bit more<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.14.0 Version 0.14.0 &quot;Green Avocado&quot;] ===<br /> * LVGL 7<br /> * Bugfixes to the build process<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.14.1 Version 0.14.1] ===<br /> * New Recovery firmware<br /> * MCUBoot based [https://github.com/JF002/pinetime-mcuboot-bootloader/releases/tag/1.0.0 bootloader]<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.15.0 Version 0.15.0 &quot;Yellow Banana&quot;] ===<br /> * Analog watch face<br /> * Support for switching watch faces<br /> * Stopwatch app<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/1.0.0 Version 1.0.0 &quot;Red Cherry&quot;] ===<br /> * Motion sensor integration<br /> * Step countin<br /> * UI redesign<br /> * Quick action menu:<br /> * Brightness setting<br /> * Do not disturb mode (disable vibrations on notifications)<br /> * Flash light application<br /> * Settings menu allowing configuration of:<br /> * Display timeout<br /> * Wakeup source (button only, single tap, double tap and wrist rotation)<br /> * Time format (12/24H)<br /> * Watchface<br /> * New navigation flow :<br /> * User settings stored in flash memory and restored on reset<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/1.1.0 Version 1.1.0 &quot;Dragon Fruit&quot;] ===<br /> * Steps application<br /> * Timer application<br /> * UI improvements<br /> * Clang-format and clang-tidy config files<br /> * Bugfixes<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/1.2.0 Version 1.2.0 &quot;Blue-purple Elderberry&quot;] ===<br /> * Added support for alternate accelerometer part BMA425<br /> * Metronome app<br /> * Memory usage optimizations<br /> * Bugfixes, minor improvements and code cleanup<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/1.3.0 Version 1.3.0 &quot;Purple Fig&quot;] ===<br /> * LittleFS integration<br /> * New watchface, PineTimeStyle<br /> * Battery level notification on BLE (supported by Gadgetbridge)<br /> * Improved stopwatch app, Paddle game and call notifications<br /> * Firmware update app is now more foolproof<br /> * The SPI flash is put in sleep mode when the watch goes to sleep (only if the new bootloader is detected)<br /> * UI improvements (better 'tick' handling in LVGL, more consistent refresh rate)<br /> * Various improvements and code cleaning<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=Reprogramming_the_PineTime&diff=12063 2021-12-17T14:13:51Z

<p>Avamander: /* CMSIS-DAP */</p> <hr /> <div>= Introduction =<br /> <br /> 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. <br /> <br /> '''Before you can use your debugger/programmer, you probably have to [[PineTime devkit wiring|wire up your pinetime]]. Heavily recommended you read this first!'''<br /> <br /> 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:<br /> <br /> * Unlocking the device '''Note: PineTime watches shipped after 20 Sep 2020 do not require unlocking. They are shipped unlocked.'''<br /> * Uploading new software<br /> * Running a debugger<br /> <br /> All of these are described in this article. <br /> <br /> 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.<br /> <br /> = SWD Pinout =<br /> <br /> See [[PineTime devkit wiring|PineTime devkit wiring]]<br /> <br /> = nrfjprog (for Segger JLink) =<br /> <br /> 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].<br /> <br /> === Hookup ===<br /> <br /> Connect the Pinetime SWD pins to the debugger (P20 on NRF52-DK)<br /> <br /> {| class=&quot;wikitable&quot;<br /> !Pinetime<br /> !JLink<br /> |-<br /> |GND<br /> |GND<br /> |-<br /> |SWDCLK<br /> |SWDCLK<br /> |-<br /> |SWDIO<br /> |SWDIO<br /> |-<br /> |VCC (3.3V)<br /> |VTG (target detect)<br /> |}<br /> <br /> === Unlocking the FLASH ===<br /> <br /> Unlocking the device and erase the memory. <br /> <br /> '''You need to execute this step only once, to remove the read protection on the memory. Note that it will erase the whole flash memory of the MCU!''' :<br /> <br /> nrfjprog -f NRF52 --recover<br /> <br /> === Uploading new software ===<br /> <br /> 1. Program the BLE softdevice (if needed by the firmware). Replace PATH_TO_NRF_SDK by the path where you unzipped the [https://www.nordicsemi.com/Software-and-Tools/Software/nRF5-SDK NRF52 SDK] :<br /> <br /> nrfjprog -f NRF52 --program /PATH_TO_NRF_SDK/components/softdevice/s132/hex/s132_nrf52_6.1.1_softdevice.hex --sectorerase<br /> <br /> 2. Program the firmware (replace firmware.hex by the actual filename of the firmware):<br /> <br /> nrfjprog -f NRF52 --program firmware.hex --sectorerase<br /> <br /> 3. Reset and run the new firmware:<br /> <br /> nrfjprog -f NRF52 --reset<br /> <br /> = OpenOCD =<br /> <br /> OpenOCD, the Open On-Chip Debugger supports multiple different adapters. You can read more about it here: http://openocd.org/<br /> <br /> == Adapters ==<br /> <br /> 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''.<br /> <br /> You can simplify your life by creating a configuration file that contains the interface, transport, target and speed configuration. Things like CLion also need one to work properly.<br /> <br /> 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'').<br /> <br /> === CMSIS-DAP ===<br /> <br /> This is a generic specification that is supported by a bunch of different hardware, things such as DAPLink also use it.<br /> <br /> Issue this command to initialize a connection to the devkit:<br /> <br /> openocd \<br /> -c 'source [find interface/cmsis-dap.cfg]' \<br /> -c 'transport select swd' \<br /> -c 'source [find target/nrf52.cfg]' \<br /> -c 'adapter speed 8000' \<br /> -c 'init'<br /> <br /> === JLink ===<br /> <br /> Start OpenOCD:<br /> <br /> openocd \<br /> -c 'source [find interface/jlink.cfg]' \<br /> -c 'transport select swd' \<br /> -c 'source [find target/nrf52.cfg]' \<br /> -c 'adapter speed 8000' \<br /> -c 'init'<br /> <br /> === Raspberry Pi ===<br /> <br /> openocd \<br /> -c 'source bcm2835spi' \<br /> -c 'bcm2835spi_speed 31200' \<br /> -c 'source [find target/nrf52.cfg]' \<br /> -c 'init'<br /> <br /> === STLink ===<br /> <br /> Connect PineTime SWD Pins to ST-Link v2 as follows:<br /> <br /> {| class=&quot;wikitable&quot;<br /> !PineTime<br /> !ST-Link<br /> |-<br /> |GND<br /> |GND<br /> |-<br /> |SWDCLK<br /> |SWDCLK<br /> |-<br /> |SWDIO<br /> |SWDIO<br /> |-<br /> |VCC (3.3V)<br /> |3.3V<br /> |}<br /> <br /> [[File:pinetime-stlink.jpg|400px]]<br /> <br /> Note that only the bottom row of pins on ST-Link are used.<br /> <br /> To flash PineTime with ST-Link on Linux and macOS, use [https://github.com/lupyuen/pinetime-updater/blob/master/README.md PineTime Updater]<br /> <br /> [[PineTime FAQ|'''ST-Link can't be used to remove nRF52 flash protection''']]<br /> <br /> == Unlocking the device ==<br /> <br /> If you need to disable access port protection then you can do this using the following commands below.<br /> <br /> This can be done in two ways:<br /> <br /> Appending this to OpenOCD command line:<br /> <br /> -c 'nrf52.dap apreg 1 0x04' -c 'nrf52.dap apreg 1 0x04 0x01' -c 'nrf52.dap apreg 1 0x04'<br /> <br /> Or by using the telnet connection, just type in ''telnet localhost 4444'' and then you can issue commands to OpenOCD:<br /> <br /> Note: ''Unlocking the device to remove access port protection will erase the contents of flash.''<br /> <br /> telnet localhost 4444<br /> Trying 127.0.0.1...<br /> Connected to localhost.<br /> Escape character is '^]'.<br /> Open On-Chip Debugger<br /> &gt; nrf52.dap apreg 1 0x04<br /> 0x00000000<br /> &gt; nrf52.dap apreg 1 0x04 0x01<br /> &gt; nrf52.dap apreg 1 0x04<br /> 0x00000001<br /> <br /> (If the ''nrf52.dap'' command cannot be found, try just ''dap'' instead.)<br /> <br /> == Uploading new software ==<br /> <br /> Just issue this command, replace ''code.hex'' with your own (and cmsis-dap.cfg with an appropriate adapter).<br /> <br /> openocd \<br /> -c 'source [find interface/cmsis-dap.cfg]' \<br /> -c 'transport select swd' \<br /> -c 'source [find target/nrf52.cfg]' \<br /> -c 'init' \<br /> -c 'halt' \<br /> -c 'nrf5 mass_erase' \<br /> -c 'program code.hex verify' \<br /> -c 'reset' \<br /> -c 'exit'<br /> <br /> = Black Magic Probe =<br /> <br /> 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].<br /> <br /> === Native adapters ===<br /> <br /> The native adapters are the official Black Magic family of debug adapters, including the original Black Magic Probe and the Black Magic Probe Mini. By buying the official hardware you are supporting the continued development of the Black Magic Probe software.<br /> <br /> Providing your native adapter is running up-to-date firmware then it can be used to program your PineTime.<br /> <br /> === STM32 (Blue Pill) ===<br /> <br /> It is possible to flash a popular development board based on STM32F103C8T6 microcontroller, known as Blue Pill, to make a BlackMagic Probe device. For example, one may follow instructions in [https://forum.pine64.org/showthread.php?tid=8816&amp;pid=57095#pid57095 forum post] or [https://gist.github.com/darnel/dac1370d057e176386ca4026418abc2b gist] (mac os). Also, it is possible to use SWD pins on the board to flash other devices, instead using arbitrary pins on the board itself. See [https://buger.dread.cz/black-magic-probe-bmp-on-bluepill-stm32f103c8-minimum-system-development-board.html this link] for more detals.<br /> <br /> === Other hardware ===<br /> <br /> The Black Magic Probe firmware can be run on a variety of host devices. See [https://github.com/blacksphere/blackmagic/wiki/Debugger-Hardware BMP Debugger Hardware] for more information.<br /> <br /> === Using the BMP to flash the PineTime ===<br /> <br /> Refer to the BMP [https://github.com/blacksphere/blackmagic/wiki/Useful-GDB-commands wiki] for the full description of commands.<br /> Overall, the process on Linux is like following. (/dev/ttyBmpGdb is a symlink created by the udev rule). It's useful to create a gdb script file (or .gdbinit) with following commands:<br /> <br /> target extended-remote /dev/ttyBmpGdb<br /> monitor swdp_scan<br /> attach 1<br /> file %firmware file%<br /> <br /> Then one may use '''load''' command to flash the firmware, '''compare-sections''' to verify the upload, or '''monitor erase_mass''' to erase the firmware. <br /> <br /> Then, proceed with debugging as normal.<br /> <br /> <br /> = External links and additional tutorials = <br /> <br /> * https://github.com/jlukanc1/pinetime-boot-flasher<br /> * https://blog.aegrel.ee/absniffer-cmsis-dap-sniffer.html<br /> * https://blog.dbrgn.ch/2020/5/16/nrf52-unprotect-flash-jlink-openocd/<br /> * https://medium.com/@ly.lee/openocd-on-raspberry-pi-better-with-swd-on-spi-7dea9caeb590<br /> * https://medium.com/@ly.lee/build-and-flash-rust-mynewt-firmware-for-pinetime-smart-watch-5e14259c55<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=InfiniTime&diff=11834 2021-11-21T13:30:43Z

<p>Avamander: /* Releases */</p> <hr /> <div>== InfiniTime ==<br /> InfiniTime (also known as JF's project, FreeRTOS firmware or Pinetime-JF) is an open source (GPLv3) firmware written in C++ and based on FreeRTOS, LVGL and NimBLE. This firmware (version 0.7.1) is preloaded at the factory since the new batch of PineTime devkits and sealed PineTimes of end of September 2020. '''This page contains general information about the project. Actual project documentation and nuances are documented in the repository'''<br /> <br /> * GitHub repo : https://github.com/JF002/InfiniTime<br /> * Official website : https://infinitime.io/<br /> <br /> == Read this first! ==<br /> * InfiniTime and the bootloader are still in heavy development, and some features might not work as expected. Any issues should be reported on GitHub.<br /> * Do not use a sealed PineTime as a development device, there is a fair amount of chances that you'll brick it with very experimental firmware.<br /> * OTA is relatively stable, but when you're on an outdated bootloader version it can freeze which will require you to wait for the battery to run out.<br /> <br /> == Known issues ==<br /> {{warning|1=Please read this section carefully before upgrading the firmware on your PineTime, especially if you are using a sealed device!}}<br /> === Black screen after a reset in sleep mode ===<br /> ==== Description ====<br /> This issue occurs if you are using the original bootloader (from InfiniTime 0.7.1), upgraded from InfiniTime 0.7.1 to 0.8.2 and the watch resets while the display is OFF : the watch is stuck on a black screen and does not respond to touch, button press or BLE.<br /> <br /> The reset can be triggered by the watchdog or manually by long pressing the button. If that doesn't work, wait for the battery to run out, it'll reboot then.<br /> <br /> This issue is caused by InfiniTime 0.8.2 that put the external SPI flash memory to sleep before switching the display off and by the bootloader that cannot wake the memory chip up. The bootloader is stuck in an infinite loop.<br /> <br /> More info : https://github.com/lupyuen/pinetime-rust-mynewt/issues/24 and https://github.com/JF002/InfiniTime/issues/60<br /> <br /> ==== Workaround ====<br /> On a development kit, a simple reset via SWD is needed to unlock the bootloader.<br /> <br /> On a sealed device, the only way to work around this issue is to wait for the battery to drain completely before trying again.<br /> <br /> This issue can be avoided by ensuring that the display is ON when manually resetting the device (long push on the button).<br /> <br /> ==== Fixed version ====<br /> This issues is fixed in [https://github.com/JF002/InfiniTime/releases/tag/0.8.3 InfiniTime 0.8.3]<br /> <br /> == Releases == <br /> <br /> In the order of oldest first.<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.7.1 Version 0.7.1] ===<br /> This is the version that ships with PineTime devkits and sealed PineTime as of September 2020.<br /> * Time synchronization over BLE<br /> * Display brightness setting<br /> * Notifications over BLE<br /> * Integration with AmazFish (SailFishOS) and Gadgetbridge (Android)<br /> * OTA using NRFConnect<br /> <br /> Bootloader : https://github.com/lupyuen/pinetime-rust-mynewt/releases/tag/v4.1.7<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.8.2 Version 0.8.2] ===<br /> * Music control app<br /> * Paint app<br /> * Manual image validation after OTA<br /> <br /> Bootloader : https://github.com/lupyuen/pinetime-rust-mynewt/releases/tag/v5.0.4.<br /> <br /> This new version of the bootloader fixes [[#Black_screen_after_a_reset_in_sleep_mode]] and enables the watchdog before launching the firmware.<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.8.3 Version 0.8.3] ===<br /> * Fixes the &quot;bootloader stuck after a reset&quot; mentioned in 0.8.2 above<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.9.0 Version 0.9.0] ===<br /> * Touch panel fixed (no more freezing)<br /> * Improved music application (possibility to control both volumes and browsing, display the song progression)<br /> * Notification UI rewritten: can now display up to 100 characters<br /> * Improved BLE connectivity<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.10.0 Version 0.10.0] ===<br /> * 2 new games: Pong and 2048<br /> * Fixed display glitches and improved needed time to turn on the display<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.11.0 Version 0.11.0] ===<br /> * Heart-rate sensor application:<br /> * Displays the current value, and when running, this value is also displayed on the clock face<br /> * Value exposed over BLE, meaning other applications can read it (e.g. companion app such as Amazfish)<br /> * Navigation app: InfiNav - works e.g. with PureMaps on SailfishOS<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.12.0 Version 0.12.0] ===<br /> * Improved BLE connection<br /> * OTA updates much more reliable<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.13.0 Version 0.13.0] ===<br /> * Vibration<br /> * Call notification: it is possible to accept/ignore/reject a call from the PineTime<br /> * Music app got nicer icons<br /> * BLE connectivity improved a bit more<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.14.0 Version 0.14.0 &quot;Green Avocado&quot;] ===<br /> * LVGL 7<br /> * Bugfixes to the build process<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.14.1 Version 0.14.1] ===<br /> * New Recovery firmware<br /> * MCUBoot based [https://github.com/JF002/pinetime-mcuboot-bootloader/releases/tag/1.0.0 bootloader]<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.15.0 Version 0.15.0 &quot;Yellow Banana&quot;] ===<br /> * Analog watch face<br /> * Support for switching watch faces<br /> * Stopwatch app<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/1.0.0 Version 1.0.0 &quot;Red Cherry&quot;] ===<br /> * Motion sensor integration<br /> * Step countin<br /> * UI redesign<br /> * Quick action menu:<br /> * Brightness setting<br /> * Do not disturb mode (disable vibrations on notifications)<br /> * Flash light application<br /> * Settings menu allowing configuration of:<br /> * Display timeout<br /> * Wakeup source (button only, single tap, double tap and wrist rotation)<br /> * Time format (12/24H)<br /> * Watchface<br /> * New navigation flow :<br /> * User settings stored in flash memory and restored on reset<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/1.1.0 Version 1.1.0 &quot;Dragon Fruit&quot;] ===<br /> * Steps application<br /> * Timer application<br /> * UI improvements<br /> * Clang-format and clang-tidy config files<br /> * Bugfixes<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/1.2.0 Version 1.2.0 &quot;Blue-purple Elderberry&quot;] ===<br /> * Added support for alternate accelerometer part BMA425<br /> * Metronome app<br /> * Memory usage optimizations<br /> * Bugfixes, minor improvements and code cleanup<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/1.3.0 Version 1.3.0 &quot;Purple Fig&quot;] ===<br /> * LittelFS integration<br /> * New watchface, PineTimeStyle<br /> * Battery level notification on BLE (supported by Gadgetbridge)<br /> * Improved stopwatch app, Paddle game and call notifications<br /> * Firmware update app is now more foolproof<br /> * The SPI flash is put in sleep mode when the watch goes to sleep (only if the new bootloader is detected)<br /> * UI improvements (better 'tick' handling in LVGL, more consistent refresh rate)<br /> * Various improvements and code cleaning<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=Upgrade_PineTime_to_InfiniTime_1.0.0&diff=11816 2021-11-18T21:00:57Z

<p>Avamander: </p> <hr /> <div>'''Devices shipped before July 2021 were pre-installed with InfiniTime 0.7.1, and an older bootloader. This features green text 'PINE TIME' on boot, and should be updated to the new bootloader as described below.'''<br /> <br /> '''Devices shipped after July 2021 were pre-installed with InfiniTime 1.2 and the new bootloader, which can be identified by the green Pinecone image on boot. The instructions below are unnecessary for these devices.'''<br /> <br /> <br /> Congratulations on receiving your new PineTime!<br /> <br /> So now you're probably wondering exactly how on earth do you go about upgrading your watch to the latest and greatest version of InfiniTime - you know, that version you've seen all those great pictures, videos and reviews of. To those of us that are developing stuff for it, it's pretty easy and straightforward, but like with all technology, it is a bit tricky. <br /> <br /> {{warning|1=Some people ran into issues during the update process that would temporarily make their watch unusable (display frozen or blank). The only know workaround consists of waiting for the battery to drain completely and try again. With the display off, and battery fully charged, you can expect a wait of 5-7 days so it is best to not fully charge it. If it freezes with the display on, it will likely be flat by the end of the day. We've never heard of any PineTimes that were permanently bricked (were not recoverable), though. }} <br /> <br /> In a nutshell, you need to:<br /> # Charge your watch, but '''not''' to 100% - keep it at approximately 50% - for the reason described above.<br /> # Update InfiniTime<br /> # Update the bootloader<br /> # Install the recovery firmware<br /> <br /> = Update Process =<br /> So how do you do this? Where do you start? Well, with a sealed PineTime, your only easy option is via Over The Air (OTA) Device Firmware Update (DFU), which is done via Bluetooth. There are a couple of different ways and apps you can use to do this. If you have an Android device, you can use [https://f-droid.org/en/packages/nodomain.freeyourgadget.gadgetbridge/ Gadgetbridge] or [https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp NRFConnect] (NRFConnect is available on iOS devices as well). Otherwise, if your laptop or desktop computer has Bluetooth and runs Linux, you can use [https://github.com/alexr4535/siglo Siglo] or [https://github.com/piggz/harbour-amazfish Amazfish]. You can also use these applications on your Pinebook Pro or Pinephone if you happen to have those devices. <br /> <br /> The reason for installing the updates in the specified order is because newer versions of InfiniTime have a more robust Bluetooth update process, and since we're updating everything over Bluetooth, the fewer retries and failures from that you have the better. It will still sometimes disconnect mid update, meaning you'll need to try again, and possibly restart the watch a few times as well. And since the recovery firmware is new to the 1.0.0 version of the bootloader, it's best to update that last. <br /> <br /> [https://video.codingfield.com/videos/watch/831077c5-16f3-47b4-9b2b-c4bbfecc6529 This video] shows the bootloader and recovery firmware installation procedure.<br /> <br /> [https://video.codingfield.com/videos/watch/f7bffb3d-a6a1-43c4-8f01-f4aeff4adf9e This video] shows the bootloader installation and firmware update using Amazfish.<br /> <br /> You can also read a [https://github.com/JF002/pinetime-mcuboot-bootloader/blob/339224cf5ed21f4e8b2d22eaeab9869120f7f752/docs/howToUpdate.md detailed installation procedure in the documentation of the bootloader].<br /> <br /> == Update InfiniTime ==<br /> To update the main InfiniTime app, you want to flash [https://github.com/JF002/InfiniTime/releases/download/1.0.0/pinetime-mcuboot-app-dfu-1.0.0.zip pinetime-mcuboot-app-dfu-1.0.0.zip].<br /> <br /> After updating InfiniTime, ensure that you validate the firmware to prevent it from being automatically reverted/rolled back if your watch is reset/restarted. To do this, swipe right to access the quick actions panel, press the gear/settings icon, swipe up once to show the second page, press on the 'Firmware' option and then on 'Validate'.<br /> <br /> [https://youtu.be/-5lwBd60k0Q Video showing validation process]<br /> <br /> <br /> === Gadgetbridge ===<br /> <br /> # Connect your PineTime to GB<br /> # Download the aforementioned file to your phone<br /> # Find the file in your file manager<br /> # 'Open With' Gadgetbridge F/W Installer (method varies by device) - on my phone, it is press and hold, select the file, and then choose 'open with app' from the more options menu<br /> # Confirm that you wish to apply the update<br /> # Wait for the update to complete<br /> <br /> [https://youtu.be/nAaaC7D5sVo Video showing how to start the update]<br /> <br /> === NRFConnect ===<br /> <br /> # Download the aforementioned file to your phone.<br /> # Open NRFConnect<br /> # Scan for your device<br /> # Connect to it<br /> # Choose the DFU option at the top right of the screen<br /> # Ensure the 'Distribution packet (ZIP)' option is selected, and press OK<br /> # Select your previously downloaded file<br /> # Wait for the update to complete<br /> <br /> [https://youtu.be/jnX7WwYDiDE Video showing how to start the update]<br /> <br /> === Siglo ===<br /> # If your device was not detected upon start, press &quot;Rescan&quot; to find it.<br /> # Select the &quot;1.0.0&quot; tag<br /> # Select the aforementioned file/asset.<br /> # Select &quot;Flash It!&quot;<br /> <br /> === Amazfish ===<br /> # Run Amazfish (service + UI)<br /> # Pair with you device:<br /> ## Unzip the DFU file to extract the .bin file.<br /> ## Click on &quot;pair with watch&quot; on the top<br /> ## Select &quot;PineTime&quot; (if your device is running InfiniTime 0.7.1 or lower) or &quot;InfiniTime (if it's running InfiniTime 0.8+) and choose your device in the list<br /> # Click on &quot;Download file&quot; on the top <br /> # Click on &quot;Choose file&quot; and select the .bin file you extracted from the DFU file<br /> # Click on &quot;Send file&quot;<br /> # Wait for the update to complete.<br /> <br /> [https://video.codingfield.com/videos/watch/41cfcf5d-b0e6-4323-8056-b0a6682d1f25 See it in action!]<br /> <br /> == Update the bootloader ==<br /> To update the bootloader, you want to flash [https://github.com/JF002/InfiniTime/releases/download/0.14.1/reloader-mcuboot.zip reloader-mcuboot.zip]. <br /> Once the bootloader is updated, you should notice that the boot logo has changed. Previously, it was a green &quot;PineTime&quot; logo, and now it is a large pinecone that is progressively drawn in green.<br /> <br /> [https://youtu.be/fvHQ8ZeqnOo Video showing what the InfiniTime 1.0.0 bootloader looks like]<br /> <br /> === Using Gadgetbridge ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> === Using NRFConnect ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> === Using Siglo ===<br /> Same process as before, but select the &quot;0.14.1&quot; tag, and the file/asset for this step.<br /> <br /> === Using Amazfish ===<br /> <br /> You may need to re-pair with your device by selecting &quot;InfiniTime&quot; (since you've already upgraded to InfiniTime 1.0) in the device type list. Then follow the same process as before, but with the file for this step.<br /> <br /> == Install the recovery firmware ==<br /> {{warning|1=Don't do this before updating the bootloader, otherwise your PineTime will freeze at the end of the process, and you will need to wait for the battery to go flat }} <br /> <br /> To install the recovery firmware, you want to flash [https://github.com/JF002/InfiniTime/releases/download/0.14.1/pinetime-mcuboot-recovery-loader-dfu-0.14.1.zip pinetime-mcuboot-recovery-loader-dfu-0.14.1.zip]. You will know when this is running when it shows an InfiniTime logo with a progress bar running across the bottom whilst it is installing the recovery firmware. <br /> <br /> === Using Gadgetbridge ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> === Using NRFConnect ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> === Using Siglo ===<br /> Same process as before, but with the file/asset for this step.<br /> <br /> === Using Amazfish ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> <br /> = Guides and Videos =<br /> <br /> = Troubleshooting =<br /> Sometimes during the update process, the connection will drop, and the update will fail. Your PineTime isn't broken, most likely the Bluetooth link dropped for a moment, so just try again. Try rebooting your phone, if it keeps failing, try restarting the watch by holding the power button down for approximately 8 seconds. Try to '''avoid''' holding down the button with the screen off. Or try with another device, just in case there are compatibility issues. <br /> <br /> Version 1.0.0 of InfiniTime is merely the first version that was considered sufficiently feature-complete and stable enough for daily use. This isn't to say there aren't still bugs present ('cause there are!). So there are a few bugs still present in the update process and the bootloader. One unfortunate bug appears to be that sometimes when the watch tries to restart after an update, the bootloader locks up, and the watch won't turn on. In this case, you will need to wait until the watch battery goes flat, to force the watch to reset. This will most likely involve waiting for a week, and then when you put the watch on the charging cradle, it will power up and you should be right to try again.<br /> <br /> If you get stuck or have any questions, join us on your preferred [[Main_Page#Chat_Platforms|chat platform]] or the product [https://forum.pine64.org/forumdisplay.php?fid=134 forum]. There's usually someone available who can help, or will get back to you in a few hours.<br /> <br /> <br /> [[Category:PineTime]][[Category:Guide]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_FAQ&diff=11786 2021-11-10T23:02:29Z

<p>Avamander: /* Troubleshooting PineTime's Bluetooth (InfiniTime firmware) */</p> <hr /> <div>== Does PineTime run Linux? ==<br /> <br /> No. [https://forum.pine64.org/showthread.php?tid=8112 Please read this forum article] for information about Linux on PineTime. Also check out the article [https://lupyuen.github.io/pinetime-rust-mynewt/articles/pinetime &quot;PineTime doesn't run Linux... But that's OK!&quot;]<br /> <br /> == Why are there two versions of the PineTime in the store? ==<br /> <br /> See the below question and answer.<br /> <br /> == Why can I only buy the closed version in a 3-pack, and the open version per one? ==<br /> <br /> TL:DR: The unsealed PineTime is for development, the sealed one is for production use, because of firmware uploads. That is also why they were initially sold three in a pack.<br /> <br /> In the current situation in development there are some reasons to want to be sure you only experiment with an open device. If you install the wrong firmware, your device could be bricked, until you find a way to open it, which will likely damage the device.<br /> The idea is that if you want to develop an application for the PineTime, you will be testing it out first, and only after you know for sure your new firmware is well tested, you will install it on sealed devices. If you are in the beta stage, having more than one PineTime is probably a good idea. So to prevent people from locking themselves out at the first test, it was decided to sell the closed version only as a pack of 3. Development can be done on an open device, so any issues can be easily handled.<br /> <br /> == How long does it take to ship my PineTime? ==<br /> <br /> That depends on whether you chose for Standard or Express shipping. Standard shipping for the dev kit may take up to a few weeks.<br /> <br /> == How do I install new software on PineTime? ==<br /> <br /> If you have a Sealed PineTime, flash only tested PineTime Firmware to your PineTime. If you flash unknown PineTime Firmware, your sealed PineTime may be bricked relatively permanently.<br /> <br /> There is a lot of different software for flashing. Check out [[PineTime Development]] page for a list of companion software.<br /> <br /> Also see [[Reprogramming_the_PineTime|this page to see various methods of reprogramming the devkit PineTime the wired way]].<br /> <br /> Remember to validate the firmware after flashing: Swipe up to show the menu, tap the checkmark icon, tap &quot;Validate&quot;.<br /> <br /> == My PineTime arrived, now what? ==<br /> <br /> You should start by testing out all the features of the watch, to make sure everything works. Power it on and check the display.<br /> <br /> PineTime is shipped with InfiniTime firmware. Press the watch button to show the clock, then swipe up on the touchscreen to reveal the menu.<br /> <br /> You probably now wish to update the bootloader and firmware.<br /> <br /> == What's the OS that's preinstalled on the PineTime by default? ==<br /> <br /> PineTime ships with the open source [https://github.com/JF002/InfiniTime InfiniTime firmware].<br /> <br /> To support firmware update and rollback, PineTime includes the open source [https://lupyuen.github.io/pinetime-rust-mynewt/articles/mcuboot MCUBoot Bootloader].<br /> <br /> == Can we use this OS or its source code? ==<br /> <br /> Yes, [https://github.com/JF002/InfiniTime InfiniTime] and the [https://lupyuen.github.io/pinetime-rust-mynewt/articles/mcuboot MCUBoot Bootloader] are open source.<br /> <br /> == Why is the back exposed? Is it supposed to snap on? ==<br /> <br /> The back cover of the PineTime devkit is exposed so that you can flash and debug the device with the SWD pins. The main unit and cover does not snap (lock) together. If you want to attach the back cover anyway, you can use glue or tape.<br /> <br /> == What hardware should I use to flash code to the PineTime? ==<br /> <br /> There are several ways you can do this, check out [[Reprogramming the PineTime]]<br /> <br /> == How do I connect the PineTime to a programmer? ==<br /> <br /> Here's how: [[PineTime devkit wiring]]<br /> <br /> == How do I set the time on PineTime? ==<br /> <br /> You can use either nRF Connect, custom GadgetBridge build or the proprietary Da Fit app. See [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#set-pinetime-date-and-time-with-nrf-connect &quot;Set PineTime Date and Time with nRF Connect&quot;]<br /> <br /> You can also set the time using your PinePhone or other Linux-based Bluetooth LE capable device with the Bluez software installed. Install the bluez package and make sure your PineTime is running and awake with InfiniTime 0.7.1 or later.<br /> <br /> $ bluetoothctl<br /> [ bluetooth ]# scan on<br /> ...<br /> [NEW] Device D7:03:FB:6E:31:B2 Pinetime-JF<br /> ...<br /> [bluetooth]# pair D7:03:FB:6E:31:B2<br /> Attempting to pair with D7:03:FB:6E:31:B2<br /> ...<br /> [NEW] Characteristic (Handle 0xfd80)<br /> /org/bluez/hci0/dev_D7_03_FB_6E_31_B2/service0015/char0016<br /> 00002a2b-0000-1000-8000-00805f9b34fb<br /> Current Time<br /> ...<br /> [Pinetime-JF]# menu gatt<br /> ...<br /> [Pinetime-JF]# select-attribute /org/bluez/hci0/dev_D7_03_FB_6E_31_B2/service0015/char0016<br /> [Pinetime-JF:/service0015/char0016]# read<br /> Attempting to read /org/bluez/hci0/dev_D7_03_FB_6E_31_B2/service0015/char0016<br /> [CHG] Attribute /org/bluez/hci0/dev_D7_03_FB_6E_31_B2/service0015/char0016 Value:<br /> b2 07 01 01 00 04 15 00 00 ......... <br /> b2 07 01 01 00 04 15 00 00 .........<br /> [Pinetime-JF:/service0015/char0016]# write &quot;0xe4 0x07 0x0c 0x1f 0x0e 0x02 0x00 0x00 0x00&quot;<br /> <br /> This is the format for the current time as hex bytes:<br /> &lt;lsb of year&gt; &lt;msb of year&gt; &lt;month (1-12)&gt; &lt;day (1-31)&gt; &lt;hour (0-23)&gt; &lt;minute (0-59)&gt; &lt;seconds (0-59)&gt; &lt;weekday (1-7 where 1=Monday)&gt; &lt;fractions (1/256th of second)&gt;<br /> <br /> == Is there a standard agreed method of pushing OTA updates so that one could seal the PineTime dev kit nicely? ==<br /> <br /> InfiniTime supports firmware updates over Bluetooth LE with the nRF Connect mobile app. See [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#download-and-test-our-pinetime-firmware &quot;Download and Test Our PineTime Firmware&quot;]<br /> <br /> == My PineTime's screen shows garbage, how do I fix it? ==<br /> <br /> This is usually caused by unplugging the device after it has booted, it needs to be reinitialised. To do so just restart the watch by removing power to it.<br /> <br /> == I have experience developing on Arduino. How does the PineTime compare? ==<br /> <br /> To learn programming on PineTime, [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud check out this article]<br /> <br /> Arduino provides the Arduino IDE (or you use the avr-gcc and avrdude command-line tools) which you can use to compile and upload code to an Arduino board. The PineTime and its ARM processor doesn't have this, so you'll have to familiarize yourself with tools like GCC for ARM, and OpenOCD. Some experience with Arduino does translate over to the PineTime, especially if you've worked with LCD's, or SPI. The PineTime is at least four times faster than an Arduino Uno (even faster at certain specific workloads due to hardware acceleration), and it has 32 times more RAM and 16 times more flash storage.<br /> <br /> [https://github.com/lupyuen/ Lup Yuen Lee] (just call him Lup, rhymes with &quot;Up&quot;) has written many articles on PineTime programming. [https://lupyuen.github.io/ Check out the articles here]<br /> <br /> == Can I code firmware for PineTime without an actual PineTime? ==<br /> <br /> Yes, you may code PineTime Watch Faces and preview them in a web browser (thanks to WebAssembly)...<br /> <br /> [https://lupyuen.github.io/pinetime-rust-mynewt/articles/simulator PineTime Simulator]<br /> <br /> Then flash your firmware remotely to a real PineTime via Telegram, and watch your firmware run in a live video stream...<br /> <br /> [https://github.com/lupyuen/remote-pinetime-bot/blob/master/README.md Remote PineTime]<br /> <br /> == What do I need for building PineTime firmware locally on my computer? ==<br /> <br /> Most flavours of PineTime firmware (InfiniTime, Hypnos, Klok, wasp-os) will build fine on Linux (x64, Arm32, Arm64) and macOS. Just follow the instructions provided.<br /> <br /> Download version 9-2020-q2-update of the [https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads Arm Embedded Toolchain arm-none-eabi-gcc]. Other versions of gcc may have problems building the firmware correctly.<br /> <br /> On Windows, install [https://docs.microsoft.com/en-us/windows/wsl/about Windows Subsystem for Linux (WSL)] and execute the build steps inside the WSL Terminal (instead of the Windows Command Prompt). USB Programmers (like ST-Link and JLink) are not supported in WSL, so use the Windows Command Prompt to flash your built firmware to PineTime.<br /> <br /> [https://github.com/lupyuen/pinetime-rust-mynewt/blob/master/README.md pinetime-rust-mynewt] firmware for PineTime supports building and flashing via the Windows Command Prompt (no need for MinGW and Docker).<br /> <br /> == Can I use Pinebook Pro for developing PineTime? ==<br /> <br /> Yes, use version 9-2020-q2-update of the [https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads Arm Embedded Toolchain arm-none-eabi-gcc]. Other versions of gcc may have problems building the firmware correctly.<br /> <br /> == What is ARM Semihosting? ==<br /> <br /> We use the SWD (Single Wire Debug) protocol created by ARM for flashing and debugging PineTime's nRF52832 microcontroller, which contains an ARM CPU. (SWD is derived from standard JTAG, but with fewer wires) With ARM CPUs you can trigger a software breakpoint, and allow the debugger (OpenOCD) to do something really nifty: Display a message, read console input, dump out a file, even read a file. That's called ARM Semihosting. [http://www.keil.com/support/man/docs/armcc/armcc_pge1358787046598.htm More about ARM Semihosting]<br /> <br /> == What is OpenOCD? ==<br /> <br /> OpenOCD is Open On-Chip Debugger. It's the software that drives your microcontroller debugger/flasher. We need it for running any kind of flashing and debugging with Pi or ST-Link. gdb talks to OpenOCD for debugging firmware. gdb also works with VSCode for debugging firmware visually. [http://openocd.org/doc-release/html/About.html#What-is-OpenOCD_003f More about OpenOCD]<br /> <br /> Please use [https://xpack.github.io/openocd xPack OpenOCD] with PineTime. Other versions of OpenOCD seem to have problems with PineTime.<br /> <br /> == How do I remove flash protection? ==<br /> <br /> PineTime watches shipped before 20 Sep 2020 have flash protection enabled.<br /> <br /> The flash protection can be removed using multiple different methods. If you don't have anything except the PineTime, not even a Raspberry Pi, then you have to order a programmer online: you can use a J-Link, CMSIS-DAP dongle and various other programmers. See [[Reprogramming_the_PineTime|this page to see various methods of reprogramming the PineTime]].<br /> <br /> If your PineTime was shipped after 20 Sep 2020, you don't need to remove flash protection. They are shipped with flash protection disabled. You can flash and debug PineTime right away with ST-Link, JLink and Raspberry Pi.<br /> <br /> == Why can't you use ST-Link to remove nRF52 Flash Protection? ==<br /> <br /> Because ST-Link is a High Level Adapter. It doesn't really implement all SWD functions, just a subset (probably to keep the price low). More details in the section &quot;Why Visual Studio Code with ST-Link (instead of nRFgo Studio with J-LINK)&quot; in the article [https://medium.com/@ly.lee/coding-nrf52-with-rust-and-apache-mynewt-on-visual-studio-code-9521bcba6004?source=friends_link&amp;sk=bb4e2523b922d0870259ab3fa696c7da &quot;Coding nRF52 with Rust and Apache Mynewt on Visual Studio Code&quot;].<br /> <br /> == Since we need a low level SWD adapter like Raspberry Pi anyway, can we do everything on a Pi instead of ST-Link + Windows? ==<br /> <br /> Yes, Raspberry Pi works for flashing and debugging PineTime, even for removing flash protection. We have a special version of OpenOCD called OpenOCD SPI that talks to PineTime's SWD port over SPI (without bit-banging). See [https://github.com/lupyuen/pinetime-updater/blob/master/README.md PineTime Updater]<br /> <br /> == Is there a 3D model of PineTime available somewhere? ==<br /> <br /> Not yet. Someone did design a cover you can snap on to keep the back shut. [https://www.thingiverse.com/thing:4172849 More details]<br /> <br /> == Are there any alternatives to the wrist band provided with the PineTime? ==<br /> <br /> No, but PineTime accepts standard 20mm wrist band that is widely available by a third party.<br /> <br /> Note that some sellers have a different point of view on what standard is. So you should always check the fitting to make sure it looks like the one used by PineTime.<br /> <br /> == Troubleshooting PineTime's Bluetooth (InfiniTime firmware) ==<br /> <br /> Old (pre 1.4) InfiniTime firmware had an issue where Bluetooth connectivity sometimes gets lost/fails.<br /> <br /> The fix was to soft-reset the watch, by holding the PineTime button for ~8 seconds until the PineCone logo appears.<br /> <br /> == I'm stuck. How can I get help? ==<br /> <br /> Chat with the PineTime Community on [[PineTime#Community|Matrix / Discord / Telegram / IRC]] (They are bridged into a single chatroom)<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_Hardware_Wishlist&diff=11715 2021-10-25T09:22:08Z

<p>Avamander: </p> <hr /> <div>This page contains a list of things people wish PineTime did differently<br /> <br /> === Hardware ===<br /> <br /> * Long pressing the button should power-cycle the watch without any software being involved<br /> * Other display technology could be explored.<br /> **[//en.Wikipedia.org/wiki/Transflective_liquid-crystal_display A transflective LCD]<br /> *** Increased readability in bright daylight<br /> **[//en.wikipedia.org/wiki/OLED OLED]<br /> *** Self-emissive display (pixels emit their own light)<br /> *** Allows for lower power usage with mostly black screens<br /> *** Allows for low power visual notifications (imagine an always-on small red square in the corner to indicate a notification)<br /> * Touchscreen with configurable sensitivity<br /> ** Ideal for gloved fingers and water droplet resistance<br /> ** Preferably it should remain capacitive, as a resistive touchscreen would have too many trade-offs.<br /> * A slightly bigger 256×256 pixel display<br /> ** This resolution is preferable for its binary alignment for low-level simplicity<br /> ** It has the property that its X and Y coordinates are each addressable with a single byte, with no bounds checking<br /> ** Its total number of pixels is a power of 2 (65536), and each pixel is addressable with exactly 2 bytes.<br /> ** The [http://Pelulamu.net/ibniz IBNIZ (Ideally Bare Numeric Impression giZmo) virtual machine], designed for minimalist demoscene graphics, has chosen 256×256 for its virtual display specifically for code efficiency.<br /> ** If PineTime also chose 256×256 then it would be a target platform for unclipped IBNIZ demoscene programmes, which would be really fun to play around with on one's wrist!<br /> * Full screen refresh is very slow<br /> ** A full 16-bit redraw on the display takes at worst 120ms, which is 8Hz<br /> ** Modest optimization is possible by adopting 12-bit color<br /> ** A smooth scrolling/usage/animation experience would be 30Hz minimum, preferably 60hz<br /> ** Display redraw is currently bottlenecked by the nRF52832 maximum SPI clock (8MHz).<br /> ** The nRF528(33/40) has one high speed SPI master which supports 32MHz, still well below the ST7789 maximum<br /> ** Parallel data transfer could be an option, but using more GPIOs (which don't look available)<br /> * Some sort of scroll wheel would be nice for convenience.<br /> * Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)<br /> * Wireless charging, or Qi Charging capability<br /> * nRF5840 update<br /> ** 32MHz HS SPI, QuadSPI, CryptoCell + Secure Key Storage, more RAM, a coprocessor and the possibility to expose USB through power pins<br /> * Preferably a pre-certified MCU module with a ceramic antenna<br /> * Version without sensors but maybe bigger battery<br /> * Pins on the programmer connector to allow UART while developing (currently there is a TX test point on PCB). (Note: There's ARM SemiHosting, ITM and Segger RTT)<br /> * Connect SDO of ST7889 LCD controller to MCU.<br /> ** Allows MCU to execute READ commands<br /> ** Possibility of leveraging ST7889 RAM to save MCU RAM?<br /> * LCD must be centered on case. Currently is not and watchfaces seems different when clock is put on the other wrist.<br /> * A NFC antenna around the case, connected to the NFC pins.<br /> * Used sensors should be NDA-free and preferably also blob-free for easier development<br /> ** Possibly replace BMA421 accelerometer<br /> *** The BMA421 doesn't have a public datasheet<br /> *** Special attention should be paid to advanced features, such as step counting integration or flick detection.<br /> * PineTime SoC could support USB or have a FTDI chip with the relevant pins exposed.<br /> ** It could allow flashing a sealed device, just like Arduinos work.<br /> ** Alternatively, an USB-C port could be added that provides these features. <br /> * A bigger pulldown resistor for the power button<br /> ** 100k still leaks a noticeable amount of power when the button is always on.<br /> * Ceramic Bluetooth antenna for better signal reception<br /> * An external RTC circuit<br /> ** Allows the main MCU go to deep-sleep while retaining time.<br /> ** Allows time retention through MCU reset.<br /> * Ultra low quiescent current PMIC<br /> ** In theory could provide a hard reset capability based on button press<br /> ** Better deep sleep/shipping/storage/off lifetime<br /> *** A nano-power system timer IC could in theory provide a RTC, MOSFET-controlled deep sleep, watchdog timer and button-controlled reset<br /> ** Built-in &quot;fuel gauge&quot; for better estimation of battery capacity<br /> * Small Piezo Buzzer<br /> ** Use case would be for very short beeps (think old-school casio watch) as notification.<br /> ** Of course developers can PWM other frequency to make it sing, but piezos tend to be shrill.<br /> <br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_Hardware_Wishlist&diff=11565 2021-10-03T14:43:03Z

<p>Avamander: </p> <hr /> <div>This page contains a list of things people wish PineTime did differently<br /> <br /> === Hardware ===<br /> <br /> * Long pressing the button should power-cycle the watch without any software being involved<br /> * Other display technology could be explored.<br /> **[//en.Wikipedia.org/wiki/Transflective_liquid-crystal_display A transflective LCD]<br /> *** Increased readability in bright daylight<br /> **[//en.wikipedia.org/wiki/OLED OLED]<br /> *** Self-emissive display (pixels emit their own light)<br /> *** Allows for lower power usage with mostly black screens<br /> *** Allows for low power visual notifications (imagine an always-on small red square in the corner to indicate a notification)<br /> * Touchscreen with configurable sensitivity<br /> ** Ideal for gloved fingers and water droplet resistance<br /> ** Preferably it should remain capacitive, as a resistive touchscreen would have too many trade-offs.<br /> * A slightly bigger 256×256 pixel display<br /> ** This resolution is preferable for its binary alignment for low-level simplicity<br /> ** It has the property that its X and Y coordinates are each addressable with a single byte, with no bounds checking<br /> ** Its total number of pixels is a power of 2 (65536), and each pixel is addressable with exactly 2 bytes.<br /> ** The [http://Pelulamu.net/ibniz IBNIZ (Ideally Bare Numeric Impression giZmo) virtual machine], designed for minimalist demoscene graphics, has chosen 256×256 for its virtual display specifically for code efficiency.<br /> ** If PineTime also chose 256×256 then it would be a target platform for unclipped IBNIZ demoscene programmes, which would be really fun to play around with on one's wrist!<br /> * Full screen refresh is very slow<br /> ** A full 16-bit redraw on the display takes at worst 120ms, which is 8Hz<br /> ** Modest optimization is possible by adopting 12-bit color<br /> ** A smooth scrolling/usage/animation experience would be 30Hz minimum, preferably 60hz<br /> ** Display redraw is currently bottlenecked by the nRF52832 maximum SPI clock (8MHz).<br /> ** The nRF528(33/40) has one high speed SPI master which supports 32MHz, still well below the ST7789 maximum<br /> ** Parallel data transfer could be an option, but using more GPIOs (which don't look available)<br /> * Some sort of scroll wheel would be nice for convenience.<br /> * Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)<br /> * Wireless charging, or Qi Charging capability<br /> * An external RTC circuit<br /> ** Allows the main MCU go to deep-sleep while retaining time.<br /> ** Allows time retention through MCU reset.<br /> * nRF5840 update<br /> ** 32MHz HS SPI, QuadSPI, CryptoCell + Secure Key Storage, more RAM, a coprocessor and the possibility to expose USB through power pins<br /> * Preferably a pre-certified MCU module with a ceramic antenna<br /> * Version without sensors but maybe bigger battery<br /> * Pins on the programmer connector to allow UART while developing (currently there is a TX test point on PCB). (Note: There's ARM SemiHosting, ITM and Segger RTT)<br /> * Connect SDO of ST7889 LCD controller to MCU.<br /> ** Allows MCU to execute READ commands<br /> ** Possibility of leveraging ST7889 RAM to save MCU RAM?<br /> * LCD must be centered on case. Currently is not and watchfaces seems different when clock is put on the other wrist.<br /> * A NFC antenna around the case, connected to the NFC pins.<br /> * Used sensors should be NDA-free and preferably also blob-free for easier development<br /> ** Possibly replace BMA421 accelerometer<br /> *** The BMA421 doesn't have a public datasheet<br /> *** Special attention should be paid to advanced features, such as step counting integration or flick detection.<br /> * PineTime SoC could support USB or have a FTDI chip with the relevant pins exposed.<br /> ** It could allow flashing a sealed device, just like Arduinos work.<br /> ** Alternatively, an USB-C port could be added that provides these features. <br /> * A bigger pulldown resistor for the power button<br /> ** 100k still leaks a noticeable amount of power when the button is always on.<br /> * Ceramic Bluetooth antenna for better signal reception<br /> * Ultra low quiescent current PMIC<br /> ** Better deep sleep/shipping/storage/off lifetime<br /> ** Built-in &quot;fuel gauge&quot; for better estimation of battery capacity<br /> * Small Piezo Buzzer<br /> ** Use case would be for very short beeps (think old-school casio watch) as notification.<br /> ** Of course developers can PWM other frequency to make it sing, but piezos tend to be shrill.<br /> <br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_Hardware_Wishlist&diff=11563 2021-10-03T14:09:05Z

<p>Avamander: </p> <hr /> <div>This page contains a list of things people wish PineTime did differently<br /> <br /> === Hardware ===<br /> <br /> * Long pressing the button should power-cycle the watch without any software being involved<br /> * Other display tech could be explored. [//en.Wikipedia.org/wiki/Transflective_liquid-crystal_display A transflective LCD] would probably be a nice option. Or potentially OLED?<br /> * Touchscreen should possibly have a configurable sensitivity level for both glove-wearing and droplet-resistance. Preferably it should still be a capacitive one, a resistive touchscreen would have too many trade-offs.<br /> * A slightly bigger 256×256 pixel graphics display size is preferable for its binary alignment, affording some low-level simplicity – it has the property that its X and Y coordinates are each addressable with a single byte, with no out-of-bounds; its total number of pixels is 65536 (another power of 2), and each pixel is addressable with exactly 2 bytes, with perfect efficiency. The [http://Pelulamu.net/ibniz IBNIZ (Ideally Bare Numeric Impression giZmo) virtual machine], designed for fun minimalist demoscene graphics, has chosen 256×256 for its virtual display, and makes use of these simplicity advantages. If PineTime also chose 256×256 then it would be a target platform for unclipped IBNIZ demoscene programmes, which would be really fun to play around with on one's wrist!<br /> * A full 16-bit redraw on the display takes 120ms at the very least, which is 8Hz (although modest optimization is possible by adopting 12-bit color). A smooth scrolling/usage/animation experience would be 30Hz minimum, preferably 60. Display redraw is currently bottlenecked by the nRF52832 maximum SPI clock (8MHz).<br /> * Some sort of scroll wheel would be nice for convenience.<br /> * Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)<br /> * Wireless charging, or Qi Charging capability<br /> * An external RTC circuit saving the current time to allow the main MCU go to deep-sleep.<br /> * nRF5840 update: QSPI, CryptoCell + Secure Key Storage, has more RAM, a coprocessor and the possibility to expose USB through power pins<br /> * Preferably a pre-certified MCU module with a ceramic antenna<br /> * Version without sensors but maybe bigger battery<br /> * A couple of pins on the programmer connector to allow UART while developing (currently there is a TX test point on PCB). (Note: There's ARM SemiHosting, ITM and Segger RTT)<br /> * Connect the pin of LCD controller that allows RD/WR from it in order to save RAM on the MCU. (The MOSI pin for the SPI is already connected to the nor flash that shares the same pins, pin number is P0.04)<br /> * LCD must be centered on case. Currently is not and watchfaces seems different when clock is put on the other wrist.<br /> * A NFC antenna around the case, connected to the NFC pins.<br /> * Used sensors should be NDA-free and preferably also blob-free. For example the BMA421 accelerometer doesn't have a datasheet (it seems private to some hardware integrators): a more open one would be much easier to develop for. Special attention should be paid to advanced features, such as step counting integration or flick detection.<br /> * PineTime SoC could support USB or have a FTDI chip with the relevant pins exposed. It could allow flashing a sealed device, just like Arduinos work. * An USB-C connector instead of a magnetic one could be used.<br /> * A bigger pulldown resistor for the power button, because 100k still leaks a noticeable amount of power when the button is always on.<br /> * Ceramic Bluetooth antenna for better signal reception<br /> * Ultra low quiescent current PMIC for better deep sleep. Better shipping/storage/turned off mode. Preferably also a built-in &quot;fuel gauge&quot; functionality for better estimation of battery capacity<br /> * A separate RTC or built-in functionality in the main MCU to maintain time setting through MCU reset<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_Hardware_Wishlist&diff=11562 2021-10-03T14:08:41Z

<p>Avamander: </p> <hr /> <div>This page contains a list of things people wish PineTime did differently<br /> <br /> === Hardware ===<br /> <br /> * Long pressing the button should power-cycle the watch without any software being involved<br /> * Other display tech could be explored. [//en.Wikipedia.org/wiki/Transflective_liquid-crystal_display A transflective LCD] would probably be a nice option. Or potentially OLED?<br /> * Touchscreen should possibly have a configurable sensitivity level for both glove-wearing and droplet-resistance. Preferably it should still be a capacitive one, a resistive touchscreen would have too many trade-offs.<br /> * A slightly bigger 256×256 pixel graphics display size is preferable for its binary alignment, affording some low-level simplicity – it has the property that its X and Y coordinates are each addressable with a single byte, with no out-of-bounds; its total number of pixels is 65536 (another power of 2), and each pixel is addressable with exactly 2 bytes, with perfect efficiency. The [http://Pelulamu.net/ibniz IBNIZ (Ideally Bare Numeric Impression giZmo) virtual machine], designed for fun minimalist demoscene graphics, has chosen 256×256 for its virtual display, and makes use of these simplicity advantages. If PineTime also chose 256×256 then it would be a target platform for unclipped IBNIZ demoscene programmes, which would be really fun to play around with on one's wrist!<br /> * A full 16-bit redraw on the display takes 120ms at the very least, which is 8Hz (although modest optimization is possible by adopting 12-bit color). A smooth scrolling/usage/animation experience would be 30Hz minimum, preferably 60. Display redraw is currently bottlenecked by the nRF52832 maximum SPI clock (8MHz).<br /> * Some sort of scroll wheel would be nice for convenience.<br /> * Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)<br /> * Wireless charging, or Qi Charging capability<br /> * An external RTC circuit saving the current time to allow the main MCU go to deep-sleep.<br /> * nRF5840 update: QSPI, CryptoCell + Secure Key Storage, has more RAM, a coprocessor and the possibility to expose USB through power pins<br /> * Preferably a pre-certified MCU module with a ceramic antenna<br /> * Version without sensors but maybe bigger battery<br /> * A couple of pins on the programmer connector to allow UART while developing (currently there is a TX test point on PCB). (Note: There's ARM SemiHosting, ITM and Segger RTT)<br /> * Connect the pin of LCD controller that allows RD/WR from it in order to save RAM on the MCU. (The MOSI pin for the SPI is already connected to the nor flash that shares the same pins, pin number is P0.04)<br /> * LCD must be centered on case. Currently is not and watchfaces seems different when clock is put on the other wrist.<br /> * A NFC antenna around the case, connected to the NFC pins.<br /> * Used sensors should be NDA-free and preferably also blob-free. For example the BMA421 accelerometer doesn't have a datasheet (it seems private to some hardware integrators): a more open one would be much easier to develop for. Special attention should be paid to advanced features, such as step counting integration or flick detection.<br /> * PineTime SoC could support USB or have a FTDI chip with the relevant pins exposed. It could allow flashing a sealed device, just like Arduinos work. * An USB-C connector instead of a magnetic one could be used.<br /> * A bigger pulldown resistor for the power button, because 100k still leaks a noticeable amount of power when the button is always on.<br /> * Ceramic Bluetooth antenna for better signal reception<br /> * Ultra low quiescent current PMIC for better deep sleep. Better shipping/storage/turned off mode<br /> * A separate RTC or built-in functionality in the main MCU to maintain time setting through MCU reset<br /> * Battery charger IC with built-in &quot;fuel gauge&quot; functionality for better estimation of battery capacity<br /> <br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_Hardware_Wishlist&diff=11561 2021-10-03T14:07:46Z

<p>Avamander: </p> <hr /> <div>This page contains a list of things people wish PineTime did differently<br /> <br /> === Hardware ===<br /> <br /> * Long pressing the button should power-cycle the watch without any software being involved<br /> * Other display tech could be explored. [//en.Wikipedia.org/wiki/Transflective_liquid-crystal_display A transflective LCD] would probably be a nice option. Or potentially OLED?<br /> * Touchscreen should possibly have a configurable sensitivity level for both glove-wearing and droplet-resistance. Preferably it should still be a capacitive one, a resistive touchscreen would have too many trade-offs.<br /> * A slightly bigger 256×256 pixel graphics display size is preferable for its binary alignment, affording some low-level simplicity – it has the property that its X and Y coordinates are each addressable with a single byte, with no out-of-bounds; its total number of pixels is 65536 (another power of 2), and each pixel is addressable with exactly 2 bytes, with perfect efficiency. The [http://Pelulamu.net/ibniz IBNIZ (Ideally Bare Numeric Impression giZmo) virtual machine], designed for fun minimalist demoscene graphics, has chosen 256×256 for its virtual display, and makes use of these simplicity advantages. If PineTime also chose 256×256 then it would be a target platform for unclipped IBNIZ demoscene programmes, which would be really fun to play around with on one's wrist!<br /> * A full 16-bit redraw on the display takes 120ms at the very least, which is 8Hz (although modest optimization is possible by adopting 12-bit color). A smooth scrolling/usage/animation experience would be 30Hz minimum, preferably 60. Display redraw is currently bottlenecked by the nRF52832 maximum SPI clock (8MHz).<br /> * Some sort of scroll wheel would be nice for convenience.<br /> * Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)<br /> * Wireless charging, or Qi Charging capability<br /> * An external RTC circuit saving the current time to allow the main MCU go to deep-sleep.<br /> * nRF5840 update: QSPI, CryptoCell + Secure Key Storage, has more RAM, a coprocessor and the possibility to expose USB through power pins<br /> * Preferably a pre-certified MCU module with a ceramic antenna<br /> * Version without sensors but maybe bigger battery<br /> * A couple of pins on the programmer connector to allow UART while developing (currently there is a TX test point on PCB). (Note: There's ARM SemiHosting, ITM and Segger RTT)<br /> * Connect the pin of LCD controller that allows RD/WR from it in order to save RAM on the MCU. (The MOSI pin for the SPI is already connected to the nor flash that shares the same pins, pin number is P0.04)<br /> * LCD must be centered on case. Currently is not and watchfaces seems different when clock is put on the other wrist.<br /> * A NFC antenna around the case, connected to the NFC pins.<br /> * Used sensors should be NDA-free and preferably also blob-free. For example the BMA421 accelerometer doesn't have a datasheet (it seems private to some hardware integrators): a more open one would be much easier to develop for. Special attention should be paid to advanced features, such as step counting integration or flick detection.<br /> * PineTime SoC could support USB or have a FTDI chip with the relevant pins exposed. It could allow flashing a sealed device, just like Arduinos work. * An USB-C connector instead of a magnetic one could be used.<br /> * A bigger pulldown resistor for the power button, because 100k still leaks a noticeable amount of power when the button is always on.<br /> * Ceramic Bluetooth antenna for better signal reception<br /> * Ultra low quiescent current PMIC for better deep sleep. Better shipping/storage/turned off mode<br /> * Separate RTC chip to maintain time setting through MCU reset<br /> * Battery charger IC with built-in &quot;fuel gauge&quot; functionality for better estimation of battery capacity<br /> <br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=Reprogramming_the_PineTime&diff=10932 2021-07-28T21:00:10Z

<p>Avamander: /* Uploading new software */</p> <hr /> <div>= Introduction =<br /> <br /> 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. <br /> <br /> '''Before you can use your debugger/programmer, you probably have to [[PineTime devkit wiring|wire up your pinetime]]. Heavily recommended you read this first!'''<br /> <br /> 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:<br /> <br /> * Unlocking the device '''Note: PineTime watches shipped after 20 Sep 2020 do not require unlocking. They are shipped unlocked.'''<br /> * Uploading new software<br /> * Running a debugger<br /> <br /> All of these are described in this article. <br /> <br /> 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.<br /> <br /> = SWD Pinout =<br /> <br /> See [[PineTime devkit wiring|PineTime devkit wiring]]<br /> <br /> = nrfjprog (for Segger JLink) =<br /> <br /> 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].<br /> <br /> === Hookup ===<br /> <br /> Connect the Pinetime SWD pins to the debugger (P20 on NRF52-DK)<br /> <br /> {| class=&quot;wikitable&quot;<br /> !Pinetime<br /> !JLink<br /> |-<br /> |GND<br /> |GND<br /> |-<br /> |SWDCLK<br /> |SWDCLK<br /> |-<br /> |SWDIO<br /> |SWDIO<br /> |-<br /> |VCC (3.3V)<br /> |VTG (target detect)<br /> |}<br /> <br /> === Unlocking the FLASH ===<br /> <br /> Unlocking the device and erase the memory. <br /> <br /> '''You need to execute this step only once, to remove the read protection on the memory. Note that it will erase the whole flash memory of the MCU!''' :<br /> <br /> nrfjprog -f NRF52 --recover<br /> <br /> === Uploading new software ===<br /> <br /> 1. Program the BLE softdevice (if needed by the firmware). Replace PATH_TO_NRF_SDK by the path where you unzipped the [https://www.nordicsemi.com/Software-and-Tools/Software/nRF5-SDK NRF52 SDK] :<br /> <br /> nrfjprog -f NRF52 --program /PATH_TO_NRF_SDK/components/softdevice/s132/hex/s132_nrf52_6.1.1_softdevice.hex --sectorerase<br /> <br /> 2. Program the firmware (replace firmware.hex by the actual filename of the firmware):<br /> <br /> nrfjprog -f NRF52 --program firmware.hex --sectorerase<br /> <br /> 3. Reset and run the new firmware:<br /> <br /> nrfjprog -f NRF52 --reset<br /> <br /> = OpenOCD =<br /> <br /> OpenOCD, the Open On-Chip Debugger supports multiple different adapters. You can read more about it here: http://openocd.org/<br /> <br /> == Adapters ==<br /> <br /> 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''.<br /> <br /> You can simplify your life by creating a configuration file that contains the interface, transport, target and speed configuration. Things like CLion also need one to work properly.<br /> <br /> 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'').<br /> <br /> === CMSIS-DAP ===<br /> <br /> Issue this command to initialize a connection to the devkit:<br /> <br /> openocd \<br /> -c 'source [find interface/cmsis-dap.cfg]' \<br /> -c 'transport select swd' \<br /> -c 'source [find target/nrf52.cfg]' \<br /> -c 'adapter speed 8000' \<br /> -c 'init'<br /> <br /> === JLink ===<br /> <br /> Start OpenOCD:<br /> <br /> openocd \<br /> -c 'source [find interface/jlink.cfg]' \<br /> -c 'transport select swd' \<br /> -c 'source [find target/nrf52.cfg]' \<br /> -c 'adapter speed 8000' \<br /> -c 'init'<br /> <br /> === Raspberry Pi ===<br /> <br /> openocd \<br /> -c 'source bcm2835spi' \<br /> -c 'bcm2835spi_speed 31200' \<br /> -c 'source [find target/nrf52.cfg]' \<br /> -c 'init'<br /> <br /> === STLink ===<br /> <br /> Connect PineTime SWD Pins to ST-Link v2 as follows:<br /> <br /> {| class=&quot;wikitable&quot;<br /> !PineTime<br /> !ST-Link<br /> |-<br /> |GND<br /> |GND<br /> |-<br /> |SWDCLK<br /> |SWDCLK<br /> |-<br /> |SWDIO<br /> |SWDIO<br /> |-<br /> |VCC (3.3V)<br /> |3.3V<br /> |}<br /> <br /> [[File:pinetime-stlink.jpg|400px]]<br /> <br /> Note that only the bottom row of pins on ST-Link are used.<br /> <br /> To flash PineTime with ST-Link on Linux and macOS, use [https://github.com/lupyuen/pinetime-updater/blob/master/README.md PineTime Updater]<br /> <br /> [[PineTime FAQ|'''ST-Link can't be used to remove nRF52 flash protection''']]<br /> <br /> == Unlocking the device ==<br /> <br /> If you need to disable access port protection then you can do this using the following commands below.<br /> <br /> This can be done in two ways:<br /> <br /> Appending this to OpenOCD command line:<br /> <br /> -c 'nrf52.dap apreg 1 0x04' -c 'nrf52.dap apreg 1 0x04 0x01' -c 'nrf52.dap apreg 1 0x04'<br /> <br /> Or by using the telnet connection, just type in ''telnet localhost 4444'' and then you can issue commands to OpenOCD:<br /> <br /> Note: ''Unlocking the device to remove access port protection will erase the contents of flash.''<br /> <br /> telnet localhost 4444<br /> Trying 127.0.0.1...<br /> Connected to localhost.<br /> Escape character is '^]'.<br /> Open On-Chip Debugger<br /> &gt; nrf52.dap apreg 1 0x04<br /> 0x00000000<br /> &gt; nrf52.dap apreg 1 0x04 0x01<br /> &gt; nrf52.dap apreg 1 0x04<br /> 0x00000001<br /> <br /> (If the ''nrf52.dap'' command cannot be found, try just ''dap'' instead.)<br /> <br /> == Uploading new software ==<br /> <br /> Just issue this command, replace ''code.hex'' with your own (and cmsis-dap.cfg with an appropriate adapter).<br /> <br /> openocd \<br /> -c 'source [find interface/cmsis-dap.cfg]' \<br /> -c 'transport select swd' \<br /> -c 'source [find target/nrf52.cfg]' \<br /> -c 'init' \<br /> -c 'halt' \<br /> -c 'nrf5 mass_erase' \<br /> -c 'program code.hex verify' \<br /> -c 'reset' \<br /> -c 'exit'<br /> <br /> = Black Magic Probe =<br /> <br /> 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].<br /> <br /> === Native adapters ===<br /> <br /> The native adapters are the official Black Magic family of debug adapters, including the original Black Magic Probe and the Black Magic Probe Mini. By buying the official hardware you are supporting the continued development of the Black Magic Probe software.<br /> <br /> Providing your native adapter is running up-to-date firmware then it can be used to program your PineTime.<br /> <br /> === STM32 (Blue Pill) ===<br /> <br /> It is possible to flash a popular development board based on STM32F103C8T6 microcontroller, known as Blue Pill, to make a BlackMagic Probe device. For example, one may follow instructions in [https://forum.pine64.org/showthread.php?tid=8816&amp;pid=57095#pid57095 forum post] or [https://gist.github.com/darnel/dac1370d057e176386ca4026418abc2b gist] (mac os). Also, it is possible to use SWD pins on the board to flash other devices, instead using arbitrary pins on the board itself. See [https://buger.dread.cz/black-magic-probe-bmp-on-bluepill-stm32f103c8-minimum-system-development-board.html this link] for more detals.<br /> <br /> === Other hardware ===<br /> <br /> The Black Magic Probe firmware can be run on a variety of host devices. See [https://github.com/blacksphere/blackmagic/wiki/Debugger-Hardware BMP Debugger Hardware] for more information.<br /> <br /> === Using the BMP to flash the PineTime ===<br /> <br /> Refer to the BMP [https://github.com/blacksphere/blackmagic/wiki/Useful-GDB-commands wiki] for the full description of commands.<br /> Overall, the process on Linux is like following. (/dev/ttyBmpGdb is a symlink created by the udev rule). It's useful to create a gdb script file (or .gdbinit) with following commands:<br /> <br /> target extended-remote /dev/ttyBmpGdb<br /> monitor swdp_scan<br /> attach 1<br /> file %firmware file%<br /> <br /> Then one may use '''load''' command to flash the firmware, '''compare-sections''' to verify the upload, or '''monitor erase_mass''' to erase the firmware. <br /> <br /> Then, proceed with debugging as normal.<br /> <br /> <br /> = External links and additional tutorials = <br /> <br /> * https://github.com/jlukanc1/pinetime-boot-flasher<br /> * https://blog.aegrel.ee/absniffer-cmsis-dap-sniffer.html<br /> * https://blog.dbrgn.ch/2020/5/16/nrf52-unprotect-flash-jlink-openocd/<br /> * https://medium.com/@ly.lee/openocd-on-raspberry-pi-better-with-swd-on-spi-7dea9caeb590<br /> * https://medium.com/@ly.lee/build-and-flash-rust-mynewt-firmware-for-pinetime-smart-watch-5e14259c55<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTimeStyle&diff=10915 2021-07-24T18:06:21Z

<p>Avamander: </p> <hr /> <div>=PineTimeStyle Watchface=<br /> PineTimeStyle is a watchface created for Infinitime and is expected to be included in version 1.3 of Infinitime.<br /> <br /> It is based on [https://www.dantilden.com/projects/timestyle/ TimeStyle for Pebble by Dan Tilden] with permission.<br /> <br /> [[File:PineTimeStyle.jpg|PineTimeStyle watchface]]<br /> <br /> ==Layout==<br /> The time is displayed on the left in either 12 or 24h format depending on the system setting.<br /> <br /> In the sidebar on the right there is a battery icon which displays the current charge level, and is replaced by a plug icon when charging. Below it is a bluetooth icon which appears only when bluetooth is connected. <br /> <br /> The current date is displayed in the middle, and at the bottom there is a small gauge which displays the step count. The gauge scales automatically based on the configured step goal, and the outside of the gauge will turn white when the step goal is reached.<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=Pinecil&diff=10855 2021-07-01T10:47:13Z

<p>Avamander: /* Specifications */</p> <hr /> <div>== Overall description ==<br /> [[File:Pinecil-bb2-01_rotate.jpg]]&lt;br&gt;<br /> The Pinecil is a portable, temperature controlled soldering iron. It also has the intended use of being a Risc-V development device using a breakout board. It's main features are:<br /> <br /> * Portability<br /> * Settable temperature<br /> * Soldering tips:<br /> ** Replaceable<br /> ** More than half a dozen available. Currently sold as 2 separate sets of 4, one fine set, the other larger.<br /> ** Compatible with TS100<br /> * Flexible power sources:<br /> ** Barrel jack<br /> ** USB Type C power delivery<br /> <br /> There are additional features that include (Useful for devkit use):<br /> <br /> * A Programmable Gigadevice Risc-V GD32V embedded processor<br /> * 0.67&quot; Monochrome Display that can render text or graphics<br /> * Support for Idle detection, for automatic power down of tip<br /> <br /> == Use ==<br /> <br /> Pinecil comes with a separate heating element / tip. After inserting its barrel into the end of the handle, lightly tighten the screw onto it. Loosen this screw when changing out the tip.<br /> <br /> The USB port, connected to any host, provides enough power to drive the user interface, but not necessarily enough to heat the tip. 5 volts from a USB 2 port will only display the user interface.<br /> <br /> To check the firmware version, hold down the &quot;-&quot; button. It will display something like &quot;v2.14.2425902 17-01-21&quot;, suggesting its actual release date, here 2021-01-17. Clicking the &quot;+&quot; button repeatedly reveals various internal settings, such as hardware version, current temperature, time since power-on, and number of motions detected. Clicking &quot;-&quot; returns to the regular display of current temperature, target temperature, and supply voltage. At other times it may show power draw.<br /> <br /> To actually heat up the tip, you will need a power supply that can provide 12V or more. This may be a dedicated power supply with a standard barrel connector (+ center, - outside) that supplies anywhere from 12V to 21V, or a USB-C supply that can negotiate up to such a voltage. (You probably have a suitable supply disused in a box somewhere.)<br /> <br /> Clicking &quot;+&quot; starts the tip heating. The display then shows power draw, current temperature, supply voltage, and estimated time to reach target temperature. You can adjust the target temperature with further clicks of &quot;+&quot; and &quot;-&quot; buttons. Waiting for the regular display to return, then holding down &quot;-&quot; for a moment turns the heat off. You can watch the temperature measurement go up and down. Certain settings involve holding down both buttons.<br /> <br /> The iron will &quot;sleep&quot;, switching to a lower temperature, after it has been put down for a short time, and heat up again when it is picked up.<br /> <br /> Clicking &quot;-&quot; when heat is off steps through menus to control a variety of settings, such as the sleep temperature, time until sleep, motion sensitivity, temperature units (C or F) etc.<br /> <br /> '''Menu Items''' items (accurate for firmware 2.1.14)<br /> <br /> * Power Source <br /> **(cutoff choices for voltage and battery operation)<br /> * QC voltage <br /> **(voltage to negotiate for with QC chargers (9, 12, 20 volts)<br /> * Soldering Settings<br /> ** Boost Temperature<br /> ** Auto Start<br /> ** Temperature Change (short click)<br /> ** Temperature Change (long click)<br /> ** Allow Lock (when soldering)<br /> * Sleep Settings<br /> ** Sleep Temperature<br /> ** Sleep Timeout<br /> ** Shutdown Time<br /> ** Motion Sensor Sensitivity<br /> ** Hall Sensor Sensitivity<br /> * User Interface<br /> ** Temperature Units (C/F)<br /> ** Display orientation (right/left)<br /> ** Cooldown Blink<br /> ** Scroll Speed (slow/fast)<br /> ** Reverse +/- buttons<br /> * Advanced Options<br /> ** Power Limit (watts)<br /> ** Detailed Idle Screen<br /> ** Detailed Solder Screen<br /> ** Factory Reset?<br /> ** Calibrate Temperature<br /> ** Calibrate Voltage<br /> ** Power Pulse (watts)<br /> <br /> == Pictures ==<br /> <br /> Pre-release:<br /> &lt;gallery&gt;<br /> File:Pinecil_Exploded_Diagram_ver_0.9.png|Pinecil renders|alt=alt language<br /> File:PinecilPrototype.jpg|Pinecil prototype|alt=alt language<br /> &lt;/gallery&gt;<br /> <br /> Production:<br /> &lt;gallery&gt;<br /> File:Pinecil-bb2-01.jpg|Pinecil and TS-B2 retail package|alt=alt language<br /> File:Pinecil-Case-Red-1.jpg|Pinecil red casing|alt=alt language<br /> &lt;/gallery&gt;<br /> <br /> == Pinecil tips ==<br /> * Uses TS-100 compatible tips<br /> * Tip model TS-B2 is the default tip supplied with the Pinecil<br /> * Tip set 1 (left) &amp; 2 (right):&lt;br/&gt;<br /> [[File:PinecilTipSets.jpg|800px]]<br /> <br /> == Specifications ==<br /> * '''Dimensions:''' 170mm with solder tip or 98mm without solder tip x 12.8mm x 16.2mm<br /> * '''Weight:''' 30g with solder tip, 20g without solder tip<br /> * '''CPU:''' GD32VF103TB 32-bit RV32IMAC RISC-V “Bumblebee Core” @ 108 MHz<br /> * '''Display:''' 0.67&quot; QUG 9616TSWCG02 96x16 Monochrome Matrix display<br /> * '''Memory:'''<br /> ** 128KB Flash<br /> ** 32KB SRAM<br /> * '''DC in (only one of the following at a time):'''<br /> ** 12V- 21V DC5525 Barrel Jack<br /> ** USB-C 12-20V PD<br /> ** QC3.0<br /> ** Recommend operating voltage 12-21V, some components can tolerate higher voltages at &quot;absolute maximum&quot; but it's very ill-advised<br /> <br /> == Pinecil board information, schematics and certifications ==<br /> <br /> * Pinecil mainboard schematic:<br /> ** [https://files.pine64.org/doc/Pinecil/Pinecil_schematic_v1.0a_20201120.pdf Pinecil mainboard schematic ver 1.0 20201120, this is production version schematic]<br /> ** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Top PDF file]<br /> ** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Bottom PDF file]<br /> ** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Top Drawing file]<br /> ** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Bottom Drawing file]<br /> <br /> * Pinecil certifications:<br /> ** [https://files.pine64.org/doc/cert/Pinecil%20CE%20RED%20Certificate-S20102803801001.pdf Pinecil CE RED Certificate]<br /> ** [https://files.pine64.org/doc/cert/Pinecil%20FCC%20Certificate-S20102803802001.pdf Pinecil FCC Certificate]<br /> ** [https://files.pine64.org/doc/cert/Pinecil%20RoHS10%20Certificate-S20102803803001.pdf Pinecil ROHS Certificate]<br /> <br /> * Pinecil breakout board schematic:<br /> ** [https://files.pine64.org/doc/Pinecil/Pinecil_Breakout_Board_Schematic_v1.0_20201005.pdf Pinecil breakout board schematic ver 1.0 20201005]<br /> ** [https://files.pine64.org/doc/Pinecil/Pinecil_Breakout_Board_PCB_layout_v1.0_20201005.pdf Pinecil breakout board PCB layout ver 1.0]<br /> * Photos:<br /> &lt;gallery&gt;<br /> File:Pinecil-breakout-board-02.jpg|Store photo<br /> File:Pinecil breakout top.jpg|Top view<br /> File:Pinecil breakout bottom.jpg|Bottom view<br /> &lt;/gallery&gt;<br /> <br /> == Firmware Image Releases ==<br /> <br /> * [https://github.com/pine64/pinecil-firmware-updater/releases/latest Latest Pinecil Firmware Updater] for MacOS and Windows<br /> <br /> * [https://files.pine64.org/os/Pinecil/Pinecil_firmware_20201115.zip Pinecil production firmware 20201115, thanks to Ralimtek]<br /> <br /> Links to development firmware and documentation:<br /> <br /> * [https://github.com/Ralim/IronOS/releases GitHub repository for IronOS, from Ralimtek]<br /> * [https://github.com/Ralim/IronOS/blob/master/Documentation/Flashing.md GitHub link for IronOS flashing documentation]<br /> <br /> == Datasheets for components and peripherals ==<br /> * GigaDevice RISC-V SoC information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_Datasheet_Rev%201.1.pdf GigaDevice RISC-V GD32VF103TB SoC Datasheet V1.1]<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_User_Manual_EN_V1.2.pdf GigaDevice RISC-V GD32VF103TB SoC Usermanual V1.2]<br /> * Display Module information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/1810010328_UG-Univision-Semicon-UG-9616TSWCG02_C88335.pdf QUG 9616TSWCG02 Display Module Datasheet]<br /> * USB Type-C PD Controller information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/FUSB302-D.PDF ON Semiconductor FUSB302 USB Type-C PD Controller Datasheet]<br /> * Sensor information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/BMA223-Bosch.pdf Bosch BMA223 Acceleration Sensor Datasheet]<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/si7210-datasheet.pdf Silicon Lab Si7210 Hall-Effect Magnetic Position Sensor Datasheet]<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/TMP35_36_37.pdf Analog Device TMP36 Temparature Sensor Datasheet]<br /> * Power Regulator information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/RT7272B-05.pdf Ricktek RT7272B 3A Switching Power Regulator Datasheet - on mainboard]<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/LP6498B6F.pdf LowPowerSemi LP6498B6F 1.2A Switching Power Regulator Datasheet - on breakout board]<br /> * Power MOSFET Switch information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/Changjiang-Electronics-Tech-CJ-CJQ7328.pdf Chang Jiang CJQ7328 8A MOSFET Datasheet]<br /> * OP Amp information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/SGM8557.pdf SGMicro SGM8557-1 Low Noise OP Amp Datasheet]<br /> <br /> == Batch changes ==<br /> <br /> * For the first manufacture batch of the Pinecil, the copper ring connecting the earth screw to the tip was omitted as the engineering team found the TS100 design lacking. For the second round onwards, an improved design copper ring has been included as standard, and is also included with the replacement red and black handles. For normal operation of the iron, omission of the ring does not impact it's operation. If you are working with ESD components, you will however need it in order to ground the iron tip via the earth screw at the back of the iron. If you from the first batch, and need that part, please contact info at pine64 dot org with the subject &quot;Pinecil copper ring&quot;, and include your order number and shipment will be arranged. <br /> <br /> * The first batch of Pinecil's were rated 12-24v @ 65W. After some heated discussion on the discussion group, it was decided that it would be downgraded to 12-21V @ 60W, due to concern over the connection of the DC jack to the USB-PD chip, which has a recommended maximum of 21v, and absolute maximum of 28v. <br /> <br /> == Development efforts ==<br /> <br /> {| class=&quot;wikitable&quot;<br /> !<br /> ! Project Homepage<br /> ! Project Source<br /> ! Implementations<br /> <br /> |-<br /> ! Ralimtek<br /> | https://ralimtek.com<br /> | https://www.gitmemory.com/Ralim<br /> <br /> |-<br /> ! Alvin Wong<br /> | <br /> | https://github.com/alvinhochun/gd32vf103-pinecil-demo-rs<br /> |}<br /> <br /> === How to update a firmware ===<br /> <br /> {{warning|1=While you can't brick your device permanently (DFU is in ROM); this can make your device inoperable if you flash an invalid firmware.}}<br /> <br /> ==== With application ====<br /> <br /> # Download Pinecil Firmware Updater for [http://pinecil.pine64.org/updater/get-binaries.php?platform=win64 Windows], [http://pinecil.pine64.org/updater/get-binaries.php?platform=macos64 MacOS], or build by yourself from [https://github.com/pine64/pinecil-firmware-updater sources].<br /> # Open it, select operating system you want to flash and click *Flash*. (Don't connect Pinecil yet)<br /> # Follow application instructions for correct Pinecil connection to your PC.<br /> <br /> ==== Manually ====<br /> <br /> (Method tested on Linux, should work on any OS which supply dfu-util 0.10, if your distro comes with 0.9 you might soft-brick your Pinecil)<br /> <br /> {{note|1=If &lt;code&gt;dfu-util&lt;/code&gt; command cannot find a device with 28e9:0189 ID, try to run it with &lt;code&gt;sudo&lt;/code&gt;}}<br /> <br /> {{note|1=To check if you can use dfu-util 0.9, you can use &lt;code&gt;dfu-util -l&lt;/code&gt;. If it reports &lt;code&gt;alt=0, name=&quot;@Internal Flash /0x08000000/128*001Kg&quot;&lt;/code&gt; you are fine, otherwise you need to upgrade to 0.10, important part is &lt;code&gt;128*001Kg&lt;/code&gt;, which is flash amount of blocks and block size, as a chip used in Pinecil have 128 KB of Flash with 1KB page size}}<br /> <br /> # Enter an update mode. For that plug USB cable while holding *-* button (button, that's closest to USB-C port)<br /> # Make a firmware backup: &lt;code&gt;dfu-util -d 28e9:0189 -a 0 -U ~/pinecil/internal.flash.stock -s 0x08000000&lt;/code&gt;<br /> ## &lt;code&gt;28e9:0189&lt;/code&gt; -- USB Device ID (can be obtained from &lt;code&gt;lsusb&lt;/code&gt; or &lt;code&gt;dfu-util -l&lt;/code&gt; but in dfu-util output it might be hard to identify the Pinecil device)<br /> ## &lt;code&gt;-a 0&lt;/code&gt; -- selects partition to flash. List of possible options can be obtained via &lt;code&gt;dfu-util -l&lt;/code&gt;. Partition 0 - internal SPI flash. Partition 1 - fuses (description of fuses can be found in User Manual for the chip)<br /> ## &lt;code&gt;-U&lt;/code&gt; -- specifies a mode. U is upload, which means that firmware will be downloaded and saved to file (yes, that's confusing, but it is what it is, feel free to verify that in a manual of your version of dfu-util). Command must be followed by a path to file where you want to save your firmware. dfu-util will refuse to dump firmware if you already have a file with that name.<br /> ## &lt;code&gt;-s 0x08000000&lt;/code&gt; -- specify the address in a flash from which dump will start. This can be obtained from &lt;code&gt;dfu-util -l&lt;/code&gt;.<br /> # Flash a new firmware: &lt;code&gt;dfu-util -d 28e9:0189 -a 0 -D Pinecil_EN.bin -s 0x08000000:mass-erase:force&lt;/code&gt;<br /> ## &lt;code&gt;-D&lt;/code&gt; -- is a mode to Download firmware to the device (yes, that's confusing, but you indeed Upload from device and Download to device with dfu-util). That should follow the file with the firmware. Update archive from Ralim usually contains two files: &lt;code&gt;.hex&lt;/code&gt; and &lt;code&gt;.bin&lt;/code&gt;. One that is required - is &lt;code&gt;.bin&lt;/code&gt;. &lt;code&gt;_EN&lt;/code&gt; is the language code of the firmware, means that &lt;code&gt;_EN&lt;/code&gt; will flash english version of firmware.<br /> ## &lt;code&gt;-s 0x08000000:mass-erase:force&lt;/code&gt; -- specified the address where to flash the file. &lt;code&gt;:mass-erase:force&lt;/code&gt; is required to force-erase flash before updating firmware, otherwise you might have unpredictable results.<br /> ## If it fails with &lt;code&gt;Error during special command &quot;MASS_ERASE&quot; get_status&lt;/code&gt; (as has happened with recent shipments) then use ...&lt;code&gt;-s 0x08000000&lt;/code&gt; without attempting &quot;mass-erase&quot;.<br /> <br /> == Disassembly steps ==<br /> <br /> # Remove tip if present.<br /> ## Let tip cool down.<br /> ## Loosen top (display side) screw (PH1) on the tip side of the device.<br /> ## Gently pull tip out.<br /> # Slide rubber off towards the tip side.<br /> # Remove the ground screw (longer screw on the top side towards the port side) (PH1).<br /> # Remove the bottom screw (at the tip side, between the legs) (PH1).<br /> # Slightly pull the two halves of the case apart at the tip side, enough to get a fingernail or guitar pick between the halves.<br /> # Move the pick down the length of the split to loosen the bottom half's clips from the top half of the case.<br /> # Once loose, remove the bottom half by moving it forward (it is retained by the top half at the port side).<br /> # Remove the screws retaining the copper tip contacts (PH000).<br /> # Remove the now loose copper tip contacts.<br /> # Gently push the board towards the tip side by pushing on one of the ports (for example, by using a misaligned USB C connector).<br /> # The PCB assembly is now free to be lifted out.<br /> ## The key caps are now no longer retained, carefully set aside the top half, or remove the caps and store them separately.<br /> <br /> == Assembly steps ==<br /> <br /> # Place the key caps into their recesses in the top half of the case.<br /> # Place the PCB assembly into the top half of the case ports first.<br /> ## Lower the rest of the board into the case and move the PCB assembly towards the port side of the case (the DC barrel connector may be a firm place to gently push).<br /> # Install the copper tip contacts.<br /> ## Orient the contact to align the alignment pin with the alignment hole next to the big hole on one of the big gold pads.<br /> ## Install and gently tighten the PH000 screw until the clip is no longer loose.<br /> # Place the bottom half of the case into the top half by sliding the lip on the port side (side without the feet) of the bottom half under the arch of the port side of the top half.<br /> # Gently close the case by bringing the two halves together, paying attention to each clip's alignment and ensuring the case edges align.<br /> # Install the short PH1 screw at the bottom of the tip side of the case.<br /> # Install the longer PH1 screw at the ground connection point at the top side of the case (between the display and the ports).<br /> # Slide the rubber sleeve on (larger ridge first).<br /> # Gently insert tip.<br /> # Gently tighten the top PH1 screw to retain the tip.<br /> <br /> == Power Supply Compatibility ==<br /> <br /> The Pinecil can either work with a 12-21V battery or power supply via the 5525 (5.5mm outer diameter, 1.5mm post) centre-positive jack, or with any USB power supply that supports the QC2, QC3 or USB-PD (Power Delivery) specification. QC2 and QC3 power supplies will only be able to provide a maximum of 12V, limiting the Pinecil to about 17W of thermal capability. A suitable USB-PD power supply / power bank will be able to provide 20V, allowing the Pinecil to deliver the full 60W of heat to soldering tip. <br /> <br /> Known working QC/PD/barrel power adapters / power banks include:<br /> <br /> Power adapter:<br /> * [https://pine64.com/product/pinepower-120w-desktop-power-supply-us-version/ PinePower Desktop]<br /> * [https://www.nekteck.com/product/usb-if-certified-usb-c-charger-nekteck-60w-type-c-wall-charger-power-delivery-pd3-0-travel-charger-compatible-with-macbook-pro-2018-macbook-air-ipad-pro-pixel-3-galaxy-note-9-s9-with-6ft-cable/ Nekteck 60W with 6ft cable]<br /> * Notebook AC Adapter HP L30757-002 (PD@20V)<br /> * Notebook AC Adapter Lenovo ADLX65YLC3D (PD@20V)<br /> * Notebook AC Adapter Lenovo LN-A0403A3C (Barrel 20V/2A)<br /> * Notebook AC Adapter Delta Electronics ADP-65JH BB (DC@19V) and ADP-90CD DB<br /> * Notebook AC Adapter LITEON PA-1700-02 (DC@18.5V, 65W)<br /> * Smartphone Charger Samsung EP-TA20EWE (QC2@9V)<br /> * Smartphone Charger Google Pixel G1000-US (PD@9V)<br /> * Nintendo Switch AC Adapter (USB-C wall-wart) (PD@15V)<br /> * Notebook Docking Station HP Thunderbolt Dock 230W G2 (PD@20V)<br /> ** (had problems with lower firmware versions, but works fine Pinecil firmware: 2.15 and DockingStation firmware: 1.0.69.1) <br /> <br /> Power bank:<br /> * [http://beta.blitzwolf.com/-p-15.html Blitzwolf BW-P1 10400mAh QC2]<br /> * [https://www.bestbuy.com/site/insignia-80w-26800-mah-portable-charger-for-most-usb-c-laptops-black/6419522.p?skuId=6419522 Insignia 80W 26,800mAh NS-PWLB80]<br /> <br /> Limited usability:<br /> * Nillkin 63W USB Car Charger Quick Charge 3.0 PD (Pinecil Firmware: 2.14.2425902)<br /> ** QC3@9V/12V and PD@15V work, PD@20V doesn't<br /> ** PD@20V works fine when using PDC004-20V or ZY12PDN on dc jack (DC@20V, limit: 45W)<br /> <br /> Blacklist / Not compatible:<br /> * Smartphone Charger RAVpower 30W Dual USB Turbo Wall Charger (Should provide QC3@9V/12V, but only provides 5 V on both ports)<br /> * Sabrent HB-B7C3 USB3 hub, 7 data ports, 3 charge ports, 60W supply -- does not negotiate higher voltages.<br /> <br /> == Cases and 3D Models ==<br /> <br /> * [https://github.com/kohkohwastaken/3D-Models/tree/main/Pine64 3D model of Pinecil by kohkoh]<br /> * [https://www.thingiverse.com/thing:4727212 Pinecil compact case]<br /> * [https://www.thingiverse.com/thing:4723235 Pinecil and tips case]<br /> * [https://www.thingiverse.com/thing:4734830 T12 Tip Adapter]<br /> * [https://www.thingiverse.com/search?q=pinecil Thingiverse search for 'Pinecil']<br /> <br /> == Caring for a soldering iron ==<br /> <br /> https://www.weller-tools.com/how-to-care-for-soldering-iron-tips/<br /> <br /> https://www.eevblog.com/forum/beginners/best-way-to-clean-oxidized-soldering-iron-tip/<br /> <br /> == Community links ==<br /> <br /> * [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Telegram]<br /> * [https://matrix.to/#/#pinecil:matrix.org Matrix]<br /> * [https://discordapp.com/invite/DgB7kzr Discord]<br /> <br /> [[Category:Pinecil]]</div>

Avamander https://wiki.pine64.org/index.php?title=Pinecil&diff=10854 2021-07-01T10:46:14Z

<p>Avamander: </p> <hr /> <div>== Overall description ==<br /> [[File:Pinecil-bb2-01_rotate.jpg]]&lt;br&gt;<br /> The Pinecil is a portable, temperature controlled soldering iron. It also has the intended use of being a Risc-V development device using a breakout board. It's main features are:<br /> <br /> * Portability<br /> * Settable temperature<br /> * Soldering tips:<br /> ** Replaceable<br /> ** More than half a dozen available. Currently sold as 2 separate sets of 4, one fine set, the other larger.<br /> ** Compatible with TS100<br /> * Flexible power sources:<br /> ** Barrel jack<br /> ** USB Type C power delivery<br /> <br /> There are additional features that include (Useful for devkit use):<br /> <br /> * A Programmable Gigadevice Risc-V GD32V embedded processor<br /> * 0.67&quot; Monochrome Display that can render text or graphics<br /> * Support for Idle detection, for automatic power down of tip<br /> <br /> == Use ==<br /> <br /> Pinecil comes with a separate heating element / tip. After inserting its barrel into the end of the handle, lightly tighten the screw onto it. Loosen this screw when changing out the tip.<br /> <br /> The USB port, connected to any host, provides enough power to drive the user interface, but not necessarily enough to heat the tip. 5 volts from a USB 2 port will only display the user interface.<br /> <br /> To check the firmware version, hold down the &quot;-&quot; button. It will display something like &quot;v2.14.2425902 17-01-21&quot;, suggesting its actual release date, here 2021-01-17. Clicking the &quot;+&quot; button repeatedly reveals various internal settings, such as hardware version, current temperature, time since power-on, and number of motions detected. Clicking &quot;-&quot; returns to the regular display of current temperature, target temperature, and supply voltage. At other times it may show power draw.<br /> <br /> To actually heat up the tip, you will need a power supply that can provide 12V or more. This may be a dedicated power supply with a standard barrel connector (+ center, - outside) that supplies anywhere from 12V to 21V, or a USB-C supply that can negotiate up to such a voltage. (You probably have a suitable supply disused in a box somewhere.)<br /> <br /> Clicking &quot;+&quot; starts the tip heating. The display then shows power draw, current temperature, supply voltage, and estimated time to reach target temperature. You can adjust the target temperature with further clicks of &quot;+&quot; and &quot;-&quot; buttons. Waiting for the regular display to return, then holding down &quot;-&quot; for a moment turns the heat off. You can watch the temperature measurement go up and down. Certain settings involve holding down both buttons.<br /> <br /> The iron will &quot;sleep&quot;, switching to a lower temperature, after it has been put down for a short time, and heat up again when it is picked up.<br /> <br /> Clicking &quot;-&quot; when heat is off steps through menus to control a variety of settings, such as the sleep temperature, time until sleep, motion sensitivity, temperature units (C or F) etc.<br /> <br /> '''Menu Items''' items (accurate for firmware 2.1.14)<br /> <br /> * Power Source <br /> **(cutoff choices for voltage and battery operation)<br /> * QC voltage <br /> **(voltage to negotiate for with QC chargers (9, 12, 20 volts)<br /> * Soldering Settings<br /> ** Boost Temperature<br /> ** Auto Start<br /> ** Temperature Change (short click)<br /> ** Temperature Change (long click)<br /> ** Allow Lock (when soldering)<br /> * Sleep Settings<br /> ** Sleep Temperature<br /> ** Sleep Timeout<br /> ** Shutdown Time<br /> ** Motion Sensor Sensitivity<br /> ** Hall Sensor Sensitivity<br /> * User Interface<br /> ** Temperature Units (C/F)<br /> ** Display orientation (right/left)<br /> ** Cooldown Blink<br /> ** Scroll Speed (slow/fast)<br /> ** Reverse +/- buttons<br /> * Advanced Options<br /> ** Power Limit (watts)<br /> ** Detailed Idle Screen<br /> ** Detailed Solder Screen<br /> ** Factory Reset?<br /> ** Calibrate Temperature<br /> ** Calibrate Voltage<br /> ** Power Pulse (watts)<br /> <br /> == Pictures ==<br /> <br /> Pre-release:<br /> &lt;gallery&gt;<br /> File:Pinecil_Exploded_Diagram_ver_0.9.png|Pinecil renders|alt=alt language<br /> File:PinecilPrototype.jpg|Pinecil prototype|alt=alt language<br /> &lt;/gallery&gt;<br /> <br /> Production:<br /> &lt;gallery&gt;<br /> File:Pinecil-bb2-01.jpg|Pinecil and TS-B2 retail package|alt=alt language<br /> File:Pinecil-Case-Red-1.jpg|Pinecil red casing|alt=alt language<br /> &lt;/gallery&gt;<br /> <br /> == Pinecil tips ==<br /> * Uses TS-100 compatible tips<br /> * Tip model TS-B2 is the default tip supplied with the Pinecil<br /> * Tip set 1 (left) &amp; 2 (right):&lt;br/&gt;<br /> [[File:PinecilTipSets.jpg|800px]]<br /> <br /> == Specifications ==<br /> * '''Dimensions:''' 170mm with solder tip or 98mm without solder tip x 12.8mm x 16.2mm<br /> * '''Weight:''' 30g with solder tip, 20g without solder tip<br /> * '''CPU:''' GD32VF103TB 32-bit RV32IMAC RISC-V “Bumblebee Core” @ 108 MHz<br /> * '''Display:''' 0.67&quot; QUG 9616TSWCG02 96x16 Monochrome Matrix display<br /> * '''Memory:'''<br /> ** 128KB Flash<br /> ** 32KB SRAM<br /> * '''DC in (only one of the following at a time):'''<br /> ** 12V- 21V DC5525 Barrel Jack<br /> ** USB-C 12-20V PD<br /> ** QC3.0<br /> ** Recommend operating voltage 12-21V, maximum rating at 21V<br /> <br /> == Pinecil board information, schematics and certifications ==<br /> <br /> * Pinecil mainboard schematic:<br /> ** [https://files.pine64.org/doc/Pinecil/Pinecil_schematic_v1.0a_20201120.pdf Pinecil mainboard schematic ver 1.0 20201120, this is production version schematic]<br /> ** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Top PDF file]<br /> ** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.pdf Pinecil mainboard ver 1.0 PCB Component Placement Bottom PDF file]<br /> ** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-topplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Top Drawing file]<br /> ** [https://files.pine64.org/doc/Pinecil/Pinecil-PCB-placement-v1.0-bottomplace.dxf Pinecil mainboard ver 1.0 PCB Component Placement Bottom Drawing file]<br /> <br /> * Pinecil certifications:<br /> ** [https://files.pine64.org/doc/cert/Pinecil%20CE%20RED%20Certificate-S20102803801001.pdf Pinecil CE RED Certificate]<br /> ** [https://files.pine64.org/doc/cert/Pinecil%20FCC%20Certificate-S20102803802001.pdf Pinecil FCC Certificate]<br /> ** [https://files.pine64.org/doc/cert/Pinecil%20RoHS10%20Certificate-S20102803803001.pdf Pinecil ROHS Certificate]<br /> <br /> * Pinecil breakout board schematic:<br /> ** [https://files.pine64.org/doc/Pinecil/Pinecil_Breakout_Board_Schematic_v1.0_20201005.pdf Pinecil breakout board schematic ver 1.0 20201005]<br /> ** [https://files.pine64.org/doc/Pinecil/Pinecil_Breakout_Board_PCB_layout_v1.0_20201005.pdf Pinecil breakout board PCB layout ver 1.0]<br /> * Photos:<br /> &lt;gallery&gt;<br /> File:Pinecil-breakout-board-02.jpg|Store photo<br /> File:Pinecil breakout top.jpg|Top view<br /> File:Pinecil breakout bottom.jpg|Bottom view<br /> &lt;/gallery&gt;<br /> <br /> == Firmware Image Releases ==<br /> <br /> * [https://github.com/pine64/pinecil-firmware-updater/releases/latest Latest Pinecil Firmware Updater] for MacOS and Windows<br /> <br /> * [https://files.pine64.org/os/Pinecil/Pinecil_firmware_20201115.zip Pinecil production firmware 20201115, thanks to Ralimtek]<br /> <br /> Links to development firmware and documentation:<br /> <br /> * [https://github.com/Ralim/IronOS/releases GitHub repository for IronOS, from Ralimtek]<br /> * [https://github.com/Ralim/IronOS/blob/master/Documentation/Flashing.md GitHub link for IronOS flashing documentation]<br /> <br /> == Datasheets for components and peripherals ==<br /> * GigaDevice RISC-V SoC information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_Datasheet_Rev%201.1.pdf GigaDevice RISC-V GD32VF103TB SoC Datasheet V1.1]<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/GD32VF103_User_Manual_EN_V1.2.pdf GigaDevice RISC-V GD32VF103TB SoC Usermanual V1.2]<br /> * Display Module information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/1810010328_UG-Univision-Semicon-UG-9616TSWCG02_C88335.pdf QUG 9616TSWCG02 Display Module Datasheet]<br /> * USB Type-C PD Controller information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/FUSB302-D.PDF ON Semiconductor FUSB302 USB Type-C PD Controller Datasheet]<br /> * Sensor information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/BMA223-Bosch.pdf Bosch BMA223 Acceleration Sensor Datasheet]<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/si7210-datasheet.pdf Silicon Lab Si7210 Hall-Effect Magnetic Position Sensor Datasheet]<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/TMP35_36_37.pdf Analog Device TMP36 Temparature Sensor Datasheet]<br /> * Power Regulator information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/RT7272B-05.pdf Ricktek RT7272B 3A Switching Power Regulator Datasheet - on mainboard]<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/LP6498B6F.pdf LowPowerSemi LP6498B6F 1.2A Switching Power Regulator Datasheet - on breakout board]<br /> * Power MOSFET Switch information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/Changjiang-Electronics-Tech-CJ-CJQ7328.pdf Chang Jiang CJQ7328 8A MOSFET Datasheet]<br /> * OP Amp information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecil/SGM8557.pdf SGMicro SGM8557-1 Low Noise OP Amp Datasheet]<br /> <br /> == Batch changes ==<br /> <br /> * For the first manufacture batch of the Pinecil, the copper ring connecting the earth screw to the tip was omitted as the engineering team found the TS100 design lacking. For the second round onwards, an improved design copper ring has been included as standard, and is also included with the replacement red and black handles. For normal operation of the iron, omission of the ring does not impact it's operation. If you are working with ESD components, you will however need it in order to ground the iron tip via the earth screw at the back of the iron. If you from the first batch, and need that part, please contact info at pine64 dot org with the subject &quot;Pinecil copper ring&quot;, and include your order number and shipment will be arranged. <br /> <br /> * The first batch of Pinecil's were rated 12-24v @ 65W. After some heated discussion on the discussion group, it was decided that it would be downgraded to 12-21V @ 60W, due to concern over the connection of the DC jack to the USB-PD chip, which has a recommended maximum of 21v, and absolute maximum of 28v. <br /> <br /> == Development efforts ==<br /> <br /> {| class=&quot;wikitable&quot;<br /> !<br /> ! Project Homepage<br /> ! Project Source<br /> ! Implementations<br /> <br /> |-<br /> ! Ralimtek<br /> | https://ralimtek.com<br /> | https://www.gitmemory.com/Ralim<br /> <br /> |-<br /> ! Alvin Wong<br /> | <br /> | https://github.com/alvinhochun/gd32vf103-pinecil-demo-rs<br /> |}<br /> <br /> === How to update a firmware ===<br /> <br /> {{warning|1=While you can't brick your device permanently (DFU is in ROM); this can make your device inoperable if you flash an invalid firmware.}}<br /> <br /> ==== With application ====<br /> <br /> # Download Pinecil Firmware Updater for [http://pinecil.pine64.org/updater/get-binaries.php?platform=win64 Windows], [http://pinecil.pine64.org/updater/get-binaries.php?platform=macos64 MacOS], or build by yourself from [https://github.com/pine64/pinecil-firmware-updater sources].<br /> # Open it, select operating system you want to flash and click *Flash*. (Don't connect Pinecil yet)<br /> # Follow application instructions for correct Pinecil connection to your PC.<br /> <br /> ==== Manually ====<br /> <br /> (Method tested on Linux, should work on any OS which supply dfu-util 0.10, if your distro comes with 0.9 you might soft-brick your Pinecil)<br /> <br /> {{note|1=If &lt;code&gt;dfu-util&lt;/code&gt; command cannot find a device with 28e9:0189 ID, try to run it with &lt;code&gt;sudo&lt;/code&gt;}}<br /> <br /> {{note|1=To check if you can use dfu-util 0.9, you can use &lt;code&gt;dfu-util -l&lt;/code&gt;. If it reports &lt;code&gt;alt=0, name=&quot;@Internal Flash /0x08000000/128*001Kg&quot;&lt;/code&gt; you are fine, otherwise you need to upgrade to 0.10, important part is &lt;code&gt;128*001Kg&lt;/code&gt;, which is flash amount of blocks and block size, as a chip used in Pinecil have 128 KB of Flash with 1KB page size}}<br /> <br /> # Enter an update mode. For that plug USB cable while holding *-* button (button, that's closest to USB-C port)<br /> # Make a firmware backup: &lt;code&gt;dfu-util -d 28e9:0189 -a 0 -U ~/pinecil/internal.flash.stock -s 0x08000000&lt;/code&gt;<br /> ## &lt;code&gt;28e9:0189&lt;/code&gt; -- USB Device ID (can be obtained from &lt;code&gt;lsusb&lt;/code&gt; or &lt;code&gt;dfu-util -l&lt;/code&gt; but in dfu-util output it might be hard to identify the Pinecil device)<br /> ## &lt;code&gt;-a 0&lt;/code&gt; -- selects partition to flash. List of possible options can be obtained via &lt;code&gt;dfu-util -l&lt;/code&gt;. Partition 0 - internal SPI flash. Partition 1 - fuses (description of fuses can be found in User Manual for the chip)<br /> ## &lt;code&gt;-U&lt;/code&gt; -- specifies a mode. U is upload, which means that firmware will be downloaded and saved to file (yes, that's confusing, but it is what it is, feel free to verify that in a manual of your version of dfu-util). Command must be followed by a path to file where you want to save your firmware. dfu-util will refuse to dump firmware if you already have a file with that name.<br /> ## &lt;code&gt;-s 0x08000000&lt;/code&gt; -- specify the address in a flash from which dump will start. This can be obtained from &lt;code&gt;dfu-util -l&lt;/code&gt;.<br /> # Flash a new firmware: &lt;code&gt;dfu-util -d 28e9:0189 -a 0 -D Pinecil_EN.bin -s 0x08000000:mass-erase:force&lt;/code&gt;<br /> ## &lt;code&gt;-D&lt;/code&gt; -- is a mode to Download firmware to the device (yes, that's confusing, but you indeed Upload from device and Download to device with dfu-util). That should follow the file with the firmware. Update archive from Ralim usually contains two files: &lt;code&gt;.hex&lt;/code&gt; and &lt;code&gt;.bin&lt;/code&gt;. One that is required - is &lt;code&gt;.bin&lt;/code&gt;. &lt;code&gt;_EN&lt;/code&gt; is the language code of the firmware, means that &lt;code&gt;_EN&lt;/code&gt; will flash english version of firmware.<br /> ## &lt;code&gt;-s 0x08000000:mass-erase:force&lt;/code&gt; -- specified the address where to flash the file. &lt;code&gt;:mass-erase:force&lt;/code&gt; is required to force-erase flash before updating firmware, otherwise you might have unpredictable results.<br /> ## If it fails with &lt;code&gt;Error during special command &quot;MASS_ERASE&quot; get_status&lt;/code&gt; (as has happened with recent shipments) then use ...&lt;code&gt;-s 0x08000000&lt;/code&gt; without attempting &quot;mass-erase&quot;.<br /> <br /> == Disassembly steps ==<br /> <br /> # Remove tip if present.<br /> ## Let tip cool down.<br /> ## Loosen top (display side) screw (PH1) on the tip side of the device.<br /> ## Gently pull tip out.<br /> # Slide rubber off towards the tip side.<br /> # Remove the ground screw (longer screw on the top side towards the port side) (PH1).<br /> # Remove the bottom screw (at the tip side, between the legs) (PH1).<br /> # Slightly pull the two halves of the case apart at the tip side, enough to get a fingernail or guitar pick between the halves.<br /> # Move the pick down the length of the split to loosen the bottom half's clips from the top half of the case.<br /> # Once loose, remove the bottom half by moving it forward (it is retained by the top half at the port side).<br /> # Remove the screws retaining the copper tip contacts (PH000).<br /> # Remove the now loose copper tip contacts.<br /> # Gently push the board towards the tip side by pushing on one of the ports (for example, by using a misaligned USB C connector).<br /> # The PCB assembly is now free to be lifted out.<br /> ## The key caps are now no longer retained, carefully set aside the top half, or remove the caps and store them separately.<br /> <br /> == Assembly steps ==<br /> <br /> # Place the key caps into their recesses in the top half of the case.<br /> # Place the PCB assembly into the top half of the case ports first.<br /> ## Lower the rest of the board into the case and move the PCB assembly towards the port side of the case (the DC barrel connector may be a firm place to gently push).<br /> # Install the copper tip contacts.<br /> ## Orient the contact to align the alignment pin with the alignment hole next to the big hole on one of the big gold pads.<br /> ## Install and gently tighten the PH000 screw until the clip is no longer loose.<br /> # Place the bottom half of the case into the top half by sliding the lip on the port side (side without the feet) of the bottom half under the arch of the port side of the top half.<br /> # Gently close the case by bringing the two halves together, paying attention to each clip's alignment and ensuring the case edges align.<br /> # Install the short PH1 screw at the bottom of the tip side of the case.<br /> # Install the longer PH1 screw at the ground connection point at the top side of the case (between the display and the ports).<br /> # Slide the rubber sleeve on (larger ridge first).<br /> # Gently insert tip.<br /> # Gently tighten the top PH1 screw to retain the tip.<br /> <br /> == Power Supply Compatibility ==<br /> <br /> The Pinecil can either work with a 12-21V battery or power supply via the 5525 (5.5mm outer diameter, 1.5mm post) centre-positive jack, or with any USB power supply that supports the QC2, QC3 or USB-PD (Power Delivery) specification. QC2 and QC3 power supplies will only be able to provide a maximum of 12V, limiting the Pinecil to about 17W of thermal capability. A suitable USB-PD power supply / power bank will be able to provide 20V, allowing the Pinecil to deliver the full 60W of heat to soldering tip. <br /> <br /> Known working QC/PD/barrel power adapters / power banks include:<br /> <br /> Power adapter:<br /> * [https://pine64.com/product/pinepower-120w-desktop-power-supply-us-version/ PinePower Desktop]<br /> * [https://www.nekteck.com/product/usb-if-certified-usb-c-charger-nekteck-60w-type-c-wall-charger-power-delivery-pd3-0-travel-charger-compatible-with-macbook-pro-2018-macbook-air-ipad-pro-pixel-3-galaxy-note-9-s9-with-6ft-cable/ Nekteck 60W with 6ft cable]<br /> * Notebook AC Adapter HP L30757-002 (PD@20V)<br /> * Notebook AC Adapter Lenovo ADLX65YLC3D (PD@20V)<br /> * Notebook AC Adapter Lenovo LN-A0403A3C (Barrel 20V/2A)<br /> * Notebook AC Adapter Delta Electronics ADP-65JH BB (DC@19V) and ADP-90CD DB<br /> * Notebook AC Adapter LITEON PA-1700-02 (DC@18.5V, 65W)<br /> * Smartphone Charger Samsung EP-TA20EWE (QC2@9V)<br /> * Smartphone Charger Google Pixel G1000-US (PD@9V)<br /> * Nintendo Switch AC Adapter (USB-C wall-wart) (PD@15V)<br /> * Notebook Docking Station HP Thunderbolt Dock 230W G2 (PD@20V)<br /> ** (had problems with lower firmware versions, but works fine Pinecil firmware: 2.15 and DockingStation firmware: 1.0.69.1) <br /> <br /> Power bank:<br /> * [http://beta.blitzwolf.com/-p-15.html Blitzwolf BW-P1 10400mAh QC2]<br /> * [https://www.bestbuy.com/site/insignia-80w-26800-mah-portable-charger-for-most-usb-c-laptops-black/6419522.p?skuId=6419522 Insignia 80W 26,800mAh NS-PWLB80]<br /> <br /> Limited usability:<br /> * Nillkin 63W USB Car Charger Quick Charge 3.0 PD (Pinecil Firmware: 2.14.2425902)<br /> ** QC3@9V/12V and PD@15V work, PD@20V doesn't<br /> ** PD@20V works fine when using PDC004-20V or ZY12PDN on dc jack (DC@20V, limit: 45W)<br /> <br /> Blacklist / Not compatible:<br /> * Smartphone Charger RAVpower 30W Dual USB Turbo Wall Charger (Should provide QC3@9V/12V, but only provides 5 V on both ports)<br /> * Sabrent HB-B7C3 USB3 hub, 7 data ports, 3 charge ports, 60W supply -- does not negotiate higher voltages.<br /> <br /> == Cases and 3D Models ==<br /> <br /> * [https://github.com/kohkohwastaken/3D-Models/tree/main/Pine64 3D model of Pinecil by kohkoh]<br /> * [https://www.thingiverse.com/thing:4727212 Pinecil compact case]<br /> * [https://www.thingiverse.com/thing:4723235 Pinecil and tips case]<br /> * [https://www.thingiverse.com/thing:4734830 T12 Tip Adapter]<br /> * [https://www.thingiverse.com/search?q=pinecil Thingiverse search for 'Pinecil']<br /> <br /> == Caring for a soldering iron ==<br /> <br /> https://www.weller-tools.com/how-to-care-for-soldering-iron-tips/<br /> <br /> https://www.eevblog.com/forum/beginners/best-way-to-clean-oxidized-soldering-iron-tip/<br /> <br /> == Community links ==<br /> <br /> * [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Telegram]<br /> * [https://matrix.to/#/#pinecil:matrix.org Matrix]<br /> * [https://discordapp.com/invite/DgB7kzr Discord]<br /> <br /> [[Category:Pinecil]]</div>

Avamander https://wiki.pine64.org/index.php?title=Upgrade_PineTime_to_InfiniTime_1.0.0&diff=10822 2021-06-21T20:58:06Z

<p>Avamander: </p> <hr /> <div>{{Note|Page under construction, information subject to review and feedback.}}<br /> <br /> Congratulations on receiving your new PineTime!<br /> <br /> From the factory, it ships with InfiniTime 0.7.1, and an older bootloader. So now you're probably wondering exactly how on earth do you go about upgrading your watch to the latest and greatest version of InfiniTime - you know, that version you've seen all those great pictures, videos and reviews of. To those of us that are developing stuff for it, it's pretty easy and straightforward, but like with all technology, it is a bit tricky. <br /> <br /> {{warning|1=Some people ran into issues during the update process that would temporarily make their watch unusable (display frozen or blank). The only know workaround consists of waiting for the battery to drain completely and try again. With the display off, and battery fully charged, you can expect a wait of 5-7 days so it is best to not fully charge it. If it freezes with the display on, it will likely be flat by the end of the day. We've never heard of any PineTimes that were permanently bricked (were not recoverable), though. }} <br /> <br /> In a nutshell, you need to:<br /> # Charge your watch, but '''not''' to 100% - keep it at approximately 50% - for the reason described above.<br /> # Update InfiniTime<br /> # Update the bootloader<br /> # Install the recovery firmware<br /> <br /> = Update Process =<br /> So how do you do this? Where do you start? Well, with a sealed PineTime, your only easy option is via Over The Air (OTA) Device Firmware Update (DFU), which is done via Bluetooth. There are a couple of different ways and apps you can use to do this. If you have an Android device, you can use [https://f-droid.org/en/packages/nodomain.freeyourgadget.gadgetbridge/ Gadgetbridge] or [https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp NRFConnect]. Otherwise, if your laptop or desktop computer has Bluetooth and runs Linux, you can use [https://github.com/alexr4535/siglo Siglo] or [https://github.com/piggz/harbour-amazfish Amazfish]. You can also use these applications on your Pinebook Pro or Pinephone if you happen to have those devices. <br /> <br /> The reason for installing the updates in the specified order is because newer versions of InfiniTime have a more robust Bluetooth update process, and since we're updating everything over Bluetooth, the fewer retries and failures from that you have the better. It will still sometimes disconnect mid update, meaning you'll need to try again, and possibly restart the watch a few times as well. And since the recovery firmware is new to the 1.0.0 version of the bootloader, it's best to update that last. <br /> <br /> [https://video.codingfield.com/videos/watch/831077c5-16f3-47b4-9b2b-c4bbfecc6529 This video] shows the bootloader and recovery firmware installation procedure.<br /> <br /> [https://video.codingfield.com/videos/watch/f7bffb3d-a6a1-43c4-8f01-f4aeff4adf9e This video] shows the bootloader installation and firmware update using Amazfish.<br /> <br /> You can also read a [https://github.com/JF002/pinetime-mcuboot-bootloader/blob/339224cf5ed21f4e8b2d22eaeab9869120f7f752/docs/howToUpdate.md detailed installation procedure in the documentation of the bootloader].<br /> <br /> == Update InfiniTime ==<br /> To update the main InfiniTime app, you want to flash [https://github.com/JF002/InfiniTime/releases/download/1.0.0/pinetime-mcuboot-app-dfu-1.0.0.zip pinetime-mcuboot-app-dfu-1.0.0.zip].<br /> <br /> After updating InfiniTime, ensure that you validate the firmware to prevent it from being automatically reverted/rolled back if your watch is reset/restarted. To do this, swipe right to access the quick actions panel, press the gear/settings icon, swipe up once to show the second page, press on the 'Firmware' option and then on 'Validate'.<br /> <br /> [https://youtu.be/-5lwBd60k0Q Video showing validation process]<br /> <br /> <br /> === Gadgetbridge ===<br /> <br /> # Connect your PineTime to GB<br /> # Download the aforementioned file to your phone<br /> # Find the file in your file manager<br /> # 'Open With' Gadgetbridge F/W Installer (method varies by device) - on my phone, it is press and hold, select the file, and then choose 'open with app' from the more options menu<br /> # Confirm that you wish to apply the update<br /> # Wait for the update to complete<br /> <br /> [https://youtu.be/nAaaC7D5sVo Video showing how to start the update]<br /> <br /> === NRFConnect ===<br /> <br /> # Download the aforementioned file to your phone.<br /> # Open NRFConnect<br /> # Scan for your device<br /> # Connect to it<br /> # Choose the DFU option at the top right of the screen<br /> # Ensure the 'Distribution packet (ZIP)' option is selected, and press OK<br /> # Select your previously downloaded file<br /> # Wait for the update to complete<br /> <br /> [https://youtu.be/jnX7WwYDiDE Video showing how to start the update]<br /> <br /> === Siglo ===<br /> # If your device was not detected upon start, press &quot;Rescan&quot; to find it.<br /> # Select the &quot;1.0.0&quot; tag<br /> # Select the aforementioned file/asset.<br /> # Select &quot;Flash It!&quot;<br /> <br /> === Amazfish ===<br /> # Run Amazfish (service + UI)<br /> # Pair with you device:<br /> ## Unzip the DFU file to extract the .bin file.<br /> ## Click on &quot;pair with watch&quot; on the top<br /> ## Select &quot;PineTime&quot; (if your device is running InfiniTime 0.7.1 or lower) or &quot;InfiniTime (if it's running InfiniTime 0.8+) and choose your device in the list<br /> # Click on &quot;Download file&quot; on the top <br /> # Click on &quot;Choose file&quot; and select the .bin file you extracted from the DFU file<br /> # Click on &quot;Send file&quot;<br /> # Wait for the update to complete.<br /> <br /> [https://video.codingfield.com/videos/watch/41cfcf5d-b0e6-4323-8056-b0a6682d1f25 See it in action!]<br /> <br /> == Update the bootloader ==<br /> To update the bootloader, you want to flash [https://github.com/JF002/InfiniTime/releases/download/0.14.1/reloader-mcuboot.zip reloader-mcuboot.zip]. <br /> Once the bootloader is updated, you should notice that the boot logo has changed. Previously, it was a green &quot;PineTime&quot; logo, and now it is a large pinecone that is progressively drawn in green.<br /> <br /> [https://youtu.be/fvHQ8ZeqnOo Video showing what the InfiniTime 1.0.0 bootloader looks like]<br /> <br /> === Using Gadgetbridge ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> === Using NRFConnect ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> === Using Siglo ===<br /> Same process as before, but select the &quot;0.14.1&quot; tag, and the file/asset for this step.<br /> <br /> === Using Amazfish ===<br /> <br /> You may need to re-pair with your device by selecting &quot;InfiniTime&quot; (since you've already upgraded to InfiniTime 1.0) in the device type list. Then follow the same process as before, but with the file for this step.<br /> <br /> == Install the recovery firmware ==<br /> {{warning|1=Don't do this before updating the bootloader, otherwise your PineTime will freeze at the end of the process, and you will need to wait for the battery to go flat }} <br /> <br /> To install the recovery firmware, you want to flash [https://github.com/JF002/InfiniTime/releases/download/0.14.1/pinetime-mcuboot-recovery-loader-dfu-0.14.1.zip pinetime-mcuboot-recovery-loader-dfu-0.14.1.zip]. You will know when this is running when it shows an InfiniTime logo with a progress bar running across the bottom whilst it is installing the recovery firmware. <br /> <br /> === Using Gadgetbridge ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> === Using NRFConnect ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> === Using Siglo ===<br /> Same process as before, but with the file/asset for this step.<br /> <br /> === Using Amazfish ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> <br /> = Guides and Videos =<br /> <br /> = Troubleshooting =<br /> Sometimes during the update process, the connection will drop, and the update will fail. Your PineTime isn't broken, most likely the Bluetooth link dropped for a moment, so just try again. Try rebooting your phone, if it keeps failing, try restarting the watch by holding the power button down for approximately 8 seconds. Try to '''avoid''' holding down the button with the screen off. Or try with another device, just in case there are compatibility issues. <br /> <br /> Version 1.0.0 of InfiniTime is merely the first version that was considered sufficiently feature-complete and stable enough for daily use. This isn't to say there aren't still bugs present ('cause there are!). So there are a few bugs still present in the update process and the bootloader. One unfortunate bug appears to be that sometimes when the watch tries to restart after an update, the bootloader locks up, and the watch won't turn on. In this case, you will need to wait until the watch battery goes flat, to force the watch to reset. This will most likely involve waiting for a week, and then when you put the watch on the charging cradle, it will power up and you should be right to try again.<br /> <br /> If you get stuck or have any questions, join us on your preferred [[Main_Page#Chat_Platforms|chat platform]] or the product [https://forum.pine64.org/forumdisplay.php?fid=134 forum]. There's usually someone available who can help, or will get back to you in a few hours.<br /> <br /> <br /> [[Category:PineTime]][[Category:Guide]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_Hardware_Wishlist&diff=10535 2021-05-27T12:31:16Z

<p>Avamander: </p> <hr /> <div>This page contains a list of things people wish PineTime did differently<br /> <br /> === Hardware ===<br /> <br /> * Long pressing the button should power-cycle the watch without any software being involved<br /> * Other display tech could be explored. [//en.Wikipedia.org/wiki/Transflective_liquid-crystal_display A transflective LCD] would probably be a nice option. Or potentially OLED?<br /> * Touchscreen should possibly have a configurable sensitivity level for both glove-wearing and droplet-resistance. Preferably it should still be a capacitive one, a resistive touchscreen would have too many trade-offs.<br /> * A slightly bigger 256×256 pixel graphics display size is preferable for its binary alignment, affording some low-level simplicity – it has the property that its X and Y coordinates are each addressable with a single byte, with no out-of-bounds; its total number of pixels is 65536 (another power of 2), and each pixel is addressable with exactly 2 bytes, with perfect efficiency. The [http://Pelulamu.net/ibniz IBNIZ (Ideally Bare Numeric Impression giZmo) virtual machine], designed for fun minimalist demoscene graphics, has chosen 256×256 for its virtual display, and makes use of these simplicity advantages. If PineTime also chose 256×256 then it would be a target platform for unclipped IBNIZ demoscene programmes, which would be really fun to play around with on one's wrist!<br /> * A full redraw on the display takes 120ms at the very least, which is 8Hz. A smooth scrolling/usage/animation experience would be 30Hz minimum, preferably 60. I heard a rumor that the SPI connection to the display is a bottleneck.<br /> * Some sort of scroll wheel would be nice for convenience.<br /> * Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)<br /> * Wireless charging, or Qi Charging capability<br /> * An external RTC circuit saving the current time to allow the main MCU go to deep-sleep.<br /> * nRF5840 update: QSPI, CryptoCell + Secure Key Storage, has more RAM, a coprocessor and the possibility to expose USB through power pins<br /> * Preferably a pre-certified MCU module with a ceramic antenna<br /> * Version without sensors but maybe bigger battery<br /> * A couple of pins on the programmer connector to allow UART while developing (currently there is a TX test point on PCB). (Note: There's ARM SemiHosting and Segger RTT)<br /> * Connect the pin of LCD controller that allows RD/WR from it in order to save RAM on the MCU. (The MOSI pin for the SPI is already connected to the nor flash that shares the same pins, pin number is P0.04)<br /> * LCD must be centered on case. Currently is not and watchfaces seems different when clock is put on the other wrist.<br /> * A NFC antenna around the case, connected to the NFC pins.<br /> * Used sensors should be NDA-free and preferably also blob-free. For example the BMA421 accelerometer doesn't have a datasheet (it seems private to some hardware integrators): a more open one would be much easier to develop for. Special attention should be paid to advanced features, such as step counting integration or flick detection.<br /> * PineTime SoC could support USB or have a FTDI chip with the relevant pins exposed. It could allow flashing a sealed device, just like Arduinos work. The same USB-C could also be used for charging. <br /> * A bigger pulldown resistor for the power button, because 100k still leaks a noticeable amount of power when the button is always on.<br /> * Ceramic Bluetooth antenna for better signal reception<br /> * Ultra low quiescent current PMIC for better deep sleep. Better shipping/storage/turned off mode<br /> <br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=Upgrade_PineTime_to_InfiniTime_1.0.0&diff=10486 2021-05-22T09:58:36Z

<p>Avamander: </p> <hr /> <div>{{Note|Page under construction, information subject to review and feedback.}}<br /> <br /> Congratulations on receiving your new PineTime!<br /> <br /> From the factory, it ships with InfiniTime 0.7.1, and an older bootloader. So now you're probably wondering exactly how on earth do you go about upgrading your watch to the latest and greatest version of InfiniTime - you know, that version you've seen all those great pictures, videos and reviews of. To those of us that are developing stuff for it, it's pretty easy and straightforward, but like with all technology, it is a bit tricky. <br /> <br /> {{warning|1=Some people ran into issues during the update process that would temporarily make their watch unusable (display frozen or blank). The only know workaround consists of waiting for the battery to drain completely and try again. With the display off, and battery fully charged, you can expect a wait of 5-7 days so it is best to not fully charge it. If it freezes with the display on, it will likely be flat by the end of the day. We've never heard of any PineTimes that were permanently bricked (were not recoverable), though. }} <br /> <br /> In a nutshell, you need to:<br /> # Charge your watch, but '''not''' to 100% - keep it at approximately 50% - for the reason described above.<br /> # Update InfiniTime<br /> # Update the bootloader<br /> # Install the recovery firmware<br /> <br /> = Update Process =<br /> So how do you do this? Where do you start? Well, with a sealed PineTime, your only easy option is via Over The Air (OTA) Device Firmware Update (DFU), which is done via Bluetooth. There are a couple of different ways and apps you can use to do this. If you have an Android device, you can use [https://f-droid.org/en/packages/nodomain.freeyourgadget.gadgetbridge/ Gadgetbridge] or [https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp NRFConnect]. Otherwise, if your laptop or desktop computer has Bluetooth and runs Linux, you can use [https://github.com/alexr4535/siglo Siglo] or [https://github.com/piggz/harbour-amazfish Amazfish]. You can also use these applications on your Pinebook Pro or Pinephone if you happen to have those devices. <br /> <br /> The reason for installing the updates in the specified order is because newer versions of InfiniTime have a more robust Bluetooth update process, and since we're updating everything over Bluetooth, the fewer retries and failures from that you have the better. It will still sometimes disconnect mid update, meaning you'll need to try again, and possibly restart the watch a few times as well. And since the recovery firmware is new to the 1.0.0 version of the bootloader, it's best to update that last. <br /> <br /> [https://video.codingfield.com/videos/watch/831077c5-16f3-47b4-9b2b-c4bbfecc6529 This video] shows the bootloader and recovery firmware installation procedure.<br /> <br /> [https://video.codingfield.com/videos/watch/f7bffb3d-a6a1-43c4-8f01-f4aeff4adf9e This video] shows the bootloader installation and firmware update using Amazfish.<br /> <br /> You can also read a [https://github.com/JF002/pinetime-mcuboot-bootloader/blob/339224cf5ed21f4e8b2d22eaeab9869120f7f752/docs/howToUpdate.md detailed installation procedure in the documentation of the bootloader].<br /> <br /> == Update InfiniTime ==<br /> To update the main InfiniTime app, you want to flash [https://github.com/JF002/InfiniTime/releases/download/1.0.0/pinetime-mcuboot-app-dfu-1.0.0.zip pinetime-mcuboot-app-dfu-1.0.0.zip].<br /> <br /> After updating InfiniTime, ensure that you validate the firmware to prevent it from being automatically reverted/rolled back if your watch is reset/restarted. To do this, swipe right to access the quick actions panel, press the gear/settings icon, swipe up once to show the second page, press on the 'Firmware' option and then on 'Validate'.<br /> <br /> [https://youtu.be/-5lwBd60k0Q Video showing validation process]<br /> <br /> <br /> === Gadgetbridge ===<br /> <br /> # Connect your PineTime to GB<br /> # Download the aforementioned file to your phone<br /> # Find the file in your file manager<br /> # 'Open With' Gadgetbridge F/W Installer (method varies by device) - on my phone, it is press and hold, select the file, and then choose 'open with app' from the more options menu<br /> # Confirm that you wish to apply the update<br /> # Wait for the update to complete<br /> <br /> [https://youtu.be/Azi0uh8UZvI Video showing how to start the update]<br /> <br /> === NRFConnect ===<br /> <br /> # Download the aforementioned file to your phone.<br /> # Open NRFConnect<br /> # Scan for your device<br /> # Connect to it<br /> # Choose the DFU option at the top right of the screen<br /> # Ensure the 'Distribution packet (ZIP)' option is selected, and press OK<br /> # Select your previously downloaded file<br /> # Wait for the update to complete<br /> <br /> [https://youtu.be/jnX7WwYDiDE Video showing how to start the update]<br /> <br /> === Siglo ===<br /> # If your device was not detected upon start, press &quot;Rescan&quot; to find it.<br /> # Select the &quot;1.0.0&quot; tag<br /> # Select the aforementioned file/asset.<br /> # Select &quot;Flash It!&quot;<br /> <br /> === Amazfish ===<br /> # Run Amazfish (service + UI)<br /> # Pair with you device:<br /> ## Unzip the DFU file to extract the .bin file.<br /> ## Click on &quot;pair with watch&quot; on the top<br /> ## Select &quot;PineTime&quot; (if your device is running InfiniTime 0.7.1 or lower) or &quot;InfiniTime (if it's running InfiniTime 0.8+) and choose your device in the list<br /> # Click on &quot;Download file&quot; on the top <br /> # Click on &quot;Choose file&quot; and select the .bin file you extracted from the DFU file<br /> # Click on &quot;Send file&quot;<br /> # Wait for the update to complete.<br /> <br /> [https://video.codingfield.com/videos/watch/41cfcf5d-b0e6-4323-8056-b0a6682d1f25 See it in action!]<br /> <br /> == Update the bootloader ==<br /> To update the bootloader, you want to flash [https://github.com/JF002/InfiniTime/releases/download/0.14.1/reloader-mcuboot.zip reloader-mcuboot.zip]. <br /> Once the bootloader is updated, you should notice that the boot logo has changed. Previously, it was a green &quot;PineTime&quot; logo, and now it is a large pinecone that is progressively drawn in green.<br /> <br /> [https://youtu.be/fvHQ8ZeqnOo Video showing what the InfiniTime 1.0.0 bootloader looks like]<br /> <br /> === Using Gadgetbridge ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> === Using NRFConnect ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> === Using Siglo ===<br /> Same process as before, but select the &quot;0.14.1&quot; tag, and the file/asset for this step.<br /> <br /> === Using Amazfish ===<br /> <br /> You may need to re-pair with your device by selecting &quot;InfiniTime&quot; (since you've already upgraded to InfiniTime 1.0) in the device type list. Then follow the same process as before, but with the file for this step.<br /> <br /> == Install the recovery firmware ==<br /> {{warning|1=Don't do this before updating the bootloader, otherwise your PineTime will freeze at the end of the process, and you will need to wait for the battery to go flat }} <br /> <br /> To install the recovery firmware, you want to flash [https://github.com/JF002/InfiniTime/releases/download/0.14.1/pinetime-mcuboot-recovery-loader-dfu-0.14.1.zip pinetime-mcuboot-recovery-loader-dfu-0.14.1.zip]. You will know when this is running when it shows an InfiniTime logo with a progress bar running across the bottom whilst it is installing the recovery firmware. <br /> <br /> === Using Gadgetbridge ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> === Using NRFConnect ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> === Using Siglo ===<br /> Same process as before, but with the file/asset for this step.<br /> <br /> === Using Amazfish ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> <br /> = Guides and Videos =<br /> <br /> = Troubleshooting =<br /> Sometimes during the update process, the connection will drop, and the update will fail. Your PineTime isn't broken, most likely the Bluetooth link dropped for a moment, so just try again. Try rebooting your phone, if it keeps failing, try restarting the watch by holding the power button down for approximately 8 seconds. Try to '''avoid''' holding down the button with the screen off. Or try with another device, just in case there are compatibility issues. <br /> <br /> Version 1.0.0 of InfiniTime is merely the first version that was considered sufficiently feature-complete and stable enough for daily use. This isn't to say there aren't still bugs present ('cause there are!). So there are a few bugs still present in the update process and the bootloader. One unfortunate bug appears to be that sometimes when the watch tries to restart after an update, the bootloader locks up, and the watch won't turn on. In this case, you will need to wait until the watch battery goes flat, to force the watch to reset. This will most likely involve waiting for a week, and then when you put the watch on the charging cradle, it will power up and you should be right to try again.<br /> <br /> If you get stuck or have any questions, join us on your preferred [https://wiki.pine64.org/index.php/Main_Page#Chat_Platforms chat platform] or the product [https://forum.pine64.org/forumdisplay.php?fid=134 forum]. There's usually someone available who can help, or will get back to you in a few hours.<br /> <br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=Switching_your_PineTime_between_InfiniTime_and_Wasp-os&diff=10485 2021-05-22T09:58:14Z

<p>Avamander: </p> <hr /> <div>== Introduction ==<br /> Both Infinitime and Wasp-os are very cool OS'es for the [[PineTime]] and many people will want to try both. This is possible, even with a sealed device!<br /> <br /> Both devices use the same Nordic (legacy) DFU protocol for updating firmware over the air. But the BLE stack and the bootloaders for both are different. That's why we need to use the [https://github.com/daniel-thompson/wasp-reloader reloader]. However, instructions you find elsewhere (including [https://www.youtube.com/watch?v=lPasAt1LJmo Daniel Thompsons video]) are somewhat outdated.<br /> <br /> Flashing can be done with any of<br /> * nRF Connect for Mobile ([https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp Android], [https://apps.apple.com/us/app/nrf-connect-bluetooth-app/id1054362403 iOS])<br /> * [https://www.gadgetbridge.org GadgetBridge] (Android &gt;= 4.4)<br /> * [https://github.com/piggz/harbour-amazfish Amazfish] (SailfishOS and Linux)<br /> * [https://github.com/alexr4535/siglo Siglo] (Linux desktop and Pinephone) (Use the 'Manual OTA File' option)<br /> * [https://github.com/ZephyrLabs/PinetimeFlasher PinetimeFlasher] (Windows)<br /> * ota-dfu-python (Linux CLI) which is included in sources of both Infinitime and Wasp-os<br /> ** &lt;code&gt;InfiniTime/bootloader/ota-dfu-python/dfu.py&lt;/code&gt;<br /> ** &lt;code&gt;wasp-os/tools/ota-dfu-python/dfu.py&lt;/code&gt;<br /> <br /> This guide has been last updated for Infinitime 1.1.0 and Wasp-os 0.4<br /> <br /> == InfiniTime =&gt; Wasp-os ==<br /> <br /> All the zips you need can be found on the [https://github.com/daniel-thompson/wasp-os/releases/ Wasp-os Releases] page, for example in [https://github.com/daniel-thompson/wasp-os/releases/download/v0.4/wasp-os-0.4.tar.gz wasp-os-0.4.tar.gz].<br /> <br /> * Make sure the watch is running Infinitime and can be found by your companion device (PC, phone, etc).<br /> * First we need to flash the reloader, with the wasp-os bootloader as payload. To do this, flash: &lt;br&gt;&lt;code&gt;wasp-os-0.4/build-pinetime/reloader-mcuboot.zip&lt;/code&gt;<br /> * After flashing, it will boot using the Infinitime bootloader (green large pine cone), then it'll hang for a few seconds, then it'll show the reloader animation (blue smaller pine cone), and then it'll boot the wasp-os bootloader.<br /> * Make sure the watch is on the screen with the pine cone and arrow. If it is in a bootloop instead, then reboot the watch by holding the button until the arrow appears.<br /> * Now you can flash micropython with wasp-os: &lt;br&gt;&lt;code&gt;wasp-os-0.4/build-pinetime/micropython.zip&lt;/code&gt;<br /> * Wasp-os should now boot. Enjoy!<br /> <br /> == Wasp-os =&gt; InfiniTime ==<br /> <br /> The &lt;code&gt;reloader-factory.zip&lt;/code&gt; are unfortunately broken in waps-os 0.4, and very outdated in older releases. I do not recommend flashing these. Older InfiniTime versions have flaky BLE which makes upgrading from there very unreliable. Trying to create new zips containing any recent version of InfiniTime also fails, because it has grown too big to fit inaide a zip together with the reloader and bootloader.<br /> <br /> Instead, I made my own containing just the [https://github.com/JF002/InfiniTime/releases/tag/0.14.1 InfiniTime 0.14.1] [https://github.com/JF002/pinetime-mcuboot-bootloader/blob/develop/README.md#recovery-firmware recovery firmware]. This allows you to flash any future release of InfiniTime without having to find a new reloader zip. [https://github.com/Peetz0r/wasp-reloader/releases/tag/infinitime-0.14.1-recovery Get the zip here].<br /> <br /> * Reboot the watch by holding the button until the pine cone arrow appears.<br /> * Flash the reloader zip: &lt;br&gt;&lt;code&gt;reloader-infinitime-recovery-0.14.1.zip&lt;/code&gt;<br /> * After flashing, the reloader will run (blue smaller pine cone), then it'll boot the InfiniTime bootloader (large pine cone) will run.<br /> * Boot the watch into recovery mode by holding the button until the pine cone turns red. It'll boot again (large pine cone will turn green) and then the InfiniTime loo will appear.<br /> * You can now flash InfiniTime 1.1.0 (or any other version): &lt;br&gt;&lt;code&gt;reloader-infinitime-recovery-0.14.1.zip&lt;/code&gt;<br /> * InfiniTime should now boot. Enjoy!<br /> <br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=Upgrade_PineTime_to_InfiniTime_1.0.0&diff=10460 2021-05-19T21:35:41Z

<p>Avamander: </p> <hr /> <div>{{Note|Page under construction, information subject to review and feedback.}}<br /> <br /> Congratulations on receiving your new PineTime!<br /> <br /> From the factory, it ships with InfiniTime 0.7.1, and an older bootloader. So now you're probably wondering exactly how on earth do you go about upgrading your watch to the latest and greatest version of InfiniTime - you know, that version you've seen all those great pictures, videos and reviews of. To those of us that are developing stuff for it, it's pretty easy and straightforward, but like with all technology, it is a bit tricky. <br /> <br /> {{warning|1=Some people ran into issues during the update process that would temporarily make their watch unusable (display frozen or blank). The only know workaround consists of waiting for the battery to drain completely and try again. With the display off, and battery fully charged, you can expect a wait of 5-7 days so it is best to not fully charge it. If it freezes with the display on, it will likely be flat by the end of the day. We've never heard of any PineTimes that were permanently bricked (were not recoverable), though. }} <br /> <br /> In a nutshell, you need to:<br /> # Charge your watch, but '''not''' to 100% - keep it at approximately 50% - for the reason described above.<br /> # Update InfiniTime<br /> # Update the bootloader<br /> # Install the recovery firmware<br /> <br /> = Update Process =<br /> So how do you do this? Where do you start? Well, with a sealed PineTime, your only easy option is via Over The Air (OTA) Device Firmware Update (DFU), which is done via Bluetooth. There are a couple of different ways and apps you can use to do this. If you have an Android device, you can use [https://f-droid.org/en/packages/nodomain.freeyourgadget.gadgetbridge/ Gadgetbridge] or [https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp NRFConnect]. Otherwise, if your laptop or desktop computer has Bluetooth and runs Linux, you can use [https://github.com/alexr4535/siglo Siglo] or [https://github.com/piggz/harbour-amazfish Amazfish]. You can also use these applications on your Pinebook Pro or Pinephone if you happen to have those devices. <br /> <br /> The reason for installing the updates in the specified order is because newer versions of InfiniTime have a more robust Bluetooth update process, and since we're updating everything over Bluetooth, the fewer retries and failures from that you have the better. It will still sometimes disconnect mid update, meaning you'll need to try again, and possibly restart the watch a few times as well. And since the recovery firmware is new to the 1.0.0 version of the bootloader, it's best to update that last. <br /> <br /> [https://video.codingfield.com/videos/watch/831077c5-16f3-47b4-9b2b-c4bbfecc6529 This video] shows the bootloader and recovery firmware installation procedure.<br /> <br /> [https://video.codingfield.com/videos/watch/f7bffb3d-a6a1-43c4-8f01-f4aeff4adf9e This video] shows the bootloader installation and firmware update using Amazfish.<br /> <br /> You can also read a [https://github.com/JF002/pinetime-mcuboot-bootloader/blob/339224cf5ed21f4e8b2d22eaeab9869120f7f752/docs/howToUpdate.md detailed installation procedure in the documentation of the bootloader].<br /> <br /> == Update InfiniTime ==<br /> To update the main InfiniTime app, you want to flash [https://github.com/JF002/InfiniTime/releases/download/1.0.0/pinetime-mcuboot-app-dfu-1.0.0.zip pinetime-mcuboot-app-dfu-1.0.0.zip].<br /> <br /> After updating InfiniTime, ensure that you validate the firmware to prevent it from being automatically reverted/rolled back if your watch is reset/restarted. To do this, swipe right to access the quick actions panel, press the gear/settings icon, swipe up once to show the second page, press on the 'Firmware' option and then on 'Validate'.<br /> <br /> [https://youtu.be/-5lwBd60k0Q Video showing validation process]<br /> <br /> <br /> === Gadgetbridge ===<br /> <br /> # Connect your PineTime to GB<br /> # Download the aforementioned file to your phone<br /> # Find the file in your file manager<br /> # 'Open With' Gadgetbridge F/W Installer (method varies by device) - on my phone, it is press and hold, select the file, and then choose 'open with app' from the more options menu<br /> # Confirm that you wish to apply the update<br /> # Wait for the update to complete<br /> <br /> [https://youtu.be/Azi0uh8UZvI Video showing how to start the update]<br /> <br /> === NRFConnect ===<br /> <br /> # Download the aforementioned file to your phone.<br /> # Open NRFConnect<br /> # Scan for your device<br /> # Connect to it<br /> # Choose the DFU option at the top right of the screen<br /> # Ensure the 'Distribution packet (ZIP)' option is selected, and press OK<br /> # Select your previously downloaded file<br /> # Wait for the update to complete<br /> <br /> [https://youtu.be/jnX7WwYDiDE Video showing how to start the update]<br /> <br /> === Siglo ===<br /> # If your device was not detected upon start, press &quot;Rescan&quot; to find it.<br /> # Select the &quot;1.0.0&quot; tag<br /> # Select the aforementioned file/asset.<br /> # Select &quot;Flash It!&quot;<br /> <br /> === Amazfish ===<br /> # Run Amazfish (service + UI)<br /> # Pair with you device:<br /> ## Unzip the DFU file to extract the .bin file.<br /> ## Click on &quot;pair with watch&quot; on the top<br /> ## Select &quot;PineTime&quot; (if your device is running InfiniTime 0.7.1 or lower) or &quot;InfiniTime (if it's running InfiniTime 0.8+) and choose your device in the list<br /> # Click on &quot;Download file&quot; on the top <br /> # Click on &quot;Choose file&quot; and select the .bin file you extracted from the DFU file<br /> # Click on &quot;Send file&quot;<br /> # Wait for the update to complete.<br /> <br /> [https://video.codingfield.com/videos/watch/41cfcf5d-b0e6-4323-8056-b0a6682d1f25 See it in action!]<br /> <br /> == Update the bootloader ==<br /> To update the bootloader, you want to flash [https://github.com/JF002/InfiniTime/releases/download/0.14.1/reloader-mcuboot.zip reloader-mcuboot.zip]. <br /> Once the bootloader is updated, you should notice that the boot logo has changed. Previously, it was a green &quot;PineTime&quot; logo, and now it is a large pinecone that is progressively drawn in green.<br /> <br /> [https://youtu.be/fvHQ8ZeqnOo Video showing what the InfiniTime 1.0.0 bootloader looks like]<br /> <br /> === Using Gadgetbridge ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> === Using NRFConnect ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> === Using Siglo ===<br /> Same process as before, but select the &quot;0.14.1&quot; tag, and the file/asset for this step.<br /> <br /> === Using Amazfish ===<br /> <br /> You may need to re-pair with your device by selecting &quot;InfiniTime&quot; (since you've already upgraded to InfiniTime 1.0) in the device type list. Then follow the same process as before, but with the file for this step.<br /> <br /> == Install the recovery firmware ==<br /> {{warning|1=Don't do this before updating the bootloader, otherwise your PineTime will freeze at the end of the process, and you will need to wait for the battery to go flat }} <br /> <br /> To install the recovery firmware, you want to flash [https://github.com/JF002/InfiniTime/releases/download/0.14.1/pinetime-mcuboot-recovery-loader-dfu-0.14.1.zip pinetime-mcuboot-recovery-loader-dfu-0.14.1.zip]. You will know when this is running when it shows an InfiniTime logo with a progress bar running across the bottom whilst it is installing the recovery firmware. <br /> <br /> === Using Gadgetbridge ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> === Using NRFConnect ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> === Using Siglo ===<br /> Same process as before, but with the file/asset for this step.<br /> <br /> === Using Amazfish ===<br /> <br /> Same process as before, but with the file for this step.<br /> <br /> <br /> = Guides and Videos =<br /> <br /> = Troubleshooting =<br /> Sometimes during the update process, the connection will drop, and the update will fail. Your PineTime isn't broken, most likely the Bluetooth link dropped for a moment, so just try again. Try rebooting your phone, if it keeps failing, try restarting the watch by holding the power button down for approximately 8 seconds. Try to '''avoid''' holding down the button with the screen off. Or try with another device, just in case there are compatibility issues. <br /> <br /> Version 1.0.0 of InfiniTime is merely the first version that was considered sufficiently feature-complete and stable enough for daily use. This isn't to say there aren't still bugs present ('cause there are!). So there are a few bugs still present in the update process and the bootloader. One unfortunate bug appears to be that sometimes when the watch tries to restart after an update, the bootloader locks up, and the watch won't turn on. In this case, you will need to wait until the watch battery goes flat, to force the watch to reset. This will most likely involve waiting for a week, and then when you put the watch on the charging cradle, it will power up and you should be right to try again.<br /> <br /> If you get stuck or have any questions, join us on your preferred [https://wiki.pine64.org/index.php/Main_Page#Chat_Platforms chat platform] or the product [https://forum.pine64.org/forumdisplay.php?fid=134 forum]. There's usually someone available who can help, or will get back to you in a few hours.</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_Development&diff=10239 2021-05-04T21:16:07Z

<p>Avamander: /* Available firmware and projects */</p> <hr /> <div>== Reprogramming ==<br /> <br /> [[PineTime devkit wiring|Wire it up]] and then [[Reprogramming the PineTime| flash something]].<br /> <br /> == Available firmware and projects ==<br /> {| class=&quot;wikitable&quot;<br /> !<br /> ! Project Homepage<br /> ! Project Source<br /> ! PineTime Implementations<br /> <br /> |-<br /> ! FreeRTOS<br /> |https://www.freertos.org<br /> | https://sourceforge.net/projects/freertos/<br /> |<br /> {|<br /> |[[InfiniTime]] (GitHub: [https://github.com/JF002/Pinetime JF002/Pinetime])<br /> |-<br /> |[https://github.com/kaythe/pinetime-os kaythe/pinetime-os]<br /> |}<br /> <br /> |-<br /> ! Zephyr<br /> | https://www.zephyrproject.org<br /> | https://github.com/zephyrproject-rtos/zephyr<br /> |<br /> {|<br /> |[https://github.com/najnesnaj/pinetime-zephyr najnesnaj/pinetime-zephyr]<br /> |- <br /> |[https://github.com/SuperPrower/pinetime_zephyr_sample_fw SuperPrower/pinetime_zephyr_sample_fw]<br /> |-<br /> |[https://github.com/Dejvino/pinetime-hermes-firmware Dejvino/pinetime-hermes-firmware]<br /> |-<br /> |[https://github.com/endian-albin/pinetime-hypnos endian-albin/pinetime-hypnos]<br /> |}<br /> <br /> |-<br /> ! mynewt<br /> | https://mynewt.apache.org/about/<br /> | https://github.com/apache/mynewt-core<br /> |<br /> {|<br /> |[https://github.com/lupyuen/pinetime-rust-mynewt lupyuen/pinetime-rust-mynewt]<br /> |-<br /> |[https://gitlab.com/caspermeijn/klok caspermeijn/klok]<br /> |}<br /> <br /> |-<br /> ! MbedOS<br /> | https://os.mbed.com<br /> | https://github.com/ARMmbed/mbed-os<br /> |<br /> {|<br /> |[https://github.com/sethitow/mbed-pinetime sethitow/mbed-pinetime]<br /> |-<br /> |[https://github.com/geoffrey-vl/mbed-pinetime geoffrey.vl/mbed-pinetime]<br /> |}<br /> <br /> |-<br /> ! RIOT<br /> | http://riot-os.org/<br /> | https://github.com/RIOT-OS/RIOT/<br /> | [https://github.com/bosmoment/PineTime-apps bosmoment/PineTime-apps]<br /> <br /> |-<br /> ! TinyGo<br /> | https://tinygo.org<br /> | https://github.com/tinygo-org/tinygo<br /> | [https://github.com/aykevl/go-smartwatch aykevl/go-smartwatch]<br /> <br /> |-<br /> ! wasp-os (MicroPython)<br /> | https://wasp-os.readthedocs.io/<br /> | https://github.com/daniel-thompson/wasp-os<br /> | [https://wasp-os.readthedocs.io/en/latest/install.html#pine64-pinetime-developer-edition WaspOS PineTime install guide]<br /> <br /> |-<br /> ! Rust + RTFM<br /> | https://rtfm.rs/<br /> | [https://github.com/rtfm-rs/cortex-m-rtfm rtfm-rs/cortex-m-rtfm]<br /> | https://github.com/dbrgn/pinetime-rtfm/<br /> <br /> |-<br /> ! Bare Metal<br /> | <br /> |<br /> {|<br /> |https://github.com/xriss/timecake<br /> |-<br /> |https://github.com/Arc13/Pyrus<br /> |}<br /> |<br /> {|<br /> |[https://github.com/xriss/timecake xriss/timecake]<br /> |-<br /> |[https://github.com/Arc13/Pyrus Arc13/Pyrus]<br /> |}<br /> <br /> |-<br /> ! AdaFruit bootloader<br /> |<br /> | https://github.com/adafruit/Adafruit_nRF52_Bootloader<br /> | [https://github.com/daniel-thompson/wasp-bootloader daniel-thompson/wasp-bootloader]<br /> <br /> |-<br /> ! Useful drivers<br /> |<br /> | https://github.com/sethitow/mbed-pinetime<br /> | [https://github.com/sethitow/mbed-pinetime/tree/master/drivers https://github.com/sethitow/mbed-pinetime]<br /> |}<br /> <br /> {| class=&quot;wikitable&quot;<br /> !<br /> ! Project Homepage<br /> ! Project Source<br /> ! PineTime Implementations<br /> <br /> |-<br /> ! Gadgetbridge (Android companion app)<br /> | https://gadgetbridge.org/<br /> | https://codeberg.org/Freeyourgadget/Gadgetbridge<br /> | InfiniTime support in mainline<br /> <br /> |-<br /> ! Arduino<br /> | https://youtu.be/4aFDjymXjOw<br /> | https://github.com/atc1441/ATCwatch<br /> | https://github.com/atc1441/ATCwatch<br /> <br /> |-<br /> ! OTA Update Flasher / DaFlasher<br /> | https://youtu.be/gUVEz-pxhgg<br /> | https://github.com/atc1441/DaFlasherFiles<br /> | https://github.com/atc1441/DaFlasherFiles<br /> <br /> |-<br /> ! InfiniTime companion app for Linux<br /> | [https://github.com/alexr4535/siglo alexr4535/siglo]<br /> | <br /> | <br /> <br /> |-<br /> ! Wasp-os companion app for Linux<br /> | [https://github.com/arteeh/wasp-companion arteeh/wasp-companion]<br /> | <br /> | <br /> <br /> |-<br /> ! UI design proposal<br /> | [https://github.com/arteeh/pinetime arteeh/pinetime]<br /> | <br /> | <br /> <br /> |-<br /> ! Flashing app for Linux<br /> | [https://github.com/arteeh/pinetime-flasher arteeh/pinetime-flasher]<br /> | <br /> | <br /> <br /> |-<br /> ! Flashing app for Windows<br /> | [https://github.com/ZephyrLabs/PinetimeFlasher ZephyrLabs/PinetimeFlasher]<br /> | <br /> | <br /> <br /> |-<br /> |}<br /> <br /> === Manuals ===<br /> <br /> * [https://github.com/JF002/Pinetime InfiniTime installation]<br /> * [https://github.com/najnesnaj/pinetime-zephyr Zephyr installation] Beginner manual which explains how to install Zephyr (by najnesnaj).<br /> * [https://wasp-os.readthedocs.io/en/latest/ Wasp-OS installation] Full manual with install instructions and an application writer's guide.<br /> <br /> == How to write battery friendly software? ==<br /> <br /> 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:<br /> <br /> * Disable / shutdown / put in sleep mode '''all devices around the MCU''' (display controller, touch controller, external memory,...). <br /> * 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.<br /> * 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.<br /> * Do not use logging (JLink RTT, SWO, semihosting,...), it uses a lot of power.<br /> * 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:<br /> - using ''nrfjprog --reset''<br /> - using JLinkExe : issue the command ''writeDP 1 0''<br /> <br /> or with OpenOCD<br /> - issue the command ''halt''<br /> - issue the command ''flash fillw 0x10001208 0xFFFFFF00 0x01''<br /> - issue the command ''reset''<br /> <br /> you can check if the debug port is enabled using the following code<br /> DWT-&gt;CYCCNT ? &quot;NO&quot;:&quot;YES&quot;<br /> * 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.<br /> <br /> == Wishlist ==<br /> <br /> In order to keep track of features and changes to the hardware people would like to see, check out this article: [[PineTime Hardware Wishlist]]<br /> <br /> == Compatibility with other projects ==<br /> <br /> Different firmware running using different bootloaders and Bluetooth stacks on the nRF52832 have different requirements on how they should be initialised and what should be placed where in the internal flash.<br /> <br /> To keep track of what, how and why things work like they do across the different projects, check out the [[PineTime SD MCUBoot|PineTime SoftDevice and MCUBoot compatibility]] article.<br /> <br /> == Compatibility with companions apps and Bluetooth communication ==<br /> <br /> There are a lot of different firmware running on the Pinetime that implement different BLE APIs (time synchronization, notifications, ...). Companion apps must be able to differentiate between different firmware and forks of the same firmware. See [[PineTime Bluetooth]].<br /> <br /> == PineTime equivalents and jailbreaking ==<br /> <br /> This page contains a list of PineTime-like smartwatches that might be &quot;jailbreakable&quot; or a good source for ideas for the PineTime: [[PineTime Equivalents]]<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=Upgrade_PineTime_to_InfiniTime_1.0.0&diff=10231 2021-05-04T14:57:57Z

<p>Avamander: </p> <hr /> <div>{{Note|Page under construction, information subject to review and feedback.}}<br /> <br /> Congratulations on receiving your new PineTime!<br /> <br /> From the factory, it ships with InfiniTime 0.7.1, and an older bootloader. So now you're probably wondering exactly how on earth do you go about upgrading your watch to the latest and greatest version of InfiniTime - you know, that version you've seen all those great pictures, videos and reviews of. To those that of us that are developing stuff for it, its pretty easy and straightforward, but like with all technology, it is a bit tricky. <br /> <br /> {{warning|1=Some people ran into issues during the update process that would temporarily make their watch unusable (display frozen or blank). The only know workaround consists of waiting for the battery to drain completely and try again. We've never heard of any PineTimes that were permanently bricked (were not recoverable), though. }} <br /> <br /> In a nutshell, you need to:<br /> # '''Not''' charge the watch to a 100%, keep it at ~50%, for the reason described above.<br /> # Update InfiniTime<br /> # Update the bootloader<br /> # Install the recovery firmware<br /> <br /> = Update Process =<br /> So how do you do this? Where do you start? Well, with a sealed PineTime, your only easy option is via Over The Air (OTA) Device Firmware Update (DFU), which is done via Bluetooth. There are a couple of different ways and apps you can use to do this. If you have an Android device, you can use [https://f-droid.org/en/packages/nodomain.freeyourgadget.gadgetbridge/ Gadgetbridge] or [https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp NRFConnect]. Otherwise, if your laptop or desktop computer has bluetooth and runs Linux, you can use [https://github.com/alexr4535/siglo Siglo]. You can also use [https://github.com/alexr4535/siglo Siglo] on your Pinebook Pro or Pinephone if you happen to have those devices. <br /> <br /> The reason for installing the updates in the the specified order is because newer versions of InfiniTime have a more robust bluetooth update process, and since we're updating everything over Bluetooth, the less retries and failures from that you have the better. It will still sometimes disconnect mid update, meaning you'll need to try again, and possibly restart the watch a few times as well. And since the recovery firmware is new to the 1.0.0 version of the bootloader, it's best to update that last. <br /> <br /> == Update InfiniTime ==<br /> To update the main InfiniTime app, you want to flash [https://github.com/JF002/InfiniTime/releases/download/1.0.0/pinetime-mcuboot-app-dfu-1.0.0.zip pinetime-mcuboot-app-dfu-1.0.0.zip].<br /> <br /> === Gadgetbridge ===<br /> <br /> # Download the aforementioned file to your phone.<br /> # Find the file in your file manager. <br /> # 'Open With' Gadgetbridge F/W Installer (method varies by device) - on my phone, it is press and hold, select the file, and then choose 'open with app' from the more options menu<br /> # If Gadgetbridge gives an 'Element cannot be installed' error, add '.fw' to the end of the downloaded zip file, and try again.<br /> # Confirm that you wish to apply the update<br /> # Wait for the update to complete<br /> <br /> [https://youtu.be/Azi0uh8UZvI Video showing how to start the update]<br /> <br /> <br /> === NRFConnect ===<br /> <br /> # Download the aforementioned file to your phone.<br /> # Open NRFConnect<br /> # Scan for for your device<br /> # Connect to it<br /> # Choose the DFU option at the top right of the screen<br /> # Ensure the 'Distribution packet (ZIP)' option is selected, and press OK<br /> # Select your previously downloaded file<br /> # Wait for the update to complete<br /> <br /> [https://youtu.be/jnX7WwYDiDE Video showing how to start the update]<br /> <br /> <br /> === Siglo ===<br /> In Siglo, you can do this by picking the 1.0.0 tag, and flashing the aforementioned file.<br /> <br /> <br /> == Update the bootloader ==<br /> To update the bootloader, you want to flash [https://github.com/JF002/InfiniTime/releases/tag/0.14.1 reloader-mcuboot.zip]. <br /> <br /> === Using Gadgetbridge ===<br /> <br /> Same as above.<br /> <br /> === Using NRFConnect ===<br /> <br /> Same as above.<br /> <br /> === Using Siglo ===<br /> In Siglo, you can do this by picking the 0.14.1 tag, and flashing the aforementioned file. <br /> <br /> <br /> == Install the recovery firmware ==<br /> To install the recovery firmware, you want to flash [https://github.com/JF002/InfiniTime/releases/tag/0.14.1 pinetime-mcuboot-recovery-loader-dfu-0.14.1.zip].<br /> <br /> === Using Gadgetbridge ===<br /> <br /> Same as above.<br /> <br /> === Using NRFConnect ===<br /> <br /> Same as above.<br /> <br /> === Using Siglo ===<br /> In Siglo, you can do this by picking the 0.14.1 tag, and flashing the aforementioned file.<br /> <br /> <br /> = Guides and Videos =<br /> <br /> = Troubleshooting =<br /> Sometimes during the update process, the connection will drop, and the update will fail. Your PineTime isn't broken, most likely the Bluetooth link dropped for a moment, so just try again. Try rebooting your phone, if it keeps failing, try restarting the watch by holding the power button down for approximately 8 seconds. Try to '''avoid''' holding down the button with the screen off. Or try with another device, just in case there are compatibility issues. <br /> <br /> Version 1.0.0 of InfiniTime is merely the first version that was considered sufficiently feature complete and stable enough for daily use. This isn't to say there aren't still bugs present ('cause there are!). So there are a few bugs still present in the update process and the bootloader. One unfortunate bug appears to be that sometimes when the watch tries to restart after an update, the bootloader locks up, and the watch won't turn on. In this case, you will need to wait until the watch battery goes flat, in order to force the watch to reset. This will most likely involve waiting for a week, and then when you put the watch on the charge cradle, it will power up and you should be right to try again.<br /> <br /> If you get stuck, or have any questions, join us on your preferred [https://wiki.pine64.org/index.php/Main_Page#Chat_Platforms chat platform] or on the product [https://forum.pine64.org/forumdisplay.php?fid=134 forum]. There's usually someone available who can help, or will get back to you in a few hours.</div>

Avamander https://wiki.pine64.org/index.php?title=Upgrade_PineTime_to_InfiniTime_1.0.0&diff=10230 2021-05-04T14:54:01Z

<p>Avamander: /* Troubleshooting */</p> <hr /> <div>{{Note|Page under construction, information subject to review and feedback.}}<br /> <br /> Congratulations on receiving your new PineTime!<br /> <br /> From the factory, it ships with InfiniTime 0.7.1, and an older bootloader. So now you're probably wondering exactly how on earth do you go about upgrading your watch to the latest and greatest version of InfiniTime - you know, that version you've seen all those great pictures, videos and reviews of. To those that of us that are developing stuff for it, its pretty easy and straightforward, but like with all technology, it is a bit tricky. <br /> <br /> {{warning|1=Some people ran into issues during the update process that would temporarily make their watch unusable (display frozen or blank). The only know workaround consists of waiting for the battery to drain completely and try again. We've never heard of any PineTimes that were permanently bricked (were not recoverable), though. }} <br /> <br /> In a nutshell, you need to:<br /> # Update InfiniTime<br /> # Update the bootloader<br /> # Install the recovery firmware<br /> <br /> = Update Process =<br /> So how do you do this? Where do you start? Well, with a sealed PineTime, your only easy option is via Over The Air (OTA) Device Firmware Update (DFU), which is done via Bluetooth. There are a couple of different ways and apps you can use to do this. If you have an Android device, you can use [https://f-droid.org/en/packages/nodomain.freeyourgadget.gadgetbridge/ Gadgetbridge] or [https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp NRFConnect]. Otherwise, if your laptop or desktop computer has bluetooth and runs Linux, you can use [https://github.com/alexr4535/siglo Siglo]. You can also use [https://github.com/alexr4535/siglo Siglo] on your Pinebook Pro or Pinephone if you happen to have those devices. <br /> <br /> The reason for installing the updates in the the specified order is because newer versions of InfiniTime have a more robust bluetooth update process, and since we're updating everything over Bluetooth, the less retries and failures from that you have the better. It will still sometimes disconnect mid update, meaning you'll need to try again, and possibly restart the watch a few times as well. And since the recovery firmware is new to the 1.0.0 version of the bootloader, it's best to update that last. <br /> <br /> == Update InfiniTime ==<br /> To update the main InfiniTime app, you want to flash [https://github.com/JF002/InfiniTime/releases/download/1.0.0/pinetime-mcuboot-app-dfu-1.0.0.zip pinetime-mcuboot-app-dfu-1.0.0.zip].<br /> <br /> === Gadgetbridge ===<br /> <br /> # Download the aforementioned file to your phone.<br /> # Find the file in your file manager. <br /> # 'Open With' Gadgetbridge F/W Installer (method varies by device) - on my phone, it is press and hold, select the file, and then choose 'open with app' from the more options menu<br /> # If Gadgetbridge gives an 'Element cannot be installed' error, add '.fw' to the end of the downloaded zip file, and try again.<br /> # Confirm that you wish to apply the update<br /> # Wait for the update to complete<br /> <br /> [https://youtu.be/Azi0uh8UZvI Video showing how to start the update]<br /> <br /> <br /> === NRFConnect ===<br /> <br /> # Download the aforementioned file to your phone.<br /> # Open NRFConnect<br /> # Scan for for your device<br /> # Connect to it<br /> # Choose the DFU option at the top right of the screen<br /> # Ensure the 'Distribution packet (ZIP)' option is selected, and press OK<br /> # Select your previously downloaded file<br /> # Wait for the update to complete<br /> <br /> [https://youtu.be/jnX7WwYDiDE Video showing how to start the update]<br /> <br /> <br /> === Siglo ===<br /> In Siglo, you can do this by picking the 1.0.0 tag, and flashing the aforementioned file.<br /> <br /> <br /> == Update the bootloader ==<br /> To update the bootloader, you want to flash [https://github.com/JF002/InfiniTime/releases/tag/0.14.1 reloader-mcuboot.zip]. <br /> <br /> === Using Gadgetbridge ===<br /> <br /> Same as above.<br /> <br /> === Using NRFConnect ===<br /> <br /> Same as above.<br /> <br /> === Using Siglo ===<br /> In Siglo, you can do this by picking the 0.14.1 tag, and flashing the aforementioned file. <br /> <br /> <br /> == Install the recovery firmware ==<br /> To install the recovery firmware, you want to flash [https://github.com/JF002/InfiniTime/releases/tag/0.14.1 pinetime-mcuboot-recovery-loader-dfu-0.14.1.zip].<br /> <br /> === Using Gadgetbridge ===<br /> <br /> Same as above.<br /> <br /> === Using NRFConnect ===<br /> <br /> Same as above.<br /> <br /> === Using Siglo ===<br /> In Siglo, you can do this by picking the 0.14.1 tag, and flashing the aforementioned file.<br /> <br /> <br /> = Guides and Videos =<br /> <br /> = Troubleshooting =<br /> Sometimes during the update process, the connection will drop, and the update will fail. Your PineTime isn't broken, most likely the Bluetooth link dropped for a moment, so just try again. Try rebooting your phone, if it keeps failing, try restarting the watch by holding the power button down for approximately 8 seconds. Try to '''avoid''' holding down the button with the screen off. Or try with another device, just in case there are compatibility issues. <br /> <br /> Version 1.0.0 of InfiniTime is merely the first version that was considered sufficiently feature complete and stable enough for daily use. This isn't to say there aren't still bugs present ('cause there are!). So there are a few bugs still present in the update process and the bootloader. One unfortunate bug appears to be that sometimes when the watch tries to restart after an update, the bootloader locks up, and the watch won't turn on. In this case, you will need to wait until the watch battery goes flat, in order to force the watch to reset. This will most likely involve waiting for a week, and then when you put the watch on the charge cradle, it will power up and you should be right to try again.<br /> <br /> If you get stuck, or have any questions, join us on your preferred [https://wiki.pine64.org/index.php/Main_Page#Chat_Platforms chat platform] or on the product [https://forum.pine64.org/forumdisplay.php?fid=134 forum]. There's usually someone available who can help, or will get back to you in a few hours.</div>

Avamander https://wiki.pine64.org/index.php?title=Upgrade_PineTime_to_InfiniTime_1.0.0&diff=10229 2021-05-04T14:53:51Z

<p>Avamander: </p> <hr /> <div>{{Note|Page under construction, information subject to review and feedback.}}<br /> <br /> Congratulations on receiving your new PineTime!<br /> <br /> From the factory, it ships with InfiniTime 0.7.1, and an older bootloader. So now you're probably wondering exactly how on earth do you go about upgrading your watch to the latest and greatest version of InfiniTime - you know, that version you've seen all those great pictures, videos and reviews of. To those that of us that are developing stuff for it, its pretty easy and straightforward, but like with all technology, it is a bit tricky. <br /> <br /> {{warning|1=Some people ran into issues during the update process that would temporarily make their watch unusable (display frozen or blank). The only know workaround consists of waiting for the battery to drain completely and try again. We've never heard of any PineTimes that were permanently bricked (were not recoverable), though. }} <br /> <br /> In a nutshell, you need to:<br /> # Update InfiniTime<br /> # Update the bootloader<br /> # Install the recovery firmware<br /> <br /> = Update Process =<br /> So how do you do this? Where do you start? Well, with a sealed PineTime, your only easy option is via Over The Air (OTA) Device Firmware Update (DFU), which is done via Bluetooth. There are a couple of different ways and apps you can use to do this. If you have an Android device, you can use [https://f-droid.org/en/packages/nodomain.freeyourgadget.gadgetbridge/ Gadgetbridge] or [https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp NRFConnect]. Otherwise, if your laptop or desktop computer has bluetooth and runs Linux, you can use [https://github.com/alexr4535/siglo Siglo]. You can also use [https://github.com/alexr4535/siglo Siglo] on your Pinebook Pro or Pinephone if you happen to have those devices. <br /> <br /> The reason for installing the updates in the the specified order is because newer versions of InfiniTime have a more robust bluetooth update process, and since we're updating everything over Bluetooth, the less retries and failures from that you have the better. It will still sometimes disconnect mid update, meaning you'll need to try again, and possibly restart the watch a few times as well. And since the recovery firmware is new to the 1.0.0 version of the bootloader, it's best to update that last. <br /> <br /> == Update InfiniTime ==<br /> To update the main InfiniTime app, you want to flash [https://github.com/JF002/InfiniTime/releases/download/1.0.0/pinetime-mcuboot-app-dfu-1.0.0.zip pinetime-mcuboot-app-dfu-1.0.0.zip].<br /> <br /> === Gadgetbridge ===<br /> <br /> # Download the aforementioned file to your phone.<br /> # Find the file in your file manager. <br /> # 'Open With' Gadgetbridge F/W Installer (method varies by device) - on my phone, it is press and hold, select the file, and then choose 'open with app' from the more options menu<br /> # If Gadgetbridge gives an 'Element cannot be installed' error, add '.fw' to the end of the downloaded zip file, and try again.<br /> # Confirm that you wish to apply the update<br /> # Wait for the update to complete<br /> <br /> [https://youtu.be/Azi0uh8UZvI Video showing how to start the update]<br /> <br /> <br /> === NRFConnect ===<br /> <br /> # Download the aforementioned file to your phone.<br /> # Open NRFConnect<br /> # Scan for for your device<br /> # Connect to it<br /> # Choose the DFU option at the top right of the screen<br /> # Ensure the 'Distribution packet (ZIP)' option is selected, and press OK<br /> # Select your previously downloaded file<br /> # Wait for the update to complete<br /> <br /> [https://youtu.be/jnX7WwYDiDE Video showing how to start the update]<br /> <br /> <br /> === Siglo ===<br /> In Siglo, you can do this by picking the 1.0.0 tag, and flashing the aforementioned file.<br /> <br /> <br /> == Update the bootloader ==<br /> To update the bootloader, you want to flash [https://github.com/JF002/InfiniTime/releases/tag/0.14.1 reloader-mcuboot.zip]. <br /> <br /> === Using Gadgetbridge ===<br /> <br /> Same as above.<br /> <br /> === Using NRFConnect ===<br /> <br /> Same as above.<br /> <br /> === Using Siglo ===<br /> In Siglo, you can do this by picking the 0.14.1 tag, and flashing the aforementioned file. <br /> <br /> <br /> == Install the recovery firmware ==<br /> To install the recovery firmware, you want to flash [https://github.com/JF002/InfiniTime/releases/tag/0.14.1 pinetime-mcuboot-recovery-loader-dfu-0.14.1.zip].<br /> <br /> === Using Gadgetbridge ===<br /> <br /> Same as above.<br /> <br /> === Using NRFConnect ===<br /> <br /> Same as above.<br /> <br /> === Using Siglo ===<br /> In Siglo, you can do this by picking the 0.14.1 tag, and flashing the aforementioned file.<br /> <br /> <br /> = Guides and Videos =<br /> <br /> = Troubleshooting =<br /> Sometimes during the update process, the connection will drop, and the update will fail. Your PineTime isn't broken, most likely the Bluetooth link dropped for a moment, so just try again. Try rebooting your phone, if it keeps failing, try restarting the watch by holding the power button down for approximately 8 seconds. Try to ''avoid'' holding down the button with the screen off. Or try with another device, just in case there are compatibility issues. <br /> <br /> Version 1.0.0 of InfiniTime is merely the first version that was considered sufficiently feature complete and stable enough for daily use. This isn't to say there aren't still bugs present ('cause there are!). So there are a few bugs still present in the update process and the bootloader. One unfortunate bug appears to be that sometimes when the watch tries to restart after an update, the bootloader locks up, and the watch won't turn on. In this case, you will need to wait until the watch battery goes flat, in order to force the watch to reset. This will most likely involve waiting for a week, and then when you put the watch on the charge cradle, it will power up and you should be right to try again.<br /> <br /> If you get stuck, or have any questions, join us on your preferred [https://wiki.pine64.org/index.php/Main_Page#Chat_Platforms chat platform] or on the product [https://forum.pine64.org/forumdisplay.php?fid=134 forum]. There's usually someone available who can help, or will get back to you in a few hours.</div>

Avamander https://wiki.pine64.org/index.php?title=Upgrade_PineTime_to_InfiniTime_1.0.0&diff=10228 2021-05-04T14:49:25Z

<p>Avamander: </p> <hr /> <div>{{Note|Page under construction, information subject to review and feedback.}}<br /> <br /> Congratulations on receiving your new PineTime!<br /> <br /> From the factory, it ships with InfiniTime 0.7.1, and an older bootloader. So now you're probably wondering exactly how on earth do you go about upgrading your watch to the latest and greatest version of InfiniTime - you know, that version you've seen all those great pictures, videos and reviews of. To those that of us that are developing stuff for it, its pretty easy and straightforward, but like with all technology, it is a bit tricky. <br /> <br /> {{warning|1=Some people ran into issues during the update process that would temporarily make their watch unusable (display frozen or blank). The only know workaround consists of waiting for the battery to drain completely and try again. We've never heard of any PineTimes that were permanently bricked (were not recoverable), though. }} <br /> <br /> In a nutshell, you need to:<br /> # Update InfiniTime<br /> # Update the bootloader<br /> # Install the recovery firmware<br /> <br /> = Update Process =<br /> So how do you do this? Where do you start? Well, with a sealed PineTime, your only easy option is via Over The Air (OTA) Device Firmware Update (DFU), which is done via Bluetooth. There are a couple of different ways and apps you can use to do this. If you have an Android device, you can use [https://f-droid.org/en/packages/nodomain.freeyourgadget.gadgetbridge/ Gadgetbridge] or [https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp NRFConnect]. Otherwise, if your laptop or desktop computer has bluetooth and runs Linux, you can use [https://github.com/alexr4535/siglo Siglo]. You can also use [https://github.com/alexr4535/siglo Siglo] on your Pinebook Pro or Pinephone if you happen to have those devices. <br /> <br /> The reason for installing the updates in the the specified order is because newer versions of InfiniTime have a more robust bluetooth update process, and since we're updating everything over Bluetooth, the less retries and failures from that you have the better. It will still sometimes disconnect mid update, meaning you'll need to try again, and possibly restart the watch a few times as well. And since the recovery firmware is new to the 1.0.0 version of the bootloader, it's best to update that last. <br /> <br /> == Update InfiniTime ==<br /> To update the main InfiniTime app, you want to flash [https://github.com/JF002/InfiniTime/releases/download/1.0.0/pinetime-mcuboot-app-dfu-1.0.0.zip pinetime-mcuboot-app-dfu-1.0.0.zip].<br /> <br /> === Gadgetbridge ===<br /> <br /> # Download the aforementioned file to your phone.<br /> # Find the file in your file manager. <br /> # 'Open With' Gadgetbridge F/W Installer (method varies by device) - on my phone, it is press and hold, select the file, and then choose 'open with app' from the more options menu<br /> # If Gadgetbridge gives an 'Element cannot be installed' error, add '.fw' to the end of the downloaded zip file, and try again.<br /> # Confirm that you wish to apply the update<br /> # Wait for the update to complete<br /> <br /> [https://youtu.be/Azi0uh8UZvI Video showing how to start the update]<br /> <br /> <br /> === NRFConnect ===<br /> <br /> # Download the aforementioned file to your phone.<br /> # Open NRFConnect<br /> # Scan for for your device<br /> # Connect to it<br /> # Choose the DFU option at the top right of the screen<br /> # Ensure the 'Distribution packet (ZIP)' option is selected, and press OK<br /> # Select your previously downloaded file<br /> # Wait for the update to complete<br /> <br /> [https://youtu.be/jnX7WwYDiDE Video showing how to start the update]<br /> <br /> <br /> === Siglo ===<br /> In Siglo, you can do this by picking the 1.0.0 tag, and flashing the aforementioned file.<br /> <br /> <br /> == Update the bootloader ==<br /> To update the bootloader, you want to flash [https://github.com/JF002/InfiniTime/releases/tag/0.14.1 reloader-mcuboot.zip]. <br /> <br /> === Using Gadgetbridge ===<br /> <br /> Same as above.<br /> <br /> === Using NRFConnect ===<br /> <br /> === Using Siglo ===<br /> In Siglo, you can do this by picking the 0.14.1 tag, and flashing the aforementioned file. <br /> <br /> <br /> == Install the recovery firmware ==<br /> To install the recovery firmware, you want to flash [https://github.com/JF002/InfiniTime/releases/tag/0.14.1 pinetime-mcuboot-recovery-loader-dfu-0.14.1.zip].<br /> <br /> === Using Gadgetbridge ===<br /> <br /> Same as above.<br /> <br /> === Using NRFConnect ===<br /> <br /> === Using Siglo ===<br /> In Siglo, you can do this by picking the 0.14.1 tag, and flashing the aforementioned file.<br /> <br /> <br /> = Guides and Videos =<br /> <br /> = Troubleshooting =<br /> Sometimes during the update process, the connection will drop, and the update will fail. Your PineTime isn't broken, most likely the bluetooth link dropped out for a moment, so just try again. If it keeps failing, try restarting the watch by holding the power button down for approximately 8 seconds. Or try with another device, just in case there are compatibility issues. <br /> <br /> Version 1.0.0 of InfiniTime is merely the first version that was considered sufficiently feature complete and stable enough for daily use. This isn't to say there aren't still bugs present ('cause there are!). So there are a few bugs still present in the update process and the bootloader. One unfortunate bug appears to be that sometimes when the watch tries to restart after an update, the bootloader locks up, and the watch won't turn on. In this case, you will need to wait until the watch battery goes flat, in order to force the watch to reset. This will most likely involve waiting for a week, and then when you put the watch on the charge cradle, it will power up and you should be right to try again.<br /> <br /> If you get stuck, or have any questions, join us on your preferred [https://wiki.pine64.org/index.php/Main_Page#Chat_Platforms chat platform] or on the product [https://forum.pine64.org/forumdisplay.php?fid=134 forum]. There's usually someone available who can help, or will get back to you in a few hours.</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime&diff=10191 2021-05-01T18:05:21Z

<p>Avamander: /* Short overview */</p> <hr /> <div>== Frequently asked questions ==<br /> <br /> '''Read these first!'''<br /> <br /> * [[PineTime FAQ| Frequently Asked Questions about the devkit]]<br /> * [[Reprogramming the PineTime|Reprogramming the PineTime (development kit)]]<br /> <br /> == Default OS ==<br /> <br /> 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.<br /> <br /> You can find a list of available firmware and other software here: [[PineTime Development]]<br /> <br /> == Short overview ==<br /> '''Dimensions:''' 37.5 x 40 x 11mm &lt;br&gt;<br /> '''Weight:''' 38 grams &lt;br&gt;<br /> '''IP Rating:''' IP67 (waterproof to 1 meter (sealed edition!)) &lt;br&gt;<br /> '''Display:'''<br /> : '''Size:''' 1.3 inches (33mm) diagonal<br /> : '''Type:''' IPS capacitive touchscreen, RGB 65K colors<br /> : '''Display Controller:''' ST7789<br /> : '''Resolution:''' 240x240 pixels &lt;br&gt;<br /> '''System on Chip:''' Nordic Semiconductor nRF52832 &lt;br&gt;<br /> '''Flash:''' 512KB with additional 4MB SPI NOR &lt;br&gt;<br /> '''RAM:''' 64KB &lt;br&gt;<br /> '''Bluetooth:''' [[PineTime_Bluetooth|5.0 (including Bluetooth Low Energy)]] &lt;br&gt;<br /> '''Sensors:''' Accelerometer, Heart rate sensor &lt;br&gt;<br /> '''Feedback:''' Vibration motor &lt;br&gt;<br /> '''Battery:''' 170-180mAh 3.8V LiPo<br /> <br /> = Community =<br /> <br /> == Forum ==<br /> * [https://forum.pine64.org/forumdisplay.php?fid=134 PineTime forum]<br /> <br /> == Chat ==<br /> * [https://app.element.io/#/room/#pinetime:matrix.org Matrix Channel] (No login required to read)<br /> * IRC Server: [ircs://irc.pine64.org#pinetime irc.pine64.org] Channel: PineTime<br /> * [https://t.me/pinetime Telegram group]<br /> * [https://discordapp.com/invite/DgB7kzr Discord server invite link]<br /> <br /> === Developers and coding ===<br /> * [https://app.element.io/#/room/#pinetime-dev:matrix.org Matrix Channel] (No login required to read)<br /> * [https://t.me/pinetime_dev Telegram group]<br /> * [https://discordapp.com/invite/DgB7kzr Discord server invite link]<br /> <br /> <br /> == Development efforts ==<br /> <br /> To read more about development on the PineTime, the projects available and more technical details, check out [[PineTime Development]]<br /> <br /> == Useful articles and blog posts == <br /> <br /> 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.<br /> <br /> * [https://www.ncartron.org/one-week-with-my-pinetime---a-feedback.html Using the PineTime in production (January 2021)]<br /> <br /> * [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]<br /> <br /> * [https://medium.com/@ly.lee/building-a-rust-driver-for-pinetimes-touch-controller-cbc1a5d5d3e9 Building a Rust Driver for PineTime’s Touch Controller]<br /> <br /> * [https://medium.com/@ly.lee/porting-druid-rust-widgets-to-pinetime-smart-watch-7e1d5a5d977a Porting (druid) Rust Widgets to PineTime Smart Watch]<br /> <br /> * [https://medium.com/@ly.lee/optimising-pinetimes-display-driver-with-rust-and-mynewt-3ba269ea2f5c Optimising PineTime’s Display Driver with Rust and Mynewt]<br /> <br /> * [https://electronut.in/getting-started-with-zephyr-rtos-on-nordic-nrf52832-hackable/ Getting Started with Zephyr RTOS on Nordic nRF52832 hackaBLE]<br /> <br /> * [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]<br /> <br /> * [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]<br /> <br /> * [https://www.nrbtech.io/blog/2020/1/4/using-clion-for-nordic-nrf52-projects Using CLion for Nordic nRF52 projects]<br /> <br /> * [https://dev.to/aaronc81/flashing-your-pinetime-using-an-st-link-and-openocd-54dd Flashing your PineTime using an ST-Link and OpenOCD]<br /> <br /> * [https://zephyrlabs.github.io/Watchfaces/ Zephyrlabs: just a bunch of watchfaces made for the pinetime]<br /> <br /> *[https://pankajraghav.com/2021/04/03/PINETIME-STOPCLOCK.html Creating a stopwatch in Pinetime (with Infinitime)]<br /> <br /> == Hardware ==<br /> <br /> === Display ===<br /> <br /> 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.<br /> <br /> The display is driven using the ST7789 display controller. Use the following pins to drive the screen:<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! PineTime pin<br /> ! ST7789 pin<br /> |-<br /> | LCD_SCK (P0.02)<br /> | SPI clock<br /> |-<br /> | LCD_SDI (P0.03)<br /> | SPI MOSI<br /> |-<br /> | LCD_RS (P0.18)<br /> | Command/Data pin (CD)<br /> |-<br /> | LCD_CS (P0.25)<br /> | Chip select<br /> |-<br /> | LCD_RESET (P0.26)<br /> | Display reset<br /> |-<br /> | LCD_BACKLIGHT_{LOW,MID,HIGH}<br /> | Backlight (active low)<br /> |}<br /> <br /> Notes:<br /> <br /> * 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.<br /> * SPI must be used in mode 3. Mode 0 (the default) won't work.<br /> * LCD_DISPLAY_* is used to enable the backlight. Set at least one to low to see anything on the screen.<br /> * Use SPI at 8MHz (the fastest clock available on the nRF52832) because otherwise refreshing will be super slow.<br /> <br /> '''References''':<br /> <br /> [https://github.com/adafruit/Adafruit-ST7735-Library/ Adafruit ST7789 driver in cpp]<br /> <br /> === Battery measurement ===<br /> <br /> 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.<br /> <br /> 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):<br /> <br /> adcVoltage = adcValue / (4095 / 3.3)<br /> <br /> 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:<br /> <br /> batteryVoltage = adcValue * 2 / (4095 / 3.3)<br /> <br /> 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:<br /> <br /> batteryVoltage = adcValue * 2000 / (4095 / 3.3)<br /> batteryVoltage = adcValue * 2000 / 1241<br /> <br /> Converting this voltage to an estimated capacity in percent requires a more complicated algorithm, because Lithium-ion batteries have a non-linear discharge curve.<br /> <br /> <br /> === Button ===<br /> <br /> The button on the side of the PineTime is disabled by default. To enable it, drive the button out pin (P0.15) high.<br /> <br /> While enabled, the button in pin (P0.13) will be high when the button is pressed, and low when it is not pressed.<br /> <br /> === Touch panel ===<br /> <br /> 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 [https://github.com/lupyuen/hynitron_i2c_cst0xxse/ 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,...).<br /> <br /> ==== Pins ====<br /> <br /> * P0.10 : Reset<br /> * P0.28 : Interrupt (signal to the CPU when a touch event is detected)<br /> * P0.06 : I²C SDA<br /> * P0.07 : I²C SCL<br /> <br /> ==== I²C ====<br /> <br /> * Device address : 0x15<br /> * Frequency : from 10Khz to 400Khz<br /> <br /> '''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.<br /> <br /> '''NOTE: ''' The I²C bus, also known as TWI bus has known issues, make sure to write your TWI driver with timeouts.<br /> <br /> ==== Touch events ====<br /> <br /> 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. <br /> <br /> These 63 bytes contain up to 10 touch point (X, Y, event type, pressure,...) : <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Byte<br /> ! Bit7<br /> ! Bit6<br /> ! Bit5<br /> ! Bit4<br /> ! Bit3<br /> ! Bit2<br /> ! Bit1<br /> ! Bit0<br /> |-<br /> |0<br /> |colspan=&quot;8&quot;|?<br /> |-<br /> |1<br /> |colspan=&quot;8&quot;|GestureID : (Gesture code ,<br /> <br /> 0x00: no gesture,<br /> <br /> 0x01: Slide down,<br /> <br /> 0x02: Slide up,<br /> <br /> 0x03: Slide left,<br /> <br /> 0x04: Slide right,<br /> <br /> 0x05: Single click,<br /> <br /> 0x0B: Double click,<br /> <br /> 0x0C: Long press) <br /> |-<br /> |2<br /> |colspan=&quot;4&quot;|? <br /> |colspan=&quot;4&quot;|Number of touch points <br /> |-<br /> |3<br /> |colspan=&quot;2&quot;|Event (0 = Down, 1 = Up, 2 = Contact)<br /> |colspan=&quot;2&quot;|?<br /> |colspan=&quot;4&quot;|X (MSB) coordinate<br /> |-<br /> |4<br /> |colspan=&quot;8&quot;|X (LSB) coordinate<br /> |-<br /> |5<br /> |colspan=&quot;2&quot;|?<br /> |colspan=&quot;2&quot;|Touch ID<br /> |colspan=&quot;4&quot;|Y (MSB) coordinate<br /> |-<br /> |6<br /> |colspan=&quot;8&quot;|Y (LSB) coordinate<br /> |-<br /> |7<br /> |colspan=&quot;8&quot;|Pressure (?)<br /> |-<br /> |8<br /> |colspan=&quot;8&quot;|Miscellaneous (?)<br /> |}<br /> <br /> Bytes 3 to 8 are repeated 10 times (10*6 + 3 = 63 bytes).<br /> <br /> '''NOTES'''<br /> <br /> * The touch controller seems to report only 1 touch point<br /> * Fields X, Y, Number of touch points and touch ID are updated. The others are always 0.<br /> <br /> ==== Registers ====<br /> <br /> The reference driver specifies some registers and value, but there is no information about them: <br /> <br /> {| class=&quot;wikitable&quot;<br /> <br /> !Register<br /> !Address<br /> !Description<br /> |-<br /> |HYN_REG_INT_CNT<br /> |0x8F<br /> |<br /> |-<br /> |HYN_REG_FLOW_WORK_CNT<br /> |0x91<br /> |<br /> |-<br /> |HYN_REG_WORKMODE <br /> |0x00<br /> |0 = WORK, 0x40 = FACTORY<br /> |-<br /> |HYN_REG_CHIP_ID<br /> |0xA3<br /> |<br /> |-<br /> |HYN_REG_CHIP_ID2<br /> |0x9F<br /> |-<br /> |HYN_REG_POWER_MODE<br /> |0xA5<br /> |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)<br /> |-<br /> |HYN_REG_FW_VER<br /> |0xA6<br /> |<br /> |-<br /> |HYN_REG_VENDOR_ID<br /> |0xA8<br /> |<br /> |-<br /> |HYN_REG_LCD_BUSY_NUM<br /> |0xAB<br /> |<br /> |-<br /> |HYN_REG_FACE_DEC_MODE_EN<br /> |0xB0<br /> |<br /> |-<br /> |HYN_REG_GLOVE_MODE_EN<br /> |0xC0<br /> |<br /> |-<br /> |HYN_REG_COVER_MODE_EN<br /> |0xC1<br /> |<br /> |-<br /> |HYN_REG_CHARGER_MODE_EN<br /> |0x8B<br /> |<br /> |-<br /> |HYN_REG_GESTURE_EN<br /> |0xD0<br /> |<br /> |-<br /> |HYN_REG_GESTURE_OUTPUT_ADDRESS<br /> |0xD3<br /> |<br /> |-<br /> |HYN_REG_ESD_SATURATE 0xED<br /> |0xED<br /> |<br /> |}<br /> <br /> '''WARNING : ''' &lt;del&gt;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!&lt;/del&gt;<br /> <br /> <br /> ===Accelerometer===<br /> The on board accelerometer is Bosch BMA421, connected to the I2C bus.<br /> <br /> ==== Pins ====<br /> <br /> * P0.06 : I²C SDA<br /> * P0.07 : I²C SCL<br /> * P0.08 : Interrupt<br /> <br /> I2C Device address : 0x18<br /> <br /> <br /> == Datasheets and Schematics ==<br /> <br /> === Schematics ===<br /> * [https://files.pine64.org/doc/PineTime/PineTime%20Schematic-V1.0a-20191103.pdf PineTime Schematic ver1.0a]<br /> * [https://files.pine64.org/doc/PineTime/PineTime%20Port%20Assignment%20rev1.0.pdf PineTime GPIO Port Assignment ver1.0]<br /> <br /> 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.<br /> <br /> === Chip Datasheets ===<br /> * NORDIC nRF52832 information:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/nRF52832%20product%20brief.pdf nRF52832 Product Brief]<br /> ** [https://infocenter.nordicsemi.com/pdf/nRF52832_PS_v1.1.pdf nRF52832 Product Specification v1.1]<br /> * ARMv7-M information:<br /> ** [https://static.docs.arm.com/ddi0403/eb/DDI0403E_B_armv7m_arm.pdf ARMv7-M Architecture Reference Manual]<br /> <br /> === Component Datasheets ===<br /> * PMU (Power Management Unit) information:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/SGM40561.pdf SGMicro SGM40561 Single Cell Charger Datasheet]<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/SGMICRO-SGM2036.pdf SGMicro SGM2036 3.3V Low Power Low Dropout RF Linear Regulator Datasheet]<br /> * SPI Flash information:<br /> ** [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])<br /> ** [https://datasheet.lcsc.com/szlcsc/2005251035_XTX-XT25F32BSOIGU-S_C558851.pdf XTX XT25F32B]<br /> ** IDs for XT25F32B are: manufacturer (0x0b), device (0x15), memory type (0x40), density (0x16)<br /> * LCD Panel:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/PineTime%20LCD%20Panel.jpg 1.3&quot; 240x240 IPS LCD Panel Specification for PineTime]<br /> ** [https://wiki.pine64.org/images/5/54/ST7789V_v1.6.pdf 11.6&quot; Sitronix LCD Driver/Controller Datasheet]<br /> * Touchpad information:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/PineTime%20Touch%20Panel.jpg Touchpad Specification for PineTimel]<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/CST816S数据手册V1.1.pdf 11.6&quot; Hynitron CST816S Capacitive Touch Controller Datasheet in Chinese]<br /> ** [https://wiki.pine64.org/images/2/2f/CST816S.zip Touch Controller Datasheet en]<br /> * Sensor:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/BST-BMA421-FL000.pdf BOSCH BMA421 Triaxial VAcceleration Sensor Product Brief]<br /> ** [https://wiki.pine64.org/images/c/cc/Bst-bma400-ds000.pdf BOSCH BMA400 3-axes ultra-low power accelerometer datasheet]<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/HRS3300%20Heart%20Rate%20Sensor.pdf TianYiHeXin HRS3300 PPG Heart Rate Sensor Data Sheet]<br /> <br /> <br /> == Community case design ==<br /> <br /> * [https://www.thingiverse.com/thing:4172849 PineTime Smart Watch case by dara0s at thingiverse]<br /> * [https://www.thingiverse.com/thing:4651462 PineTime dev kit back fix by joaquimorg at thingiverse]<br /> * [https://www.thingiverse.com/thing:4763267 PineTime dev kit charging holder v4 by zevix81 at thingiverse]<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime&diff=10004 2021-04-22T19:05:21Z

<p>Avamander: </p> <hr /> <div>== Frequently asked questions ==<br /> <br /> '''Read these first!'''<br /> <br /> * [[PineTime FAQ| Frequently Asked Questions about the devkit]]<br /> * [[Reprogramming the PineTime|Reprogramming the PineTime (development kit)]]<br /> <br /> == Default OS ==<br /> <br /> 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.<br /> <br /> You can find a list of available firmware and other software here: [[PineTime Development]]<br /> <br /> == Short overview ==<br /> '''Dimensions:''' 37.5 x 40 x 11mm &lt;br&gt;<br /> '''Weight:''' 38 grams &lt;br&gt;<br /> '''IP Rating:''' IP67 (waterproof to 1 meter (sealed edition!)) &lt;br&gt;<br /> '''Display:'''<br /> : '''Size:''' 1.3 inches (33mm) diagonal<br /> : '''Type:''' IPS capacitive touchscreen, RGB 65K colors<br /> : '''Display Controller:''' ST7789<br /> : '''Resolution:''' 240x240 pixels &lt;br&gt;<br /> '''System on Chip:''' Nordic Semiconductor nRF52832 &lt;br&gt;<br /> '''Flash:''' 512KB with additional 4MB SPI NOR &lt;br&gt;<br /> '''RAM:''' 64KB &lt;br&gt;<br /> '''Bluetooth:''' [[PineTime_Bluetooth|5.0 (including Bluetooth Low Energy)]] &lt;br&gt;<br /> '''Sensors:''' Accelerometer, Heart rate sensor &lt;br&gt;<br /> '''Feedback:''' Vibration motor &lt;br&gt;<br /> '''Battery:''' 170-180mAh LiPo<br /> <br /> = Community =<br /> <br /> == Forum ==<br /> * [https://forum.pine64.org/forumdisplay.php?fid=134 PineTime forum]<br /> <br /> == Chat ==<br /> * [https://app.element.io/#/room/#pinetime:matrix.org Matrix Channel] (No login required to read)<br /> * IRC Server: [ircs://irc.pine64.org#pinetime irc.pine64.org] Channel: PineTime<br /> * [https://t.me/pinetime Telegram group]<br /> * [https://discordapp.com/invite/DgB7kzr Discord server invite link]<br /> <br /> === Developers and coding ===<br /> * [https://app.element.io/#/room/#pinetime-dev:matrix.org Matrix Channel] (No login required to read)<br /> * [https://t.me/pinetime_dev Telegram group]<br /> * [https://discordapp.com/invite/DgB7kzr Discord server invite link]<br /> <br /> <br /> == Development efforts ==<br /> <br /> To read more about development on the PineTime, the projects available and more technical details, check out [[PineTime Development]]<br /> <br /> == Useful articles and blog posts == <br /> <br /> 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.<br /> <br /> * [https://www.ncartron.org/one-week-with-my-pinetime---a-feedback.html Using the PineTime in production (January 2021)]<br /> <br /> * [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]<br /> <br /> * [https://medium.com/@ly.lee/building-a-rust-driver-for-pinetimes-touch-controller-cbc1a5d5d3e9 Building a Rust Driver for PineTime’s Touch Controller]<br /> <br /> * [https://medium.com/@ly.lee/porting-druid-rust-widgets-to-pinetime-smart-watch-7e1d5a5d977a Porting (druid) Rust Widgets to PineTime Smart Watch]<br /> <br /> * [https://medium.com/@ly.lee/optimising-pinetimes-display-driver-with-rust-and-mynewt-3ba269ea2f5c Optimising PineTime’s Display Driver with Rust and Mynewt]<br /> <br /> * [https://electronut.in/getting-started-with-zephyr-rtos-on-nordic-nrf52832-hackable/ Getting Started with Zephyr RTOS on Nordic nRF52832 hackaBLE]<br /> <br /> * [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]<br /> <br /> * [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]<br /> <br /> * [https://www.nrbtech.io/blog/2020/1/4/using-clion-for-nordic-nrf52-projects Using CLion for Nordic nRF52 projects]<br /> <br /> * [https://dev.to/aaronc81/flashing-your-pinetime-using-an-st-link-and-openocd-54dd Flashing your PineTime using an ST-Link and OpenOCD]<br /> <br /> * [https://zephyrlabs.github.io/Watchfaces/ Zephyrlabs: just a bunch of watchfaces made for the pinetime]<br /> <br /> *[https://pankajraghav.com/2021/04/03/PINETIME-STOPCLOCK.html Creating a stopwatch in Pinetime (with Infinitime)]<br /> <br /> == Hardware ==<br /> <br /> === Display ===<br /> <br /> 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.<br /> <br /> The display is driven using the ST7789 display controller. Use the following pins to drive the screen:<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! PineTime pin<br /> ! ST7789 pin<br /> |-<br /> | LCD_SCK (P0.02)<br /> | SPI clock<br /> |-<br /> | LCD_SDI (P0.03)<br /> | SPI MOSI<br /> |-<br /> | LCD_RS (P0.18)<br /> | Command/Data pin (CD)<br /> |-<br /> | LCD_CS (P0.25)<br /> | Chip select<br /> |-<br /> | LCD_RESET (P0.26)<br /> | Display reset<br /> |-<br /> | LCD_BACKLIGHT_{LOW,MID,HIGH}<br /> | Backlight (active low)<br /> |}<br /> <br /> Notes:<br /> <br /> * 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.<br /> * SPI must be used in mode 3. Mode 0 (the default) won't work.<br /> * LCD_DISPLAY_* is used to enable the backlight. Set at least one to low to see anything on the screen.<br /> * Use SPI at 8MHz (the fastest clock available on the nRF52832) because otherwise refreshing will be super slow.<br /> <br /> '''References''':<br /> <br /> [https://github.com/adafruit/Adafruit-ST7735-Library/ Adafruit ST7789 driver in cpp]<br /> <br /> === Battery measurement ===<br /> <br /> 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.<br /> <br /> 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):<br /> <br /> adcVoltage = adcValue / (4095 / 3.3)<br /> <br /> 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:<br /> <br /> batteryVoltage = adcValue * 2 / (4095 / 3.3)<br /> <br /> 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:<br /> <br /> batteryVoltage = adcValue * 2000 / (4095 / 3.3)<br /> batteryVoltage = adcValue * 2000 / 1241<br /> <br /> Converting this voltage to an estimated capacity in percent requires a more complicated algorithm, because Lithium-ion batteries have a non-linear discharge curve.<br /> <br /> <br /> === Button ===<br /> <br /> The button on the side of the PineTime is disabled by default. To enable it, drive the button out pin (P0.15) high.<br /> <br /> While enabled, the button in pin (P0.13) will be high when the button is pressed, and low when it is not pressed.<br /> <br /> === Touch panel ===<br /> <br /> 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 [https://github.com/lupyuen/hynitron_i2c_cst0xxse/ 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,...).<br /> <br /> ==== Pins ====<br /> <br /> * P0.10 : Reset<br /> * P0.28 : Interrupt (signal to the CPU when a touch event is detected)<br /> * P0.06 : I²C SDA<br /> * P0.07 : I²C SCL<br /> <br /> ==== I²C ====<br /> <br /> * Device address : 0x15<br /> * Frequency : from 10Khz to 400Khz<br /> <br /> '''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.<br /> <br /> '''NOTE: ''' The I²C bus, also known as TWI bus has known issues, make sure to write your TWI driver with timeouts.<br /> <br /> ==== Touch events ====<br /> <br /> 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. <br /> <br /> These 63 bytes contain up to 10 touch point (X, Y, event type, pressure,...) : <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Byte<br /> ! Bit7<br /> ! Bit6<br /> ! Bit5<br /> ! Bit4<br /> ! Bit3<br /> ! Bit2<br /> ! Bit1<br /> ! Bit0<br /> |-<br /> |0<br /> |colspan=&quot;8&quot;|?<br /> |-<br /> |1<br /> |colspan=&quot;8&quot;|GestureID : (Gesture code ,<br /> <br /> 0x00: no gesture,<br /> <br /> 0x01: Slide down,<br /> <br /> 0x02: Slide up,<br /> <br /> 0x03: Slide left,<br /> <br /> 0x04: Slide right,<br /> <br /> 0x05: Single click,<br /> <br /> 0x0B: Double click,<br /> <br /> 0x0C: Long press) <br /> |-<br /> |2<br /> |colspan=&quot;4&quot;|? <br /> |colspan=&quot;4&quot;|Number of touch points <br /> |-<br /> |3<br /> |colspan=&quot;2&quot;|Event (0 = Down, 1 = Up, 2 = Contact)<br /> |colspan=&quot;2&quot;|?<br /> |colspan=&quot;4&quot;|X (MSB) coordinate<br /> |-<br /> |4<br /> |colspan=&quot;8&quot;|X (LSB) coordinate<br /> |-<br /> |5<br /> |colspan=&quot;2&quot;|?<br /> |colspan=&quot;2&quot;|Touch ID<br /> |colspan=&quot;4&quot;|Y (MSB) coordinate<br /> |-<br /> |6<br /> |colspan=&quot;8&quot;|Y (LSB) coordinate<br /> |-<br /> |7<br /> |colspan=&quot;8&quot;|Pressure (?)<br /> |-<br /> |8<br /> |colspan=&quot;8&quot;|Miscellaneous (?)<br /> |}<br /> <br /> Bytes 3 to 8 are repeated 10 times (10*6 + 3 = 63 bytes).<br /> <br /> '''NOTES'''<br /> <br /> * The touch controller seems to report only 1 touch point<br /> * Fields X, Y, Number of touch points and touch ID are updated. The others are always 0.<br /> <br /> ==== Registers ====<br /> <br /> The reference driver specifies some registers and value, but there is no information about them: <br /> <br /> {| class=&quot;wikitable&quot;<br /> <br /> !Register<br /> !Address<br /> !Description<br /> |-<br /> |HYN_REG_INT_CNT<br /> |0x8F<br /> |<br /> |-<br /> |HYN_REG_FLOW_WORK_CNT<br /> |0x91<br /> |<br /> |-<br /> |HYN_REG_WORKMODE <br /> |0x00<br /> |0 = WORK, 0x40 = FACTORY<br /> |-<br /> |HYN_REG_CHIP_ID<br /> |0xA3<br /> |<br /> |-<br /> |HYN_REG_CHIP_ID2<br /> |0x9F<br /> |-<br /> |HYN_REG_POWER_MODE<br /> |0xA5<br /> |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)<br /> |-<br /> |HYN_REG_FW_VER<br /> |0xA6<br /> |<br /> |-<br /> |HYN_REG_VENDOR_ID<br /> |0xA8<br /> |<br /> |-<br /> |HYN_REG_LCD_BUSY_NUM<br /> |0xAB<br /> |<br /> |-<br /> |HYN_REG_FACE_DEC_MODE_EN<br /> |0xB0<br /> |<br /> |-<br /> |HYN_REG_GLOVE_MODE_EN<br /> |0xC0<br /> |<br /> |-<br /> |HYN_REG_COVER_MODE_EN<br /> |0xC1<br /> |<br /> |-<br /> |HYN_REG_CHARGER_MODE_EN<br /> |0x8B<br /> |<br /> |-<br /> |HYN_REG_GESTURE_EN<br /> |0xD0<br /> |<br /> |-<br /> |HYN_REG_GESTURE_OUTPUT_ADDRESS<br /> |0xD3<br /> |<br /> |-<br /> |HYN_REG_ESD_SATURATE 0xED<br /> |0xED<br /> |<br /> |}<br /> <br /> '''WARNING : ''' &lt;del&gt;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!&lt;/del&gt;<br /> <br /> <br /> ===Accelerometer===<br /> The on board accelerometer is Bosch BMA421, connected to the I2C bus.<br /> <br /> ==== Pins ====<br /> <br /> * P0.06 : I²C SDA<br /> * P0.07 : I²C SCL<br /> * P0.08 : Interrupt<br /> <br /> I2C Device address : 0x18<br /> <br /> <br /> == Datasheets and Schematics ==<br /> <br /> === Schematics ===<br /> * [https://files.pine64.org/doc/PineTime/PineTime%20Schematic-V1.0a-20191103.pdf PineTime Schematic ver1.0a]<br /> * [https://files.pine64.org/doc/PineTime/PineTime%20Port%20Assignment%20rev1.0.pdf PineTime GPIO Port Assignment ver1.0]<br /> <br /> 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.<br /> <br /> === Chip Datasheets ===<br /> * NORDIC nRF52832 information:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/nRF52832%20product%20brief.pdf nRF52832 Product Brief]<br /> ** [https://infocenter.nordicsemi.com/pdf/nRF52832_PS_v1.1.pdf nRF52832 Product Specification v1.1]<br /> * ARMv7-M information:<br /> ** [https://static.docs.arm.com/ddi0403/eb/DDI0403E_B_armv7m_arm.pdf ARMv7-M Architecture Reference Manual]<br /> <br /> === Component Datasheets ===<br /> * PMU (Power Management Unit) information:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/SGM40561.pdf SGMicro SGM40561 Single Cell Charger Datasheet]<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/SGMICRO-SGM2036.pdf SGMicro SGM2036 3.3V Low Power Low Dropout RF Linear Regulator Datasheet]<br /> * SPI Flash information:<br /> ** [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])<br /> ** [https://datasheet.lcsc.com/szlcsc/2005251035_XTX-XT25F32BSOIGU-S_C558851.pdf XTX XT25F32B]<br /> ** IDs for XT25F32B are: manufacturer (0x0b), device (0x15), memory type (0x40), density (0x16)<br /> * LCD Panel:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/PineTime%20LCD%20Panel.jpg 1.3&quot; 240x240 IPS LCD Panel Specification for PineTime]<br /> ** [https://wiki.pine64.org/images/5/54/ST7789V_v1.6.pdf 11.6&quot; Sitronix LCD Driver/Controller Datasheet]<br /> * Touchpad information:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/PineTime%20Touch%20Panel.jpg Touchpad Specification for PineTimel]<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/CST816S数据手册V1.1.pdf 11.6&quot; Hynitron CST816S Capacitive Touch Controller Datasheet in Chinese]<br /> ** [https://wiki.pine64.org/images/2/2f/CST816S.zip Touch Controller Datasheet en]<br /> * Sensor:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/BST-BMA421-FL000.pdf BOSCH BMA421 Triaxial VAcceleration Sensor Product Brief]<br /> ** [https://wiki.pine64.org/images/c/cc/Bst-bma400-ds000.pdf BOSCH BMA400 3-axes ultra-low power accelerometer datasheet]<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/HRS3300%20Heart%20Rate%20Sensor.pdf TianYiHeXin HRS3300 PPG Heart Rate Sensor Data Sheet]<br /> <br /> <br /> == Community case design ==<br /> <br /> * [https://www.thingiverse.com/thing:4172849 PineTime Smart Watch case by dara0s at thingiverse]<br /> * [https://www.thingiverse.com/thing:4651462 PineTime dev kit back fix by joaquimorg at thingiverse]<br /> * [https://www.thingiverse.com/thing:4763267 PineTime dev kit charging holder v4 by zevix81 at thingiverse]<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime&diff=10003 2021-04-22T19:03:32Z

<p>Avamander: </p> <hr /> <div>== Frequently asked questions ==<br /> <br /> '''Read these first!'''<br /> <br /> * [[PineTime FAQ| Frequently Asked Questions about the devkit]]<br /> * [[Reprogramming the PineTime|Reprogramming the PineTime (development kit)]]<br /> <br /> == Default OS ==<br /> <br /> 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.<br /> <br /> You can find a list of available firmware and other software here: [[PineTime Development]]<br /> <br /> == Short overview ==<br /> '''Dimensions:''' 37.5 x 40 x 11mm &lt;br&gt;<br /> '''Weight:''' 38 grams &lt;br&gt;<br /> '''IP Rating:''' IP67 (waterproof to 1 meter (sealed edition!)) &lt;br&gt;<br /> '''Display:'''<br /> : '''Size:''' 1.3 inches (33mm) diagonal<br /> : '''Type:''' IPS capacitive touchscreen, RGB 65K colors<br /> : '''Display Controller:''' ST7789<br /> : '''Resolution:''' 240x240 pixels &lt;br&gt;<br /> '''System on Chip:''' Nordic Semiconductor nRF52832 &lt;br&gt;<br /> '''Flash:''' 512KB with additional 4MB SPI NOR &lt;br&gt;<br /> '''RAM:''' 64KB &lt;br&gt;<br /> '''Bluetooth:''' [[PineTime_Bluetooth|5.0 (including Bluetooth Low Energy)]] &lt;br&gt;<br /> '''Sensors:''' Accelerometer, Heart rate sensor &lt;br&gt;<br /> '''Feedback:''' Vibration motor &lt;br&gt;<br /> '''Battery:''' 170-180mAh LiPo<br /> <br /> = Community =<br /> <br /> == Forum ==<br /> * [https://forum.pine64.org/forumdisplay.php?fid=134 PineTime forum]<br /> <br /> == Chat ==<br /> * [https://app.element.io/#/room/#pinetime:matrix.org Matrix Channel] (No login required to read)<br /> * IRC Server: [ircs://irc.pine64.org#pinetime irc.pine64.org] Channel: PineTime<br /> * [https://t.me/pinetime Telegram group]<br /> * [https://discordapp.com/invite/DgB7kzr Discord server invite link]<br /> <br /> === Developers and coding ===<br /> * [https://app.element.io/#/room/#pinetime-dev:matrix.org Matrix Channel] (No login required to read)<br /> * [https://t.me/pinetime_dev Telegram group]<br /> * [https://discordapp.com/invite/DgB7kzr Discord server invite link]<br /> <br /> <br /> == Development efforts ==<br /> <br /> To read more about development on the PineTime, the projects available and more technical details, check out [[PineTime Development]]<br /> <br /> == Useful articles and blog posts == <br /> <br /> 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.<br /> <br /> * [https://www.ncartron.org/one-week-with-my-pinetime---a-feedback.html Using the PineTime in production (January 2021)]<br /> <br /> * [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]<br /> <br /> * [https://medium.com/@ly.lee/building-a-rust-driver-for-pinetimes-touch-controller-cbc1a5d5d3e9 Building a Rust Driver for PineTime’s Touch Controller]<br /> <br /> * [https://medium.com/@ly.lee/porting-druid-rust-widgets-to-pinetime-smart-watch-7e1d5a5d977a Porting (druid) Rust Widgets to PineTime Smart Watch]<br /> <br /> * [https://medium.com/@ly.lee/optimising-pinetimes-display-driver-with-rust-and-mynewt-3ba269ea2f5c Optimising PineTime’s Display Driver with Rust and Mynewt]<br /> <br /> * [https://electronut.in/getting-started-with-zephyr-rtos-on-nordic-nrf52832-hackable/ Getting Started with Zephyr RTOS on Nordic nRF52832 hackaBLE]<br /> <br /> * [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]<br /> <br /> * [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]<br /> <br /> * [https://www.nrbtech.io/blog/2020/1/4/using-clion-for-nordic-nrf52-projects Using CLion for Nordic nRF52 projects]<br /> <br /> * [https://dev.to/aaronc81/flashing-your-pinetime-using-an-st-link-and-openocd-54dd Flashing your PineTime using an ST-Link and OpenOCD]<br /> <br /> * [https://zephyrlabs.github.io/Watchfaces/ Zephyrlabs: just a bunch of watchfaces made for the pinetime]<br /> <br /> *[https://pankajraghav.com/2021/04/03/PINETIME-STOPCLOCK.html Creating a stopwatch in Pinetime (with Infinitime)]<br /> <br /> == Hardware ==<br /> <br /> === Display ===<br /> <br /> 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.<br /> <br /> The display is driven using the ST7789 display controller. Use the following pins to drive the screen:<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! PineTime pin<br /> ! ST7789 pin<br /> |-<br /> | LCD_SCK (P0.02)<br /> | SPI clock<br /> |-<br /> | LCD_SDI (P0.03)<br /> | SPI MOSI<br /> |-<br /> | LCD_RS (P0.18)<br /> | Command/Data pin (CD)<br /> |-<br /> | LCD_CS (P0.25)<br /> | Chip select<br /> |-<br /> | LCD_RESET (P0.26)<br /> | Display reset<br /> |-<br /> | LCD_BACKLIGHT_{LOW,MID,HIGH}<br /> | Backlight (active low)<br /> |}<br /> <br /> Notes:<br /> <br /> * 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.<br /> * SPI must be used in mode 3. Mode 0 (the default) won't work.<br /> * LCD_DISPLAY_* is used to enable the backlight. Set at least one to low to see anything on the screen.<br /> * Use SPI at 8MHz (the fastest clock available on the nRF52832) because otherwise refreshing will be super slow.<br /> <br /> '''References''':<br /> <br /> [https://github.com/adafruit/Adafruit-ST7735-Library/ Adafruit ST7789 driver in cpp]<br /> <br /> === Battery measurement ===<br /> <br /> 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.<br /> <br /> 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):<br /> <br /> adcVoltage = adcValue / (4095 / 3.3)<br /> <br /> 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:<br /> <br /> batteryVoltage = adcValue * 2 / (4095 / 3.3)<br /> <br /> 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:<br /> <br /> batteryVoltage = adcValue * 2000 / (4095 / 3.3)<br /> batteryVoltage = adcValue * 2000 / 1241<br /> <br /> Converting this voltage to an estimated capacity in percent requires a more complicated algorithm, because Lithium-ion batteries have a non-linear discharge curve.<br /> <br /> <br /> === Button ===<br /> <br /> The button on the side of the PineTime is disabled by default. To enable it, drive the button out pin (P0.15) high.<br /> <br /> While enabled, the button in pin (P0.13) will be high when the button is pressed, and low when it is not pressed.<br /> <br /> === Touch panel ===<br /> <br /> 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 [https://github.com/lupyuen/hynitron_i2c_cst0xxse/ 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,...).<br /> <br /> ==== Pins ====<br /> <br /> * P0.10 : Reset<br /> * P0.28 : Interrupt (signal to the CPU when a touch event is detected)<br /> * P0.06 : I²C SDA<br /> * P0.07 : I²C SCL<br /> <br /> ==== I²C ====<br /> <br /> * Device address : 0x15<br /> * Frequency : from 10Khz to 400Khz<br /> <br /> '''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.<br /> <br /> '''NOTE: ''' The I²C bus, also known as TWI bus has known issues, make sure to write your TWI driver with timeouts.<br /> <br /> ==== Touch events ====<br /> <br /> 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. <br /> <br /> These 63 bytes contain up to 10 touch point (X, Y, event type, pressure,...) : <br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Byte<br /> ! Bit7<br /> ! Bit6<br /> ! Bit5<br /> ! Bit4<br /> ! Bit3<br /> ! Bit2<br /> ! Bit1<br /> ! Bit0<br /> |-<br /> |0<br /> |colspan=&quot;8&quot;|?<br /> |-<br /> |1<br /> |colspan=&quot;8&quot;|GestureID : (Gesture code ,<br /> <br /> 0x00: no gesture,<br /> <br /> 0x01: Slide down,<br /> <br /> 0x02: Slide up,<br /> <br /> 0x03: Slide left,<br /> <br /> 0x04: Slide right,<br /> <br /> 0x05: Single click,<br /> <br /> 0x0B: Double click,<br /> <br /> 0x0C: Long press) <br /> |-<br /> |2<br /> |colspan=&quot;4&quot;|? <br /> |colspan=&quot;4&quot;|Number of touch points <br /> |-<br /> |3<br /> |colspan=&quot;2&quot;|Event (0 = Down, 1 = Up, 2 = Contact)<br /> |colspan=&quot;2&quot;|?<br /> |colspan=&quot;4&quot;|X (MSB) coordinate<br /> |-<br /> |4<br /> |colspan=&quot;8&quot;|X (LSB) coordinate<br /> |-<br /> |5<br /> |colspan=&quot;2&quot;|?<br /> |colspan=&quot;2&quot;|Touch ID<br /> |colspan=&quot;4&quot;|Y (MSB) coordinate<br /> |-<br /> |6<br /> |colspan=&quot;8&quot;|Y (LSB) coordinate<br /> |-<br /> |7<br /> |colspan=&quot;8&quot;|Pressure (?)<br /> |-<br /> |8<br /> |colspan=&quot;8&quot;|Miscellaneous (?)<br /> |}<br /> <br /> Bytes 3 to 8 are repeated 10 times (10*6 + 3 = 63 bytes).<br /> <br /> '''NOTES'''<br /> <br /> * The touch controller seems to report only 1 touch point<br /> * Fields X, Y, Number of touch points and touch ID are updated. The others are always 0.<br /> <br /> ==== Registers ====<br /> <br /> The reference driver specifies some registers and value, but there is no information about them: <br /> <br /> {| class=&quot;wikitable&quot;<br /> <br /> !Register<br /> !Address<br /> !Description<br /> |-<br /> |HYN_REG_INT_CNT<br /> |0x8F<br /> |<br /> |-<br /> |HYN_REG_FLOW_WORK_CNT<br /> |0x91<br /> |<br /> |-<br /> |HYN_REG_WORKMODE <br /> |0x00<br /> |0 = WORK, 0x40 = FACTORY<br /> |-<br /> |HYN_REG_CHIP_ID<br /> |0xA3<br /> |<br /> |-<br /> |HYN_REG_CHIP_ID2<br /> |0x9F<br /> |-<br /> |HYN_REG_POWER_MODE<br /> |0xA5<br /> |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)<br /> |-<br /> |HYN_REG_FW_VER<br /> |0xA6<br /> |<br /> |-<br /> |HYN_REG_VENDOR_ID<br /> |0xA8<br /> |<br /> |-<br /> |HYN_REG_LCD_BUSY_NUM<br /> |0xAB<br /> |<br /> |-<br /> |HYN_REG_FACE_DEC_MODE_EN<br /> |0xB0<br /> |<br /> |-<br /> |HYN_REG_GLOVE_MODE_EN<br /> |0xC0<br /> |<br /> |-<br /> |HYN_REG_COVER_MODE_EN<br /> |0xC1<br /> |<br /> |-<br /> |HYN_REG_CHARGER_MODE_EN<br /> |0x8B<br /> |<br /> |-<br /> |HYN_REG_GESTURE_EN<br /> |0xD0<br /> |<br /> |-<br /> |HYN_REG_GESTURE_OUTPUT_ADDRESS<br /> |0xD3<br /> |<br /> |-<br /> |HYN_REG_ESD_SATURATE 0xED<br /> |0xED<br /> |<br /> |}<br /> <br /> '''WARNING : ''' &lt;del&gt;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!&lt;/del&gt;<br /> <br /> <br /> ===Accelerometer===<br /> The on board accelerometer is Bosch BMA421, connected to the I2C bus.<br /> <br /> ==== Pins ====<br /> <br /> * P0.06 : I²C SDA<br /> * P0.07 : I²C SCL<br /> * P0.08 : Interrupt<br /> <br /> I2C Device address : 0x18<br /> <br /> <br /> == Datasheets and Schematics ==<br /> <br /> === Schematics ===<br /> * [https://files.pine64.org/doc/PineTime/PineTime%20Schematic-V1.0a-20191103.pdf PineTime Schematic ver1.0a]<br /> * [https://files.pine64.org/doc/PineTime/PineTime%20Port%20Assignment%20rev1.0.pdf PineTime GPIO Port Assignment ver1.0]<br /> <br /> 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.<br /> <br /> === Chip Datasheets ===<br /> * NORDIC nRF52832 information:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/nRF52832%20product%20brief.pdf nRF52832 Product Brief]<br /> ** [https://infocenter.nordicsemi.com/pdf/nRF52832_PS_v1.1.pdf nRF52832 Product Specification v1.1]<br /> * ARMv7-M information:<br /> ** [https://static.docs.arm.com/ddi0403/eb/DDI0403E_B_armv7m_arm.pdf ARMv7-M Architecture Reference Manual]<br /> <br /> === Component Datasheets ===<br /> * PMU (Power Management Unit) information:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/SGM40561.pdf SGMicro SGM40561 Single Cell Charger Datasheet]<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/SGMICRO-SGM2036.pdf SGMicro SGM2036 3.3V Low Power Low Dropout RF Linear Regulator Datasheet]<br /> * SPI Flash information:<br /> ** [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])<br /> ** [https://datasheet.lcsc.com/szlcsc/2005251035_XTX-XT25F32BSOIGU-S_C558851.pdf XTX XT25F32B]<br /> ** IDs for XT25F32B are: manufacturer (0x0b), device (0x15), memory type (0x40), density (0x16)<br /> * LCD Panel:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/PineTime%20LCD%20Panel.jpg 1.3&quot; 240x240 IPS LCD Panel Specification for PineTime]<br /> ** [https://wiki.pine64.org/images/5/54/ST7789V_v1.6.pdf 11.6&quot; Sitronix LCD Driver/Controller Datasheet]<br /> * Touchpad information:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/PineTime%20Touch%20Panel.jpg Touchpad Specification for PineTimel]<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/CST816S数据手册V1.1.pdf 11.6&quot; Hynitron CST816S Capacitive Touch Controller Datasheet in Chinese]<br /> ** [https://wiki.pine64.org/images/2/2f/CST816S.zip Touch Controller Datasheet en]<br /> * Sensor:<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/BST-BMA421-FL000.pdf BOSCH BMA421 Triaxial VAcceleration Sensor Product Brief]<br /> ** [https://wiki.pine64.org/images/c/cc/Bst-bma400-ds000.pdf BOSCH BMA400 3-axes ultra-low power accelerometer datasheet]<br /> ** [https://files.pine64.org/doc/datasheet/pinetime/HRS3300%20Heart%20Rate%20Sensor.pdf TianYiHeXin HRS3300 PPG Heart Rate Sensor Data Sheet]<br /> <br /> <br /> == Community case design ==<br /> <br /> * [https://www.thingiverse.com/thing:4172849 PineTime Smart Watch case by dara0s at thingiverse]<br /> * [https://www.thingiverse.com/thing:4651462 PineTime dev kit back fix by joaquimorg at thingiverse]<br /> * [https://www.thingiverse.com/thing:4763267 PineTime dev kit charging holder v4 by zevix81 at thingiverse]<br /> <br /> [[Category:PineTime]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_Equivalents&diff=10002 2021-04-22T19:02:11Z

<p>Avamander: </p> <hr /> <div>This page contains a list of PineTime hardware equivalents or very close clones. Primarily to keep track of which devices could possibly be &quot;jailbroken&quot; and run PineTime firmware.<br /> <br /> ''Please add devices that use the same chipset to this list.''<br /> <br /> ==== Kalakate ====<br /> <br /> Seems to be PineTime hardware, interesting GUI, seems DaFit-y<br /> <br /> * https://www.youtube.com/watch?v=1VdMxbOYxgA<br /> <br /> <br /> ==== Colmi P8 ====<br /> <br /> A few firmware already support both the P8 and PineTime, the physical differences are minor - only a few MCU pins are mapped differently. There are a few open issues on InfiniTime's GitHub page to add support for this device.<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_Equivalents&diff=10001 2021-04-22T19:02:04Z

<p>Avamander: </p> <hr /> <div>This page contains a list of PineTime hardware equivalents or very close clones. Primarily to keep track of which devices could possibly be &quot;jailbroken&quot; and run PineTime firmware.<br /> <br /> Please add devices that use the same chipset to this list.<br /> <br /> ==== Kalakate ====<br /> <br /> Seems to be PineTime hardware, interesting GUI, seems DaFit-y<br /> <br /> * https://www.youtube.com/watch?v=1VdMxbOYxgA<br /> <br /> <br /> ==== Colmi P8 ====<br /> <br /> A few firmware already support both the P8 and PineTime, the physical differences are minor - only a few MCU pins are mapped differently. There are a few open issues on InfiniTime's GitHub page to add support for this device.<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_FAQ&diff=10000 2021-04-22T19:01:06Z

<p>Avamander: </p> <hr /> <div>=== Does PineTime run Linux? ===<br /> <br /> No. [https://forum.pine64.org/showthread.php?tid=8112 Please read this forum article] for information about Linux on PineTime. Also check out the article [https://lupyuen.github.io/pinetime-rust-mynewt/articles/pinetime &quot;PineTime doesn't run Linux... But that's OK!&quot;]<br /> <br /> === Why are there two versions of the PineTime in the store? ===<br /> <br /> See the below question and answer.<br /> <br /> === Why can I only buy the closed version in a 3-pack, and the open version per one? ===<br /> <br /> TL:DR: The unsealed PineTime is for development, the sealed one is for production use, because of firmware uploads. That is also why they were initially sold three in a pack.<br /> <br /> In the current situation in development there are some reasons to want to be sure you only experiment with an open device. If you install the wrong firmware, your device could be bricked, until you find a way to open it, which will likely damage the device.<br /> The idea is that if you want to develop an application for the PineTime, you will be testing it out first, and only after you know for sure your new firmware is well tested, you will install it on sealed devices. If you are in the beta stage, having more than one PineTime is probably a good idea. So to prevent people from locking themselves out at the first test, it was decided to sell the closed version only as a pack of 3. Development can be done on an open device, so any issues can be easily handled.<br /> <br /> === How long does it take to ship my PineTime? ===<br /> <br /> That depends on whether you chose for Standard or Express shipping. Standard shipping for the dev kit may take up to a few weeks.<br /> <br /> === How do I install new software on PineTime? ===<br /> <br /> If you have a Sealed PineTime, flash only tested PineTime Firmware to your PineTime. If you flash unknown PineTime Firmware, your sealed PineTime may be bricked relatively permanently.<br /> <br /> There is a lot of different software for flashing. Check out [[PineTime Development]] page for a list of companion software.<br /> <br /> Also see [[Reprogramming_the_PineTime|this page to see various methods of reprogramming the devkit PineTime the wired way]].<br /> <br /> Remember to validate the firmware after flashing: Swipe up to show the menu, tap the checkmark icon, tap &quot;Validate&quot;.<br /> <br /> === My PineTime arrived, now what? ===<br /> <br /> You should start by testing out all the features of the watch, to make sure everything works. Power it on and check the display.<br /> <br /> PineTime is shipped with InfiniTime firmware. Press the watch button to show the clock, then swipe up on the touchscreen to reveal the menu.<br /> <br /> You probably now wish to update the bootloader and firmware.<br /> <br /> === What's the OS that's preinstalled on the PineTime by default? ===<br /> <br /> PineTime ships with the open source [https://github.com/JF002/InfiniTime InfiniTime firmware].<br /> <br /> To support firmware update and rollback, PineTime includes the open source [https://lupyuen.github.io/pinetime-rust-mynewt/articles/mcuboot MCUBoot Bootloader].<br /> <br /> === Can we use this OS or its source code? ===<br /> <br /> Yes, [https://github.com/JF002/InfiniTime InfiniTime] and the [https://lupyuen.github.io/pinetime-rust-mynewt/articles/mcuboot MCUBoot Bootloader] are open source.<br /> <br /> === Why is the back exposed? Is it supposed to snap on? ===<br /> <br /> The back cover of the PineTime devkit is exposed so that you can flash and debug the device with the SWD pins. The main unit and cover does not snap (lock) together. If you want to attach the back cover anyway, you can use glue or tape.<br /> <br /> === What hardware should I use to flash code to the PineTime? ===<br /> <br /> There are several ways you can do this, check out [[Reprogramming the PineTime]]<br /> <br /> === How do I connect the PineTime to a programmer? ===<br /> <br /> Here's how: [[PineTime devkit wiring]]<br /> <br /> === How do I set the time on PineTime? ===<br /> <br /> You can use either nRF Connect, custom GadgetBridge build or the proprietary Da Fit app. See [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#set-pinetime-date-and-time-with-nrf-connect &quot;Set PineTime Date and Time with nRF Connect&quot;]<br /> <br /> You can also set the time using your PinePhone or other Linux-based Bluetooth LE capable device with the Bluez software installed. Install the bluez package and make sure your PineTime is running and awake with InfiniTime 0.7.1 or later.<br /> <br /> $ bluetoothctl<br /> [ bluetooth ]# scan on<br /> ...<br /> [NEW] Device D7:03:FB:6E:31:B2 Pinetime-JF<br /> ...<br /> [bluetooth]# pair D7:03:FB:6E:31:B2<br /> Attempting to pair with D7:03:FB:6E:31:B2<br /> ...<br /> [NEW] Characteristic (Handle 0xfd80)<br /> /org/bluez/hci0/dev_D7_03_FB_6E_31_B2/service0015/char0016<br /> 00002a2b-0000-1000-8000-00805f9b34fb<br /> Current Time<br /> ...<br /> [Pinetime-JF]# menu gatt<br /> ...<br /> [Pinetime-JF]# select-attribute /org/bluez/hci0/dev_D7_03_FB_6E_31_B2/service0015/char0016<br /> [Pinetime-JF:/service0015/char0016]# read<br /> Attempting to read /org/bluez/hci0/dev_D7_03_FB_6E_31_B2/service0015/char0016<br /> [CHG] Attribute /org/bluez/hci0/dev_D7_03_FB_6E_31_B2/service0015/char0016 Value:<br /> b2 07 01 01 00 04 15 00 00 ......... <br /> b2 07 01 01 00 04 15 00 00 .........<br /> [Pinetime-JF:/service0015/char0016]# write &quot;0xe4 0x07 0x0c 0x1f 0x0e 0x02 0x00 0x00 0x00&quot;<br /> <br /> This is the format for the current time as hex bytes:<br /> &lt;lsb of year&gt; &lt;msb of year&gt; &lt;month (1-12)&gt; &lt;day (1-31)&gt; &lt;hour (0-23)&gt; &lt;minute (0-59)&gt; &lt;seconds (0-59)&gt; &lt;weekday (1-7 where 1=Monday)&gt; &lt;fractions (1/256th of second)&gt;<br /> <br /> === Is there a standard agreed method of pushing OTA updates so that one could seal the PineTime dev kit nicely? ===<br /> <br /> InfiniTime supports firmware updates over Bluetooth LE with the nRF Connect mobile app. See [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#download-and-test-our-pinetime-firmware &quot;Download and Test Our PineTime Firmware&quot;]<br /> <br /> === My PineTime's screen shows garbage, how do I fix it? ===<br /> <br /> This is usually caused by unplugging the device after it has booted, it needs to be reinitialised. To do so just restart the watch by removing power to it.<br /> <br /> === I have experience developing on Arduino. How does the PineTime compare? ===<br /> <br /> To learn programming on PineTime, [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud check out this article]<br /> <br /> Arduino provides the Arduino IDE (or you use the avr-gcc and avrdude command-line tools) which you can use to compile and upload code to an Arduino board. The PineTime and its ARM processor doesn't have this, so you'll have to familiarize yourself with tools like GCC for ARM, and OpenOCD. Some experience with Arduino does translate over to the PineTime, especially if you've worked with LCD's, or SPI. The PineTime is at least four times faster than an Arduino Uno (even faster at certain specific workloads due to hardware acceleration), and it has 32 times more RAM and 16 times more flash storage.<br /> <br /> [https://github.com/lupyuen/ Lup Yuen Lee] (just call him Lup, rhymes with &quot;Up&quot;) has written many articles on PineTime programming. [https://lupyuen.github.io/ Check out the articles here]<br /> <br /> === Can I code firmware for PineTime without an actual PineTime? ===<br /> <br /> Yes, you may code PineTime Watch Faces and preview them in a web browser (thanks to WebAssembly)...<br /> <br /> [https://lupyuen.github.io/pinetime-rust-mynewt/articles/simulator PineTime Simulator]<br /> <br /> Then flash your firmware remotely to a real PineTime via Telegram, and watch your firmware run in a live video stream...<br /> <br /> [https://github.com/lupyuen/remote-pinetime-bot/blob/master/README.md Remote PineTime]<br /> <br /> === What do I need for building PineTime firmware locally on my computer? ===<br /> <br /> Most flavours of PineTime firmware (InfiniTime, Hypnos, Klok, wasp-os) will build fine on Linux (x64, Arm32, Arm64) and macOS. Just follow the instructions provided.<br /> <br /> Download version 9-2020-q2-update of the [https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads Arm Embedded Toolchain arm-none-eabi-gcc]. Other versions of gcc may have problems building the firmware correctly.<br /> <br /> On Windows, install [https://docs.microsoft.com/en-us/windows/wsl/about Windows Subsystem for Linux (WSL)] and execute the build steps inside the WSL Terminal (instead of the Windows Command Prompt). USB Programmers (like ST-Link and JLink) are not supported in WSL, so use the Windows Command Prompt to flash your built firmware to PineTime.<br /> <br /> [https://github.com/lupyuen/pinetime-rust-mynewt/blob/master/README.md pinetime-rust-mynewt] firmware for PineTime supports building and flashing via the Windows Command Prompt (no need for MinGW and Docker).<br /> <br /> === Can I use Pinebook Pro for developing PineTime? ===<br /> <br /> Yes, use version 9-2020-q2-update of the [https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads Arm Embedded Toolchain arm-none-eabi-gcc]. Other versions of gcc may have problems building the firmware correctly.<br /> <br /> === What is ARM Semihosting? ===<br /> <br /> We use the SWD (Single Wire Debug) protocol created by ARM for flashing and debugging PineTime's nRF52832 microcontroller, which contains an ARM CPU. (SWD is derived from standard JTAG, but with fewer wires) With ARM CPUs you can trigger a software breakpoint, and allow the debugger (OpenOCD) to do something really nifty: Display a message, read console input, dump out a file, even read a file. That's called ARM Semihosting. [http://www.keil.com/support/man/docs/armcc/armcc_pge1358787046598.htm More about ARM Semihosting]<br /> <br /> === What is OpenOCD? ===<br /> <br /> OpenOCD is Open On-Chip Debugger. It's the software that drives your microcontroller debugger/flasher. We need it for running any kind of flashing and debugging with Pi or ST-Link. gdb talks to OpenOCD for debugging firmware. gdb also works with VSCode for debugging firmware visually. [http://openocd.org/doc-release/html/About.html#What-is-OpenOCD_003f More about OpenOCD]<br /> <br /> Please use [https://xpack.github.io/openocd xPack OpenOCD] with PineTime. Other versions of OpenOCD seem to have problems with PineTime.<br /> <br /> === How do I remove flash protection? ===<br /> <br /> PineTime watches shipped before 20 Sep 2020 have flash protection enabled.<br /> <br /> The flash protection can be removed using multiple different methods. If you don't have anything except the PineTime, not even a Raspberry Pi, then you have to order a programmer online: you can use a J-Link, CMSIS-DAP dongle and various other programmers. See [[Reprogramming_the_PineTime|this page to see various methods of reprogramming the PineTime]].<br /> <br /> If your PineTime was shipped after 20 Sep 2020, you don't need to remove flash protection. They are shipped with flash protection disabled. You can flash and debug PineTime right away with ST-Link, JLink and Raspberry Pi.<br /> <br /> === Why can't you use ST-Link to remove nRF52 Flash Protection? ===<br /> <br /> Because ST-Link is a High Level Adapter. It doesn't really implement all SWD functions, just a subset (probably to keep the price low). More details in the section &quot;Why Visual Studio Code with ST-Link (instead of nRFgo Studio with J-LINK)&quot; in the article [https://medium.com/@ly.lee/coding-nrf52-with-rust-and-apache-mynewt-on-visual-studio-code-9521bcba6004?source=friends_link&amp;sk=bb4e2523b922d0870259ab3fa696c7da &quot;Coding nRF52 with Rust and Apache Mynewt on Visual Studio Code&quot;].<br /> <br /> === Since we need a low level SWD adapter like Raspberry Pi anyway, can we do everything on a Pi instead of ST-Link + Windows? ===<br /> <br /> Yes, Raspberry Pi works for flashing and debugging PineTime, even for removing flash protection. We have a special version of OpenOCD called OpenOCD SPI that talks to PineTime's SWD port over SPI (without bit-banging). See [https://github.com/lupyuen/pinetime-updater/blob/master/README.md PineTime Updater]<br /> <br /> === Is there a 3D model of PineTime available somewhere? ===<br /> <br /> Not yet. Someone did design a cover you can snap on to keep the back shut. [https://www.thingiverse.com/thing:4172849 More details]<br /> <br /> === Are there any alternatives to the wrist band provided with the PineTime? ===<br /> <br /> No, but PineTime accepts standard 20mm wrist band that is widely available by a third party.<br /> <br /> Note that some sellers have a different point of view on what standard is. So you should always check the fitting to make sure it looks like the one used by PineTime.<br /> <br /> === I'm stuck. How can I get help? ===<br /> <br /> Chat with the PineTime Community on [[PineTime#Community|Matrix / Discord / Telegram / IRC]] (They are bridged into a single chatroom)<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_FAQ&diff=9999 2021-04-22T18:58:01Z

<p>Avamander: </p> <hr /> <div>=== Does PineTime run Linux? ===<br /> <br /> No. [https://forum.pine64.org/showthread.php?tid=8112 Please read this forum article] for information about Linux on PineTime. Also check out the article [https://lupyuen.github.io/pinetime-rust-mynewt/articles/pinetime &quot;PineTime doesn't run Linux... But that's OK!&quot;]<br /> <br /> === Why are there two versions of the PineTime in the store? ===<br /> <br /> See the below question and answer.<br /> <br /> === Why can I only buy the closed version in a 3-pack, and the open version per one? ===<br /> <br /> TL:DR: The unsealed PineTime is for development, the sealed one is for production use, because of firmware uploads. That is also why they were initially sold three in a pack.<br /> <br /> In the current situation in development there are some reasons to want to be sure you only experiment with an open device. If you install the wrong firmware, your device could be bricked, until you find a way to open it, which will likely damage the device.<br /> The idea is that if you want to develop an application for the PineTime, you will be testing it out first, and only after you know for sure your new firmware is well tested, you will install it on sealed devices. If you are in the beta stage, having more than one PineTime is probably a good idea. So to prevent people from locking themselves out at the first test, it was decided to sell the closed version only as a pack of 3. Development can be done on an open device, so any issues can be easily handled.<br /> <br /> === How long does it take to ship my PineTime? ===<br /> <br /> That depends on whether you chose for Standard or Express shipping. Standard shipping for the dev kit may take up to a few weeks.<br /> <br /> === How do I install new software on PineTime? ===<br /> <br /> The nRF Connect mobile app (Android and iOS) may also be used to update the firmware on your PineTime. See [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#download-and-test-our-pinetime-firmware &quot;Download and Test Our PineTime Firmware&quot;]<br /> <br /> Also see [[Reprogramming_the_PineTime|this page to see various methods of reprogramming the devkit PineTime the wired way]].<br /> <br /> If you have a Sealed PineTime, flash only Certified PineTime Firmware to your PineTime. If you flash non-Certified PineTime Firmware, your Sealed PineTime may be bricked permanently.<br /> <br /> The only Certified PineTime Firmware available today is [https://github.com/JF002/InfiniTime/releases/tag/0.14.0 InfiniTime 0.14.0]. Download the file &quot;dfu-0.14.0.zip&quot; under &quot;Assets&quot; and flash to PineTime with nRF Connect. Refer to the instructions here: [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#download-and-test-our-pinetime-firmware &quot;Download and Test Our PineTime Firmware&quot;]<br /> <br /> Remember to validate the firmware after flashing: Swipe up to show the menu, tap the Ticks icon, tap &quot;Validate&quot;<br /> <br /> === My PineTime arrived, now what? ===<br /> <br /> You should start by testing out all the features of the watch, to make sure everything works. Power it on and check the display.<br /> <br /> PineTime is shipped with InfiniTime firmware. Press the watch button to show the clock, then swipe up on the touchscreen to reveal the menu.<br /> <br /> On your Android phone, install the nRF Connect mobile app to sync the date and time with PineTime. See [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#set-pinetime-date-and-time-with-nrf-connect &quot;Set PineTime Date and Time with nRF Connect&quot;] (nRF Connect on iOS can't be used for setting the date and time, because it doesn't implement the GATT Time Service)<br /> <br /> Download the latest Certified PineTime Firmware (see the previous question) and flash to PineTime with nRF Connect. Refer to the instructions here: [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#download-and-test-our-pinetime-firmware &quot;Download and Test Our PineTime Firmware&quot;]<br /> <br /> Remember to validate the firmware after flashing: Swipe up to show the menu, tap the Ticks icon, tap &quot;Validate&quot;<br /> <br /> === What's the OS that's preinstalled on the PineTime by default? ===<br /> <br /> PineTime ships with the open source [https://github.com/JF002/InfiniTime InfiniTime firmware].<br /> <br /> To support firmware update and rollback, PineTime includes the open source [https://lupyuen.github.io/pinetime-rust-mynewt/articles/mcuboot MCUBoot Bootloader].<br /> <br /> === Can we use this OS or its source code? ===<br /> <br /> Yes, [https://github.com/JF002/InfiniTime InfiniTime] and the [https://lupyuen.github.io/pinetime-rust-mynewt/articles/mcuboot MCUBoot Bootloader] are open source.<br /> <br /> === Why is the back exposed? Is it supposed to snap on? ===<br /> <br /> The back cover of the PineTime dev kit is exposed so that you can flash and debug the device with the SWD pins. The main unit and cover does not snap (lock) together. If you want to attach the back cover anyway, you can use glue or tape.<br /> <br /> === What hardware should I use to flash code to the PineTime? ===<br /> <br /> There are several ways you can do this, check out [[Reprogramming the PineTime]]<br /> <br /> === How do I connect the PineTime to a programmer? ===<br /> <br /> Here's how: [[PineTime devkit wiring]]<br /> <br /> === How do I set the time on PineTime? ===<br /> <br /> You can use either nRF Connect, custom GadgetBridge build or the proprietary Da Fit app. See [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#set-pinetime-date-and-time-with-nrf-connect &quot;Set PineTime Date and Time with nRF Connect&quot;]<br /> <br /> You can also set the time using your PinePhone or other Linux-based Bluetooth LE capable device with the Bluez software installed. Install the bluez package and make sure your PineTime is running and awake with InfiniTime 0.7.1 or later.<br /> <br /> $ bluetoothctl<br /> [ bluetooth ]# scan on<br /> ...<br /> [NEW] Device D7:03:FB:6E:31:B2 Pinetime-JF<br /> ...<br /> [bluetooth]# pair D7:03:FB:6E:31:B2<br /> Attempting to pair with D7:03:FB:6E:31:B2<br /> ...<br /> [NEW] Characteristic (Handle 0xfd80)<br /> /org/bluez/hci0/dev_D7_03_FB_6E_31_B2/service0015/char0016<br /> 00002a2b-0000-1000-8000-00805f9b34fb<br /> Current Time<br /> ...<br /> [Pinetime-JF]# menu gatt<br /> ...<br /> [Pinetime-JF]# select-attribute /org/bluez/hci0/dev_D7_03_FB_6E_31_B2/service0015/char0016<br /> [Pinetime-JF:/service0015/char0016]# read<br /> Attempting to read /org/bluez/hci0/dev_D7_03_FB_6E_31_B2/service0015/char0016<br /> [CHG] Attribute /org/bluez/hci0/dev_D7_03_FB_6E_31_B2/service0015/char0016 Value:<br /> b2 07 01 01 00 04 15 00 00 ......... <br /> b2 07 01 01 00 04 15 00 00 .........<br /> [Pinetime-JF:/service0015/char0016]# write &quot;0xe4 0x07 0x0c 0x1f 0x0e 0x02 0x00 0x00 0x00&quot;<br /> <br /> This is the format for the current time as hex bytes:<br /> &lt;lsb of year&gt; &lt;msb of year&gt; &lt;month (1-12)&gt; &lt;day (1-31)&gt; &lt;hour (0-23)&gt; &lt;minute (0-59)&gt; &lt;seconds (0-59)&gt; &lt;weekday (1-7 where 1=Monday)&gt; &lt;fractions (1/256th of second)&gt;<br /> <br /> === Is there a standard agreed method of pushing OTA updates so that one could seal the PineTime dev kit nicely? ===<br /> <br /> InfiniTime supports firmware updates over Bluetooth LE with the nRF Connect mobile app. See [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#download-and-test-our-pinetime-firmware &quot;Download and Test Our PineTime Firmware&quot;]<br /> <br /> === My PineTime's screen shows garbage, how do I fix it? ===<br /> <br /> This is usually caused by unplugging the device after it has booted, it needs to be reinitialised. To do so just restart the watch by removing power to it.<br /> <br /> === I have experience developing on Arduino. How does the PineTime compare? ===<br /> <br /> To learn programming on PineTime, [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud check out this article]<br /> <br /> Arduino provides the Arduino IDE (or you use the avr-gcc and avrdude command-line tools) which you can use to compile and upload code to an Arduino board. The PineTime and its ARM processor doesn't have this, so you'll have to familiarize yourself with tools like GCC for ARM, and OpenOCD. Some experience with Arduino does translate over to the PineTime, especially if you've worked with LCD's, or SPI. The PineTime is at least four times faster than an Arduino Uno (even faster at certain specific workloads due to hardware acceleration), and it has 32 times more RAM and 16 times more flash storage.<br /> <br /> [https://github.com/lupyuen/ Lup Yuen Lee] (just call him Lup, rhymes with &quot;Up&quot;) has written many articles on PineTime programming. [https://lupyuen.github.io/ Check out the articles here]<br /> <br /> === Can I code firmware for PineTime without an actual PineTime? ===<br /> <br /> Yes, you may code PineTime Watch Faces and preview them in a web browser (thanks to WebAssembly)...<br /> <br /> [https://lupyuen.github.io/pinetime-rust-mynewt/articles/simulator PineTime Simulator]<br /> <br /> Then flash your firmware remotely to a real PineTime via Telegram, and watch your firmware run in a live video stream...<br /> <br /> [https://github.com/lupyuen/remote-pinetime-bot/blob/master/README.md Remote PineTime]<br /> <br /> === What do I need for building PineTime firmware locally on my computer? ===<br /> <br /> Most flavours of PineTime firmware (InfiniTime, Hypnos, Klok, wasp-os) will build fine on Linux (x64, Arm32, Arm64) and macOS. Just follow the instructions provided.<br /> <br /> Download version 9-2020-q2-update of the [https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads Arm Embedded Toolchain arm-none-eabi-gcc]. Other versions of gcc may have problems building the firmware correctly.<br /> <br /> On Windows, install [https://docs.microsoft.com/en-us/windows/wsl/about Windows Subsystem for Linux (WSL)] and execute the build steps inside the WSL Terminal (instead of the Windows Command Prompt). USB Programmers (like ST-Link and JLink) are not supported in WSL, so use the Windows Command Prompt to flash your built firmware to PineTime.<br /> <br /> [https://github.com/lupyuen/pinetime-rust-mynewt/blob/master/README.md pinetime-rust-mynewt] firmware for PineTime supports building and flashing via the Windows Command Prompt (no need for MinGW and Docker).<br /> <br /> === Can I use Pinebook Pro for developing PineTime? ===<br /> <br /> Yes, use version 9-2020-q2-update of the [https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads Arm Embedded Toolchain arm-none-eabi-gcc]. Other versions of gcc may have problems building the firmware correctly.<br /> <br /> === What is ARM Semihosting? ===<br /> <br /> We use the SWD (Single Wire Debug) protocol created by ARM for flashing and debugging PineTime's nRF52832 microcontroller, which contains an ARM CPU. (SWD is derived from standard JTAG, but with fewer wires) With ARM CPUs you can trigger a software breakpoint, and allow the debugger (OpenOCD) to do something really nifty: Display a message, read console input, dump out a file, even read a file. That's called ARM Semihosting. [http://www.keil.com/support/man/docs/armcc/armcc_pge1358787046598.htm More about ARM Semihosting]<br /> <br /> === What is OpenOCD? ===<br /> <br /> OpenOCD is Open On-Chip Debugger. It's the software that drives your microcontroller debugger/flasher. We need it for running any kind of flashing and debugging with Pi or ST-Link. gdb talks to OpenOCD for debugging firmware. gdb also works with VSCode for debugging firmware visually. [http://openocd.org/doc-release/html/About.html#What-is-OpenOCD_003f More about OpenOCD]<br /> <br /> Please use [https://xpack.github.io/openocd xPack OpenOCD] with PineTime. Other versions of OpenOCD seem to have problems with PineTime.<br /> <br /> === How do I remove flash protection? ===<br /> <br /> PineTime watches shipped before 20 Sep 2020 have flash protection enabled.<br /> <br /> The flash protection can be removed using multiple different methods. If you don't have anything except the PineTime, not even a Raspberry Pi, then you have to order a programmer online: you can use a J-Link, CMSIS-DAP dongle and various other programmers. See [[Reprogramming_the_PineTime|this page to see various methods of reprogramming the PineTime]].<br /> <br /> If your PineTime was shipped after 20 Sep 2020, you don't need to remove flash protection. They are shipped with flash protection disabled. You can flash and debug PineTime right away with ST-Link, JLink and Raspberry Pi.<br /> <br /> === Why can't you use ST-Link to remove nRF52 Flash Protection? ===<br /> <br /> Because ST-Link is a High Level Adapter. It doesn't really implement all SWD functions, just a subset (probably to keep the price low). More details in the section &quot;Why Visual Studio Code with ST-Link (instead of nRFgo Studio with J-LINK)&quot; in the article [https://medium.com/@ly.lee/coding-nrf52-with-rust-and-apache-mynewt-on-visual-studio-code-9521bcba6004?source=friends_link&amp;sk=bb4e2523b922d0870259ab3fa696c7da &quot;Coding nRF52 with Rust and Apache Mynewt on Visual Studio Code&quot;].<br /> <br /> === Since we need a low level SWD adapter like Raspberry Pi anyway, can we do everything on a Pi instead of ST-Link + Windows? ===<br /> <br /> Yes, Raspberry Pi works for flashing and debugging PineTime, even for removing flash protection. We have a special version of OpenOCD called OpenOCD SPI that talks to PineTime's SWD port over SPI (without bit-banging). See [https://github.com/lupyuen/pinetime-updater/blob/master/README.md PineTime Updater]<br /> <br /> === Is there a 3D model of PineTime available somewhere? ===<br /> <br /> Not yet. Someone did design a cover you can snap on to keep the back shut. [https://www.thingiverse.com/thing:4172849 More details]<br /> <br /> === Are there any alternatives to the wrist band provided with the PineTime? ===<br /> <br /> No, but PineTime accepts standard 20mm wrist band that is widely available by a third party.<br /> <br /> Note that some sellers have a different point of view on what standard is. So you should always check the fitting to make sure it looks like the one used by PineTime.<br /> <br /> === I'm stuck. How can I get help? ===<br /> <br /> Chat with the PineTime Community on [[PineTime#Community|Matrix / Discord / Telegram / IRC]] (They are bridged into a single chatroom)<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=InfiniTime&diff=9998 2021-04-22T18:55:43Z

<p>Avamander: </p> <hr /> <div>== InfiniTime ==<br /> InfiniTime (also known as JF's project, FreeRTOS firmware or Pinetime-JF) is an open source (GPLv3) firmware written in C++ and based on FreeRTOS, LVGL and NimBLE. This firmware (version 0.7.1) is preloaded at the factory since the new batch of PineTime devkits and sealed PineTimes of end of September 2020. '''This page contains general information about the project. Actual project documentation and nuances are documented in the repository'''<br /> <br /> * GitHub repo : https://github.com/JF002/InfiniTime<br /> * Official website : https://infinitime.io/<br /> <br /> == Read this first! ==<br /> * InfiniTime and the bootloader are still in heavy development, and some features might not work as expected. Any issues should be reported on GitHub.<br /> * Do not use a sealed PineTime as a development device, there is a fair amount of chances that you'll brick it with very experimental firmware.<br /> * OTA is relatively stable, but when you're on an outdated bootloader version it can freeze which will require you to wait for the battery to run out.<br /> <br /> == Known issues ==<br /> {{warning|1=Please read this section carefully before upgrading the firmware on your PineTime, especially if you are using a sealed device!}}<br /> === Black screen after a reset in sleep mode ===<br /> ==== Description ====<br /> This issue occurs if you are using the original bootloader (from InfiniTime 0.7.1), upgraded from InfiniTime 0.7.1 to 0.8.2 and the watch resets while the display is OFF : the watch is stuck on a black screen and does not respond to touch, button press or BLE.<br /> <br /> The reset can be triggered by the watchdog or manually by long pressing the button. If that doesn't work, wait for the battery to run out, it'll reboot then.<br /> <br /> This issue is caused by InfiniTime 0.8.2 that put the external SPI flash memory to sleep before switching the display off and by the bootloader that cannot wake the memory chip up. The bootloader is stuck in an infinite loop.<br /> <br /> More info : https://github.com/lupyuen/pinetime-rust-mynewt/issues/24 and https://github.com/JF002/InfiniTime/issues/60<br /> <br /> ==== Workaround ====<br /> On a development kit, a simple reset via SWD is needed to unlock the bootloader.<br /> <br /> On a sealed device, the only way to work around this issue is to wait for the battery to drain completely before trying again.<br /> <br /> This issue can be avoided by ensuring that the display is ON when manually resetting the device (long push on the button).<br /> <br /> ==== Fixed version ====<br /> This issues is fixed in [https://github.com/JF002/InfiniTime/releases/tag/0.8.3 InfiniTime 0.8.3]<br /> <br /> == Releases == <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.7.1 Version 0.7.1] ===<br /> This is the version that ships with PineTime devkits and sealed PineTime as of September 2020.<br /> * Time synchronization over BLE<br /> * Display brightness setting<br /> * Notifications over BLE<br /> * Integration with AmazFish (SailFishOS) and Gadgetbridge (Android)<br /> * OTA using NRFConnect<br /> <br /> Bootloader : https://github.com/lupyuen/pinetime-rust-mynewt/releases/tag/v4.1.7<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.8.2 Version 0.8.2] ===<br /> * Music control app<br /> * Paint app<br /> * Manual image validation after OTA<br /> <br /> Bootloader : https://github.com/lupyuen/pinetime-rust-mynewt/releases/tag/v5.0.4.<br /> <br /> This new version of the bootloader fixes [[#Black_screen_after_a_reset_in_sleep_mode]] and enables the watchdog before launching the firmware.<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.8.3 Version 0.8.3] ===<br /> * Fixes the &quot;bootloader stuck after a reset&quot; mentioned in 0.8.2 above<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.9.0 Version 0.9.0] ===<br /> * Touch panel fixed (no more freezing)<br /> * Improved music application (possibility to control both volumes and browsing, display the song progression)<br /> * Notification UI rewritten: can now display up to 100 characters<br /> * Improved BLE connectivity<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.10.0 Version 0.10.0] ===<br /> * 2 new games: Pong and 2048<br /> * Fixed display glitches and improved needed time to turn on the display<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.11.0 Version 0.11.0] ===<br /> * Heart-rate sensor application:<br /> * Displays the current value, and when running, this value is also displayed on the clock face<br /> * Value exposed over BLE, meaning other applications can read it (e.g. companion app such as Amazfish)<br /> * Navigation app: InfiNav - works e.g. with PureMaps on SailfishOS<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.12.0 Version 0.12.0] ===<br /> * Improved BLE connection<br /> * OTA updates much more reliable<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.13.0 Version 0.13.0] ===<br /> * Vibration<br /> * Call notification: it is possible to accept/ignore/reject a call from the PineTime<br /> * Music app got nicer icons<br /> * BLE connectivity improved a bit more<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.14.0 Version 0.14.0] ===<br /> * LVGL 7<br /> * Bugfixes to the build process<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_Hardware_Wishlist&diff=9880 2021-04-17T14:24:12Z

<p>Avamander: </p> <hr /> <div>This page contains a list of things people wish PineTime did differently<br /> <br /> === Hardware ===<br /> <br /> * Long pressing the button should power-cycle the watch without any software being involved<br /> * Other display tech could be explored. [//en.Wikipedia.org/wiki/Transflective_liquid-crystal_display A transflective LCD] would probably be a nice option. Or potentially OLED?<br /> * Touchscreen should possibly have a configurable sensitivity level for both glove-wearing and droplet-resistance. Preferably it should still be a capacitive one, a resistive touchscreen would have too many trade-offs.<br /> * A slightly bigger 256×256 pixel graphics display size is preferable for its binary alignment, affording some low-level simplicity – it has the property that its X and Y coordinates are each addressable with a single byte, with no out-of-bounds; its total number of pixels is 65536 (another power of 2), and each pixel is addressable with exactly 2 bytes, with perfect efficiency. The [http://Pelulamu.net/ibniz IBNIZ (Ideally Bare Numeric Impression giZmo) virtual machine], designed for fun minimalist demoscene graphics, has chosen 256×256 for its virtual display, and makes use of these simplicity advantages. If PineTime also chose 256×256 then it would be a target platform for unclipped IBNIZ demoscene programmes, which would be really fun to play around with on one's wrist!<br /> * A full redraw on the display takes 120ms at the very least, which is 8Hz. A smooth scrolling/usage/animation experience would be 30Hz minimum, preferably 60. I heard a rumor that the SPI connection to the display is a bottleneck.<br /> * Some sort of scroll wheel would be nice for convenience.<br /> * Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)<br /> * Wireless charging, or Qi Charging capability<br /> * An external RTC circuit saving the current time to allow the main MCU go to deep-sleep.<br /> * nRF5340 update: QSPI, CryptoCell + Secure Key Storage, has more RAM, a coprocessor and the possibility to expose USB through power pins<br /> * Preferably a pre-certified MCU module with a ceramic antenna<br /> * Version without sensors but maybe bigger battery<br /> * A couple of pins on the programmer connector to allow UART while developing (currently there is a TX test point on PCB). (Note: There's ARM SemiHosting and Segger RTT)<br /> * Connect the pin of LCD controller that allows RD/WR from it in order to save RAM on the MCU.<br /> * LCD must be centered on case. Currently is not and watchfaces seems different when clock is put on the other wrist.<br /> * A NFC antenna around the case, connected to the NFC pins.<br /> * Used sensors should be NDA-free and preferably also blob-free. For example the BMA421 accelerometer doesn't have a datasheet (it seems private to some hardware integrators): a more open one would be much easier to develop for. Special attention should be paid to advanced features, such as step counting integration or flick detection.<br /> <br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineCube&diff=9612 2021-03-27T14:31:41Z

<p>Avamander: /* Specifications */</p> <hr /> <div>{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}<br /> <br /> <br /> <br /> == Specifications ==<br /> * '''Dimensions:''' 55mm x 51mm x 51.5mm<br /> * '''Weight:''' 55g<br /> * '''Storage:'''<br /> ** MicroSD slot, bootable<br /> ** 128Mb SPI Nor Flash, bootable<br /> * '''Cameras:''' OV5640, 5Mpx <br /> * '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz<br /> * '''RAM:''' 128MB DDR3<br /> * '''I/O:'''<br /> ** 10/100Mbps Ethernet with passive PoE (''4-18V!'')<br /> ** USB 2.0 A host<br /> ** 26 pins GPIO port<br /> *** 2x 3.3V Ouptut<br /> *** 2x 5V Output<br /> *** 1x I2C<br /> *** 2x UART<br /> *** 2x PWM<br /> *** 1x SPI<br /> *** 1x eMMC/SDIO/SD (8-bit)<br /> *** 6x Interrupts<br /> *** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''<br /> ** Internal microphone<br /> * '''Network:'''<br /> ** WiFi<br /> * '''Screen:''' optional 4.5&quot; RGB LCD screen<br /> * '''Misc. features:''' <br /> ** Volume and home buttons<br /> ** Speakers and Microphone<br /> * '''Power DC in:'''<br /> ** 5V 1A from MicroUSB Port or GPIO port<br /> ** 4V-18V from Ethernet passive PoE<br /> * '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]<br /> <br /> == PineCube board information, schematics and certifications ==<br /> * PineCube mainboard schematic:<br /> ** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]<br /> * PineCube faceboard schematic:<br /> ** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]<br /> * PineCube certifications:<br /> ** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]<br /> ** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]<br /> ** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]<br /> <br /> <br /> <br /> == Datasheets for components and peripherals ==<br /> * Allwinner (Sochip) S3 SoC information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]<br /> <br /> * X-Powers AXP209 PMU (Power Management Unit) information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]<br /> <br /> * CMOS camera module information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]<br /> ** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]<br /> <br /> * LCD touch screen panel information:<br /> <br /> * Lithium battery information:<br /> <br /> * WiFi/BT module information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]<br /> <br /> * GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML]) (Pin1 is marked on the board by a white dot on the PCB)<br /> [[File:PineCube_GPIO_Pinout.png|700px]]<br /> <br /> <br /> * Case information:<br /> ** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PinePhone 3D file]<br /> <br /> [[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]<br /> <br /> == Operating Systems ==<br /> <br /> === Mainlining Efforts ===<br /> <br /> Please note:<br /> <br /> * this list is most likely not complete<br /> * no review of functionality is done here, it only serves as a collection of efforts<br /> <br /> {| class=&quot;wikitable&quot;<br /> !colspan=&quot;3&quot;|Linux kernel<br /> |-<br /> | Type<br /> | Link<br /> | Available in version<br /> |-<br /> | Devicetree Entry Pinecube<br /> | https://lkml.org/lkml/2020/9/22/1241<br /> | 5.10<br /> |-<br /> | Correction for AXP209 driver<br /> | https://lkml.org/lkml/2020/9/22/1243<br /> | 5.9<br /> |-<br /> | Additional Fixes for AXP209 driver<br /> | https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/<br /> | tdb (5.11?)<br /> |-<br /> | Device Tree Fixes<br /> | https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/<br /> | 5.10<br /> |-<br /> !colspan=&quot;3&quot;|U-boot<br /> |-<br /> | Type<br /> | Link<br /> | Available in version<br /> |-<br /> | PineCube Board Support<br /> | https://patchwork.ozlabs.org/project/uboot/list/?series=210044<br /> | expected in v2021.01<br /> |-<br /> !colspan=&quot;3&quot;|Buildroot<br /> |-<br /> | No known mainlining efforts yet<br /> |<br /> |<br /> |}<br /> <br /> <br /> === NixOS ===<br /> <br /> * [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]<br /> <br /> <br /> <br /> === Buildroot ===<br /> [https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.<br /> <br /> This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.<br /> The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.<br /> This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.<br /> <br /> === Armbian ===<br /> <br /> The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.<br /> <br /> <br /> ==== Armbian Build Image with motion [microSD Boot] [20201222] ====<br /> * Armbian Ubuntu Focal build for the Pinecube with the motion (detection) package preinstalled.<br /> * There are 2 ways to interact with the OS:<br /> ** Scan for the the device IP (with hostname pinecube)<br /> ** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER to login to the serial console, then check for assigned IP<br /> * DD image (for 8GB micoSD card and above)<br /> ** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]<br /> *** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b<br /> *** File Size: 328MGB<br /> <br /> [https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 GitHub gist] for the userpatch which pre-installs and configures the motion (detection) package. <br /> <br /> Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.<br /> Although [https://www.armbian.com/download/?device_support=No+official+support+(CSC) not officially supported] it enables the usage of Debian and Ubuntu.<br /> <br /> A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian (login: root, password: 1234).<br /> <br /> Motion daemon can be enabled using systemctl (With root) &lt;code&gt;systemctl enable motion&lt;/code&gt;. Then just reboot.<br /> <br /> ==== Serial connection using screen and the woodpecker USB serial device ====<br /> <br /> First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.<br /> <br /> On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:<br /> <br /> &lt;code&gt;screen /dev/ttyUSB0 115200&lt;/code&gt;<br /> <br /> ==== Serial connection using screen and Arduino Uno ====<br /> <br /> You can use the Arduino Uno or other Arduino boards as a USB serial device.<br /> <br /> First you must either remove the microcontroller from it's socket, or if your Arduino board does not allow this, then you can use wires to jump RESET (RST) and GND to isolate the SOC.<br /> <br /> After this you can either use the Arduino IDE and it's Serial monitor after selecting your &lt;code&gt;/dev/ttyACMx&lt;/code&gt; Arduino device, or screen:<br /> <br /> &lt;code&gt;screen /dev/ttyACM0 115200&lt;/code&gt;<br /> <br /> [[File:ArduinoSerialPinecube.jpg|400px]]<br /> <br /> ==== Serial connection using pinephone/pinebook pro serial debugging cable ====<br /> <br /> You can use the [https://wiki.pine64.org/wiki/PinePhone#Serial_console serial console] USB cable for pinephone and pinebook pro at the [https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/ store]. With a [https://www.amazon.com/3-5mm-Stereo-Female-terminal-connector/dp/B077XPSKQD female terminal block] wire using breadboard wire into the GPIO block at the following locations in a &quot;null modem&quot; configuration with transmit and receive crossed between your computer and the pinecube:<br /> <br /> S - Ground (to pin 9)<br /> R - Transmit (to pin 8)<br /> T - Receive (to pin 10)<br /> <br /> From Linux you can access the console of the pinecube using the screen command:<br /> <br /> &lt;code&gt;screen /dev/ttyUSB0 115200&lt;/code&gt;<br /> <br /> ==== Basic bandwidth tests with iperf3 ====<br /> <br /> Install armbian-config:<br /> &lt;code&gt;apt install armbian-config&lt;/code&gt;<br /> <br /> Enable iperf3 through the menu in armbian-config:<br /> &lt;code&gt;armbian-config&lt;/code&gt;<br /> <br /> On a test computer on the same network segment run iperf3 as a client:<br /> &lt;code&gt;iperf3 -c pinecube -t 60&lt;/code&gt;<br /> <br /> The same test computer, run iperf3 in the reverse direction:<br /> &lt;code&gt;iperf3 -c pinecube -t 60 -R&lt;/code&gt;<br /> <br /> === Performance results ===<br /> <br /> ==== Wireless network performance ====<br /> The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.<br /> <br /> Client rate for sixty seconds:<br /> <br /> [ ID] Interval Transfer Bitrate Retr<br /> [ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender<br /> [ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver<br /> <br /> <br /> Client rate with -R for sixty seconds:<br /> <br /> [ ID] Interval Transfer Bitrate Retr<br /> [ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender<br /> [ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver<br /> <br /> Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.<br /> <br /> Client rate for sixty seconds with WireGuard:<br /> <br /> [ ID] Interval Transfer Bitrate Retr<br /> [ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender<br /> [ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver<br /> <br /> Client rate with -R for sixty seconds with WireGuard:<br /> <br /> [ ID] Interval Transfer Bitrate Retr<br /> [ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender<br /> [ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver<br /> <br /> ====== Wired network performance ======<br /> <br /> The Ethernet network does not work in the current Ubuntu Focal Armbian image or the Ubuntu Groovy Armbian image.<br /> <br /> The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.<br /> <br /> Client rate for sixty seconds:<br /> <br /> [ ID] Interval Transfer Bitrate Retr<br /> [ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender<br /> [ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver<br /> <br /> Client rate with -R for sixty seconds:<br /> <br /> [ ID] Interval Transfer Bitrate Retr<br /> [ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender<br /> [ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver<br /> <br /> Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.<br /> <br /> Client rate for sixty seconds with WireGuard:<br /> <br /> [ ID] Interval Transfer Bitrate Retr<br /> [ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender<br /> [ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver<br /> <br /> Client rate with -R for sixty seconds with WireGuard:<br /> <br /> [ ID] Interval Transfer Bitrate Retr<br /> [ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender<br /> [ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver<br /> <br /> == Streaming the camera to the network ==<br /> <br /> In this section we document a variety of ways to stream video to the network from the PineCube. Unless specified otherwise, all of these examples have been tested on Ubuntu groovy (20.10). See [https://github.com/ioerror/pinecube this small project for the pinecube] for easy to use programs tuned for the PineCube.<br /> <br /> In the examples which use h264, we are currently encoding using the x264 library which is not very fast on this CPU. The SoC in the PineCube does have a hardware h264 encoder, which the authors of these examples have so far not tried to use. It appears that https://github.com/gtalusan/gst-plugin-cedar might provide easy access to it, however. Please update this wiki if you find out how to use the hardware encoder!<br /> <br /> === gstreamer: h264 HLS ===<br /> <br /> HLS (HTTP Live Streaming) has the advantage that it is easy to play in any modern web browser, including Android and iPhone devices, and that it is easy to put an HTTP caching proxy in front of it to scale to many viewers. It has the disadvantages of adding (at minimum) several seconds of latency, and of requiring an h264 encoder (which we have in hardware, but haven't figured out how to use yet, so, we're stuck with the slow software one).<br /> <br /> HLS segments a video stream into small chunks which are stored as .ts (MPEG Transport Stream) files, and (re)writes a playlist.m3u8 file which clients constantly refresh to discover which .ts files they should download. We use a tmpfs file system to avoid needing to write these files to the sdcard in the PineCube. Besides the program which writes the .ts and .m3u8 files (gst-launch-1.0, in our case), we'll also need a very basic web page in tmpfs and a webserver to serve the files.<br /> <br /> Create an hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:<br /> <br /> &lt;code&gt;mkdir /dev/shm/hls/&lt;/code&gt;<br /> <br /> Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js]. We recommend downloading the hls.js file and editing the example index.html to serve your local copy of it instead of fetching it from a CDN. This file provides HLS playback capabilities in browsers which don't natively support it (which is most browsers aside from the iPhone).<br /> <br /> In one terminal, run the camera capture pipeline:<br /> &lt;code&gt;<br /> cd /dev/shm/hls/ &amp;&amp; <br /> media-ctl --set-v4l2 '&quot;ov5640 1-003c&quot;:0[fmt:UYVY8_2X8/240x320@1/15]' &amp;&amp; <br /> gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3<br /> &lt;/code&gt;<br /> <br /> Alternatively it is possible to capture at a higher resolution:<br /> &lt;code&gt;<br /> media-ctl --set-v4l2 '&quot;ov5640 1-003c&quot;:0[fmt:UYVY8_2X8/1920x1080@1/15]'<br /> cd /dev/shm/hls/ &amp;&amp; gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3<br /> &lt;/code&gt;<br /> <br /> In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:<br /> &lt;code&gt;<br /> cd /dev/shm/hls/ &amp;&amp; python3 -m http.server<br /> &lt;/code&gt;<br /> <br /> Alternately, install a more efficient web server (&lt;code&gt;apt install nginx&lt;/code&gt;) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.<br /> <br /> It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.<br /> <br /> You can also view the HLS stream with VLC: &lt;code&gt;vlc http://pinecube:8000/playlist.m3u8&lt;/code&gt;<br /> <br /> Or with gst-play-1.0: &lt;code&gt;gst-play-1.0 http://pinecube:8000/playlist.m3u8&lt;/code&gt; (or with mpv, ffplay, etc)<br /> <br /> To find out about other options you can configure in the &lt;code&gt;hlssink&lt;/code&gt; gstreamer element, you can run &lt;code&gt;gst-inspect-1.0 hlssink&lt;/code&gt;.<br /> <br /> It is worth noting here that the &lt;code&gt;hlssink&lt;/code&gt; element in GStreamer is not widely used in production environments. It is handy for testing, but for real-world free-software HLS live streaming deployments the standard tool today (January 2021) is nginx's RTMP module which can be used with ffmpeg to produce &quot;adaptive streams&quot; which are reencoded at varying quality levels. You can send data to an nginx-rtmp server from a gstreamer pipeline using the &lt;code&gt;rtmpsink&lt;/code&gt; element. It is also worth noting that gstreamer has a new &lt;code&gt;hlssink2&lt;/code&gt; element which we have not tested; perhaps in the future it will even have a webserver!<br /> <br /> === v4l2rtspserver: h264 RTSP ===<br /> <br /> Install dependencies:<br /> <br /> apt install -y cmake gstreamer1.0-plugins-bad gstreamer1.0-tools \<br /> gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \<br /> libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \<br /> gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \<br /> libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \<br /> liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \<br /> libvpx-dev libx264-dev libjpeg-dev libx265-dev linux-headers-dev-sunxi;<br /> <br /> Install kernel source and build v4l2loopback module:<br /> <br /> apt install linux-source-5.11.3-dev-sunxi64 #Adjust kernel version number to match current installation with &quot;uname -r&quot;<br /> cd /usr/src/v4l2loopback-0.12.3; make &amp;&amp; make install &amp;&amp; depmod -a<br /> <br /> Build required v4l2 software:<br /> <br /> git clone --recursive https://github.com/mpromonet/v4l2tools &amp;&amp; cd v4l2tools &amp;&amp; make &amp;&amp; make install;<br /> git clone --recursive https://github.com/mpromonet/v4l2rtspserver &amp;&amp; cd v4l2rtspserver &amp;&amp; cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . &amp;&amp; make &amp;&amp; make install;<br /> <br /> Running the camera:<br /> media-ctl --set-v4l2 '&quot;ov5640 1-003c&quot;:0[fmt:UYVY8_2X8/640x480@1/30]';<br /> modprobe v4l2loopback video_nr=10 debug=2;<br /> v4l2compress -fH264 -w -vv /dev/video0 /dev/video10 &amp;<br /> v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10<br /> <br /> Note that you might get an error when running media-ctl indicating that the resource is busy. This could be because of the motion program that runs on the stock OS installation. Check and kill any running /usr/bin/motion processes before running the above steps.<br /> <br /> The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.<br /> <br /> You'll probably see about a 2-3s lag with this approach, possibly due to the H264 compression and the lack of hardware acceleration at the moment.<br /> <br /> === gstreamer: JPEG RTSP ===<br /> <br /> GStreamer's RTSP server isn't an element you can use with gst-launch, but rather a library. We failed to build its example program, so instead used this very small 3rd party tool which is based on it: https://github.com/sfalexrog/gst-rtsp-launch/<br /> <br /> After building gst-rtsp-launch (which is relatively simple on Ubuntu groovy; just &lt;code&gt;apt install libgstreamer1.0-dev libgstrtspserver-1.0-dev&lt;/code&gt; first), you can read JPEG data directly from the camera and stream it via RTSP: &lt;code&gt;media-ctl --set-v4l2 '&quot;ov5640 1-003c&quot;:0[fmt:JPEG_1X8/1280x720]' &amp;&amp; gst-rtsp-launch 'v4l2src ! image/jpeg,width=1280,height=720 ! rtpjpegpay name=pay0'&lt;/code&gt;<br /> <br /> This stream can be played using &lt;code&gt;vlc rtsp://pinecube.local:8554/video&lt;/code&gt; or mpv, ffmpeg, gst-play-1.0, etc. If you increase the resolution to 1920x1080, mpv and gst-play can still play it, but VLC will complain &lt;code&gt;The total received frame size exceeds the client's buffer size (2000000). 73602 bytes of trailing data will be dropped!&lt;/code&gt; if you don't tell it to increase its buffer size with &lt;code&gt;--rtsp-frame-buffer-size=300000&lt;/code&gt;.<br /> <br /> === gstreamer: h264 RTSP ===<br /> <br /> Left as an exercise to the reader (please update the wiki). Hint: involves bits from the HLS and the JPEG RTSP examples above, but needs a &lt;code&gt;rtph264pay name=pay0&lt;/code&gt; element.<br /> <br /> === gstreamer: JPEG RTP UDP ===<br /> <br /> Configure camera: &lt;code&gt;media-ctl --set-v4l2 '&quot;ov5640 1-003c&quot;:0[fmt:JPEG_1X8/1920x1080]'&lt;/code&gt;<br /> <br /> Transmit with: &lt;code&gt;gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 ! udpsink host=$client_ip port=8000&lt;/code&gt;<br /> <br /> Receive with: &lt;code&gt;gst-launch-1.0 udpsrc port=8000 ! application/x-rtp, encoding-name=JPEG,payload=26 ! rtpjpegdepay ! jpegdec ! autovideosink&lt;/code&gt;<br /> <br /> Note that the sender must specify the recipient's IP address in place of &lt;code&gt;$client_ip&lt;/code&gt;; this can actually be a multicast address allowing for many receivers! (You'll need to specify a valid multicast address in the receivers' pipeline also; see &lt;code&gt;gst-inspect-1.0 udpsrc&lt;/code&gt; and &lt;code&gt;gst-inspect-1.0 udpsink&lt;/code&gt; for details.)<br /> <br /> === gstreamer: JPEG RTP TCP ===<br /> <br /> Configure camera: &lt;code&gt;media-ctl --set-v4l2 '&quot;ov5640 1-003c&quot;:0[fmt:JPEG_1X8/1920x1080]'&lt;/code&gt;<br /> <br /> Transmit with: &lt;code&gt;gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 ! rtpstreampay ! tcpserversink host=0.0.0.0 port=1234&lt;/code&gt;<br /> <br /> Receive with: &lt;code&gt;gst-launch-1.0 tcpclientsrc host=pinecube.local port=1234 ! application/x-rtp-stream,encoding-name=JPEG ! rtpstreamdepay ! application/x-rtp, media=video, encoding-name=JPEG ! rtpjpegdepay ! jpegdec ! autovideosink&lt;/code&gt;<br /> <br /> === gstreamer and socat: MJPEG HTTP server ===<br /> <br /> This rather ridiculous method uses bash, socat, and gstreamer to implement an HTTP-ish server which will serve your video as an MJPEG stream which is playable in browsers.<br /> <br /> This approach has the advantage of being relatively low latency (under a second), browser-compatible, and not needing to reencode anything on the CPU (it gets JPEG data from the camera itself). Compared to HLS, it has the disadvantages that MJPEG requires more bandwidth than h264 for similar quality, pause and seek are not possible, stalled connections cannot jump ahead when they are unstalled, and, in the case of this primitive implementation, it only supports one viewer at a time. (Though, really, the RTSP examples on this page perform very poorly with multiple viewers, so...)<br /> <br /> Gstreamer can almost do this by itself, as it has a multipartmux element which produces the headers which precede each frame. But sadly, despite various forum posts lamenting the lack of one over the last 12+ years, as of the end of the 50th year of the UNIX era (aka 2020), somehow nobody has yet gotten a webserver element merged in to gstreamer (which is necessary to produce the HTTP response, which is required for browsers other than firefox to play it). So, here is an absolutely minimal &quot;webserver&quot; which will get MJPEG displaying in a (single) browser.<br /> <br /> Create a file called &lt;code&gt;mjpeg-response.sh&lt;/code&gt;:<br /> #!/bin/bash<br /> media-ctl --set-v4l2 '&quot;ov5640 1-003c&quot;:0[fmt:JPEG_1X8/1920x1080]'<br /> b=&quot;--duct_tape_boundary&quot;<br /> echo -en &quot;HTTP/1.1 200 OK\r\nContent-type: multipart/x-mixed-replace;boundary=$b\r\n\r\n&quot;<br /> gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! multipartmux boundary=$b ! fdsink fd=2 2&gt;&amp;1 &gt;/dev/null<br /> <br /> Make it executable: &lt;code&gt;chmod +x mjpeg-response.sh&lt;/code&gt;<br /> <br /> Run the server: &lt;code&gt;socat TCP-LISTEN:8080,reuseaddr,fork EXEC:./mjpeg-response.sh&lt;/code&gt;<br /> <br /> And browse to http://pinecube.local:8080/ in your browser.<br /> <br /> === virtual web camera: gstreamer, mjpeg, udp rtp unicast ===<br /> <br /> It's possible to set up the pinecube as a virtual camera video device (Video 4 Linux) so that you can use it with video conferencing software, such as Jitsi Meet. Note that this has fairly minimal (&lt;1s) lag when tested on a wired 1Gb ethernet network connection and the frame rate is passable. MJPEG is very wasteful in terms of network resources, so this is something to keep in mind. The following instructions assume Debian Linux (Bullseye) as your desktop machine, but could work with other Linux OSes too. It's possible that someday a similar system could work with Mac OS X provided that someone writes a gstreamer plugin that exposes a Mac OS Core Media DAL device as a virtual webcam, like they did [https://github.com/johnboiles/obs-mac-virtualcam here] for OBS.<br /> <br /> First, you will need to set up the pinecube with gstreamer much like the above gstreamer, but in 1280x720 resolution. Also, you will be streaming to the desktop machine using UDP, with IP address represented by $desktop below at UDP port 8000.<br /> <br /> media-ctl --set-v4l2 '&quot;ov5640 1-003c&quot;:0[fmt:JPEG_1X8/1280x720]'<br /> gst-launch-1.0 v4l2src device=/dev/video0 ! image/jpeg,width=1280,height=720,framerate=30/1 ! rtpjpegpay name=pay0 ! udpsink host=$desktop port=8000<br /> <br /> On your desktop machine, you will need to install the gstreamer suite and the special v4l2loopback kernel module to bring the mjpeg stream to the Video 4 Linux device /dev/video10.<br /> <br /> sudo apt install gstreamer1.0-tools gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad gstreamer1.0-plugins-ugly v4l2loopback-dkms<br /> sudo modprobe v4l2loopback video_nr=10 max_buffers=32 exclusive_caps=1 # Creates /dev/video10 as a virtual v4l2 device, allocates increased buffers and exposes exclusive capabilities for chromium to find the video device<br /> gst-launch-1.0 udpsrc port=8000 ! application/x-rtp, encoding-name=JPEG,payload=26,framerate=30/1 ! rtpjpegdepay ! jpegdec ! video/x-raw, format=I420, width=1280, height=720 ! autovideoconvert ! v4l2sink device=/dev/video10<br /> <br /> The most common error found when launching the gstreamer pipeline above is the following error message, which seems to happen when the [https://github.com/umlaeute/v4l2loopback/issues/174 max_buffers aren't set] on the v4l2loopback module (see above), or if there is a v4l client (vlc, chromium) already connected to /dev/video10 when starting the pipeline. There does seem to be a small level of instability in this stack that could be improved.<br /> <br /> gstbasesrc.c(3055): gst_base_src_loop (): /GstPipeline:pipeline0/GstUDPSrc:udpsrc0:<br /> streaming stopped, reason not-negotiated (-4)<br /> <br /> Now that you have /dev/video10 hooked into the gstreamer pipeline you can then connect to it using VLC. VLC is a good local test that things are working. You can view the stream like this. Note that you could do the same thing with mpv/ffmpeg, but there are [https://www.raspberrypi.org/forums/viewtopic.php?t=270023 problems] currently.<br /> <br /> vlc v4l2:///dev/video10<br /> <br /> Be sure to disconnect vlc before trying to use the virtual web camera with chromium. Launch chromium and go to a web conference like [https://meet.jit.si jitsi]. When it prompts you for the camera pick the &quot;Dummy Video Device...&quot; and it should be much like what you see in vlc. Note that firefox isn't really working at this moment and the symptoms appear very similar to the problem with mpv/ffmpeg mentioned above, ie. when they connect to the camera they show only the first frame and then drop. It's unclear whether the bug is in gstreamer, v4l, or ffmpeg (or somewhere in these instructions).<br /> <br /> == Debugging camera issues with the gstreamer pipeline ==<br /> <br /> If the camera does not appear to work, it is possible to change the &lt;code&gt;v4l2src&lt;/code&gt; to &lt;code&gt;videotestsrc&lt;/code&gt; and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.<br /> <br /> If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:<br /> &lt;pre&gt;<br /> [ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy<br /> [ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy<br /> [ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy<br /> [ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy<br /> [ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy<br /> [ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy<br /> [ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy<br /> [ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy<br /> [ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy<br /> [ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy<br /> &lt;/pre&gt;<br /> <br /> == SDK ==<br /> <br /> ==== Stock Linux ====<br /> * [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]<br /> ** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8<br /> ** File Size: 3.50GB<br /> ===== How to compile =====<br /> <br /> You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]<br /> <br /> ====== On a dedicated machine ======<br /> <br /> Recommended system requirements:<br /> * OS: (L)Ubuntu 16.04<br /> * CPU: 64-bit based<br /> * Memory: 8 GB or higher<br /> * Disk: 15 GB free hard disk space<br /> <br /> '''Install required packages'''<br /> &lt;pre&gt;<br /> sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev<br /> &lt;/pre&gt;<br /> '''Install older Make 3.82 and Java JDK 6'''<br /> &lt;pre&gt;<br /> pushd /tmp<br /> wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz<br /> tar xfv make-3.82.tar.gz<br /> cd make-3.82<br /> ./configure<br /> make<br /> sudo apt purge -y make<br /> sudo ./make install<br /> cd ..<br /> # Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)<br /> chmod +x jdk-6u45-linux-x64.bin <br /> ./jdk-6u45-linux-x64.bin <br /> sudo mkdir /opt/java/<br /> sudo mv jdk1.6.0_45/ /opt/java/<br /> sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1<br /> sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1<br /> sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1<br /> sudo update-alternatives --config javac<br /> sudo update-alternatives --config java<br /> sudo update-alternatives --config javaws<br /> popd<br /> &lt;/pre&gt;<br /> '''Unpack SDK and then compile and pack the image'''<br /> &lt;pre&gt;<br /> 7z x 'PineCube Stock BSP-SDK ver1.0.7z'<br /> mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk<br /> cd pinecube-sdk/camdroid<br /> source build/envsetup.sh<br /> lunch<br /> mklichee<br /> make -j3<br /> pack<br /> &lt;/pre&gt;<br /> <br /> ====== Using Vagrant ======<br /> <br /> You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.<br /> <br /> Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]<br /> <br /> After spinning up the VM, you just need to run the build:<br /> &lt;pre&gt;<br /> cd pinecube-sdk/camdroid<br /> source build/envsetup.sh<br /> lunch<br /> mklichee<br /> make -j3<br /> pack<br /> &lt;/pre&gt;<br /> <br /> <br /> == Community Projects ==<br /> <br /> Share your project with a PineCube here!<br /> <br /> <br /> [[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineCube&diff=9611 2021-03-27T14:31:33Z

<p>Avamander: /* Specifications */</p> <hr /> <div>{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}<br /> <br /> <br /> <br /> == Specifications ==<br /> * '''Dimensions:''' 55mm x 51mm x 51.5mm<br /> * '''Weight:''' 55g<br /> * '''Storage:'''<br /> ** MicroSD slot, bootable<br /> ** 128Mb SPI Nor Flash, bootable<br /> * '''Cameras:''' OV5640, 5Mpx <br /> * '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz<br /> * '''RAM:''' 128MB DDR3<br /> * '''I/O:'''<br /> ** 10/100Mbps Ethernet with passive PoE (**4-18V!**)<br /> ** USB 2.0 A host<br /> ** 26 pins GPIO port<br /> *** 2x 3.3V Ouptut<br /> *** 2x 5V Output<br /> *** 1x I2C<br /> *** 2x UART<br /> *** 2x PWM<br /> *** 1x SPI<br /> *** 1x eMMC/SDIO/SD (8-bit)<br /> *** 6x Interrupts<br /> *** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''<br /> ** Internal microphone<br /> * '''Network:'''<br /> ** WiFi<br /> * '''Screen:''' optional 4.5&quot; RGB LCD screen<br /> * '''Misc. features:''' <br /> ** Volume and home buttons<br /> ** Speakers and Microphone<br /> * '''Power DC in:'''<br /> ** 5V 1A from MicroUSB Port or GPIO port<br /> ** 4V-18V from Ethernet passive PoE<br /> * '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]<br /> <br /> == PineCube board information, schematics and certifications ==<br /> * PineCube mainboard schematic:<br /> ** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]<br /> * PineCube faceboard schematic:<br /> ** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]<br /> * PineCube certifications:<br /> ** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]<br /> ** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]<br /> ** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]<br /> <br /> <br /> <br /> == Datasheets for components and peripherals ==<br /> * Allwinner (Sochip) S3 SoC information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]<br /> <br /> * X-Powers AXP209 PMU (Power Management Unit) information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]<br /> <br /> * CMOS camera module information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]<br /> ** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]<br /> <br /> * LCD touch screen panel information:<br /> <br /> * Lithium battery information:<br /> <br /> * WiFi/BT module information:<br /> ** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]<br /> <br /> * GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML]) (Pin1 is marked on the board by a white dot on the PCB)<br /> [[File:PineCube_GPIO_Pinout.png|700px]]<br /> <br /> <br /> * Case information:<br /> ** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PinePhone 3D file]<br /> <br /> [[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]<br /> <br /> == Operating Systems ==<br /> <br /> === Mainlining Efforts ===<br /> <br /> Please note:<br /> <br /> * this list is most likely not complete<br /> * no review of functionality is done here, it only serves as a collection of efforts<br /> <br /> {| class=&quot;wikitable&quot;<br /> !colspan=&quot;3&quot;|Linux kernel<br /> |-<br /> | Type<br /> | Link<br /> | Available in version<br /> |-<br /> | Devicetree Entry Pinecube<br /> | https://lkml.org/lkml/2020/9/22/1241<br /> | 5.10<br /> |-<br /> | Correction for AXP209 driver<br /> | https://lkml.org/lkml/2020/9/22/1243<br /> | 5.9<br /> |-<br /> | Additional Fixes for AXP209 driver<br /> | https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/<br /> | tdb (5.11?)<br /> |-<br /> | Device Tree Fixes<br /> | https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/<br /> | 5.10<br /> |-<br /> !colspan=&quot;3&quot;|U-boot<br /> |-<br /> | Type<br /> | Link<br /> | Available in version<br /> |-<br /> | PineCube Board Support<br /> | https://patchwork.ozlabs.org/project/uboot/list/?series=210044<br /> | expected in v2021.01<br /> |-<br /> !colspan=&quot;3&quot;|Buildroot<br /> |-<br /> | No known mainlining efforts yet<br /> |<br /> |<br /> |}<br /> <br /> <br /> === NixOS ===<br /> <br /> * [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]<br /> <br /> <br /> <br /> === Buildroot ===<br /> [https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.<br /> <br /> This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.<br /> The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.<br /> This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.<br /> <br /> === Armbian ===<br /> <br /> The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.<br /> <br /> <br /> ==== Armbian Build Image with motion [microSD Boot] [20201222] ====<br /> * Armbian Ubuntu Focal build for the Pinecube with the motion (detection) package preinstalled.<br /> * There are 2 ways to interact with the OS:<br /> ** Scan for the the device IP (with hostname pinecube)<br /> ** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER to login to the serial console, then check for assigned IP<br /> * DD image (for 8GB micoSD card and above)<br /> ** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]<br /> *** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b<br /> *** File Size: 328MGB<br /> <br /> [https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 GitHub gist] for the userpatch which pre-installs and configures the motion (detection) package. <br /> <br /> Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.<br /> Although [https://www.armbian.com/download/?device_support=No+official+support+(CSC) not officially supported] it enables the usage of Debian and Ubuntu.<br /> <br /> A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian (login: root, password: 1234).<br /> <br /> Motion daemon can be enabled using systemctl (With root) &lt;code&gt;systemctl enable motion&lt;/code&gt;. Then just reboot.<br /> <br /> ==== Serial connection using screen and the woodpecker USB serial device ====<br /> <br /> First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.<br /> <br /> On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:<br /> <br /> &lt;code&gt;screen /dev/ttyUSB0 115200&lt;/code&gt;<br /> <br /> ==== Serial connection using screen and Arduino Uno ====<br /> <br /> You can use the Arduino Uno or other Arduino boards as a USB serial device.<br /> <br /> First you must either remove the microcontroller from it's socket, or if your Arduino board does not allow this, then you can use wires to jump RESET (RST) and GND to isolate the SOC.<br /> <br /> After this you can either use the Arduino IDE and it's Serial monitor after selecting your &lt;code&gt;/dev/ttyACMx&lt;/code&gt; Arduino device, or screen:<br /> <br /> &lt;code&gt;screen /dev/ttyACM0 115200&lt;/code&gt;<br /> <br /> [[File:ArduinoSerialPinecube.jpg|400px]]<br /> <br /> ==== Serial connection using pinephone/pinebook pro serial debugging cable ====<br /> <br /> You can use the [https://wiki.pine64.org/wiki/PinePhone#Serial_console serial console] USB cable for pinephone and pinebook pro at the [https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/ store]. With a [https://www.amazon.com/3-5mm-Stereo-Female-terminal-connector/dp/B077XPSKQD female terminal block] wire using breadboard wire into the GPIO block at the following locations in a &quot;null modem&quot; configuration with transmit and receive crossed between your computer and the pinecube:<br /> <br /> S - Ground (to pin 9)<br /> R - Transmit (to pin 8)<br /> T - Receive (to pin 10)<br /> <br /> From Linux you can access the console of the pinecube using the screen command:<br /> <br /> &lt;code&gt;screen /dev/ttyUSB0 115200&lt;/code&gt;<br /> <br /> ==== Basic bandwidth tests with iperf3 ====<br /> <br /> Install armbian-config:<br /> &lt;code&gt;apt install armbian-config&lt;/code&gt;<br /> <br /> Enable iperf3 through the menu in armbian-config:<br /> &lt;code&gt;armbian-config&lt;/code&gt;<br /> <br /> On a test computer on the same network segment run iperf3 as a client:<br /> &lt;code&gt;iperf3 -c pinecube -t 60&lt;/code&gt;<br /> <br /> The same test computer, run iperf3 in the reverse direction:<br /> &lt;code&gt;iperf3 -c pinecube -t 60 -R&lt;/code&gt;<br /> <br /> === Performance results ===<br /> <br /> ==== Wireless network performance ====<br /> The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.<br /> <br /> Client rate for sixty seconds:<br /> <br /> [ ID] Interval Transfer Bitrate Retr<br /> [ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender<br /> [ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver<br /> <br /> <br /> Client rate with -R for sixty seconds:<br /> <br /> [ ID] Interval Transfer Bitrate Retr<br /> [ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender<br /> [ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver<br /> <br /> Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.<br /> <br /> Client rate for sixty seconds with WireGuard:<br /> <br /> [ ID] Interval Transfer Bitrate Retr<br /> [ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender<br /> [ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver<br /> <br /> Client rate with -R for sixty seconds with WireGuard:<br /> <br /> [ ID] Interval Transfer Bitrate Retr<br /> [ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender<br /> [ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver<br /> <br /> ====== Wired network performance ======<br /> <br /> The Ethernet network does not work in the current Ubuntu Focal Armbian image or the Ubuntu Groovy Armbian image.<br /> <br /> The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.<br /> <br /> Client rate for sixty seconds:<br /> <br /> [ ID] Interval Transfer Bitrate Retr<br /> [ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender<br /> [ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver<br /> <br /> Client rate with -R for sixty seconds:<br /> <br /> [ ID] Interval Transfer Bitrate Retr<br /> [ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender<br /> [ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver<br /> <br /> Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.<br /> <br /> Client rate for sixty seconds with WireGuard:<br /> <br /> [ ID] Interval Transfer Bitrate Retr<br /> [ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender<br /> [ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver<br /> <br /> Client rate with -R for sixty seconds with WireGuard:<br /> <br /> [ ID] Interval Transfer Bitrate Retr<br /> [ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender<br /> [ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver<br /> <br /> == Streaming the camera to the network ==<br /> <br /> In this section we document a variety of ways to stream video to the network from the PineCube. Unless specified otherwise, all of these examples have been tested on Ubuntu groovy (20.10). See [https://github.com/ioerror/pinecube this small project for the pinecube] for easy to use programs tuned for the PineCube.<br /> <br /> In the examples which use h264, we are currently encoding using the x264 library which is not very fast on this CPU. The SoC in the PineCube does have a hardware h264 encoder, which the authors of these examples have so far not tried to use. It appears that https://github.com/gtalusan/gst-plugin-cedar might provide easy access to it, however. Please update this wiki if you find out how to use the hardware encoder!<br /> <br /> === gstreamer: h264 HLS ===<br /> <br /> HLS (HTTP Live Streaming) has the advantage that it is easy to play in any modern web browser, including Android and iPhone devices, and that it is easy to put an HTTP caching proxy in front of it to scale to many viewers. It has the disadvantages of adding (at minimum) several seconds of latency, and of requiring an h264 encoder (which we have in hardware, but haven't figured out how to use yet, so, we're stuck with the slow software one).<br /> <br /> HLS segments a video stream into small chunks which are stored as .ts (MPEG Transport Stream) files, and (re)writes a playlist.m3u8 file which clients constantly refresh to discover which .ts files they should download. We use a tmpfs file system to avoid needing to write these files to the sdcard in the PineCube. Besides the program which writes the .ts and .m3u8 files (gst-launch-1.0, in our case), we'll also need a very basic web page in tmpfs and a webserver to serve the files.<br /> <br /> Create an hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:<br /> <br /> &lt;code&gt;mkdir /dev/shm/hls/&lt;/code&gt;<br /> <br /> Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js]. We recommend downloading the hls.js file and editing the example index.html to serve your local copy of it instead of fetching it from a CDN. This file provides HLS playback capabilities in browsers which don't natively support it (which is most browsers aside from the iPhone).<br /> <br /> In one terminal, run the camera capture pipeline:<br /> &lt;code&gt;<br /> cd /dev/shm/hls/ &amp;&amp; <br /> media-ctl --set-v4l2 '&quot;ov5640 1-003c&quot;:0[fmt:UYVY8_2X8/240x320@1/15]' &amp;&amp; <br /> gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3<br /> &lt;/code&gt;<br /> <br /> Alternatively it is possible to capture at a higher resolution:<br /> &lt;code&gt;<br /> media-ctl --set-v4l2 '&quot;ov5640 1-003c&quot;:0[fmt:UYVY8_2X8/1920x1080@1/15]'<br /> cd /dev/shm/hls/ &amp;&amp; gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3<br /> &lt;/code&gt;<br /> <br /> In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:<br /> &lt;code&gt;<br /> cd /dev/shm/hls/ &amp;&amp; python3 -m http.server<br /> &lt;/code&gt;<br /> <br /> Alternately, install a more efficient web server (&lt;code&gt;apt install nginx&lt;/code&gt;) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.<br /> <br /> It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.<br /> <br /> You can also view the HLS stream with VLC: &lt;code&gt;vlc http://pinecube:8000/playlist.m3u8&lt;/code&gt;<br /> <br /> Or with gst-play-1.0: &lt;code&gt;gst-play-1.0 http://pinecube:8000/playlist.m3u8&lt;/code&gt; (or with mpv, ffplay, etc)<br /> <br /> To find out about other options you can configure in the &lt;code&gt;hlssink&lt;/code&gt; gstreamer element, you can run &lt;code&gt;gst-inspect-1.0 hlssink&lt;/code&gt;.<br /> <br /> It is worth noting here that the &lt;code&gt;hlssink&lt;/code&gt; element in GStreamer is not widely used in production environments. It is handy for testing, but for real-world free-software HLS live streaming deployments the standard tool today (January 2021) is nginx's RTMP module which can be used with ffmpeg to produce &quot;adaptive streams&quot; which are reencoded at varying quality levels. You can send data to an nginx-rtmp server from a gstreamer pipeline using the &lt;code&gt;rtmpsink&lt;/code&gt; element. It is also worth noting that gstreamer has a new &lt;code&gt;hlssink2&lt;/code&gt; element which we have not tested; perhaps in the future it will even have a webserver!<br /> <br /> === v4l2rtspserver: h264 RTSP ===<br /> <br /> Install dependencies:<br /> <br /> apt install -y cmake gstreamer1.0-plugins-bad gstreamer1.0-tools \<br /> gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \<br /> libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \<br /> gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \<br /> libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \<br /> liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \<br /> libvpx-dev libx264-dev libjpeg-dev libx265-dev linux-headers-dev-sunxi;<br /> <br /> Install kernel source and build v4l2loopback module:<br /> <br /> apt install linux-source-5.11.3-dev-sunxi64 #Adjust kernel version number to match current installation with &quot;uname -r&quot;<br /> cd /usr/src/v4l2loopback-0.12.3; make &amp;&amp; make install &amp;&amp; depmod -a<br /> <br /> Build required v4l2 software:<br /> <br /> git clone --recursive https://github.com/mpromonet/v4l2tools &amp;&amp; cd v4l2tools &amp;&amp; make &amp;&amp; make install;<br /> git clone --recursive https://github.com/mpromonet/v4l2rtspserver &amp;&amp; cd v4l2rtspserver &amp;&amp; cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . &amp;&amp; make &amp;&amp; make install;<br /> <br /> Running the camera:<br /> media-ctl --set-v4l2 '&quot;ov5640 1-003c&quot;:0[fmt:UYVY8_2X8/640x480@1/30]';<br /> modprobe v4l2loopback video_nr=10 debug=2;<br /> v4l2compress -fH264 -w -vv /dev/video0 /dev/video10 &amp;<br /> v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10<br /> <br /> Note that you might get an error when running media-ctl indicating that the resource is busy. This could be because of the motion program that runs on the stock OS installation. Check and kill any running /usr/bin/motion processes before running the above steps.<br /> <br /> The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.<br /> <br /> You'll probably see about a 2-3s lag with this approach, possibly due to the H264 compression and the lack of hardware acceleration at the moment.<br /> <br /> === gstreamer: JPEG RTSP ===<br /> <br /> GStreamer's RTSP server isn't an element you can use with gst-launch, but rather a library. We failed to build its example program, so instead used this very small 3rd party tool which is based on it: https://github.com/sfalexrog/gst-rtsp-launch/<br /> <br /> After building gst-rtsp-launch (which is relatively simple on Ubuntu groovy; just &lt;code&gt;apt install libgstreamer1.0-dev libgstrtspserver-1.0-dev&lt;/code&gt; first), you can read JPEG data directly from the camera and stream it via RTSP: &lt;code&gt;media-ctl --set-v4l2 '&quot;ov5640 1-003c&quot;:0[fmt:JPEG_1X8/1280x720]' &amp;&amp; gst-rtsp-launch 'v4l2src ! image/jpeg,width=1280,height=720 ! rtpjpegpay name=pay0'&lt;/code&gt;<br /> <br /> This stream can be played using &lt;code&gt;vlc rtsp://pinecube.local:8554/video&lt;/code&gt; or mpv, ffmpeg, gst-play-1.0, etc. If you increase the resolution to 1920x1080, mpv and gst-play can still play it, but VLC will complain &lt;code&gt;The total received frame size exceeds the client's buffer size (2000000). 73602 bytes of trailing data will be dropped!&lt;/code&gt; if you don't tell it to increase its buffer size with &lt;code&gt;--rtsp-frame-buffer-size=300000&lt;/code&gt;.<br /> <br /> === gstreamer: h264 RTSP ===<br /> <br /> Left as an exercise to the reader (please update the wiki). Hint: involves bits from the HLS and the JPEG RTSP examples above, but needs a &lt;code&gt;rtph264pay name=pay0&lt;/code&gt; element.<br /> <br /> === gstreamer: JPEG RTP UDP ===<br /> <br /> Configure camera: &lt;code&gt;media-ctl --set-v4l2 '&quot;ov5640 1-003c&quot;:0[fmt:JPEG_1X8/1920x1080]'&lt;/code&gt;<br /> <br /> Transmit with: &lt;code&gt;gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 ! udpsink host=$client_ip port=8000&lt;/code&gt;<br /> <br /> Receive with: &lt;code&gt;gst-launch-1.0 udpsrc port=8000 ! application/x-rtp, encoding-name=JPEG,payload=26 ! rtpjpegdepay ! jpegdec ! autovideosink&lt;/code&gt;<br /> <br /> Note that the sender must specify the recipient's IP address in place of &lt;code&gt;$client_ip&lt;/code&gt;; this can actually be a multicast address allowing for many receivers! (You'll need to specify a valid multicast address in the receivers' pipeline also; see &lt;code&gt;gst-inspect-1.0 udpsrc&lt;/code&gt; and &lt;code&gt;gst-inspect-1.0 udpsink&lt;/code&gt; for details.)<br /> <br /> === gstreamer: JPEG RTP TCP ===<br /> <br /> Configure camera: &lt;code&gt;media-ctl --set-v4l2 '&quot;ov5640 1-003c&quot;:0[fmt:JPEG_1X8/1920x1080]'&lt;/code&gt;<br /> <br /> Transmit with: &lt;code&gt;gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 ! rtpstreampay ! tcpserversink host=0.0.0.0 port=1234&lt;/code&gt;<br /> <br /> Receive with: &lt;code&gt;gst-launch-1.0 tcpclientsrc host=pinecube.local port=1234 ! application/x-rtp-stream,encoding-name=JPEG ! rtpstreamdepay ! application/x-rtp, media=video, encoding-name=JPEG ! rtpjpegdepay ! jpegdec ! autovideosink&lt;/code&gt;<br /> <br /> === gstreamer and socat: MJPEG HTTP server ===<br /> <br /> This rather ridiculous method uses bash, socat, and gstreamer to implement an HTTP-ish server which will serve your video as an MJPEG stream which is playable in browsers.<br /> <br /> This approach has the advantage of being relatively low latency (under a second), browser-compatible, and not needing to reencode anything on the CPU (it gets JPEG data from the camera itself). Compared to HLS, it has the disadvantages that MJPEG requires more bandwidth than h264 for similar quality, pause and seek are not possible, stalled connections cannot jump ahead when they are unstalled, and, in the case of this primitive implementation, it only supports one viewer at a time. (Though, really, the RTSP examples on this page perform very poorly with multiple viewers, so...)<br /> <br /> Gstreamer can almost do this by itself, as it has a multipartmux element which produces the headers which precede each frame. But sadly, despite various forum posts lamenting the lack of one over the last 12+ years, as of the end of the 50th year of the UNIX era (aka 2020), somehow nobody has yet gotten a webserver element merged in to gstreamer (which is necessary to produce the HTTP response, which is required for browsers other than firefox to play it). So, here is an absolutely minimal &quot;webserver&quot; which will get MJPEG displaying in a (single) browser.<br /> <br /> Create a file called &lt;code&gt;mjpeg-response.sh&lt;/code&gt;:<br /> #!/bin/bash<br /> media-ctl --set-v4l2 '&quot;ov5640 1-003c&quot;:0[fmt:JPEG_1X8/1920x1080]'<br /> b=&quot;--duct_tape_boundary&quot;<br /> echo -en &quot;HTTP/1.1 200 OK\r\nContent-type: multipart/x-mixed-replace;boundary=$b\r\n\r\n&quot;<br /> gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! multipartmux boundary=$b ! fdsink fd=2 2&gt;&amp;1 &gt;/dev/null<br /> <br /> Make it executable: &lt;code&gt;chmod +x mjpeg-response.sh&lt;/code&gt;<br /> <br /> Run the server: &lt;code&gt;socat TCP-LISTEN:8080,reuseaddr,fork EXEC:./mjpeg-response.sh&lt;/code&gt;<br /> <br /> And browse to http://pinecube.local:8080/ in your browser.<br /> <br /> === virtual web camera: gstreamer, mjpeg, udp rtp unicast ===<br /> <br /> It's possible to set up the pinecube as a virtual camera video device (Video 4 Linux) so that you can use it with video conferencing software, such as Jitsi Meet. Note that this has fairly minimal (&lt;1s) lag when tested on a wired 1Gb ethernet network connection and the frame rate is passable. MJPEG is very wasteful in terms of network resources, so this is something to keep in mind. The following instructions assume Debian Linux (Bullseye) as your desktop machine, but could work with other Linux OSes too. It's possible that someday a similar system could work with Mac OS X provided that someone writes a gstreamer plugin that exposes a Mac OS Core Media DAL device as a virtual webcam, like they did [https://github.com/johnboiles/obs-mac-virtualcam here] for OBS.<br /> <br /> First, you will need to set up the pinecube with gstreamer much like the above gstreamer, but in 1280x720 resolution. Also, you will be streaming to the desktop machine using UDP, with IP address represented by $desktop below at UDP port 8000.<br /> <br /> media-ctl --set-v4l2 '&quot;ov5640 1-003c&quot;:0[fmt:JPEG_1X8/1280x720]'<br /> gst-launch-1.0 v4l2src device=/dev/video0 ! image/jpeg,width=1280,height=720,framerate=30/1 ! rtpjpegpay name=pay0 ! udpsink host=$desktop port=8000<br /> <br /> On your desktop machine, you will need to install the gstreamer suite and the special v4l2loopback kernel module to bring the mjpeg stream to the Video 4 Linux device /dev/video10.<br /> <br /> sudo apt install gstreamer1.0-tools gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad gstreamer1.0-plugins-ugly v4l2loopback-dkms<br /> sudo modprobe v4l2loopback video_nr=10 max_buffers=32 exclusive_caps=1 # Creates /dev/video10 as a virtual v4l2 device, allocates increased buffers and exposes exclusive capabilities for chromium to find the video device<br /> gst-launch-1.0 udpsrc port=8000 ! application/x-rtp, encoding-name=JPEG,payload=26,framerate=30/1 ! rtpjpegdepay ! jpegdec ! video/x-raw, format=I420, width=1280, height=720 ! autovideoconvert ! v4l2sink device=/dev/video10<br /> <br /> The most common error found when launching the gstreamer pipeline above is the following error message, which seems to happen when the [https://github.com/umlaeute/v4l2loopback/issues/174 max_buffers aren't set] on the v4l2loopback module (see above), or if there is a v4l client (vlc, chromium) already connected to /dev/video10 when starting the pipeline. There does seem to be a small level of instability in this stack that could be improved.<br /> <br /> gstbasesrc.c(3055): gst_base_src_loop (): /GstPipeline:pipeline0/GstUDPSrc:udpsrc0:<br /> streaming stopped, reason not-negotiated (-4)<br /> <br /> Now that you have /dev/video10 hooked into the gstreamer pipeline you can then connect to it using VLC. VLC is a good local test that things are working. You can view the stream like this. Note that you could do the same thing with mpv/ffmpeg, but there are [https://www.raspberrypi.org/forums/viewtopic.php?t=270023 problems] currently.<br /> <br /> vlc v4l2:///dev/video10<br /> <br /> Be sure to disconnect vlc before trying to use the virtual web camera with chromium. Launch chromium and go to a web conference like [https://meet.jit.si jitsi]. When it prompts you for the camera pick the &quot;Dummy Video Device...&quot; and it should be much like what you see in vlc. Note that firefox isn't really working at this moment and the symptoms appear very similar to the problem with mpv/ffmpeg mentioned above, ie. when they connect to the camera they show only the first frame and then drop. It's unclear whether the bug is in gstreamer, v4l, or ffmpeg (or somewhere in these instructions).<br /> <br /> == Debugging camera issues with the gstreamer pipeline ==<br /> <br /> If the camera does not appear to work, it is possible to change the &lt;code&gt;v4l2src&lt;/code&gt; to &lt;code&gt;videotestsrc&lt;/code&gt; and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.<br /> <br /> If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:<br /> &lt;pre&gt;<br /> [ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy<br /> [ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy<br /> [ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy<br /> [ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy<br /> [ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy<br /> [ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy<br /> [ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy<br /> [ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy<br /> [ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy<br /> [ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy<br /> &lt;/pre&gt;<br /> <br /> == SDK ==<br /> <br /> ==== Stock Linux ====<br /> * [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]<br /> ** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8<br /> ** File Size: 3.50GB<br /> ===== How to compile =====<br /> <br /> You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]<br /> <br /> ====== On a dedicated machine ======<br /> <br /> Recommended system requirements:<br /> * OS: (L)Ubuntu 16.04<br /> * CPU: 64-bit based<br /> * Memory: 8 GB or higher<br /> * Disk: 15 GB free hard disk space<br /> <br /> '''Install required packages'''<br /> &lt;pre&gt;<br /> sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev<br /> &lt;/pre&gt;<br /> '''Install older Make 3.82 and Java JDK 6'''<br /> &lt;pre&gt;<br /> pushd /tmp<br /> wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz<br /> tar xfv make-3.82.tar.gz<br /> cd make-3.82<br /> ./configure<br /> make<br /> sudo apt purge -y make<br /> sudo ./make install<br /> cd ..<br /> # Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)<br /> chmod +x jdk-6u45-linux-x64.bin <br /> ./jdk-6u45-linux-x64.bin <br /> sudo mkdir /opt/java/<br /> sudo mv jdk1.6.0_45/ /opt/java/<br /> sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1<br /> sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1<br /> sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1<br /> sudo update-alternatives --config javac<br /> sudo update-alternatives --config java<br /> sudo update-alternatives --config javaws<br /> popd<br /> &lt;/pre&gt;<br /> '''Unpack SDK and then compile and pack the image'''<br /> &lt;pre&gt;<br /> 7z x 'PineCube Stock BSP-SDK ver1.0.7z'<br /> mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk<br /> cd pinecube-sdk/camdroid<br /> source build/envsetup.sh<br /> lunch<br /> mklichee<br /> make -j3<br /> pack<br /> &lt;/pre&gt;<br /> <br /> ====== Using Vagrant ======<br /> <br /> You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.<br /> <br /> Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]<br /> <br /> After spinning up the VM, you just need to run the build:<br /> &lt;pre&gt;<br /> cd pinecube-sdk/camdroid<br /> source build/envsetup.sh<br /> lunch<br /> mklichee<br /> make -j3<br /> pack<br /> &lt;/pre&gt;<br /> <br /> <br /> == Community Projects ==<br /> <br /> Share your project with a PineCube here!<br /> <br /> <br /> [[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]</div>

Avamander https://wiki.pine64.org/index.php?title=Reprogramming_the_PineTime&diff=9379 2021-03-04T19:27:36Z

<p>Avamander: Minor copy from lupyuen/openocd-spi</p> <hr /> <div>= Introduction =<br /> <br /> 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. <br /> <br /> '''Before you can use your debugger/programmer, you probably have to [[PineTime devkit wiring|wire up your pinetime]]. Heavily recommended you read this first!'''<br /> <br /> 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:<br /> <br /> * Unlocking the device '''Note: PineTime watches shipped after 20 Sep 2020 do not require unlocking. They are shipped unlocked.'''<br /> * Uploading new software<br /> * Running a debugger<br /> <br /> All of these are described in this article. <br /> <br /> 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.<br /> <br /> = SWD Pinout =<br /> <br /> See [[PineTime devkit wiring|PineTime devkit wiring]]<br /> <br /> = nrfjprog (for Segger JLink) =<br /> <br /> 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].<br /> <br /> === Hookup ===<br /> <br /> Connect the Pinetime SWD pins to the debugger (P20 on NRF52-DK)<br /> <br /> {| class=&quot;wikitable&quot;<br /> !Pinetime<br /> !JLink<br /> |-<br /> |GND<br /> |GND<br /> |-<br /> |SWDCLK<br /> |SWDCLK<br /> |-<br /> |SWDIO<br /> |SWDIO<br /> |-<br /> |VCC (3.3V)<br /> |VTG (target detect)<br /> |}<br /> <br /> === Unlocking the FLASH ===<br /> <br /> Unlocking the device and erase the memory. <br /> <br /> '''You need to execute this step only once, to remove the read protection on the memory. Note that it will erase the whole flash memory of the MCU!''' :<br /> <br /> nrfjprog -f NRF52 --recover<br /> <br /> === Uploading new software ===<br /> <br /> 1. Program the BLE softdevice (if needed by the firmware). Replace PATH_TO_NRF_SDK by the path where you unzipped the [https://www.nordicsemi.com/Software-and-Tools/Software/nRF5-SDK NRF52 SDK] :<br /> <br /> nrfjprog -f NRF52 --program /PATH_TO_NRF_SDK/components/softdevice/s132/hex/s132_nrf52_6.1.1_softdevice.hex --sectorerase<br /> <br /> 2. Program the firmware (replace firmware.hex by the actual filename of the firmware):<br /> <br /> nrfjprog -f NRF52 --program firmware.hex --sectorerase<br /> <br /> 3. Reset and run the new firmware:<br /> <br /> nrfjprog -f NRF52 --reset<br /> <br /> = OpenOCD =<br /> <br /> OpenOCD, the Open On-Chip Debugger supports multiple different adapters. You can read more about it here: http://openocd.org/<br /> <br /> == Adapters ==<br /> <br /> 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''.<br /> <br /> You can simplify your life by creating a configuration file that contains the interface, transport, target and speed configuration. Things like CLion also need one to work properly.<br /> <br /> 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'').<br /> <br /> === CMSIS-DAP ===<br /> <br /> Issue this command to initialize a connection to the devkit:<br /> <br /> openocd \<br /> -c 'source [find interface/cmsis-dap.cfg]' \<br /> -c 'transport select swd' \<br /> -c 'source [find target/nrf52.cfg]' \<br /> -c 'adapter speed 8000' \<br /> -c 'init'<br /> <br /> === JLink ===<br /> <br /> Start OpenOCD:<br /> <br /> openocd \<br /> -c 'source [find interface/jlink.cfg]' \<br /> -c 'transport select swd' \<br /> -c 'source [find target/nrf52.cfg]' \<br /> -c 'adapter speed 8000' \<br /> -c 'init'<br /> <br /> === Raspberry Pi ===<br /> <br /> openocd \<br /> -c 'source bcm2835spi' \<br /> -c 'bcm2835spi_speed 31200' \<br /> -c 'source [find target/nrf52.cfg]' \<br /> -c 'init'<br /> <br /> === STLink ===<br /> <br /> Connect PineTime SWD Pins to ST-Link v2 as follows:<br /> <br /> {| class=&quot;wikitable&quot;<br /> !PineTime<br /> !ST-Link<br /> |-<br /> |GND<br /> |GND<br /> |-<br /> |SWDCLK<br /> |SWDCLK<br /> |-<br /> |SWDIO<br /> |SWDIO<br /> |-<br /> |VCC (3.3V)<br /> |3.3V<br /> |}<br /> <br /> [[File:pinetime-stlink.jpg|400px]]<br /> <br /> Note that only the bottom row of pins on ST-Link are used.<br /> <br /> To flash PineTime with ST-Link on Linux and macOS, use [https://github.com/lupyuen/pinetime-updater/blob/master/README.md PineTime Updater]<br /> <br /> [[PineTime FAQ|'''ST-Link can't be used to remove nRF52 flash protection''']]<br /> <br /> == Unlocking the device ==<br /> <br /> If you need to disable access port protection then you can do this using the following commands below.<br /> <br /> This can be done in two ways:<br /> <br /> Appending this to OpenOCD command line:<br /> <br /> -c 'nrf52.dap apreg 1 0x04' -c 'nrf52.dap apreg 1 0x04 0x01' -c 'nrf52.dap apreg 1 0x04'<br /> <br /> Or by using the telnet connection, just type in ''telnet localhost 4444'' and then you can issue commands to OpenOCD:<br /> <br /> Note: ''Unlocking the device to remove access port protection will erase the contents of flash.''<br /> <br /> telnet localhost 4444<br /> Trying 127.0.0.1...<br /> Connected to localhost.<br /> Escape character is '^]'.<br /> Open On-Chip Debugger<br /> &gt; nrf52.dap apreg 1 0x04<br /> 0x00000000<br /> &gt; nrf52.dap apreg 1 0x04 0x01<br /> &gt; nrf52.dap apreg 1 0x04<br /> 0x00000001<br /> <br /> (If the ''nrf52.dap'' command cannot be found, try just ''dap'' instead.)<br /> <br /> == Uploading new software ==<br /> <br /> Just issue this command, replace ''code.hex'' with your own (and cmsis-dap.cfg with an appropriate adapter).<br /> <br /> openocd \<br /> -c 'source [find interface/cmsis-dap.cfg]' \<br /> -c 'transport select swd' \<br /> -c 'source [find target/nrf52.cfg]' \<br /> -c 'init' \<br /> -c 'nrf5 mass_erase' \<br /> -c 'program code.hex verify' \<br /> -c 'reset' \<br /> -c 'exit'<br /> <br /> = Black Magic Probe =<br /> <br /> 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].<br /> <br /> === Native adapters ===<br /> <br /> The native adapters are the official Black Magic family of debug adapters, including the original Black Magic Probe and the Black Magic Probe Mini. By buying the official hardware you are supporting the continued development of the Black Magic Probe software.<br /> <br /> Providing your native adapter is running up-to-date firmware then it can be used to program your PineTime.<br /> <br /> === STM32 (Blue Pill) ===<br /> <br /> It is possible to flash a popular development board based on STM32F103C8T6 microcontroller, known as Blue Pill, to make a BlackMagic Probe device. For example, one may follow instructions in [https://forum.pine64.org/showthread.php?tid=8816&amp;pid=57095#pid57095 forum post] or [https://gist.github.com/darnel/dac1370d057e176386ca4026418abc2b gist] (mac os). Also, it is possible to use SWD pins on the board to flash other devices, instead using arbitrary pins on the board itself. See [https://buger.dread.cz/black-magic-probe-bmp-on-bluepill-stm32f103c8-minimum-system-development-board.html this link] for more detals.<br /> <br /> === Other hardware ===<br /> <br /> The Black Magic Probe firmware can be run on a variety of host devices. See [https://github.com/blacksphere/blackmagic/wiki/Debugger-Hardware BMP Debugger Hardware] for more information.<br /> <br /> === Using the BMP to flash the PineTime ===<br /> <br /> Refer to the BMP [https://github.com/blacksphere/blackmagic/wiki/Useful-GDB-commands wiki] for the full description of commands.<br /> Overall, the process on Linux is like following. (/dev/ttyBmpGdb is a symlink created by the udev rule). It's useful to create a gdb script file (or .gdbinit) with following commands:<br /> <br /> target extended-remote /dev/ttyBmpGdb<br /> monitor swdp_scan<br /> attach 1<br /> file %firmware file%<br /> <br /> Then one may use '''load''' command to flash the firmware, '''compare-sections''' to verify the upload, or '''monitor erase_mass''' to erase the firmware. <br /> <br /> Then, proceed with debugging as normal.<br /> <br /> <br /> = External links and additional tutorials = <br /> <br /> * https://github.com/jlukanc1/pinetime-boot-flasher<br /> * https://blog.aegrel.ee/absniffer-cmsis-dap-sniffer.html<br /> * https://blog.dbrgn.ch/2020/5/16/nrf52-unprotect-flash-jlink-openocd/<br /> * https://medium.com/@ly.lee/openocd-on-raspberry-pi-better-with-swd-on-spi-7dea9caeb590<br /> * https://medium.com/@ly.lee/build-and-flash-rust-mynewt-firmware-for-pinetime-smart-watch-5e14259c55<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_Equivalents&diff=9344 2021-02-24T22:00:45Z

<p>Avamander: </p> <hr /> <div>This page contains a list of PineTime hardware equivalents or very close clones. Primarily to keep track of which devices could possibly be &quot;jailbroken&quot; and run PineTime firmware.<br /> <br /> Please add devices that use the same chipset to this list.<br /> <br /> ==== Kalakate ====<br /> <br /> Seems to be PineTime hardware, interesting GUI, seems DaFit-y<br /> <br /> * https://www.youtube.com/watch?v=1VdMxbOYxgA<br /> <br /> <br /> ==== P8 ====<br /> <br /> A few firmware already support both the P8 and PineTime, the physical differences are minor - only a few MCU pins are mapped differently.<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=Main_Page&diff=9343 2021-02-24T21:26:14Z

<p>Avamander: /* Chat platforms */</p> <hr /> <div>PINE64 is a community-driven company focused on creating high-quality, low cost ARM devices for businesses and individuals around the globe. PINE64 made its debut with the [[PINE_A64|Pine A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.<br /> <br /> PINE64 has a large and active community and offers a variety of resources for businesses and hobbyists to take advantage of their projects. To learn more about PINE64 and the available devices, please visit the main [https://www.pine64.org/ PINE64 website].<br /> <br /> = Devices =<br /> <br /> * [[Nutcracker]]<br /> * [[PINE A64]]<br /> * [[PINE A64-LTS/SOPine]], [[SOPine_Clusterboard | Clusterboard]]<br /> * [[PINE H64]]<br /> * Pinebook:<br /> ** [[Pinebook]]<br /> ** [[Pinebook Pro]]<br /> * [[Pinecil]]<br /> * [[PineCube]]<br /> * [[PinePhone]]<br /> * [[PinePower]]<br /> * [[PineTab]]<br /> * [[PineTime]]<br /> * [[Quartz64]]<br /> * [[ROCK64]]<br /> * [[ROCKPro64]]<br /> * [[SOEdge]]<br /> <br /> = Community and Support =<br /> <br /> == Chat platforms ==<br /> Pine64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together - messages sent via one platform will be sent to all other platforms automatically.<br /> <br /> The community chat platforms are:<br /> <br /> '''IRC'''<br /> : Server: [ircs://irc.pine64.org irc.pine64.org], type &lt;code&gt;/list&lt;/code&gt; to see all available channels (web IRC: https://www.pine64.org/web-irc/). Only some of the channels are available.<br /> <br /> '''Discord'''<br /> : [https://discordapp.com/invite/DgB7kzr Discord invite link] (all channels are available)<br /> <br /> '''Matrix and Telegram'''<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Name !! Matrix !! Telegram<br /> |-<br /> | PINE64 News || missing || [https://t.me/PINE64_News @PINE64_News]<br /> |-<br /> | PINE A64 SBC || [https://riot.im/app/#/room/#pine64:matrix.org #pine64:matrix.org] || [https://t.me/mtrx_rock64 @mtrx_pine64]<br /> |-<br /> | ROCK64 / ROCKPro64 || [https://riot.im/app/#/room/#rock64:matrix.org #rock64:matrix.org] || [https://t.me/mtrx_rock64 @mtrx_rock64]<br /> |-<br /> | Pinebook and Pinebook Pro || [https://riot.im/app/#/room/#pinebook:matrix.org #pinebook:matrix.org] || [https://t.me/mtx_pinebook @mtx_pinebook]<br /> |-<br /> | PinePhone || [https://riot.im/app/#/room/#pinephone:matrix.org #pinephone:matrix.org] || [https://t.me/pinephone @pinephone]<br /> |-<br /> | PineTab || [https://riot.im/app/#/room/#pinetab:pine64.org #pinetab:matrix.org] || [https://t.me/PineTab @PineTab]<br /> |-<br /> | PineTime || [https://riot.im/app/#/room/#pinetime:matrix.org #pinetime:matrix.org] || [https://t.me/pinetime @pinetime]<br /> |-<br /> | PineTime Development || [https://riot.im/app/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org] || [https://t.me/pinetime_dev @pinetime_dev]<br /> |-<br /> | Pinecil || [https://riot.im/app/#/room/#pinecil:matrix.org #pinecil:matrix.org] || [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]<br /> |-<br /> | Pinetalk || missing || missing<br /> |-<br /> | Cube || [https://riot.im/app/#/room/#cube64:matrix.org #cube64:matrix.org] || missing<br /> |-<br /> | Nutcracker || [https://riot.im/app/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org] || [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]<br /> |-<br /> | Off-topic || [https://riot.im/app/#/room/#offtopic64:matrix.org #offtopic64:matrix.org] || [https://t.me/pine64offtopic @pine64offtopic]<br /> |-<br /> |}<br /> <br /> &lt;!--<br /> '''Matrix'''<br /> : PINE64 News (missing)<br /> : [https://riot.im/app/#/room/#pine64:matrix.org #pine64:matrix.org] - PINE A64 SBC room<br /> : [https://riot.im/app/#/room/#rock64:matrix.org #rock64:matrix.org] - ROCK64 / ROCKPro64 room<br /> : [https://riot.im/app/#/room/#pinebook:matrix.org #pinebook:matrix.org] - Pinebook and Pinebook Pro room<br /> : [https://riot.im/app/#/room/#pinephone:matrix.org #pinephone:matrix.org] - PinePhone room<br /> : [https://riot.im/app/#/room/#pinetab:pine64.org #pinetab:matrix.org] - PineTab room<br /> : [https://riot.im/app/#/room/#pinetime64:matrix.org #pinetime64:matrix.org] - PineTime room<br /> : [https://riot.im/app/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org] - PineTime Development room<br /> : [https://riot.im/app/#/room/#pinecil:matrix.org #pinecil:matrix.org] - Pinecil room<br /> : Pinetalk (missing)<br /> : [https://riot.im/app/#/room/#cube64:matrix.org #cube64:matrix.org] - Cube room<br /> : [https://riot.im/app/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org] - Nutcracker room<br /> : [https://riot.im/app/#/room/#offtopic64:matrix.org #offtopic64:matrix.org] - Off-topic room<br /> <br /> '''Telegram'''<br /> : [https://t.me/PINE64_News PINE64 News]<br /> : [https://t.me/mtrx_pine64 PINE A64 SBC]<br /> : [https://t.me/mtrx_rock64 ROCK64 / ROCKPro64]<br /> : [https://t.me/mtx_pinebook Pinebook and Pinebook Pro]<br /> : [https://t.me/pinephone PinePhone]<br /> : [https://t.me/PineTab PineTab]<br /> : [https://t.me/pinetime PineTime]<br /> : [https://t.me/pinetime_dev PineTime Development]<br /> : [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]<br /> : Pinetalk (missing)<br /> : Cube (missing)<br /> : [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]<br /> : [https://t.me/pine64offtopic Pine64 Off-topic]<br /> --&gt;<br /> <br /> == Forums ==<br /> PINE64 runs an offical forum powered by open source [https://mybb.com/ MyBB] forum server software. According to [https://www.pine64.org/gettings-started/ Getting Started | PINE64], on the forum one can report issues, help out other users, offer up findings and new information, but also engage directly with community and partner-project developers, as well as with PINE64 members.<br /> <br /> : [https://forum.pine64.org/ Official Pine64 Forum]<br /> <br /> '''Reddit'''<br /> : [https://www.reddit.com/r/PINE64official/ Official Pine64 Reddit]<br /> : [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]<br /> <br /> = Helpful Information for Beginners =<br /> Sections dedicated to the very beginners who are just getting started in the SBC and ARM64 world. If you're just starting out and having issues with getting going, please consider browsing both sections for pointers. <br /> <br /> '''Getting Started'''<br /> : [[NOOB]] - Basic information on how to flash SD cards and eMMC modules as well as handling your devices.<br /> <br /> '''Project Ideas'''<br /> : [[Project]] - A variety of well-documented PINE64 projects to serve as inspiration.<br /> <br /> __FORCETOC__</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_Hardware_Wishlist&diff=9342 2021-02-24T21:23:26Z

<p>Avamander: </p> <hr /> <div>This page contains a list of things people wish PineTime did differently<br /> <br /> === Hardware ===<br /> <br /> * Long pressing the button should power-cycle the watch without any software being involved<br /> * Used sensors should be NDA-free and preferably also blob-free<br /> * Other display tech could be explored. [//en.Wikipedia.org/wiki/Transflective_liquid-crystal_display A transflective LCD] would probably be a nice option. Or potentially OLED?<br /> * Touchscreen should possibly have a configurable sensitivity level for both glove-wearing and droplet-resistance. Preferably it should still be a capacitive one, a resistive touchscreen would have too many trade-offs.<br /> * A slightly bigger 256×256 pixel graphics display size is preferable for its binary alignment, affording some low-level simplicity – it has the property that its X and Y coordinates are each addressable with a single byte, with no out-of-bounds; its total number of pixels is 65536 (another power of 2), and each pixel is addressable with exactly 2 bytes, with perfect efficiency. The [http://Pelulamu.net/ibniz IBNIZ (Ideally Bare Numeric Impression giZmo) virtual machine], designed for fun minimalist demoscene graphics, has chosen 256×256 for its virtual display, and makes use of these simplicity advantages. If PineTime also chose 256×256 then it would be a target platform for unclipped IBNIZ demoscene programmes, which would be really fun to play around with on one's wrist!<br /> * A full redraw on the display takes 120ms at the very least, which is 8Hz. A smooth scrolling/usage/animation experience would be 30Hz minimum, preferably 60. I heard a rumor that the SPI connection to the display is a bottleneck.<br /> * Some sort of scroll wheel would be nice for convenience.<br /> * Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)<br /> * Wireless charging, or Qi Charging capability<br /> * An external RTC circuit saving the current time to allow the main MCU go to deep-sleep.<br /> * nRF5340 update: QSPI, CryptoCell + Secure Key Storage, has more RAM, a coprocessor and the possibility to expose USB through power pins<br /> * Version without sensors but maybe bigger battery<br /> * A couple of pins on the programmer connector to allow UART while developing (currently there is a TX test point on PCB). (Note: There's ARM SemiHosting and Segger RTT)<br /> * Connect the pin of LCD controller that allows RD/WR from it in order to save RAM on the MCU.<br /> * LCD must be centered on case. Currently is not and watchfaces seems different when clock is put on the other wrist.<br /> * A NFC antenna around the case, connected to the NFC pins.<br /> * BMA421 accelerometer doesn't have a datasheet (it seems private to some hardware integrators): take it off and put alternative with open documentation.<br /> <br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_Hardware_Wishlist&diff=9341 2021-02-24T21:22:59Z

<p>Avamander: </p> <hr /> <div>This page contains a list of things people wish PineTime did differently<br /> <br /> === Hardware ===<br /> <br /> * Long pressing the button should power-cycle the watch without any software being involved<br /> * Used sensors should be NDA-free and preferably also blob-free<br /> * Other display tech could be explored. [//en.Wikipedia.org/wiki/Transflective_liquid-crystal_display A transflective LCD] would probably be a nice option. Or potentially OLED?<br /> * Touchscreen should possibly have a configurable sensitivity level for both glove-wearing and droplet-resistance. Preferably it should still be a capacitive one, a resistive touchscreen would have too many trade-offs.<br /> * A slightly bigger 256×256 pixel graphics display size is preferable for its binary alignment, affording some low-level simplicity – it has the property that its X and Y coordinates are each addressable with a single byte, with no out-of-bounds; its total number of pixels is 65536 (another power of 2), and each pixel is addressable with exactly 2 bytes, with perfect efficiency. The [http://Pelulamu.net/ibniz IBNIZ (Ideally Bare Numeric Impression giZmo) virtual machine], designed for fun minimalist demoscene graphics, has chosen 256×256 for its virtual display, and makes use of these simplicity advantages. If PineTime also chose 256×256 then it would be a target platform for unclipped IBNIZ demoscene programmes, which would be really fun to play around with on one's wrist!<br /> * A full redraw on the display takes 120ms at the very least, which is 8Hz. A smooth scrolling/usage/animation experience would be 30Hz minimum, preferably 60. I heard a rumor that the SPI connection to the display is a bottleneck. Can this be fixed?<br /> * Some sort of scroll wheel would be nice for convenience.<br /> * Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)<br /> * Wireless charging, or Qi Charging capability<br /> * An external RTC circuit saving the current time to allow the main MCU go to deep-sleep.<br /> * nRF5340 update: QSPI, CryptoCell + Secure Key Storage, has more RAM, a coprocessor and the possibility to expose USB through power pins<br /> * Version without sensors but maybe bigger battery<br /> * A couple of pins on the programmer connector to allow UART while developing (currently there is a TX test point on PCB). (Note: There's ARM SemiHosting and Segger RTT)<br /> * Connect the pin of LCD controller that allows RD/WR from it in order to save RAM on the MCU.<br /> * LCD must be centered on case. Currently is not and watchfaces seems different when clock is put on the other wrist.<br /> * A NFC antenna around the case, connected to the NFC pins.<br /> * BMA421 accelerometer doesn't have a datasheet (it seems private to some hardware integrators): take it off and put alternative with open documentation.<br /> <br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_Hardware_Wishlist&diff=9340 2021-02-24T21:22:19Z

<p>Avamander: </p> <hr /> <div>This page contains a list of things people wish PineTime did differently<br /> <br /> === Hardware ===<br /> <br /> * Long pressing the button should power-cycle the watch without any software being involved<br /> * Used sensors should be NDA-free and preferably also blob-free<br /> * Other display tech could be explored. [//en.Wikipedia.org/wiki/Transflective_liquid-crystal_display A transflective LCD] would probably be a nice option. Or potentially OLED?<br /> * Touchscreen should possibly have a configurable sensitivity level for both glove-wearing and droplet-resistance. Preferably it should still be a capacitive one, a resistive touchscreen would have too many trade-offs.<br /> * A slightly bigger 256×256 pixel graphics display size is preferable for its binary alignment, affording some low-level simplicity – it has the property that its X and Y coördinates are each addressable with a single byte, with no out-of-bounds; its total number of pixels is 65536 (another power of 2), and each pixel is addressable with exactly 2 bytes, with perfect efficiency. The [http://Pelulamu.net/ibniz IBNIZ (Ideally Bare Numeric Impression giZmo) virtual machine], designed for fun minimalist demoscene graphics, has chosen 256×256 for its virtual display, and makes use of these simplicity advantages. If PineTime also chose 256×256 then it would be a target platform for unclipped IBNIZ demoscene programmes, which would be really fun to play around with on one's wrist!<br /> * A full redraw on the display takes 120ms at the very least, which is 8Hz. A smooth scrolling/usage/animation experience would be 30Hz minimum, preferably 60. I heard a rumor that the SPI connection to the display is a bottleneck. Can this be fixed?<br /> * Some sort of scroll wheel would be nice for convenience.<br /> * Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)<br /> * Wireless charging, or Qi Charging capability<br /> * An external RTC circuit saving the current time to allow the main MCU go to deep-sleep.<br /> * nRF5340 update: QSPI, CryptoCell + Secure Key Storage, has more RAM, a coprocessor and the possibility to expose USB through power pins<br /> * Version without sensors but maybe bigger battery<br /> * A couple of pins on the programmer connector to allow UART while developing (currently there is a TX test point on PCB). (Note: There's ARM SemiHosting and Segger RTT)<br /> * Connect the pin of LCD controller that allows RD/WR from it in order to save RAM on the MCU.<br /> * LCD must be centered on case. Currently is not and watchfaces seems different when clock is put on the other wrist.<br /> * A NFC antenna around the case, connected to the NFC pins.<br /> * BMA421 accelerometer doesn't have a datasheet (it seems private to some hardware integrators): take it off and put alternative with open documentation.<br /> <br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=PineTime_FAQ&diff=9339 2021-02-24T21:19:47Z

<p>Avamander: </p> <hr /> <div>=== Does PineTime run Linux? ===<br /> <br /> No. [https://forum.pine64.org/showthread.php?tid=8112 Please read this forum article] for information about Linux on PineTime. Also check out the article [https://lupyuen.github.io/pinetime-rust-mynewt/articles/pinetime &quot;PineTime doesn't run Linux... But that's OK!&quot;]<br /> <br /> === Why are there two versions of the PineTime in the store? ===<br /> See the below question and answer<br /> <br /> === Why can I only buy the closed version in a 3-pack, and the open version per one? ===<br /> <br /> TL:DR: The open PineTime is to develop on, The closed one only for production use, because of firmware uploads. That is why they are sold per 3. <br /> <br /> In the current situation in development there are some reasons to want to be sure you only experiment with an open device. If you install the wrong firmware, your device could be bricked, until you find a way to open it, which will likely damage the device.<br /> The idea is that if you want to develop an application for the PineTime, you will be testing it out first, and only after you know for sure your new firmware is well tested, you will install it on deployment devices. If you are in the deploy stage, having more than one PineTime is likely the point. So to prevent people from locking themselves out at the first test, it was decided to sell the closed version only as a pack of 3. Development can be done on an open device, so any issues can be easily handled.<br /> <br /> === How long does it take to ship my PineTime? ===<br /> <br /> That depends on whether you chose for Standard or Express shipping. Standard shipping for the dev kit may take up to a few weeks.<br /> <br /> === How do I install new software on PineTime? ===<br /> <br /> The nRF Connect mobile app (Android and iOS) may also be used to update the firmware on your PineTime. See [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#download-and-test-our-pinetime-firmware &quot;Download and Test Our PineTime Firmware&quot;]<br /> <br /> Also see [[Reprogramming_the_PineTime|this page to see various methods of reprogramming the devkit PineTime the wired way]].<br /> <br /> If you have a Sealed PineTime, flash only Certified PineTime Firmware to your PineTime. If you flash non-Certified PineTime Firmware, your Sealed PineTime may be bricked permanently.<br /> <br /> The only Certified PineTime Firmware available today is [https://github.com/JF002/InfiniTime/releases/tag/0.14.0 InfiniTime 0.14.0]. Download the file &quot;dfu-0.14.0.zip&quot; under &quot;Assets&quot; and flash to PineTime with nRF Connect. Refer to the instructions here: [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#download-and-test-our-pinetime-firmware &quot;Download and Test Our PineTime Firmware&quot;]<br /> <br /> Remember to validate the firmware after flashing: Swipe up to show the menu, tap the Ticks icon, tap &quot;Validate&quot;<br /> <br /> === My PineTime arrived, now what? ===<br /> <br /> You should start by testing out all the features of the watch, to make sure everything works. Power it on and check the display.<br /> <br /> PineTime is shipped with InfiniTime firmware. Press the watch button to show the clock, then swipe up on the touchscreen to reveal the menu.<br /> <br /> On your Android phone, install the nRF Connect mobile app to sync the date and time with PineTime. See [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#set-pinetime-date-and-time-with-nrf-connect &quot;Set PineTime Date and Time with nRF Connect&quot;] (nRF Connect on iOS can't be used for setting the date and time, because it doesn't implement the GATT Time Service)<br /> <br /> Download the latest Certified PineTime Firmware (see the previous question) and flash to PineTime with nRF Connect. Refer to the instructions here: [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#download-and-test-our-pinetime-firmware &quot;Download and Test Our PineTime Firmware&quot;]<br /> <br /> Remember to validate the firmware after flashing: Swipe up to show the menu, tap the Ticks icon, tap &quot;Validate&quot;<br /> <br /> === What's the OS that's preinstalled on the PineTime by default? ===<br /> <br /> PineTime ships with the open source [https://github.com/JF002/InfiniTime InfiniTime firmware].<br /> <br /> To support firmware update and rollback, PineTime includes the open source [https://lupyuen.github.io/pinetime-rust-mynewt/articles/mcuboot MCUBoot Bootloader].<br /> <br /> === Can we use this OS or its source code? ===<br /> <br /> Yes, [https://github.com/JF002/InfiniTime InfiniTime] and the [https://lupyuen.github.io/pinetime-rust-mynewt/articles/mcuboot MCUBoot Bootloader] are open source.<br /> <br /> === Why is the back exposed? Is it supposed to snap on? ===<br /> <br /> The back cover of the PineTime dev kit is exposed so that you can flash and debug the device with the SWD pins. The main unit and cover does not snap (lock) together. If you want to attach the back cover anyway, you can use glue or tape.<br /> <br /> === What hardware should I use to flash code to the PineTime? ===<br /> <br /> There are several ways you can do this, check out [[Reprogramming the PineTime]]<br /> <br /> === How do I connect the PineTime to a programmer? ===<br /> <br /> Here's how: [[PineTime devkit wiring]]<br /> <br /> === How do I set the time on PineTime? ===<br /> <br /> You can use either nRF Connect, custom GadgetBridge build or the proprietary Da Fit app. See [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#set-pinetime-date-and-time-with-nrf-connect &quot;Set PineTime Date and Time with nRF Connect&quot;]<br /> <br /> You can also set the time using your PinePhone or other Linux-based Bluetooth LE capable device with the Bluez software installed. Install the bluez package and make sure your PineTime is running and awake with InfiniTime 0.7.1 or later.<br /> <br /> $ bluetoothctl<br /> [ bluetooth ]# scan on<br /> ...<br /> [NEW] Device D7:03:FB:6E:31:B2 Pinetime-JF<br /> ...<br /> [bluetooth]# pair D7:03:FB:6E:31:B2<br /> Attempting to pair with D7:03:FB:6E:31:B2<br /> ...<br /> [NEW] Characteristic (Handle 0xfd80)<br /> /org/bluez/hci0/dev_D7_03_FB_6E_31_B2/service0015/char0016<br /> 00002a2b-0000-1000-8000-00805f9b34fb<br /> Current Time<br /> ...<br /> [Pinetime-JF]# menu gatt<br /> ...<br /> [Pinetime-JF]# select-attribute /org/bluez/hci0/dev_D7_03_FB_6E_31_B2/service0015/char0016<br /> [Pinetime-JF:/service0015/char0016]# read<br /> Attempting to read /org/bluez/hci0/dev_D7_03_FB_6E_31_B2/service0015/char0016<br /> [CHG] Attribute /org/bluez/hci0/dev_D7_03_FB_6E_31_B2/service0015/char0016 Value:<br /> b2 07 01 01 00 04 15 00 00 ......... <br /> b2 07 01 01 00 04 15 00 00 .........<br /> [Pinetime-JF:/service0015/char0016]# write &quot;0xe4 0x07 0x0c 0x1f 0x0e 0x02 0x00 0x00 0x00&quot;<br /> <br /> This is the format for the current time as hex bytes:<br /> &lt;lsb of year&gt; &lt;msb of year&gt; &lt;month (1-12)&gt; &lt;day (1-31)&gt; &lt;hour (0-23)&gt; &lt;minute (0-59)&gt; &lt;seconds (0-59)&gt; &lt;weekday (1-7 where 1=Monday)&gt; &lt;fractions (1/256th of second)&gt;<br /> <br /> === Is there a standard agreed method of pushing OTA updates so that one could seal the PineTime dev kit nicely? ===<br /> <br /> InfiniTime supports firmware updates over Bluetooth LE with the nRF Connect mobile app. See [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud#download-and-test-our-pinetime-firmware &quot;Download and Test Our PineTime Firmware&quot;]<br /> <br /> === My PineTime's screen shows garbage, how do I fix it? ===<br /> <br /> This is usually caused by unplugging the device after it has booted, it needs to be reinitialised. To do so just restart the watch by removing power to it.<br /> <br /> === I have experience developing on Arduino. How does the PineTime compare? ===<br /> <br /> To learn programming on PineTime, [https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud check out this article]<br /> <br /> Arduino provides the Arduino IDE (or you use the avr-gcc and avrdude command-line tools) which you can use to compile and upload code to an Arduino board. The PineTime and its ARM processor doesn't have this, so you'll have to familiarize yourself with tools like GCC for ARM, and OpenOCD. Some experience with Arduino does translate over to the PineTime, especially if you've worked with LCD's, or SPI. The PineTime is at least four times faster than an Arduino Uno (even faster at certain specific workloads due to hardware acceleration), and it has 32 times more RAM and 16 times more flash storage.<br /> <br /> [https://github.com/lupyuen/ Lup Yuen Lee] (just call him Lup, rhymes with &quot;Up&quot;) has written many articles on PineTime programming. [https://lupyuen.github.io/ Check out the articles here]<br /> <br /> === Can I code firmware for PineTime without an actual PineTime? ===<br /> <br /> Yes, you may code PineTime Watch Faces and preview them in a web browser (thanks to WebAssembly)...<br /> <br /> [https://lupyuen.github.io/pinetime-rust-mynewt/articles/simulator PineTime Simulator]<br /> <br /> Then flash your firmware remotely to a real PineTime via Telegram, and watch your firmware run in a live video stream...<br /> <br /> [https://github.com/lupyuen/remote-pinetime-bot/blob/master/README.md Remote PineTime]<br /> <br /> === What do I need for building PineTime firmware locally on my computer? ===<br /> <br /> Most flavours of PineTime firmware (InfiniTime, Hypnos, Klok, wasp-os) will build fine on Linux (x64, Arm32, Arm64) and macOS. Just follow the instructions provided.<br /> <br /> Download version 9-2020-q2-update of the [https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads Arm Embedded Toolchain arm-none-eabi-gcc]. Other versions of gcc may have problems building the firmware correctly.<br /> <br /> On Windows, install [https://docs.microsoft.com/en-us/windows/wsl/about Windows Subsystem for Linux (WSL)] and execute the build steps inside the WSL Terminal (instead of the Windows Command Prompt). USB Programmers (like ST-Link and JLink) are not supported in WSL, so use the Windows Command Prompt to flash your built firmware to PineTime.<br /> <br /> [https://github.com/lupyuen/pinetime-rust-mynewt/blob/master/README.md pinetime-rust-mynewt] firmware for PineTime supports building and flashing via the Windows Command Prompt (no need for MinGW and Docker).<br /> <br /> === Can I use Pinebook Pro for developing PineTime? ===<br /> <br /> Yes, use version 9-2020-q2-update of the [https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads Arm Embedded Toolchain arm-none-eabi-gcc]. Other versions of gcc may have problems building the firmware correctly.<br /> <br /> === What is ARM Semihosting? ===<br /> <br /> We use the SWD (Single Wire Debug) protocol created by ARM for flashing and debugging PineTime's nRF52832 microcontroller, which contains an ARM CPU. (SWD is derived from standard JTAG, but with fewer wires) With ARM CPUs you can trigger a software breakpoint, and allow the debugger (OpenOCD) to do something really nifty: Display a message, read console input, dump out a file, even read a file. That's called ARM Semihosting. [http://www.keil.com/support/man/docs/armcc/armcc_pge1358787046598.htm More about ARM Semihosting]<br /> <br /> === What is OpenOCD? ===<br /> <br /> OpenOCD is Open On-Chip Debugger. It's the software that drives your microcontroller debugger/flasher. We need it for running any kind of flashing and debugging with Pi or ST-Link. gdb talks to OpenOCD for debugging firmware. gdb also works with VSCode for debugging firmware visually. [http://openocd.org/doc-release/html/About.html#What-is-OpenOCD_003f More about OpenOCD]<br /> <br /> Please use [https://xpack.github.io/openocd xPack OpenOCD] with PineTime. Other versions of OpenOCD seem to have problems with PineTime.<br /> <br /> === How do I remove flash protection? ===<br /> <br /> PineTime watches shipped before 20 Sep 2020 have flash protection enabled.<br /> <br /> The flash protection can be removed using multiple different methods. If you don't have anything except the PineTime, not even a Raspberry Pi, then you have to order a programmer online: you can use a J-Link, CMSIS-DAP dongle and various other programmers. See [[Reprogramming_the_PineTime|this page to see various methods of reprogramming the PineTime]].<br /> <br /> If your PineTime was shipped after 20 Sep 2020, you don't need to remove flash protection. They are shipped with flash protection disabled. You can flash and debug PineTime right away with ST-Link, JLink and Raspberry Pi.<br /> <br /> === Why can't you use ST-Link to remove nRF52 Flash Protection? ===<br /> <br /> Because ST-Link is a High Level Adapter. It doesn't really implement all SWD functions, just a subset (probably to keep the price low). More details in the section &quot;Why Visual Studio Code with ST-Link (instead of nRFgo Studio with J-LINK)&quot; in the article [https://medium.com/@ly.lee/coding-nrf52-with-rust-and-apache-mynewt-on-visual-studio-code-9521bcba6004?source=friends_link&amp;sk=bb4e2523b922d0870259ab3fa696c7da &quot;Coding nRF52 with Rust and Apache Mynewt on Visual Studio Code&quot;].<br /> <br /> === Since we need a low level SWD adapter like Raspberry Pi anyway, can we do everything on a Pi instead of ST-Link + Windows? ===<br /> <br /> Yes, Raspberry Pi works for flashing and debugging PineTime, even for removing flash protection. We have a special version of OpenOCD called OpenOCD SPI that talks to PineTime's SWD port over SPI (without bit-banging). See [https://github.com/lupyuen/pinetime-updater/blob/master/README.md PineTime Updater]<br /> <br /> === Is there a 3D model of PineTime available somewhere? ===<br /> <br /> Not yet. Someone did design a cover you can snap on to keep the back shut. [https://www.thingiverse.com/thing:4172849 More details]<br /> <br /> === Are there any alternatives to the wrist band provided with the PineTime? ===<br /> <br /> No, but PineTime accepts standard 20mm wrist band that is widely available by a third party.<br /> <br /> Note that some sellers have a different point of view on what standard is. So you should always check the fitting to make sure it looks like the one used by PineTime.<br /> <br /> === I'm stuck. How can I get help? ===<br /> <br /> Chat with the PineTime Community on [[PineTime#Community|Matrix / Discord / Telegram / IRC]] (They are bridged into a single chatroom)<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=InfiniTime&diff=9338 2021-02-24T21:17:37Z

<p>Avamander: /* Black screen after a reset in sleep mode */</p> <hr /> <div>== InfiniTime ==<br /> InfiniTime (also known as JF's project, FreeRTOS firmware or Pinetime-JF) is an open source (GPLv3) firmware written in C++ and based on FreeRTOS, LVGL and NimBLE. This firmware (version 0.7.1) is preloaded at the factory since the new batch of PineTime devkits and sealed PineTimes of end of September 2020.<br /> <br /> * Github repo : https://github.com/JF002/InfiniTime<br /> * Official website : https://infinitime.io/<br /> <br /> == Read this first! ==<br /> * PineTime is still considered as a development device. InfiniTime and the bootloader are still in heavy development, and some features might not work as expected.<br /> * OTA is a critical feature which is still considered as risky on sealed devices. There is no known way to recover a sealed device from a failed OTA upgrade.<br /> * There is currently no way to upgrade the bootloader on a sealed device.<br /> * Do not use a sealed PineTime as a development device, there is a lot of chances that you'll brick it.<br /> <br /> == Known issues ==<br /> {{warning|1=Please read this section carefully before upgrading the firmware on your PineTime, especially if you are using a sealed device!}}<br /> === Black screen after a reset in sleep mode ===<br /> ==== Description ====<br /> This issue occurs if you are using the original bootloader (from InfiniTime 0.7.1), upgraded from InfiniTime 0.7.1 to 0.8.2 and the watch resets while the display is OFF : the watch is stuck on a black screen and does not respond to touch, button press or BLE.<br /> <br /> The reset can be triggered by the watchdog or manually by long pressing the button.<br /> <br /> This issue is caused by InfiniTime 0.8.2 that put the external SPI flash memory to sleep before switching the display off and by the bootloader that cannot wake the memory chip up. The bootloader is stuck in an infinite loop.<br /> <br /> More info : https://github.com/lupyuen/pinetime-rust-mynewt/issues/24 and https://github.com/JF002/InfiniTime/issues/60<br /> <br /> ==== Workaround ====<br /> On a development kit, a simple reset via SWD is needed to unlock the bootloader.<br /> <br /> On a sealed device, the only way to work around this issue is to wait for the battery to drain completely before trying again.<br /> <br /> This issue can be avoided by ensuring that the display is ON when manually resetting the device (long push on the button).<br /> <br /> ==== Fixed version ====<br /> This issues is fixed in [https://github.com/JF002/InfiniTime/releases/tag/0.8.3 InfiniTime 0.8.3]<br /> <br /> == Releases == <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.7.1 Version 0.7.1] ===<br /> This is the version that ships with PineTime devkits and sealed PineTime as of September 2020.<br /> * Time synchronization over BLE<br /> * Display brightness setting<br /> * Notifications over BLE<br /> * Integration with AmazFish (SailFishOS) and Gadgetbridge (Android)<br /> * OTA using NRFConnect<br /> <br /> Bootloader : https://github.com/lupyuen/pinetime-rust-mynewt/releases/tag/v4.1.7<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.8.2 Version 0.8.2] ===<br /> * Music control app<br /> * Paint app<br /> * Manual image validation after OTA<br /> <br /> Bootloader : https://github.com/lupyuen/pinetime-rust-mynewt/releases/tag/v5.0.4.<br /> <br /> This new version of the bootloader fixes [[#Black_screen_after_a_reset_in_sleep_mode]] and enables the watchdog before launching the firmware.<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.8.3 Version 0.8.3] ===<br /> * Fixes the &quot;bootloader stuck after a reset&quot; mentioned in 0.8.2 above<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.9.0 Version 0.9.0] ===<br /> * Touch panel fixed (no more freezing)<br /> * Improved music application (possibility to control both volumes and browsing, display the song progression)<br /> * Notification UI rewritten: can now display up to 100 characters<br /> * Improved BLE connectivity<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.10.0 Version 0.10.0] ===<br /> * 2 new games: Pong and 2048<br /> * Fixed display glitches and improved needed time to turn on the display<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.11.0 Version 0.11.0] ===<br /> * Heart-rate sensor application:<br /> * Displays the current value, and when running, this value is also displayed on the clock face<br /> * Value exposed over BLE, meaning other applications can read it (e.g. companion app such as Amazfish)<br /> * Navigation app: InfiNav - works e.g. with PureMaps on SailfishOS<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.12.0 Version 0.12.0] ===<br /> * Improved BLE connection<br /> * OTA updates much more reliable<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.13.0 Version 0.13.0] ===<br /> * Vibration<br /> * Call notification: it is possible to accept/ignore/reject a call from the PineTime<br /> * Music app got nicer icons<br /> * BLE connectivity improved a bit more<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.14.0 Version 0.14.0] ===<br /> * LVGL 7<br /> * Bugfixes to the build process<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=InfiniTime&diff=9337 2021-02-24T21:17:08Z

<p>Avamander: /* Version 0.14.0 */</p> <hr /> <div>== InfiniTime ==<br /> InfiniTime (also known as JF's project, FreeRTOS firmware or Pinetime-JF) is an open source (GPLv3) firmware written in C++ and based on FreeRTOS, LVGL and NimBLE. This firmware (version 0.7.1) is preloaded at the factory since the new batch of PineTime devkits and sealed PineTimes of end of September 2020.<br /> <br /> * Github repo : https://github.com/JF002/InfiniTime<br /> * Official website : https://infinitime.io/<br /> <br /> == Read this first! ==<br /> * PineTime is still considered as a development device. InfiniTime and the bootloader are still in heavy development, and some features might not work as expected.<br /> * OTA is a critical feature which is still considered as risky on sealed devices. There is no known way to recover a sealed device from a failed OTA upgrade.<br /> * There is currently no way to upgrade the bootloader on a sealed device.<br /> * Do not use a sealed PineTime as a development device, there is a lot of chances that you'll brick it.<br /> <br /> == Known issues ==<br /> {{warning|1=Please read this section carefully before upgrading the firmware on your PineTime, especially if you are using a sealed device!}}<br /> === Black screen after a reset in sleep mode ===<br /> ==== Description ====<br /> This issue occurs if you are using the original bootloader (from InfiniTime 0.7.1), upgraded from InfiniTime 0.7.1 to 0.8.2 and the watch resets while the display is OFF : the watch is stuck on a black screen and does not respond to touch, button press or BLE.<br /> <br /> The reset can be triggered by the watchdog or manually by long pressing the button.<br /> <br /> This issue is caused by InfiniTime 0.8.2 that put the external SPI flash memory to sleep before switching the display off and by the bootloader that cannot wake the memory chip up. The bootloader is stuck in an infinite loop.<br /> <br /> More info : https://github.com/lupyuen/pinetime-rust-mynewt/issues/24 and https://github.com/JF002/Pinetime/issues/60<br /> <br /> ==== Workaround ====<br /> On a development kit, a simple reset via SWD is needed to unlock the bootloader.<br /> <br /> On a sealed device, the only way to work around this issue is to wait for the battery to drain completely before trying again.<br /> <br /> This issue can be avoided by ensuring that the display is ON when manually resetting the device (long push on the button).<br /> <br /> ==== Fixed version ====<br /> This issues is fixed in [https://github.com/JF002/Pinetime/releases/tag/0.8.3 InfiniTime 0.8.3]<br /> <br /> == Releases == <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.7.1 Version 0.7.1] ===<br /> This is the version that ships with PineTime devkits and sealed PineTime as of September 2020.<br /> * Time synchronization over BLE<br /> * Display brightness setting<br /> * Notifications over BLE<br /> * Integration with AmazFish (SailFishOS) and Gadgetbridge (Android)<br /> * OTA using NRFConnect<br /> <br /> Bootloader : https://github.com/lupyuen/pinetime-rust-mynewt/releases/tag/v4.1.7<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.8.2 Version 0.8.2] ===<br /> * Music control app<br /> * Paint app<br /> * Manual image validation after OTA<br /> <br /> Bootloader : https://github.com/lupyuen/pinetime-rust-mynewt/releases/tag/v5.0.4.<br /> <br /> This new version of the bootloader fixes [[#Black_screen_after_a_reset_in_sleep_mode]] and enables the watchdog before launching the firmware.<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.8.3 Version 0.8.3] ===<br /> * Fixes the &quot;bootloader stuck after a reset&quot; mentioned in 0.8.2 above<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.9.0 Version 0.9.0] ===<br /> * Touch panel fixed (no more freezing)<br /> * Improved music application (possibility to control both volumes and browsing, display the song progression)<br /> * Notification UI rewritten: can now display up to 100 characters<br /> * Improved BLE connectivity<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.10.0 Version 0.10.0] ===<br /> * 2 new games: Pong and 2048<br /> * Fixed display glitches and improved needed time to turn on the display<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.11.0 Version 0.11.0] ===<br /> * Heart-rate sensor application:<br /> * Displays the current value, and when running, this value is also displayed on the clock face<br /> * Value exposed over BLE, meaning other applications can read it (e.g. companion app such as Amazfish)<br /> * Navigation app: InfiNav - works e.g. with PureMaps on SailfishOS<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.12.0 Version 0.12.0] ===<br /> * Improved BLE connection<br /> * OTA updates much more reliable<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.13.0 Version 0.13.0] ===<br /> * Vibration<br /> * Call notification: it is possible to accept/ignore/reject a call from the PineTime<br /> * Music app got nicer icons<br /> * BLE connectivity improved a bit more<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.14.0 Version 0.14.0] ===<br /> * LVGL 7<br /> * Bugfixes to the build process<br /> <br /> [[Category:PineTime]]</div>

Avamander https://wiki.pine64.org/index.php?title=InfiniTime&diff=9336 2021-02-24T21:16:53Z

<p>Avamander: </p> <hr /> <div>== InfiniTime ==<br /> InfiniTime (also known as JF's project, FreeRTOS firmware or Pinetime-JF) is an open source (GPLv3) firmware written in C++ and based on FreeRTOS, LVGL and NimBLE. This firmware (version 0.7.1) is preloaded at the factory since the new batch of PineTime devkits and sealed PineTimes of end of September 2020.<br /> <br /> * Github repo : https://github.com/JF002/InfiniTime<br /> * Official website : https://infinitime.io/<br /> <br /> == Read this first! ==<br /> * PineTime is still considered as a development device. InfiniTime and the bootloader are still in heavy development, and some features might not work as expected.<br /> * OTA is a critical feature which is still considered as risky on sealed devices. There is no known way to recover a sealed device from a failed OTA upgrade.<br /> * There is currently no way to upgrade the bootloader on a sealed device.<br /> * Do not use a sealed PineTime as a development device, there is a lot of chances that you'll brick it.<br /> <br /> == Known issues ==<br /> {{warning|1=Please read this section carefully before upgrading the firmware on your PineTime, especially if you are using a sealed device!}}<br /> === Black screen after a reset in sleep mode ===<br /> ==== Description ====<br /> This issue occurs if you are using the original bootloader (from InfiniTime 0.7.1), upgraded from InfiniTime 0.7.1 to 0.8.2 and the watch resets while the display is OFF : the watch is stuck on a black screen and does not respond to touch, button press or BLE.<br /> <br /> The reset can be triggered by the watchdog or manually by long pressing the button.<br /> <br /> This issue is caused by InfiniTime 0.8.2 that put the external SPI flash memory to sleep before switching the display off and by the bootloader that cannot wake the memory chip up. The bootloader is stuck in an infinite loop.<br /> <br /> More info : https://github.com/lupyuen/pinetime-rust-mynewt/issues/24 and https://github.com/JF002/Pinetime/issues/60<br /> <br /> ==== Workaround ====<br /> On a development kit, a simple reset via SWD is needed to unlock the bootloader.<br /> <br /> On a sealed device, the only way to work around this issue is to wait for the battery to drain completely before trying again.<br /> <br /> This issue can be avoided by ensuring that the display is ON when manually resetting the device (long push on the button).<br /> <br /> ==== Fixed version ====<br /> This issues is fixed in [https://github.com/JF002/Pinetime/releases/tag/0.8.3 InfiniTime 0.8.3]<br /> <br /> == Releases == <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.7.1 Version 0.7.1] ===<br /> This is the version that ships with PineTime devkits and sealed PineTime as of September 2020.<br /> * Time synchronization over BLE<br /> * Display brightness setting<br /> * Notifications over BLE<br /> * Integration with AmazFish (SailFishOS) and Gadgetbridge (Android)<br /> * OTA using NRFConnect<br /> <br /> Bootloader : https://github.com/lupyuen/pinetime-rust-mynewt/releases/tag/v4.1.7<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.8.2 Version 0.8.2] ===<br /> * Music control app<br /> * Paint app<br /> * Manual image validation after OTA<br /> <br /> Bootloader : https://github.com/lupyuen/pinetime-rust-mynewt/releases/tag/v5.0.4.<br /> <br /> This new version of the bootloader fixes [[#Black_screen_after_a_reset_in_sleep_mode]] and enables the watchdog before launching the firmware.<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.8.3 Version 0.8.3] ===<br /> * Fixes the &quot;bootloader stuck after a reset&quot; mentioned in 0.8.2 above<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.9.0 Version 0.9.0] ===<br /> * Touch panel fixed (no more freezing)<br /> * Improved music application (possibility to control both volumes and browsing, display the song progression)<br /> * Notification UI rewritten: can now display up to 100 characters<br /> * Improved BLE connectivity<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.10.0 Version 0.10.0] ===<br /> * 2 new games: Pong and 2048<br /> * Fixed display glitches and improved needed time to turn on the display<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.11.0 Version 0.11.0] ===<br /> * Heart-rate sensor application:<br /> * Displays the current value, and when running, this value is also displayed on the clock face<br /> * Value exposed over BLE, meaning other applications can read it (e.g. companion app such as Amazfish)<br /> * Navigation app: InfiNav - works e.g. with PureMaps on SailfishOS<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.12.0 Version 0.12.0] ===<br /> * Improved BLE connection<br /> * OTA updates much more reliable<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.13.0 Version 0.13.0] ===<br /> * Vibration<br /> * Call notification: it is possible to accept/ignore/reject a call from the PineTime<br /> * Music app got nicer icons<br /> * BLE connectivity improved a bit more<br /> <br /> === [https://github.com/JF002/InfiniTime/releases/tag/0.14.0 Version 0.14.0] ===<br /> * **LVGL 7**<br /> * Bugfixes to the build process<br /> <br /> [[Category:PineTime]]</div>

Avamander