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.

CCS/SMV320C6727B-SP: Recommended debug & software development tools

Part Number: SMV320C6727B-SP
Other Parts Discussed in Thread: TMS320C6727B

Tool/software: Code Composer Studio

We are using the space qualified version of the TMS320C6727B DSP chip.  What is the recommended development and debug environment for this DSP?  Should I use Blackhawk's "USB560v2 STM Emulator (USB only) - BH-USB-560v2" (as was recommended elsewhere in this forum), or perhaps the older XDS510 USB PLUS JTAG Emulator from Spectrum Digital?  Must I use the latest version of DSPBIOS (in external SRAM), to be compatible with the latest CCS & emulator?  Or should I use an older version of CCS and an older emulator, so that I can use the existing DSPBIOS that's in the on-chip ROM?  Thanks!

  • Hi David,
    You can use CCS for development on this device. As for which debug probe, both are supported by CCS. However, the XDS510 is much older and being deprecated in support. Hence, of the two options, the XDS560v2 is a better investment.

    As for your other questions about that various versions, I will let the experts in the device forum answer those.

    Thanks
    ki
  • David, Brad Davis pointed me to this thread.
    With respect to DSPBIOS. The last version of CCS that could use the on chip ROM DSPBIOS libraries was CCS 3.3. This is way out of date, and not supportable. If DSPBIOS is used, it would need to be loaded externally.
    Regards,
    Wade
  • David,

    The on-board ROM has DSPBIOS code from a specific release. If you want to use that ROM-based code, then you will need to use header files that are compatible with it. The advantages are that the ROM executes faster than external memory and its use reduces some of the program memory required for your application.

    You do not have to use the ROM DSPBIOS. If you prefer, you can use any newer release that still supports the C6727B.

    There are some specific boot-related issues listed in the device errata that you have to handle in your loaded code, in either case. A few parameters must be placed at the right location as described in the errata.

    There are support files required for using the C6727B, and they will help with this. Have you found these files from TI.com?

    Regards,
    RandyP