9

Esc boston 2015_jonny_doin_rtos_small

Embed Size (px)

Citation preview

RTOS  or  not  RTOS?  

Jonny  Doin  CEO,  GridVortex  

System  Architecture  

More  important  than  the  RTOS.    Architecture  is  what  you  can  explain    aCer  a  SixPack.    ImplementaGon  is  everything  else.      

YOU,  the  Designer,  are  Responsible  

Embedded  Reliability:  Full  Control  

CriGcal  systems  need    Full  Control  over  the  ImplementaGon  

Bare-­‐Metal  but  not  Barefoot  •  Over  200K  lines  •  Event-­‐driven  •  Hard-­‐RealGme  •  FIPS-­‐140-­‐2  Security  •  Streams  •  MulGtasking  

•  CommunicaGon  Protocols  •  Ethernet  •  Precision  Analog  •  Webservers  and  Sockets  •  Industrial  Networking  •  OTAP  

Full  Control  is  Fast  Response  Er,  

Houston,  ...    

Design  Failures  Design  Responsibility    

is  sGll  on  the  Designer!  

Final  Point  Good  Embedded  Engineering  has  no  shortcuts.  Regardless  of  using  an  RTOS,  your  code  is  what  makes  or  breaks  your  system.    Always  design  as  if    people’s  lives  depend  on  you.