Hi!
This subject has been discussed on IRC, but, I'd really want to know where it's from.
So, if anyone have any idea about what's the devkit's default binary, or if there's a repo for it, I'd be really thankful for sharing.
Thanks!
How come noone knows what's have been flashed on those devkits? LCD, touch, Bluetooth and peripherals are testing ok, and there must be an author to this?
Or, the pinout matches another model? But why is it not finished if it's from an existing hardware? And which one?
well, lots of questions here, but absolutely no answer. I digged around other nrf52xx based smatwatches, and i think i have some candidates that matches the PineTime, but no definitive answer yet.
I really hope someone could help us on that, as it apparently contains everything needed to kickstart the development without fiddling around doing what's already have been done by someone aware of the specific hardware of the watch...
thanks.
I don't have my devkit yet so I don't know for sure, but it's likely the firmware from one of the watches which the PineTime is derived from. I highly doubt they are interested in sharing their source code.
Community administrator and sysadmin for PINE64
(Translation: If something breaks on the website, forum, or chat network, I'm a good person to yell at about it)
Moyoung CEO, Mario Mo, is my friend and he allows me to use his binary as an example for PineTime. However, his company making their living based on customize for various smartwatch in market and for sure he will not release the source code to me :-) However, he is already kind enough to allow me reference their schematic and build up the PineTime. Da Fit app with works with the default binary build on PineTime also comes from his company.
Is the pre-installed firmware binary available somewhere? I need to re-flash it to check if my dev kit is still working.
Interesting, my PineTime runs "MOY-TBH3-1.7.8", not "MOY-TBH5-1.7.8".
mine also runs on MOY-TBH3-1.7.8, and i would also love to get the binaries (updated) to flash it back to the device, so that i can use it after my experiments / or to see if the device is working normaly after tampering with own code.