• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 52 subscribers
  • Views 1004 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Using DSP/BIOS from DVSDK in CCS 5.3

Steve Osselton
Prodigy 130 points
Other Parts Discussed in Thread: DM3730

Hi,

I am trying to configure CCS to use the version of DSP/BIOS that is part of a bundled DVSDK (4.03).

I am using Window->Preferences->Code Composer Studio->RTSC->Products

and adding the DVSDK install directory to the tool discovery path. After doing this the XDAIS and

XDCtools versions are updated to include the versions bundled in the DVSDK but not DSP/BIOS?

Is there a reason for this? The workround is to manually copy the DSP/BIOS directory into /opt/ti

but is hardly an ideal solution.

Cheers Steve

  • 0
    TI__Guru*** 130875 points

    Hi Steve,

    where had BIOS initially been installed before you moved it to resolve the issue?  Was it in the program files directory?  If so that could be the reason as that directory has odd permissions in windows.  We have seen the issue of certain packages only coming in when in the same directory tree.  This seems more likely to be what you experience.

    I hope this helps explain.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Prodigy 130 points

    I'm using CCS on Linux not Windows.

    My DVSDK is installed in  /usr/local/dvsdk4_03_00_06 and CCS in /opt/ti

    The DBS/BIOS release is in /usr/local/dvsdk4_03_00_06/dspbios_5_41_03_17

    All the file protections look fine (a normal user can see all the files).

  • 0 in reply to Steve Osselton
    TI__Guru*** 130875 points

    HI Steve,

    sorry, yes I should have picked up on the opt/ti.  Well I am still glad you found a way to get your package.  In your case it could still be permissions related.  In Linux we have see behaviour such as when ccs is launched with different permissions as installed (ie installed as sudo, launched as user) or as a different login, then certain packages are not available.  Permissions beyond read/seeing the file are required.

    Hope this helps and once again all the best.

    Best Regards,

    LIsa

  • 0 in reply to Lisa TI
    Prodigy 130 points

    Hi Lisa,

    Have found the problem, it's the directory name. CCS is checking for subdirectories called

    "bios_xxx", in the DVSDK the subdirectory is "dspbios_xxx", so CCS doesn't recognise it.

    If the directory is re-named the CCS picks it up fine. Perhaps CCS should check for both

    for compatibility with TI SDKs.

    Cheers Steve.

  • 0 in reply to Steve Osselton
    TI__Guru*** 130875 points

    Hi Steve,

    very happy to hear you found the root cause and thanks for reporting this.  I will pass along the feedback.

    All the best with development.

    Best Regards,

    Lisa

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

    HI Steve,

    we are looking into dspbios was used instead of bios as ccs expects.  May I ask what target you are using?  Specific dvsdk brand?

    Thanks and best regards,

    Lisa

  • 0 in reply to Lisa TI
    Prodigy 130 points

    Hi Lisa,

    We are using the TI DVSDK for the DM3730 processor. We use two versions 4.01.00.09

    and 4.03.00.06. The same naming convention is used in both.

    Cheers Steve.

  • 0 in reply to Steve Osselton
    TI__Guru*** 130875 points

    Hi Steve,

    ok, many thanks.   It is good to get this type of feedback.

    Best Regards,
    Lisa