PINE64 - Development Discussion on PineTime

Update pinetime bootloader OTA?

Sat, 04 Oct 2025 21:25:01 +0000

Hi, I'm trying to upload a modified pinetime bootloader using the reloader-mcuboot-1.0.1.zip from https://github.com/InfiniTimeOrg/pinetim.../tag/1.0.1
I tried with the simplest test possible changing the version of the header to 2.0.0 in the reloader-mcuboot.bin of the reloader-mcuboot.zip with:
"printf '\x02\x00\x00\x00\x00\x00\x00\x00' | dd of=reloader-mcuboot.bin bs=1 seek=$((0x14)) conv=notrunc"
and build it again with the same command of the Makefile:
"python3 -m nordicsemi dfu genpkg --dev-type 0x0052 --application reloader-mcuboot.bin reloader-mcuboot.zip"
After uploading the zip with Watchmate for Linux I got the image is ok but the InfiniTime shows the same version for the bootloader "1.0.1".
It is still possible to update the bootloader OTA? I'm missing something? Thank you!
Last try was using: Python 3.10.13, adafruit-nrfutil version 0.5.3.post16

wasp-os bluetooth dev documentation?

Thu, 16 Jan 2025 21:43:17 +0000

Having a bit of a time trying to develop bluetooth on the PineTime under wasp-os 0.4.

There is little documentation about this from what ive seen, but Ive figured out that I need to use ubluepy, and set up and advertise a service. I can do this, but it nukes the Nordic UART Service, leaving development from that point problematic. Ive tried adding the NUS service and characteristics using the UUID's found in pynus, but the app fails to load when I do so with very little information about whats wrong.

Any ideas on how to move forward?

keep state across invocations

Thu, 31 Oct 2024 19:06:29 +0000

In InfiniTime, is there a way for my screen (app) to maintain some state across invocations? E.g. for app settings, but also for a stopwatch/timer that can resume even if the user switched to another screen and back. I would just store the time point at which the stopwatch/timer started, and then recompute the elapsed/remaining time from the current time point when it is reopened.

multithreading issue / SIGSEGV under InfiniSim

Sat, 26 Oct 2024 15:57:44 +0000

I get various crashes/SIGSEGV/SIGFPE/uncaught exceptions/"mutex released when not held"/... when running InfiniTime under InfiniSim.

I opened the discussion for one of the reproducible ones at https://github.com/InfiniTimeOrg/InfiniSim/issues/160

Another reproducible one seems too subtle / incomprehensible for me, and it seems to me that different threads get mixed up. I was hoping someone here would have more clue than me.

The backtrace looks like:

Code:
Thread 5 "displayapp" received signal SIGSEGV, Segmentation fault.

[Switching to Thread 0x7fffe29fe6c0 (LWP 642677)]

0x00005555555cf26b in lv_refr_obj (obj=0x7ffff79f1c, mask_ori_p=0x7fffe29fdb2e) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_core/lv_refr.c:892

892        if(obj->hidden != 0) return;

(gdb) bt

#0  0x00005555555cf26b in lv_refr_obj (obj=0x7ffff79f1c, mask_ori_p=0x7fffe29fdb2e) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_core/lv_refr.c:892

#1  0x00005555555cf1d6 in lv_refr_obj_and_children (top_p=0x555556bb96c8, mask_p=0x7fffe29fdb2e) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_core/lv_refr.c:867

#2  0x00005555555cef04 in lv_refr_area_part (area_p=0x7fffdc0017c2) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_core/lv_refr.c:773

#3  0x00005555555ce3d6 in lv_refr_area (area_p=0x7fffdc0017c2) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_core/lv_refr.c:515

#4  0x00005555555cdf7a in lv_refr_areas () at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_core/lv_refr.c:405

#5  0x00005555555cd9ba in _lv_disp_refr_task (task=0x7fffdc001918) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_core/lv_refr.c:204

#6  0x00005555555e53e4 in lv_task_exec (task=0x7fffdc001918) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_misc/lv_task.c:386

#7  0x00005555555e4e6f in lv_task_handler () at /home/master/src/pinetime/InfiniSim/InfiniTime/src/libs/lvgl/src/lv_misc/lv_task.c:134

#8  0x00005555555af57a in Pinetime::Applications::DisplayApp::Refresh (this=0x5555556a4ae0 ) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/displayapp/DisplayApp.cpp:251

#9  0x00005555555af208 in Pinetime::Applications::DisplayApp::Process (instance=0x5555556a4ae0 ) at /home/master/src/pinetime/InfiniSim/InfiniTime/src/displayapp/DisplayApp.cpp:149

