28
A Zephyr User Story Franco Saworski

A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

  • Upload
    others

  • View
    1

  • Download
    0

Embed Size (px)

Citation preview

Page 1: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

A Zephyr User Story

Franco Saworski

Page 2: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

ProGlove

© Workaround GmbH, 2016

Page 3: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

ProGlove• First bare metal

– Hardware components

dictated by product

– Bare metal prototypes

became product

© Workaround GmbH, 2016

Page 4: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

ProGlove• First bare metal

– Hardware components

dictated by product

– Bare metal prototypes

became product

• Then port to Zephyr

– Externalize build system

– Abstract architecture

– Modular board support

© Workaround GmbH, 2016

Page 5: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

ProGlove• First bare metal

– Hardware components

dictated by product

– Bare metal prototypes

became product

• Then port to Zephyr

– Externalize build system

– Abstract architecture

– Modular board support

• From prototype to CE in twelve,

later nine months

© Workaround GmbH, 2016

Page 6: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

blik

Images © blik GmbH, 2018

Page 7: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

blik

• Zephyr on the sensor unit from day one

• From prototype to CE in six months

Images © blik GmbH, 2018

Page 8: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Lessons Learnt• Four years shipping industry grade products with small teams in startups

• First job bare metal

– Did not scale

– Reinventing the wheel

Page 9: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Lessons Learnt• Four years shipping industry grade products with small teams in startups

• First job bare metal

– Did not scale

– Reinventing the wheel

• Then port to Zephyr

– Ported too many legacy dependencies

– Did not upstream enough custom code

Page 10: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Lessons Learnt• Four years shipping industry grade products with small teams in startups

• First job bare metal

– Did not scale

– Reinventing the wheel

• Then port to Zephyr

– Ported too many legacy dependencies

– Did not upstream enough custom code

Page 11: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Lessons Learnt• Four years shipping industry grade products with small teams in startups

• First job bare metal

– Did not scale

– Reinventing the wheel

• Then port to Zephyr

– Ported too many legacy dependencies

– Did not upstream enough custom code

• Second job native Zephyr

– Still not upstreaming enough

– Using off the shelf components where possible

– Sticking them together with Zephyr

Page 12: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Lessons Learnt• Four years shipping industry grade products with small teams in startups

• First job bare metal

– Did not scale

– Reinventing the wheel

• Then port to Zephyr

– Ported too many legacy dependencies

– Did not upstream enough custom code

• Second job native Zephyr

– Still not upstreaming enough

– Using off the shelf components where possible

– Sticking them together with Zephyr

Page 13: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Requirements

Page 14: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Requirements

Product

• Fast prototypes

• Fast iterations

• Fast to market

Page 15: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Requirements

Product

• Fast prototypes

• Fast iterations

• Fast to market

• Low resources

• Growing feature backlog

Page 16: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Requirements

Product

• Fast prototypes

• Fast iterations

• Fast to market

• Low resources

• Growing feature backlog

Development

• Solid build system

• Solid architecture

• Solid interfaces

• Solid ecosystem

Page 17: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Requirements

Product

• Fast prototypes

• Fast iterations

• Fast to market

• Low resources

• Growing feature backlog

Development

• Solid build system

• Solid architecture

• Solid interfaces

• Solid ecosystem

• Community

• Standards

Page 18: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

The RTOS choice

• Hardware Support

• Toolchain

• Testing

• APIs / Interfaces

• Drivers

• Application libraries

• License

Page 19: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

The RTOS choice

• Hardware Support

• Toolchain

• Testing

• APIs / Interfaces

• Drivers

• Application libraries

• License

• Zephyr

• mbedOS

• Contiki

• FreeRTOS

• (RiOT)

Page 20: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Looking back

• Zephyr meets all requirements

Page 21: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Looking back

• Zephyr meets all requirements

• It helped me ship products fast

Page 22: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Looking back

• Zephyr meets all requirements

• It helped me ship products fast

• I was able to maintain products with small teams

Page 23: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Looking back

• Zephyr meets all requirements

• It helped me ship products fast

• I was able to maintain products with small teams

• Its active community encourages participation

Page 24: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Looking back

• Zephyr meets all requirements

• It helped me ship products fast

• I was able to maintain products with small teams

• Its active community encourages participation

Page 25: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Thank you!Questions?

Join the monthly Munich Embedded Meetup:https://groups.io/g/embeddedmeetup

[email protected]

All pictures attribution free from https://pixabay.com unless indicated otherwise.

Page 26: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to
Page 27: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Slide not shown in presentation. For image source documentation only.All images on this slide royalty free and attribution free.

https://github.com/zephyrproject-rtos/zephyr/blob/master/doc/images/Zephyr-Project.pnghttps://pixabay.com/en/communication-internet-1927697/https://pixabay.com/en/emotions-man-happy-sad-face-adult-371238/https://pixabay.com/en/business-plan-tree-growth-grow-2987962/

Page 28: A Zephyr User Story - Linux Foundation Events · ProGlove • First bare metal – Hardware components dictated by product – Bare metal prototypes became product • Then port to

Slide not shown in presentation. For image source documentation only.All images on this slide royalty free and need attribution.

http://www.proglove.de/wp-content/uploads/2016/10/STE9899.jpg