Please use this identifier to cite or link to this item:
http://10.1.7.192:80/jspui/handle/123456789/8837
Full metadata record
DC Field | Value | Language |
---|---|---|
dc.contributor.author | Vyas, Chandni | - |
dc.date.accessioned | 2019-08-31T07:17:47Z | - |
dc.date.available | 2019-08-31T07:17:47Z | - |
dc.date.issued | 2018-06-01 | - |
dc.identifier.uri | http://10.1.7.192:80/jspui/handle/123456789/8837 | - |
dc.description.abstract | An Integrated Firmware Image consists of various system firmware blobs with multiple feature configuration per silicon architecture.There are multiple issues that need to be addressed such as automating the build and sanity verification, differenti- ating between verified and custom images, identifying embedded software packages used and generating multiple configurations once at an early stage of the program cadence. This thesis aims to build an automated clean integrated image, which goes through the various stage of image verification (static analysis), pre-packing, build, authentication, and release with rollback feature. We cover each of these automated build infrastructure and test suite developed to make it seamless. Each stage has pre-defined tasks; image verification has to verify payload size, signature, updating intermediate configuration files; pre-packing has to re-create the previous build for incremental and delta build setup, updating all intermediate configuration files, pattern matching for JSON files that dictate each binary attributes, creating version information binary table. Once all the configuration details are set, binaries are copied in a appropriate location, the build will be triggered to generate various different configurations for silicon. This build automation is fully implemented and used for all active programs. Other enhancements such as verification of an image whether its a release or custom build is also the part of test suite post build. The generated images through these automated build infrastructure are then verified and debugged in the shell environment once the platform is powered up with all the configuration that is enabled for the silicon. Hence, to ease the verification analysis in the process and to improvise build environment, automation tool suite is used. | en_US |
dc.publisher | Institute of Technology | en_US |
dc.relation.ispartofseries | 16MECE27; | - |
dc.subject | EC 2016 | en_US |
dc.subject | Project Report | en_US |
dc.subject | Project Report 2016 | en_US |
dc.subject | EC Project Report | en_US |
dc.subject | EC (ES) | en_US |
dc.subject | Embedded Systems | en_US |
dc.subject | Embedded Systems 2016 | en_US |
dc.subject | 16MEC | en_US |
dc.subject | 16MECE | en_US |
dc.subject | 16MECE27 | en_US |
dc.title | Automated Pre-OS (Firmware) Build and Continuous Integration | en_US |
dc.type | Dissertation | en_US |
Appears in Collections: | Dissertation, EC (ES) |
Files in This Item:
File | Description | Size | Format | |
---|---|---|---|---|
16MECE27.pdf | 16MECE27 | 2.47 MB | Adobe PDF | ![]() View/Open |
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.