• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 53 subscribers
  • Views 1115 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Problem building DSPLIB c64px 3.1.0.0

Tim Jackson
Intellectual 480 points

I'm having problems using "DSP_ifft16x16" and would like to eliminate incompatibility issues regarding CCS versions, i.e. the lib as distributed was built with a later version than mine (Version: 4.2.4.00033).  All looks OK up to:

But when I click Finish, I get:

 A fresh install made no difference.  Has anyone else managed to build the lib?

(Graphics look a bit of a mess - sorry!)

 

  • 0
    Intellectual 480 points

    Continued: 

    And if I click on the "Details" button I get:

    "Invalid project description.   C:\Texas Instruments\dsplib_c64Px_3_1_0_0\lib overlaps the workspace location: C:\Texas Instruments\dsplib_c64Px_3_1_0_0\lib "

     

  • 0 in reply to Tim Jackson
    Intellectual 480 points

    Continued:

    And if I tick the "Copy project into workspace" box, it sits there, 'importing', in what looks like some sort of recursive trap, DSPLIB \ DSPLIB \ DSPLIB \ DSPLIB:

     

  • 0 in reply to Tim Jackson
    TI__Guru*** 130875 points

    HI Tim,

    was this initially a v3 project?  In that case you need to use the legacy import.  Project ->Import legacy CCSv3.3 project.

    What if you move it to another directory or try a fresh workspace?  I notice your directory has a space (Texas Instruments) and CCS has had some issues at time handling directories which contain spaces.

    A few further details might help us.

    Best Regards,

    LIsa

  • 0 in reply to Lisa TI
    Intellectual 480 points

    Lisa,

    Yes, it was a v3.3 project at some stage but has been running in v4 for quite a while.  Or are you suggesting there may still be some issues with the conversion that are only now showing up because of trying to add DSPLIB?

    Ironically, I installed in "c:\Texas Instruments" partly to avoid the space in "c:\Program Files".  That wasn't the smartest move was it!  To correct that now will be a bit of a pain!

    I confess I've 'done the dirty' and lifted the one routine I needed from the source of the library and added it to my project, so I'm not currently chasing the issue of DSPLIB.

    What might encourage me back down the path of straight and narrow would be confirmation that dsplib_3_1_0_0  definitely has the binaries for the "_i" version, i.e. DSP_ifft16x16_i().  It feels like a mis-match between dsplib.h and the lib itself.  I can use other functions, like DSP_autocor() without a problem, so I think I've got the lib generally setup correctly.

  • 0 in reply to Tim Jackson
    TI__Guru*** 130875 points

    Hi Tim,

    I can try to get confirmation for you.  In the mean time, I would try without the space just in case.  If the project was already converted and is essentially a v4 project they you should not need the legacy import.

    Best Regards,

    Lisa

  • 0 in reply to Lisa TI
    TI__Guru*** 130875 points

    HI Tim,

    Regarding the _i version support.  This is something I would recommend posting to the device forum.  But from what I can see, you may be correct in this being a possible item here.  Have a look at the screenshot from the API documentation.

    Please keep us informed if these last couple posts help.

    Best Regards,

    Lisa

  • 0 in reply to Lisa TI
    Intellectual 480 points

    Lisa,

    I don't think 'we may have a problem somewhere' would be viewed by many as 'answered'?

    Re-reading the thread I've realised we may have been mixing up DSPLIB and the project I'd like to have added it to.  I tried to build DSPLIB to ensure the header and binaries aligned, but got error messages, i.e. error messages building DSPLIB.  Can you confirm that DSPLIB 3.1.0.0 is buildable in CCS 4?

    Regards,    Tim

  • 0 in reply to Tim Jackson
    TI__Guru*** 130875 points

    Hi Tim,

    There really should be not dependancy on CCS version.  So yes, you can build the library in v4.   If you need detailed informaiton on dependancies, the best thing to do is post to the device forum as these dsp libraries come from there.

    Hope this can help further.

    Best Regards,
    Lisa