FAQ: Moving SSL/DD 1.0 (VisualDSP++) Projects to CrossCore Embedded Studio

Document created by CraigG on Sep 18, 2012Last modified by CraigG on Oct 29, 2013
Version 3Show Document
  • View in full screen mode

Question

 

I have a VisualDSP++ project that uses the Device Drivers and System Services, which I would like to move to CrossCore Embedded Studio. Is this possible? What needs to be done?

 

===============================

 

Answer

Projects from VisualDSP++ that use the Device Drivers and System Services will not work in CrossCore Embedded Studio (CCES) without significant modification. This is due to inherent incompatibilities between the SSL/DD 1.0 model used in VisualDSP++ and the newer SSL/DD 2.0 model used in CrossCore Embedded Studio

 

This was a conscious decision on our part, as we drastically simplified the driver model in CrossCore Embedded Studio. If you need to continue working with an SSL/DD 1.0 project then you will need to stay with the VisualDSP++ tools. Moving an SSL/DD 1.0 project forward to CCES will require the project to be rewritten to conform to the new driver model.

 

Attached is a document outlining the differences between the SSL/DD 1.0 model used in VisualDSP++ and the SSL/DD 2.0 model used in CrossCore Embedded Studio.

 

There is also a training video available on videos.analog.com that walks through the steps required for migrating a VisualDSP++ Blackfin project using System Services and Device Drivers 1.0 API to CrossCore Embedded Studio and the Device Drivers and System Services 2.0 API. More information is available here:

System Services and Device Drivers for CrossCore® Embedded Studio Training Videos

Outcomes