#10 0x0000555555609dec in sdl_function_wrapper (instance=0x5555556a5bf8 ) at /home/master/src/pinetime/InfiniSim/sim/task.cpp:61

Note that according to gdb, in frame 1 lv_refr_obj_and_children is called with top_p=0x555556bb96c8 in thread LWP 642677. I have modified this function to make debug outputs to a file, one file per thread, as follows:

Near the top of the file:

Code:
#include 

#define __USE_GNU

#include 

#undef __USE_GNU

then in the function:

Code:
    char buf[40];

    snprintf(buf, sizeof(buf), "VERBOSE_DEBUG_lv_core_%d.txt", gettid());

    buf[sizeof(buf)-1] = (char)0;

    FILE* vdf = fopen(buf, "a");

and then I fprintf(vdf, ...), in particular I log the value of top_p. Now, the "funny thing" is according to the logs, lv_refr_obj_and_children is called with top_p=0x555556bb96c8 only in thread 642669!

Code:
$ grep -l 96c8 VERBOSE_DEBUG_lv_core_6426*

VERBOSE_DEBUG_lv_core_642669.txt

According to gdb, that thread is:

Code:
Thread 1 (Thread 0x7ffff6e22cc0 (LWP 642669) "infinisim"):

#0  0x00007ffff790d11f in __GI___poll (fds=0x7fffffffdac8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29

29    ../sysdeps/unix/sysv/linux/poll.c: No such file or directory.

(gdb) thread 1

[Switching to thread 1 (Thread 0x7ffff6e22cc0 (LWP 642669))]

#0  0x00007ffff790d11f in __GI___poll (fds=0x7fffffffdac8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29

29    in ../sysdeps/unix/sysv/linux/poll.c

(gdb) bt

#0  0x00007ffff790d11f in __GI___poll (fds=0x7fffffffdac8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29

#1  0x00007ffff71f0d12 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1

#2  0x00007ffff71f2d8f in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1

#3  0x00007ffff71f2f00 in xcb_wait_for_reply64 () from /lib/x86_64-linux-gnu/libxcb.so.1

#4  0x00007ffff743810c in _XReply () from /lib/x86_64-linux-gnu/libX11.so.6

#5  0x00007ffff74336ff in XSync () from /lib/x86_64-linux-gnu/libX11.so.6

#6  0x00007ffff6498166 in ?? () from /lib/x86_64-linux-gnu/libGLX_mesa.so.0

#7  0x00007ffff648823b in ?? () from /lib/x86_64-linux-gnu/libGLX_mesa.so.0

#8  0x00007ffff7ecbbe6 in ?? () from /lib/x86_64-linux-gnu/libSDL2-2.0.so.0

#9  0x00007ffff7e2f276 in ?? () from /lib/x86_64-linux-gnu/libSDL2-2.0.so.0

#10 0x0000555555572074 in Framework::refresh (this=0x7fffffffdee0) at /home/master/src/pinetime/InfiniSim/main.cpp:609

#11 0x000055555556f5d5 in main (argc=1, argv=0x7fffffffe0c8) at /home/master/src/pinetime/InfiniSim/main.cpp:1145

Somehow the threads get mixed up???

According to the logs, that function is called in thread 642677 only with values top_p = 0x7fffdc001958, 0x7fffdc001c58 or 0x7fffdc001d58 and each time it is called, lv_obj_get_parent(top_p) == NULL (this is the value with which par is initialised), meaning the function exits without entering the while(par != NULL) loop, and never enters the lv_refr_obj call where the SIGSEGV happens, which is the one in the loop.

Still according to the logs, in thread 642669, all calls where top_p == 0x555556bb96c8 return, and the last call has another top_p value and has lv_obj_get_parent(top_p) == NULL.

Developing on Mac (M3)

Sun, 22 Sep 2024 13:48:52 +0000

Hi,

I just bought PineTime and started working on my own watch face.

