Insights on the Re-Architecting to a Single Codebase.pdf

1、#EMBEDDEDOSSUMMITInsights on the Re-Architecting to a Single CodebaseErez Shaul,AuguryZiv Hershkovitch,AugurySelf presentationZiv Hershkovitch,AuguryEmbedded Firmware Engineer Erez Shaul,AuguryEmbedded Firmware Engineer and Team LCellularWiFi/LANBLEWiFiWifi or CellularBLEWiFi/LANWhat is Augury?Our F

2、ocus is on the Sensors todayWere Building A World Where You Can Always Rely On The Machines That MatterWhat is Augury?Were Building A World Where You Can Always Rely On The Machines That MatterWhat is Augury?Were Building A World Where You Can Always Rely On The Machines That MatterIntro Single Code

3、 Base what it isZephyr for a single code baseWhy Zephyr is a good fit Extra value Migrating to zephyrCan we do it?Our Strategic plan layout Deployment POC explainedMemory footprint PerformanceSingle Code Base DesignGeneral approach Zephyr Driver API expansion a POC Example OutlineThe start pointSing

4、le Code Base Conceptone common code base,in one managed Project,for our complete device portfolioHardware abstractionDevice tree structure&BindingDevice Model and DriversModularitySubsystem Architecture kernel,networking,file systems,device drivers,and moreKconfig SystemCmake&CMakeListsWhy Zephyr fi

5、ts SCBArchitecture that allow flexibilityWhy Zephyr fits SCBHW abstraction visualizationWhy Zephyr fits SCBHW abstraction visualizationWhy Zephyr fits SCBHW abstraction visualizationWhy Zephyr fits SCBDesirable features already built inNrf connect SDK integrated zephyr RTOSCompatible with MCUboot bo

6、ot loaderSecure boot mechanismImage slots handlingIntegrated with MCUmgr-management subsystemBuilt-In file system API over littlefsBuilt-In Memfault supportintegration of CMSIS-DSP libraryBuilt-in devices drivers(sensors,flash,etc)Built-In lz4 Data Compression library SupportDFU OTA?Migrating to Zep