Device Creation_Daniel Rubio_Symbian Foundation
Transcript of Device Creation_Daniel Rubio_Symbian Foundation
-
8/14/2019 Device Creation_Daniel Rubio_Symbian Foundation
1/15
Symbian^x Platform Overview: How to achieve
HW abstraction and Faster Device CreationDaniel A. Rubio
Chief ArchitectSymbian Foundation
-
8/14/2019 Device Creation_Daniel Rubio_Symbian Foundation
2/15
Motivation Facilitating a dynamic and agile yet predictable portfolio
Facilitate HW migration (towards innovative HW)
Product innovation is intimately tied to change, and often the needfor change appears midstream in a project.
The ability to make changes during development without being toodisruptive can be valuable
a s y cus omers: cou e ac eve y a us ng pro ucrequirements during development in response to customerfeedback.
TTM could be measured from the last change in requirements untilthe product is delivered.
Scope (HW/SW integration) Lead Product andsubsequent products
-
8/14/2019 Device Creation_Daniel Rubio_Symbian Foundation
3/15
Why do products flop? Fail to deliver expected performance
Too late Competitors got the upper hand
Not attractive to consumers even if fulfillingrequirements
Even if it sales well doesnt pay for itself Development
cost was too high
-
8/14/2019 Device Creation_Daniel Rubio_Symbian Foundation
4/15
-
8/14/2019 Device Creation_Daniel Rubio_Symbian Foundation
5/15
Wouldnt it be better if
Bring to the start what causes problems in the end
UI/Apps dev starts while finalizing requirements Simulator Kernel/basic drivers (FlashMem/Keyboard/LCD/USB/SD Card)
up and running ASAP Minimal dev effort, off the shelfcomponents available
Fast vertical bring up tried and tested (but representative)UI/App frameworks on new or phone form factor
Transition UI dev from Simulator to HW
Horizontal Bring-up Sequentially hook peripherals (minimum
integration effort) Integration Tests driven from UI (Smoke, Stability,
Interoperability)
Minimal effort to spin-off HW variants
-
8/14/2019 Device Creation_Daniel Rubio_Symbian Foundation
6/15
How can the SF and community help?
Kernel Open Source Adoption, porting effort
Vertical bring-up SHAI HW Abstraction
TTM Operational Programmes
Pre Validation of HW/SW Productization Task Force
Supporting new projects
-
8/14/2019 Device Creation_Daniel Rubio_Symbian Foundation
7/15
Kernel is open now
Development kit available low adoption barrier
Kernel EPL is available through PDK as well
Will Provide Starting Point and Off-the-shelfcomponents
Better system knowledge
-
8/14/2019 Device Creation_Daniel Rubio_Symbian Foundation
8/15
Symbian Architecture
Application Layer
HW
Middleware
OS Layer
-
8/14/2019 Device Creation_Daniel Rubio_Symbian Foundation
9/15
Vertical bring-up
HomescreenFinal UIA sA s A sA s
1- Bring-up a basic UI to enable app development
2- Continue system bring-up horizontally
Stubbed Components
Kernel +
BasicDrivers
HW
Basic MW
+ as c pps
HW
Complete MW
Complete OS/BASE
-
8/14/2019 Device Creation_Daniel Rubio_Symbian Foundation
10/15
What is SHAI? Symbian Hardware Abstraction Interface
A standard for HW abstraction for Symbian OS based devices
New definition of Symbian/S60 Adaptation
Based on S60 Chipset API's, expands also to area of peripheralcomponent abstraction
Common HW adaptation standard across Symbian Foundationmember companies
Future evolution managed through Symbian Foundation in
collaborative OSS mode
Most of the initial adaptation provided by Nokia through packageowners
-
8/14/2019 Device Creation_Daniel Rubio_Symbian Foundation
11/15
Architectural Vision
Symbian
Symbian Device SW
ApplicationsApplications
MiddlewareMiddleware
DeviceSpeci
andCo
SymbianFoundationAsset
SHAISymbianHardware
OS services
HW Adaptation Middleware
DeviceClassDriver
DCD2
ficDifferentiation
nfiguration
DCD3
DCD4 DCD n
DD2 DD3 DD4 DD nHW DeviceDriver
Abstraction
Interface
SHAIcompliant
modulesfrom HWmoduleproviders
-
8/14/2019 Device Creation_Daniel Rubio_Symbian Foundation
12/15
Why SHAI? We need to secure our future access to most compelling HW
technologies
Industry commitment to Symbian Foundation will increase availableHW options for Symbian -powered devices
Quicker productisation of new HW offering and more options for HWcomponent sourcing
Lower barrier for extending the SHAI compliancy to wider range ofHW modules
Technical soundness and productivity increase (for OEMs and HWvendors)
Active and healthy ecosystem -> will ensure overall HWcompetitivness of Symbian powered devices
-
8/14/2019 Device Creation_Daniel Rubio_Symbian Foundation
13/15
Drivers and benefits of SHAI
Lower costs, better productivity Less effort and shorter TTM in porting SW to new HW
Remove unneccessary duplicate investments in non-differentiating areas in Symbian Foundation Ecosystem
Enable HW vendors to supply one standard solution to allcustomers
Clear worksplit HW vendors to supply Adaptation SW specific to their HW
Industry best HW Abstraction Interface and Architecture for Symbian
-
8/14/2019 Device Creation_Daniel Rubio_Symbian Foundation
14/15
Key Areas
Telephony
MM (Audio, Video, Capture, HW Acceleration)
GFX Com osition Gamin
Power Mgt (Centralisation, Product Optimisation)
Peripherals (Interfaces, HW Enablers)
Security
-
8/14/2019 Device Creation_Daniel Rubio_Symbian Foundation
15/15
The SHAI story so far Nokia contributed major parts of S60 Chipset APIs to Symbian
Foundation (June -09)
Established SHAI WG, chaired by Daniel Rubio
Other members (as of today) from: Nokia, Samsung,Broadcomm, Fujitsu, STE, NTT-DoCoMo, TI, SEMC
WG Members are currently reviewing and providing comments onthe API proposals
Community feedback is very positive so far High anticipation for the initiative
Considered as a significant development proposal to SymbianFoundation