I managed to compile and run LVGL simulator for Mac with M3 (https://docs.lvgl.io/7.11/get-started/pc-simulator.html)

I tested my watch face with the LVGL simulator and it works as I would like it to work. Next step is to try to get my watch face running on the InfiniSim simulator.

I managed to compile the InfiniSim simulator on Mac but it won't start. These are the error messages I get when trying to run the compiled simulator on mac.

Has anyone managed to run the InfiniSim simulator on mac? Any ideas what's going on? I know I might be able to build InfiniTime project itself and upload my new code on my device but I'd feel much more safe if I can verify that the code runs on the simulator first.

Code:
initial free_size = 40360

info:  systemtask task started!

info:  Last reset reason : Reset pin

info:  [SpiNorFlash] Manufacturer : 0, Memory type : 0, memory density : 0

info:  [SpiNorFlash] Wakeup

info:  DISABLE

info:  displayapp task started!

info:  DISABLE

*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'nextEventMatchingMask should only be called from the Main Thread!'

*** First throw call stack:

(

0  CoreFoundation                      0x0000000186420540 __exceptionPreprocess + 176

1  libobjc.A.dylib                    0x0000000185f11eb4 objc_exception_throw + 60

2  AppKit                              0x000000018a37487c -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3164

3  SDL2                                0x000000010502d76c SDL2 + 87916

4  SDL2                                0x000000010502da08 SDL2 + 88584

5  SDL2                                0x00000001050aca00 SDL_DYNAPI_entry + 218324

6  SDL2                                0x00000001050acb30 SDL_DYNAPI_entry + 218628

7  infinisim                          0x0000000104706af8 sdl_event_handler + 44

8  infinisim                          0x00000001046dd328 lv_task_exec + 96

9  infinisim                          0x00000001046dd0a0 lv_task_handler + 536

10  infinisim                          0x00000001046944c8 _ZN8Pinetime12Applications10DisplayApp7RefreshEv + 328

11  infinisim                          0x000000010469433c _ZN8Pinetime12Applications10DisplayApp7ProcessEPv + 88

12  infinisim                          0x000000010470b8bc _Z20sdl_function_wrapperPv + 44

13  SDL2                                0x0000000105037e80 SDL2 + 130688

14  SDL2                                0x000000010503aef8 SDL2 + 143096

15  libsystem_pthread.dylib            0x00000001862ce034 _pthread_start + 136

16  libsystem_pthread.dylib            0x00000001862c8e3c thread_start + 8

)

libc++abi: terminating due to uncaught exception of type NSException

zsh: abort      ./infinisim

Pinetime - Kids with special needs

Wed, 12 Jun 2024 04:42:22 +0000

A friend of mine has a 4-year-old kid who is deaf and now that he's riding a bike they have to chase after him to get his attention. I have discovered that this is common in this particular special-needs community and I purchased 2x pinetimes to see if I could create an app that at the press of a button would make the other watch vibrate. Watches arrived today

I'm pretty comfortable with Linux, Python and development in general but haven't used MicroPython that much.
I would greatly appreciate any tips on this project and plan to share it on Github for other parents in the same situation

COMPLETE

WaspOS is installed on both watches. I'm more comfortable with Python for app dev but can revert to Infinitime if there is reason

TODO Tips are welcome for these (especially if something is/is not possible)

Find some way to pair the two watches over Bluetooth LE. In waspOS I couldn't find a Bluetooth setting to connect the watch to another device but I have found that I can discover the watch with my phone. Ideally, I would have a settings menu in case one watch is damaged and I don't have to embed the connection details in the code but happy to hard code the connection for now
Find some way to trigger the vibration on a software button press or better still, have a background app that sends the Bluetooth message trigger on a double hardware button press would be perfect
Ensure that the devices connect automatically and I'm not sure what to do about battery management. Is there deep sleep on these?
A warning when the device goes out of range would be nice for parents

I'll start chipping away at these but any help would be great. Cheers

Dev/Prod Setup

Sun, 09 Jun 2024 22:32:27 +0000

Hi,
I was wondering if it would be a good idea to buy two watches, one that is for development (dev kit) and another that is for my use (sealed) as in being prod. Would this setup by any means guarantee that if I flash the prod one with a properly tested firmware from the dev watch then I won't brick the prod one? Your thoughts please, thank you!

Regards,
Fady

Infinitime Build problem

Fri, 20 Oct 2023 15:31:21 +0000

Hi guys,

I'm trying to build Infinitime project on my windows machine but with no success. I have been following the steps in:

https://github.com/InfiniTimeOrg/InfiniT...Program.md

I'm stuck in the last step, the make command.

Cmake command:

Code:
Cmake -DARM_NONE_EABI_TOOLCHAIN_PATH="C:/Program Files (x86)/GNU Arm Embedded Toolchain/10 2021.10" -DNRF5_SDK_PATH="C:/Users/blackdev/pinetime/nRF5_SDK_15.3.0_59ac345" -DCMAKE_BUILD_TYPE=Debug -DBUILD_DFU=1 -DBUILD_RESOURCES=1 -DTARGET_DEVICE=PINETIME -S . -B build

Which results in adding the following files inside build folder

Code:
├───CMakeFiles

│   ├───3.28.0-rc2

│   │   ├───CompilerIdASM

│   │   ├───CompilerIdC

│   │   │   ├───Debug

│   │   │   │   └───CompilerIdC.tlog

│   │   │   └───tmp

│   │   ├───CompilerIdCXX

│   │   │   ├───Debug

│   │   │   │   └───CompilerIdCXX.tlog

│   │   │   └───tmp

│   │   └───x64

│   │       └───Debug

│   │           └───VCTargetsPath.tlog

│   ├───58e9d56eaa4cb413b76d7d838cbc8fb1

│   ├───74be971449aa6aebb611e3cfdd9dd126

│   ├───83f795d81ab7de042a55dc014fe330ec

│   ├───CMakeScratch

│   └───pkgRedirects

└───src

    ├───CMakeFiles

    └───displayapp

        └───fonts

            └───CMakeFiles

Then I enter the build folder and I try to use make command as described in the above link

Code:
make -j4 pinetime-app

It doesn't work, it says:
"make: *** No rule to make target 'pinetime-app'. Stop."

I also tried make -j4, but similar issue.

Any hints and guidance would be greatly appreciated.

Thanks

Schematics for components not on the main board

Fri, 22 Sep 2023 14:24:39 +0000

Hello, I've been looking at the PineTime schematics, and I don't see any documentation on what is connected to the other ends of the various connectors on the main board. Is there some additional documentation about those components? For example, I'm curious on what is attached to the KEY connector - I can't quite tell from the main board schematic what exactly would go on the other end.

Is Dev kit still a must for application programming in 2023? thx

Tue, 19 Sep 2023 04:10:34 +0000

hi,

1. just ordered a sealed version as i saw people on youtube (likely the leader from wasp-os) could still use bluetooth to flash OS, flash software to pinetime.

2. this post from lwn also claims that unless doing very low level development, otherwise it's not necessary:
PINE64 does sell a developer kit, which has the same hardware as the PineTime but is not sealed, allowing access to pins for resetting and reflashing the watch. Developers who want to work on the bootloader will probably want a developer kit, but, because of the watchdog, it should not be necessary for other development. The developer kit is currently out of stock, but it appears that this is temporary. It is also possible to break the seal and open the watch, but there is a risk of damaging the hardware.

3. i knew sometimes if the watch freezes, having the kit could instantly reboot it and it is more reasonable than wait till it drain, but the kit is semi...either you drill a hole, solder some wires and cover up the watch,
OR it would be one that easily tear away. so, in addition to money (which i could afford next month), there still a lot of DIY to do.

So, i just write some simple programs, esp with help of gpt4 for application. if it freezed once/twice per month, i am ok to wait till it drain.
then can i avoid the dev kit? avoid the soldering and drilling as i dont have these DIY tools myself.

thanks

ref:
https://lwn.net/Articles/941796/

Bluetooth BLE-MIDI-controller app for PineTime / InfiniTime

Sun, 20 Aug 2023 11:17:22 +0000

Hi there,

I've made a BLE-MIDI-controller app for PineTime, which can send MIDI-data over BLE to music synthesizers:
https://codeberg.org/Luno/InfiniTime_ble-midi

Python programme for a vibration signal from Raspberry Pi 4 via bluetooth connection

Thu, 01 Jun 2023 07:33:33 +0000

Hi,
please, I need some help to make a vibration signal, if possible with adjustable vibration-length, out from a Python programme from a Raspberry Pi 4 via bluetooth connection.

Best regards,
Gerald

Zephyr Backlight Examples for PineTime

Sat, 06 May 2023 20:54:09 +0000

This is a very junior question but I am just trying to get the backlight going using Zephyr, VS Code (with nRF Connect for VS Code Add-In), the PineTime DevKit0 board in Zephyr, and a PineTime DK.

I am trying to figure out how to do the backlight from the button example (which replaced the board specific example). I have not been able to get it working. It uses code like this:

Code:
static const struct gpio_dt_spec button = GPIO_DT_SPEC_GET_OR(SW0_NODE, gpios,

                                  {0});

static struct gpio_callback button_cb_data;

/*

 * The led0 devicetree alias is optional. If present, we'll use it

 * to turn on the LED whenever the button is pressed.

 */

static struct gpio_dt_spec led = GPIO_DT_SPEC_GET_OR(DT_ALIAS(led0), gpios,

                             {0});

void button_pressed(const struct device *dev, struct gpio_callback *cb,

            uint32_t pins)

{

    printk("Button pressed at %" PRIu32 "\n", k_cycle_get_32());

}

void main(void)

{

    int ret;

    if (!device_is_ready(button.port)) {

        printk("Error: button device %s is not ready\n",

               button.port->name);

        return;

    }

    ret = gpio_pin_configure_dt(&button, GPIO_INPUT);

    if (ret != 0) {

        printk("Error %d: failed to configure %s pin %d\n",

               ret, button.port->name, button.pin);

        return;

    }

    ret = gpio_pin_interrupt_configure_dt(&button,

                          GPIO_INT_EDGE_TO_ACTIVE);

    if (ret != 0) {

        printk("Error %d: failed to configure interrupt on %s pin %d\n",

            ret, button.port->name, button.pin);

        return;

    }

...

}

These other examples:

pinetime-zephyr/main.c at master · najnesnaj/pinetime-zephyr · GitHub

[/url][url=https://github.com/albsod/pinetime-hypnos/blob/master/app/hypnos/src/backlight.c]pinetime-hypnos/backlight.c at master · albsod/pinetime-hypnos · GitHub

pinetime/backlight.c at develop · ck-telecom/pinetime · GitHub

Use code which looks like this:

Code:
#if DT_NODE_HAS_STATUS(LED0_NODE, okay)

#define LED0    DT_GPIO_LABEL(LED0_NODE, gpios)

#define PIN     DT_GPIO_PIN(LED0_NODE, gpios)

#define FLAGS   DT_GPIO_FLAGS(LED0_NODE, gpios)

#endif

static void backlight_init(void)

{

        const struct device *dev;

        dev = device_get_binding(LED0);

        /* If you have a backlight, set it up and turn it on here */

        gpio_pin_configure(dev, PIN, GPIO_OUTPUT_ACTIVE | FLAGS);

        gpio_pin_set(dev, PIN, 1);

}

or this:

Code:
/* ********** ********** DEFINES ********** ********** ********** */

#define BACKLIGHT_PORT  DT_GPIO_LABEL(DT_ALIAS(led1), gpios)

#define BACKLIGHT_1     DT_GPIO_PIN(DT_ALIAS(led0), gpios)

#define BACKLIGHT_2     DT_GPIO_PIN(DT_ALIAS(led1), gpios)

#define BACKLIGHT_3     DT_GPIO_PIN(DT_ALIAS(led2), gpios)

/* ********** **********  ********** ********** ********** */

/* ********** ********** VARIABLES AND STRUCTS ********** ********** */

static const struct device* backlight_dev;

static bool backlight_enabled = false;

/* ********** ********** ********** ********** ********** ********** */

/* ********** ********** FUNCTIONS ********** ********** */

void backlight_init()

{

    backlight_dev = device_get_binding(BACKLIGHT_PORT);

    gpio_pin_configure(backlight_dev, BACKLIGHT_1, GPIO_OUTPUT);

    gpio_pin_configure(backlight_dev, BACKLIGHT_2, GPIO_OUTPUT);

    gpio_pin_configure(backlight_dev, BACKLIGHT_3, GPIO_OUTPUT);

    backlight_enable(true);

    LOG_DBG("Backlight init: Done");

}

I guess my questions is should I try to use the GPIO_DT_SPEC_GET_OR syntax or DT_GPIO_PIN, DT_GPIO_LABEL, and DT_GPIO_FLAGS.

I'm really new at this, as you can probably tell. I might be mixing things up. Trying to figure out the GPIO to turn on/off the backlight and it seems like this commonly/historically used device* structure and the gpio_dt_spec from the examples.

Realtime heartrate and accelerometer via bluetooth

Mon, 01 May 2023 11:40:44 +0000

Hello!

I'm working on an interactive installation where I want some audio to react to visitors heart rate and activity. I am planning to stream realtime (or every ≈0.5 sec?) the heart rate and accelerometer data to a computer or Rasperry Pi or similar device via Bluetooth. That should be done for several hours a day.

I'm trying to find the perfect smartwatch to do it. Is something that can be done in a Pinetime? From my overview of the device, there should be no problem, but there may be some stuff that I missed. Those more experienced in the platform can advise me on any foreseeable issues?

Thanks!

help on developing BLE bluetooth MIDI

Wed, 05 Apr 2023 18:08:17 +0000

Hi there,

I want BLE-MIDI on the PineTime, overall preferred running in InfiniTime, because it seems the only still active OS. And I really like that OS.
I tried a library from Adafruit, with no success. Then I found this: https://novelbits.io/bluetooth-gatt-serv...teristics/ which explains very detailed how everything works, and I can compile it with Segger development tools (almost: There is a known bug in creating the binary, but that's ok, I don't want to stay on Segger anyway). But I can't find out how I could integrate it into InfiniTime. There are so many dependencies. How can one do something like port a new library?

Best regards,
Luno