07-20-2020, 05:14 AM
(06-14-2020, 10:33 AM)mcr314 Wrote: I'm not sure I understand buying the entire Pine*, it's not like these things go exclusively together. In general, you will write code in C on a Unix-platform, probably Linux, maybe MacOS, and if you like cruel and unusual punishment, using the Linux Binary environment on Winblows.
There are a few RTOS that run on PineTime, the one I know is RIOTOS, and you develop that on a Linux desktop/laptop using your favourite editor and make. You program the watch using some python tools that drive the right pins. An Android phone is not involved in writing code for the watch. The watch is designed to communicate over BTLE with a smartphone, and given that Android phones are way easier to debug than Apple iOS phones, since you can actually open them (metaphorically, logically, and physically), it's hardly surprising that most howto's on BTLE tutorials deal with using AndroidWear.
Programming for a very restricted environment like the PineTime is not where I'd start, if this is to your introduction to programming or embedded programming. I get the impression that this might be the case for you, but I could be entirely wrong.
Thank you very much for your response. I appreciate your thoughts.
I am a very experienced firmware engineer with extensive experience in machine communications.
This is my first experience thou programming a watch or using BTLE.
As for buying Pine*, I am always learning new things and I was intrigued by the products. For instance, I bought the Pine64so ClusterBoard and have the seven modules purring away and it has been the ideal host for my Virtual Protocol Adapter development, which is a distributed application that among other things will communicate with the phone and PineBookPro.