Converting VisualDSP++ project to CCES project

Hello,

Thank you for your inquiry.

As you mentioned this line: 'which was compiled and linked with errors, but the generated .ldr file does not run after loaded to the board', please confirm this. Normally, the loader file (*.ldr) will not be generated if there are errors during compilation or linking.

Could you please provide the below details to assist you further on this issue:

1.If you are facing error message please share the screenshot of that.
2.Share us your example project that replicates the issue.

If you're unable to share your project on this public forum, feel free to contact private support through the below mail,

processor.tools.support@analog.com

Please make sure to add the link of this EZone thread while contacting private support.

Also, please refer "FAQ: Importing VisualDSP++ project files to CrossCore Embedded Studio" linked below:

ez.analog.com/.../importing-visualdsp-project-files-to-crosscore-embedded-studio

Hope this helps.

Regards,
Santhakumari.V

Hi Santhakumari,

Thanks for looking into this issue! When the VDSP++ project was first converted to CCES, it won't build. The error message was [Error ld0068]: Too many input files. Please see the attached screenshot below. Also showed in the screenshot, I noticed in the project properties->C/C++ Build->Settings->CrossCore SHARC Loader->Multiprocessor, the Multiprocessor input file fields are not empty. 

After I cleared those Multiprocessor input fields, the project compile and link without any errors and a .ldr file was generated, but the .ldr file does not run in our target. Please see the screenshot below with the Multiprocessor input file fields cleared:

Please let me know if you need anything else. 

Hi,

Could you please confirm whether the loader file was created according to the method described in the attached README file? Please refer to Chapter 5, 'Using Loader Files'.

If so, please run the below example CLDP command in the CCES installation path using your loader file. In that, please include the required driver and the loader file you are using.

cldp -proc ADSP-21489 -emu ICE-1000 -driver 21489_m25p16_dpia.dxe -cmd prog -erase affected -format hex -file Project.ldr -cmd compare -format hex -file Project.ldr

Where,
The "-cmd compare" command is used to compare the data stored in device memory with the data in a specified file(*.ldr).

Once this command runs successfully, we can confirm that the loader content has been successfully flashed.

Regards,
Santhakumari.V

readme.zip

Hi Santhakumari,

Thanks for providing helps! I went through the README file, and confirmed that we followed Chapter 5, 'Using Loader Files'. We are currently unable to run the CLDP command due to the reason that we flash our board through the serial port. We are ordering our ICE-1000 programmer, so in a few days, we would be able to run the CLDP command as you suggested.

In the meantime, I included the two .ldr files generated by VisualDSP++ and CCES respectively. File old.ldr was generated by VisualDSP++, and new.ldr by CCES. A binary compare of the two files found that many bytes of the old file are 5 less than the corresponding bytes of the new. Don't know if this can provide a hint to identify the problem. If not, I would be able to provide the outcome of the CLDP command in a few days.

Thanks again!

  ldr files.zip

Hi,

There is difference between the compiler version of CCES and VDSP, because there are number of ways in which VisualDSP++ applications differ from CCES applications: RTOS, interrupt handling, SSL/DD APIs, and enhancements and bug fixes and more.

The CCES compiler (and other build tools - assembler, linker, loader) were branched from the VisualDSP++ sources. There are obvious differences - e.g. the VisualDSP++ Compiler has not received support for the newest processors, as well as less obvious changes - such as a different ELF format in CrossCore Embedded Studio vs. VisualDSP++. That is, pre-build objects, libraries and executables from VisualDSP++ cannot be used in CrossCore Embedded Studio, as the ELF structure is different. 

Therefore, if you are migrating your project from VisualDSP to CCES, the .dxe and .ldr size will differ.

Hope this is helps.

Regards,
Santhakumari.V

Hi Santhakumari,

We finally received our ICE-1000 programmer. The following is the result of running cldp command with the error message. Our loader file is C:\Data\Dpm2_wdir\DSP\Debug\DPM2_DSP.ldr.

C:\Analog Devices\CrossCore Embedded Studio 2.12.1>cldp -proc ADSP-21489 -emu ICE-1000 -driver 21489_m25p16_dpia.dxe -cmd prog -erase affected -format hex -file C:\Data\Dpm2_wdir\DSP\Debug\DPM2_DSP.ldr -cmd compare -format hex -file C:\Data\Dpm2_wdir\DSP\Debug\DPM2_DSP.ldr
Target Sharc Emulators/EZ-KIT Lites
Platform ADSP-21489 via ICE-1000
Processor ADSP-21489
Core 0
Driver 21489_m25p16_dpia.dxe
Error: [TpsdkServer] Failed to load file: 21489_m25p16_dpia.dxe [Error: Can not find the file specified, Code=0x80047343]

I attempted to use the CCES provided the driver file .\SHARC\ldr\489_spi.dxe, but failed too:

C:\Analog Devices\CrossCore Embedded Studio 2.12.1>cldp -proc ADSP-21489 -emu ICE-1000 -driver .\SHARC\ldr\489_spi.dxe -cmd prog -erase affected -format hex -file C:\Data\Dpm2_wdir\DSP\Debug\DPM2_DSP.ldr -cmd compare -format hex -file C:\Data\Dpm2_wdir\DSP\Debug\DPM2_DSP.ldr
Target Sharc Emulators/EZ-KIT Lites
Platform ADSP-21489 via ICE-1000
Processor ADSP-21489
Core 0
Driver .\SHARC\ldr\489_spi.dxe
Error: failed to resolve symbol "AFP_BreakReady".
Error: driver load failed.

Can you tell what's wrong of my command lines? 

Regards,

Rudy

Hi ,

The error message " [Error: Can not find the file specified, Code=0x80047343]" occurs when the driver file (21489_m25p16_dpia.dxe) is not present in the specified path.
We suspect that in your CLDP command, you only specified the driver file name. Please include the full path to the driver file in the -driver command (or) place the driver file in the CCES installation directory.

Below are the updated CLDP commands. Please refer to them and verify that the files and paths are correct:

cldp.exe -proc ADSP-21489 -emu ICE-1000 -driver C:\Analog Devices\ADSP-21489_EZKIT-Rel1.0.0\21489_EZ-Board\Examples\Device_Programmer\serial\21489_m25p16_dpia.dxe -cmd prog -erase affected -format hex -file C:\Data\Dpm2_wdir\DSP\Debug\DPM2_DSP.ldr -cmd compare -format hex -file C:\Data\Dpm2_wdir\DSP\Debug\DPM2_DSP.ldr

Regards,
Santhakumari.V

Hi,

Thank you for answering my question! My coworker figured out the issue and solved it. Thanks anyway.

Rudy

Hi Rudy,

Thank you for the update and glad to know that the issue got resolved.

Best Regards,
Santha kumari.