PineTime Hardware Wishlist - Revision history

Fxc: fix

2023-03-16T00:49:34Z

fix

← Older revision		Revision as of 00:49, 16 March 2023
Line 1:		Line 1:
	This page contains a list of things people wish PineTime did differently		This page contains a list of things people wish PineTime did differently

	=== Hardware ===		== Hardware ==

	* Other display technology could be explored.		* Other display technology could be explored.

Avamander at 14:42, 15 January 2023

2023-01-15T14:42:54Z

← Older revision		Revision as of 14:42, 15 January 2023
Line 20:		Line 20:
	** Its total number of pixels is a power of 2 (65536), and each pixel is addressable with exactly 2 bytes.		** Its total number of pixels is a power of 2 (65536), and each pixel is addressable with exactly 2 bytes.
	** 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.		** 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.
	** 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!		*** 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!
	* Full screen refresh is very slow		* Full screen refresh is very slow
	** A full 16-bit redraw on the display takes at worst 120ms, which is 8Hz		** A full 16-bit redraw on the display takes at worst 120ms, which is 8Hz

Avamander at 14:07, 15 January 2023

2023-01-15T14:07:23Z

← Older revision		Revision as of 14:07, 15 January 2023
Line 41:		Line 41:
	*** Significant jump in performance		*** Significant jump in performance
	*** Significant jump in memory and storage, allowing for more features and better UI's		*** Significant jump in memory and storage, allowing for more features and better UI's
	* ~~Preferably~~ a pre-certified MCU module with a ceramic antenna		** Possibly a pre-certified MCU module with a ceramic antenna
	* Version without sensors but maybe bigger battery		* Version without sensors but maybe bigger battery
	* 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)		* 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)

Avamander at 14:06, 15 January 2023

2023-01-15T14:06:58Z

Avamander at 23:05, 16 November 2022

2022-11-16T23:05:01Z

← Older revision		Revision as of 23:05, 16 November 2022
Line 5:		Line 5:
	* Long pressing the button should power-cycle the watch without any software being involved		* Long pressing the button should power-cycle the watch without any software being involved
	* Other display technology could be explored.		* Other display technology could be explored.
			** E-ink
			*** Still images require no power to maintain
	**[//en.Wikipedia.org/wiki/Transflective_liquid-crystal_display A transflective LCD]		**[//en.Wikipedia.org/wiki/Transflective_liquid-crystal_display A transflective LCD]
	*** Increased readability in bright daylight		*** Increased readability in bright daylight
Line 30:		Line 32:
	* Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)		* Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)
	* Wireless charging, or Qi Charging capability		* Wireless charging, or Qi Charging capability
	* nRF5840 update		* Different MCU with more RAM and ROM, higher clock
	** 32MHz HS SPI, QuadSPI, CryptoCell + Secure Key Storage~~, more~~ RAM, a coprocessor ~~and the~~ possibility to expose USB through power pins		** nRF5840 update
			*** 32MHz HS SPI, QuadSPI
			*** CryptoCell + Secure Key Storage
			*** More RAM, a coprocessor
			*** The possibility to expose USB through power pins
			** Ox64/BL808
			*** Open hardware RISC-V based MCU
			*** Significant jump in performance
			*** Significant jump in memory and storage, allowing for more features and better UI's
	* Preferably a pre-certified MCU module with a ceramic antenna		* Preferably a pre-certified MCU module with a ceramic antenna
	* Version without sensors but maybe bigger battery		* Version without sensors but maybe bigger battery
Line 58:		Line 68:
	*** A nano-power system timer IC could in theory provide a RTC, MOSFET-controlled deep sleep, watchdog timer and button-controlled reset		*** A nano-power system timer IC could in theory provide a RTC, MOSFET-controlled deep sleep, watchdog timer and button-controlled reset
	** Built-in "fuel gauge" for better estimation of battery capacity		** Built-in "fuel gauge" for better estimation of battery capacity
	* ~~Small~~ Piezo ~~Buzzer~~		* Improved haptic or audible feedback
			** E.g. small Piezo buzzer
	** Use case would be for very short beeps (think old-school casio watch) as notification.		** Use case would be for very short beeps (think old-school casio watch) as notification.
	** Of course developers can PWM other frequency to make it sing, but piezos tend to be shrill.		** Of course developers can PWM other frequency to make it sing, but piezos tend to be shrill.
	* More RAM and external flash storage
	** Currently, the 64 KB of RAM significantly restricts the possible complexity of the UI and other software.
	** At least 1 MB of RAM would be required to enable more advanced features like text input with spelling checking and more images in the UI.
	** At least 8 MB of flash storage would also be beneficial, as it would significantly increase the potential number of apps and possible functionality of the watch.
	* A built-in microphone		* A built-in microphone
	** Would allow phone call functionality to be built into the watch.		** Would allow phone call functionality to be built into the watch.
	** Could potentially allow for speech recognition for text input.		** Could potentially allow for speech recognition for text input.
	* ~~PineTime Pro based on the Ox64/BL808~~		** Direct access to the external (flash) storage
	** Open hardware RISC-V based MCU
	** Significant jump in performance
	** Significant jump in memory and storage, allowing for more features and better UI's
	** Bluetooth 5.2 with BLE
	** SPI with up to ~~80MHz clock speed, addressing~~ the ~~bottleneck issue posted above~~
	** Only a small jump in price		** Only a small jump in price

	[[Category:PineTime]]		[[Category:PineTime]]

