Visual Linker Final presentation

slide 2  Background and Vision  Problem Domain  System Design  Challenges, Problems and Conclusions  So What Next? Outline

slide 3  What is DSP?  Who is Ceva?  What is a Linker anyway? Background

slide 4  What is SmartNcode?  Why linking in DSP environment is difficult?  What is linker script file? BackgroundBackground (cont.) SmartNcode™ Software Development Tools

slide 5 BackgroundBackground (cont.)

Our Solution : Visual Linker  Our solution will give the user the tools to write her linking script visually. The user will be able to:  Create memory classes on a visualized memory layout drawing canvas.  Locate Code and Data section in the memory classes by simple drag and drop operations.  Configure the linker directives by editing sections and class properties.  load and generate linking script files

slide 7 Our Solution : Visual Linker (cont.)

slide 8 Problem Domain

slide 9  The Visual Linker will provide an easy, user friendly visual linking configuration tool.  The Visual Linker will ease the linker usage and reduce scripting mistakes.  The Visual Linker will minimize the time and effort one need to invest in the linking script writing. Vision

slide 10 System Design

slide 11 Visual Linker, what? Lets have a look!

slide 12 Challenges, Problems and Conclusions Challenges:  Re-implementing GUI views and models in Qt C++.|  Developing and implementing linker algorithms with multiple constrains.  Interfacing with Ceva-DSP IDE platform.

slide 13 Challenges, Problems and Conclusions Problems:  Parsing post-complied files wasn’t enough – required additional processing.  Zoom-In and Zoom-Out support was complicated both algorithmically and visually.  The linker complexity was hard to grasp when implementing the linker script parser

slide 14 Challenges, Problems and Conclusions Conclusions:  The project was much bigger than a standard project for two team members.  As a result, implementation for some features were suspended.  The core components of the initial design were successfully implemented.

slide 15 So What Next?  Full integration with the (CEVA) Linker  Full directives and core types support  Delivering the visual linker to CEVA  Distributing the Visual linker to CEVA’s clients along side with the rest of the binary tools

slide 16 Questions?

slide 17 THANK YOU!