• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 100 subscribers
  • Views 518 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.

MCSDK v.1.0 vs. MCSDK v.2.0

Alex
Expert 2430 points
Other Parts Discussed in Thread: TMS320C6472, TMS320C6457, TMS320C6474, TMS320TCI6608, TMS320TCI6618, TMS320C6670, TMS320C6678

My platform utilizes C6474 DSPs.  On the MCSDK home pages, the following is cited:

MCBSP v.1.0:  Supported devices include TMS320C6472, TMS320C6474, and TMS320C6457.

MCBSP v.2.0:  Supported devices include TMS320C6670, TMS320TCI6618, TMS320C6678, and TMS320TCI6608.

So how should I interpret that?  v1.0 is only for C64x devices, and v2.0 is only for C66x devices?

I am not interested in the PSP, since, obviously, we have written our own.  (We call them BSPs, but I guess that terminology is so last century. :-) )  I custom build the NDK library (using the latest release), and I already custom build the CSL for the C6474 (which I got from either MCBSP v.1.0 or one of the NDKs, I forget which).

So given this, should I or can I install MCBSP v.2.0 to get all the other goodies, namely, the UIA modules?  Or since I'm using a C6474, am I just out of luck?

  • 0
    Expert 2430 points

    Two days and still silence.  Nice.

  • 0 in reply to Alex
    TI__Intellectual 1840 points

    Hi Alex,

    You can certainly install BIOS MCSDK 2.0 to pick up updated components and their bugfixes.

    But, I would be careful choosing the components to update, some components might require to update other components. In perticular UIA (or MCSA) requires CCS v5 and above. So to use this you need to upgrade to CCSv5 as opposed to CCSv4 which comes with BIOS MCSDK 1.0. Please see individual components user guide for supported architectures.

     Regards

    Sajesh

  • 0
    TI__Expert 8055 points

    Alex,

    Unfortunately, MCSDK 2.0 currently only supports 66x devices. There are plans to support 64x+ devices in the future, but at present, 64x+ users are stuck on MCSDK 1.0.

    I don't believe that there is any UIA functionality that you can get from downloading 2.0 while on a 64x+ device.

    Regards,
    Dan

     

  • 0 in reply to DanRinkes
    Expert 2430 points

    I am using CCS v5.1, so that's covered.  It's disappointing to hear that about the new UIA component, though.  That was my main interest since, from what little bits and pieces I can gather about it, it seems to be RTDX's replacement.

    RTDX and RTA were already dodgy at best starting with CCSv4 when official/active support for it was dropped, but now with CCS v.5.1 (M5), it's better in some regards but worse in others.  For instance, CCSv5.1, all streamed data (I'm just talking simple Log_printx()/Log_writex() data) is thrown away, or lost, if CCS is not the active (foreground) application.  So if I want to initiate a trace of a file exchange (simple TCP client/server), I have no way of doing that because by the time I hit enter in the Cmd window and switch back to CCS, all the relevant packet transactions I'm interested in monitoring have already transpired.

    That said, I have to admit that at least when CCSv5.1 is in focus, RTDX/RTA is a lot more reliable than in CCSv4.  For instance, in CCSv4, every time I restarted the application, I would have to close and then reopen any RTA log tabs I had open to reinitialize the interface,otherwise, I would see no updates.  It was very annoying.  And it would only work in STOP mode regardless of what I set it to.

    Needless to say, given all this trouble with simple (buffered) log statements, I have had little desire to endure the headaches involved in utilizing all the other more useful system analysis tools (load balancing, statistics, etc.).  It's kind of sad, to, because it's 2011, and I am still developing, debugging, and profiling my systems the same rudimentary way I had to do it back in 1990, over two decades ago! :-)

  • 0 in reply to Alex
    TI__Expert 5670 points

    Alex,

    System Analyzer (UIA target package + DVT for Analysis and Visualization) can also be used independent of the MCSDK and it supports c64x+. It is available in CCSv5.1 M6 and newer (it can also be added to CCS5.0). See here for more info http://processors.wiki.ti.com/index.php?title=Multicore_System_Analyzer. See chapter 3 of the User Guide on how to get BIOS Load/Execution graph etc.

    Regards,

    Imtaz.

  • 0 in reply to Imtaz Ali
    Expert 2430 points

    That's fantastic news!  But when is CCSv5.1 M6 due to be released?  (CCS v5 Wiki still shows M5 as the latest available pre-release build.)

  • 0 in reply to Alex
    TI__Expert 5670 points

    Alex,

    M6 is expected any day now (could be as early as today).

    Regards,

    Imtaz.

  • 0 in reply to Imtaz Ali
    TI__Expert 5670 points

    Alex,

    M6 has been posted. Note that we found one issue with the installer with the UIA examples not showing up in project templates. You can work around this by moving the folder <ccs install folder>\ccsv5\uia_1_00_01_16_eng up one folder to <ccs install folder>\uia_1_00_01_16_eng and restarting CCS. This problem will be fixed in M7. Let us know if you run into any other issues or require help with System Analyzer.

    Regards,

    Imtaz.

  • 0 in reply to Imtaz Ali
    Expert 2430 points

    Thanks for the heads-up and workaround.

    I actually did install it earlier today, but I made the same bone-head mistake I made once before and installed in a directory with some non-alphanumeric characters, so I can't compile anything.  (xdc complains).  (I installed it to "c:\dev\ccs5.1(M6)" and xdc can't handle the parentheses.)

    Anyway, I'm going to uninstall and reinstall tomorrow, and I am very eager to check out the UIA stuff, so, again,  thank you so much for this quick heads-up and workaround.