• State Verified Answer
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 39 subscribers
  • Views 290 views
  • Users 0 members are here
Options
Related

Migration from Visual DSP++ to Crosscore ad1980

ErangaW
on May 5, 2014

Hey Im currently in the process of Migrating some visual DSP+ code to crosscore embedded stuidos, for the ADSP-BF548 board

The code makes extensive use of the AD1980 codec , AD1980 driver includes and a callback routine. . Currently I am watching this video

http://videos.analog.com/video/products/processors-dsp/2751956133001/Migrating-from-VisualDSP-to-CrossCore-Embedded-Studio/

To assists with the migration. In the video they replaces the BF2x onchip codec drivers includes an all mentions to the codec with the ssm2603.

My question is do I follow a similar process to the above video and replace all mention too the AD1980 with the ssm2603, and if so why?

Cheers Eranga

Parents
  • 0 on May 6, 2014 4:02 PM over 6 years ago

    Hi Eranga,

    Are you using a BF548 EZ-KIT Lite, or a custom board that uses the AD1980 codec?

    The changes in the example used to illustrate the porting process in that video were required because the name of the driver differs between VisualDSP++ and CrossCore Embedded Studio. In VDSP++ the driver for the on-chip codec in the BF52xC processors was "adi_bf52xc1.c" - though the underlying codec is actually an SSM2603 (with a separate adi_ssm2603.c file for other processors to use with the SSM2603 codec). In CCES this is unified into a single driver, adi_ssm2603.

    So, changing your code to use the SSM2603 codec is not a requirement when porting other code to CCES. Typically, you would identify the appropriate driver from the Board Support Package (BSP) and port your code to use this. For example, for the BF533 EZ-KIT Lite you will find the CCES driver in the BSP at "...\BF533_EZ-Kit_Lite\Blackfin\src\drivers\codec\ad1836a\".

    Unfortunately we do not have a driver for the AD1980 codec with CrossCore Embedded Studio. The AD1980 is an obsolete part, and one that is considered quite inefficient for the world of embedded processing. In VisualDSP++ this device required a significant software overhead in the device driver.

    We recommend using an alternative codec - and I would suggest you take a look at the Audio/Video Ez-Extender board, which uses the AD1836 Audio Codec. Examples for this particular codec are available in the Board Support Package (available on the product page) and demonstrate its use in both I2S and TDM modes.

    I'm sorry I couldn't be of more help on this occasion. I notice that you are listed a University in your profile. You may want to use the University Program page to enquire whether a discount is available for the EZ-Extender.

    Regards,

    Craig.

Reply
  • 0 on May 6, 2014 4:02 PM over 6 years ago

    Hi Eranga,

    Are you using a BF548 EZ-KIT Lite, or a custom board that uses the AD1980 codec?

    The changes in the example used to illustrate the porting process in that video were required because the name of the driver differs between VisualDSP++ and CrossCore Embedded Studio. In VDSP++ the driver for the on-chip codec in the BF52xC processors was "adi_bf52xc1.c" - though the underlying codec is actually an SSM2603 (with a separate adi_ssm2603.c file for other processors to use with the SSM2603 codec). In CCES this is unified into a single driver, adi_ssm2603.

    So, changing your code to use the SSM2603 codec is not a requirement when porting other code to CCES. Typically, you would identify the appropriate driver from the Board Support Package (BSP) and port your code to use this. For example, for the BF533 EZ-KIT Lite you will find the CCES driver in the BSP at "...\BF533_EZ-Kit_Lite\Blackfin\src\drivers\codec\ad1836a\".

    Unfortunately we do not have a driver for the AD1980 codec with CrossCore Embedded Studio. The AD1980 is an obsolete part, and one that is considered quite inefficient for the world of embedded processing. In VisualDSP++ this device required a significant software overhead in the device driver.

    We recommend using an alternative codec - and I would suggest you take a look at the Audio/Video Ez-Extender board, which uses the AD1836 Audio Codec. Examples for this particular codec are available in the Board Support Package (available on the product page) and demonstrate its use in both I2S and TDM modes.

    I'm sorry I couldn't be of more help on this occasion. I notice that you are listed a University in your profile. You may want to use the University Program page to enquire whether a discount is available for the EZ-Extender.

    Regards,

    Craig.

Children
No Data