Arteeh: Improve and expand Ox64 suggestion

2022-11-07T10:49:36Z

Improve and expand Ox64 suggestion

← Older revision		Revision as of 10:49, 7 November 2022
Line 32:		Line 32:
	* nRF5840 update		* nRF5840 update
	** 32MHz HS SPI, QuadSPI, CryptoCell + Secure Key Storage, more RAM, a coprocessor and the possibility to expose USB through power pins		** 32MHz HS SPI, QuadSPI, CryptoCell + Secure Key Storage, more RAM, a coprocessor and the possibility to expose USB through power pins
	* PineTime Pro based on the Ox64
	** RISV-V based MCU with high performance, lots of memory, bluetooth 5.2 and peripherals (SPI, I2C, USB)
	* Preferably a pre-certified MCU module with a ceramic antenna		* Preferably a pre-certified MCU module with a ceramic antenna
	* Version without sensors but maybe bigger battery		* Version without sensors but maybe bigger battery
Line 70:		Line 68:
	** Would allow phone call functionality to be built into the watch.		** Would allow phone call functionality to be built into the watch.
	** Could potentially allow for speech recognition for text input.		** Could potentially allow for speech recognition for text input.
			* PineTime Pro based on the Ox64/BL808
			** Open hardware RISC-V based MCU
			** Significant jump in performance
			** Significant jump in memory and storage, allowing for more features and better UI's
			** Bluetooth 5.2 with BLE
			** SPI with up to 80MHz clock speed, addressing the bottleneck issue posted above
			** Only a small jump in price

	[[Category:PineTime]]		[[Category:PineTime]]

Arteeh: Add Ox64 based pinetime idea

2022-11-07T10:10:26Z

Add Ox64 based pinetime idea

← Older revision		Revision as of 10:10, 7 November 2022
Line 32:		Line 32:
	* nRF5840 update		* nRF5840 update
	** 32MHz HS SPI, QuadSPI, CryptoCell + Secure Key Storage, more RAM, a coprocessor and the possibility to expose USB through power pins		** 32MHz HS SPI, QuadSPI, CryptoCell + Secure Key Storage, more RAM, a coprocessor and the possibility to expose USB through power pins
			* PineTime Pro based on the Ox64
			** RISV-V based MCU with high performance, lots of memory, bluetooth 5.2 and peripherals (SPI, I2C, USB)
	* Preferably a pre-certified MCU module with a ceramic antenna		* Preferably a pre-certified MCU module with a ceramic antenna
	* Version without sensors but maybe bigger battery		* Version without sensors but maybe bigger battery

JacobCrume: Added microphone and extended RAM and flash

2022-10-05T11:03:04Z

Added microphone and extended RAM and flash

← Older revision		Revision as of 11:03, 5 October 2022
Line 61:		Line 61:
	** Use case would be for very short beeps (think old-school casio watch) as notification.		** Use case would be for very short beeps (think old-school casio watch) as notification.
	** Of course developers can PWM other frequency to make it sing, but piezos tend to be shrill.		** Of course developers can PWM other frequency to make it sing, but piezos tend to be shrill.
			* More RAM and external flash storage
			** Currently, the 64 KB of RAM significantly restricts the possible complexity of the UI and other software.
			** At least 1 MB of RAM would be required to enable more advanced features like text input with spelling checking and more images in the UI.
			** At least 8 MB of flash storage would also be beneficial, as it would significantly increase the potential number of apps and possible functionality of the watch.
			* A built-in microphone
			** Would allow phone call functionality to be built into the watch.
			** Could potentially allow for speech recognition for text input.

	[[Category:PineTime]]		[[Category:PineTime]]

Avamander at 09:22, 25 October 2021

2021-10-25T09:22:08Z

← Older revision		Revision as of 09:22, 25 October 2021
Line 30:		Line 30:
	* Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)		* Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)
	* Wireless charging, or Qi Charging capability		* Wireless charging, or Qi Charging capability
	* An external RTC circuit
	** Allows the main MCU go to deep-sleep while retaining time.
	** Allows time retention through MCU reset.
	* nRF5840 update		* nRF5840 update
	** 32MHz HS SPI, QuadSPI, CryptoCell + Secure Key Storage, more RAM, a coprocessor and the possibility to expose USB through power pins		** 32MHz HS SPI, QuadSPI, CryptoCell + Secure Key Storage, more RAM, a coprocessor and the possibility to expose USB through power pins
