• Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 274 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.

CCSv5.1 (M8.5) Breaks MCSDK 1.0

Alex
Expert 2430 points

My target is a C6474, so I have MCSDK 1.0 installed for my networking (TCP/IP stack) support.

My projects currently have dependencies on the following components:

mcsdk_1_00_00_08
ndk_2_20_02_22
pdk_c64x_1_00_00_06

M5, M6, and M7 "discovered" them fine, and my project was actively using them.  Tonight, I installed M8.5, and now CCS (Eclipse) won't "discover" them automatically; and even if I try to add them manually, they are not recognized.  A fresh install of the MCSDK didn't help, either.

Please help ASAP!  My application won't function without networking support.

Edit: To sound a little less dramatic, I can still load up M7, and all still works fine there.  It's just that with M9 a couple of weeks away, and 5.1 (Final) due out by the end of next month, and I am just hoping I won't be stuck on a still slightly buggy milestone build for the remainder of my current project (which doesn't end for a couple of more years). ;-)

  • TI__Guru**** 162305 points

    Alex,

    M8 and M8.5 will have trouble discovering some versions of target content packages, especially if you have more than 1 version installed.  It depends on how they are packaged. M9 should be good for this.  We are planning on trying it out with MCSDK 2.x.

    Regards,

    John

  • in reply to JohnS
    Expert 2430 points

    It's never been documented how to install these milestone builds, and since there is never any clearly defined "upgrade" option, I just have been doing a complete install into a new directory.  I did completely uninstall M5, but since then, I now have three installs on my system:  M6, M7, and M8.5.

    It's good to hear about M9, but what worries me, though, is that my NDK is actually a custom build which I have under version control.  (The PDK I don't really need anymore as my own BSP needs to provide that functionality anyway, and the same somewhat applies to the MCSDK.)  I custom built and rebranded the NDK, though, precisely so something like this couldn't happen.

    My NDK is just a copy of your NDK (obviously), so are you saying (hopefully) that M8/8.5 is currently broken in regard to some component definition files, or are you saying that my custom NDK is now incompatible with this and all future versions of CCS?

  • in reply to Alex
    Prodigy 210 points

    Hi,

    When is the M9 build is due?

    Thanks,

    Yishay

  • in reply to Yishay Hayardeni
    Expert 2430 points

    According to the Wiki, October 10, i.e., next Monday.