I want to make a wearable smartwatch which works on keil mcbstm32f400 running android wear/wear os ,i want to know the procedure how to install wear os on the dev board.I did some research and i got to know that that only some devices have wear os like qualcomm's wear 3100 and ti omap but they are not available for purchase so i also got to know about other os like tizen which can also be used for wearables but i am stuck at which one to choose ,how to start , how to install on the board.Please guide how to proceed.
It seems that you first need to get a good understanding of what, exactly, is required for the Google Wear OS.
That's outside the scope of this forum - try: developer.android.com/.../
Are you sure that a 168MHz Cortex-M4 with 1MB Flash & 192KB RAM is even suitable for Wear OS?
According to en.wikipedia.org/.../Wear_OS it's still basically a Linux kernel - so (at least) a Cortex-A would sound more likely ... ?
Thanks for the reply , i understood that for a smartwatch ,cortex-a series multiple cores may be required but even if I buy it ,the wear os is not available to everyone what i read online.It is available only on select SOCs(system on chips);correct me if i am wrong.So what are other options for os for wearable systems which can be run on cortex A series. The mentioned link: developer.android.com/.../ is meant for app development so assuming i develop the app ,how to download it to the cortex a processor and if i download it to the processor will the app only take care of all the peripherals interface (adc/i2c/usb otg).
What you're asking is really beyond the scope of this forum - you need to find a Wear OS support community for those questions. They have nothing to do with Keil.
A more fundamental question is: do you really need Wear OS - or anything like it - at all?
What is it that you're actually trying to build? Why did you think that a Cortex-M4 would be suitable?
As with any project, you should start with the requirements of your project - and then find things with which you can meet those requirements.
"Wearable" is largely meaningless as a technical specification - it's mostly just a marketing buzzword.
Doesn't stop sa1esmen asking for these things though.
Dumbest technical specification i received was when sa1es asked if we could develop some sort of wearable fridge (to be placed in a backpack). When asked for further details they came back with "it must be cold". I didn't bother staying there long.
Indeed.
It's the engineer's job to turn the sa1es request into a technical specification.
"some sort of wearable fridge (to be placed in a backpack)"
Now seen on the backs of Deliveroo operatives everywhere ?
(although I guess they need one that can do hot and cold)
View all questions in Keil forum