This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

XDS integration in DevRocket

Hi!

Maybe somebody can help me with the following problem I'm currently struggeling with:

I'm working on the DM6467 EVM and currently I'm playing with the encoder/decoder demo applications that come with the DVSDK (2.0.0.18). Using the provided Makefile works fine, I can build and run the appliation on the EVM. Now I'm trying to write my own encoder/decoder application based on this demos. But as we use Montavista DevRocket IDE for software development, I'm struggeling with the integration of the linker.cmd and compiler.opt. These files are autogenerated by XDS configuro based on the XDS application configuration and contain include paths and pre-compiled libraries from the DVSDK package. To be more prezise I don't know how to integrate these files in the IDE, and adding the content manually doesn't work at least for the libraries. All external functions lead to an error like this: "*.c: undefined reference to ...()". So it seems that the libraries are not correctly added to my project, as (as far as I understand) an external library has to use a "lib" prefix in it's filename, which isn't the case for the libraries provieded in DVSDK.

Would be great if somebody has an idea how to make the XDS outputs working together with Montavista DevRocket IDE!

Kind regards,

Holger

 

 

 

 

 

  • My understanding is that DevRocker is a tool for the ARM/Linux side and since the demos include dependencies on both ARM and DSP software, I am not sure if DevRocket can handle building of the demos.  Green Hills has an IDE called MULTI which can handle both ARM and DSP side development and debug within a single IDE.  Personally, I have little experience with DevRocket, but I have not seen the setup you are describing before.  If there is a way to accomplish this, it would make a great article.

  • Juan, thanks for your fast response.

    You are right that the demo applications include both, ARM and DSP code. But as I use the pre compiled libs from DVSDK (such as CodecEngine, ACPY3, DMAN3, etc.), in my opinion I only consider the ARM code of the encoder/decoder demo itself to be compiled via DevRocket.

    Maybe my question is rather more about the Eclipse/DevRocket interface itself. In other words I can add the generated linker.cmd and compiler.opt files to a Makefile so that compiler and linker use their content. But I don't find a way to do the same with DevRocket. And I even fail when adding the content manually to the project settings, as the pre-compiled DVSDK libraries don't come in the way lib<name>.a, which seems to be required for Eclipse CDT.

    Then the next step would be to build the pre compiled libraries on my own, but as mentioned by Juan this might fail as the output is not only plain ARM code.

    Any help welcome!

    Kind regards,

    Holger

     

     

     

     

     

     

     

     

  • I'm still working on this issue. Currently I'm renaming all the required precompiled libraries from DVSDK to lib<name>.a,  whichs works but is a very poor hack. And the include paths have to be added manually to the project settings, which is also quite bothering.

    Is there really nobody using XDS outputs within Montavista DevRocket? Or does somebody use another IDE which works together with the XDS integration?

    Kind regards,

    Holger