Line 53:		Line 50:
	** 100k still leaks a noticeable amount of power when the button is always on.		** 100k still leaks a noticeable amount of power when the button is always on.
	* Ceramic Bluetooth antenna for better signal reception		* Ceramic Bluetooth antenna for better signal reception
			* An external RTC circuit
			** Allows the main MCU go to deep-sleep while retaining time.
			** Allows time retention through MCU reset.
	* Ultra low quiescent current PMIC		* Ultra low quiescent current PMIC
			** In theory could provide a hard reset capability based on button press
	** Better deep sleep/shipping/storage/off lifetime		** Better deep sleep/shipping/storage/off lifetime
			*** A nano-power system timer IC could in theory provide a RTC, MOSFET-controlled deep sleep, watchdog timer and button-controlled reset
	** Built-in "fuel gauge" for better estimation of battery capacity		** Built-in "fuel gauge" for better estimation of battery capacity
	* Small Piezo Buzzer		* Small Piezo Buzzer

Avamander at 14:43, 3 October 2021

2021-10-03T14:43:03Z

← Older revision		Revision as of 14:06, 15 January 2023
Line 3:		Line 3:
	=== Hardware ===		=== Hardware ===

	* Long pressing the button should power-cycle the watch without any software being involved
	* Other display technology could be explored.		* Other display technology could be explored.
	** E-ink		** E-ink
Line 29:		Line 28:
	** The nRF528(33/40) has one high speed SPI master which supports 32MHz, still well below the ST7789 maximum		** The nRF528(33/40) has one high speed SPI master which supports 32MHz, still well below the ST7789 maximum
	** Parallel data transfer could be an option, but using more GPIOs (which don't look available)		** Parallel data transfer could be an option, but using more GPIOs (which don't look available)
	* Some sort of scroll wheel would be nice ~~for convenience.~~		* Some sort of scroll wheel (and possibly button combination) would be nice as an additional input method
	* Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)		* Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)
	* Wireless charging, or Qi Charging capability		* Wireless charging, or Qi Charging capability
Line 44:		Line 43:
	* Preferably a pre-certified MCU module with a ceramic antenna		* Preferably a pre-certified MCU module with a ceramic antenna
	* Version without sensors but maybe bigger battery		* Version without sensors but maybe bigger battery
	* 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)		* 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)
	* Connect SDO of ST7889 LCD controller to MCU.		* Connect SDO of ST7889 LCD controller to MCU
	** Allows MCU to execute READ commands		** Allows MCU to execute READ commands
	** Possibility of leveraging ST7889 RAM to save MCU RAM?		** Possibility of leveraging ST7889 RAM to save MCU RAM?
Line 51:		Line 50:
	* A NFC antenna around the case, connected to the NFC pins.		* A NFC antenna around the case, connected to the NFC pins.
	* Used sensors should be NDA-free and preferably also blob-free for easier development		* Used sensors should be NDA-free and preferably also blob-free for easier development
	** Possibly replace BMA421 accelerometer		** Possibly replace BMA421 accelerometer with a magnetometer + gyroscope + accelerometer combination
	*** The BMA421 doesn't have a public datasheet		*** The BMA421 doesn't have a public datasheet
	*** Special attention should be paid to advanced features, such as step counting integration or flick detection.		*** Special attention should be paid to advanced features, such as step counting integration or flick detection.
	* PineTime SoC could support USB or have a FTDI chip with the relevant pins exposed.		* 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.		** It could allow flashing a sealed device, just like Arduinos work.
	** Alternatively, an USB-C port could be added that provides these features.		** Alternatively, an USB-C port could be added that provides these features.

← Older revision		Revision as of 14:43, 3 October 2021
Line 44:		Line 44:
	* A NFC antenna around the case, connected to the NFC pins.		* A NFC antenna around the case, connected to the NFC pins.
	* Used sensors should be NDA-free and preferably also blob-free for easier development		* Used sensors should be NDA-free and preferably also blob-free for easier development
	* Possibly replace BMA421 accelerometer		** Possibly replace BMA421 accelerometer
	** The BMA421 doesn't have a public datasheet		*** The BMA421 doesn't have a public datasheet
	** Special attention should be paid to advanced features, such as step counting integration or flick detection.		*** Special attention should be paid to advanced features, such as step counting integration or flick detection.
	* PineTime SoC could support USB or have a FTDI chip with the relevant pins exposed.		* 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.		** It could allow flashing a sealed device, just like Arduinos work.
	** ~~The same~~ USB-C could ~~also~~ be ~~used for charging~~.		** Alternatively, an USB-C port could be added that provides these features.
	* A bigger pulldown resistor for the power button		* A bigger pulldown resistor for the power button
	** 100k still leaks a noticeable amount of power when the button is always on.		** 100k still leaks a noticeable amount of power when the button is always on.
Line 55:		Line 55:
	* Ultra low quiescent current PMIC		* Ultra low quiescent current PMIC
	** Better deep sleep/shipping/storage/off lifetime		** Better deep sleep/shipping/storage/off lifetime
	* ~~Battery charger IC with built~~-in "fuel gauge"		** Built-in "fuel gauge" for better estimation of battery capacity
	** Better estimation of battery capacity
	* Small Piezo Buzzer		* Small Piezo Buzzer
	** Use case would be for very short beeps (think old-school casio watch) as notification.		** Use case would be for very short beeps (think old-school casio watch) as notification.