1. www.ceva-dsp.com Visual Linker Final presentation

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

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

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

5. slide 5 BackgroundBackground (cont.)

6. 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

7. slide 7 Our Solution : Visual Linker (cont.)

8. slide 8 Problem Domain

9. 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

10. slide 10 System Design

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

12. 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.

13. 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

14. 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.

15. 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

16. slide 16 Questions?

17. slide 17 THANK YOU!