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.

SMJ320C40: Code Composer/JTAG Emulator Recommendation

Part Number: SMJ320C40
Other Parts Discussed in Thread: TMS320C40

Hello,

I need an info on a JTAG emulator for the SMJ320C40 DSP for programming a connected flash memory device during production test.

Originally a Spectrum Digital XDS510PP and some version of Code Composer Studio was used.  This equipment is no longer available.

Is there a currently available Code Composer/JTAG Emulator combination that would support the following test operation?

The test procedure sequence is:

  1. Use the File->Load Program... menu to load a file with a ".out" extension.
  2. Click the "Run" button, after which some dialog boxes appear prompting for:
    1. The manufacturing ID of the attached flash device:
    2. The name of the file to program into the flash device (".hex" extension).
    3. Some system configuration information.

It appears that these dialog boxes are generated by the program loaded into the C40, in conjunction with Code Composer (I haven't dug in to the CC docs yet).

Thanks.

  • Hi, Douglas,

    I am getting info and will get back to you.

    Rex

  • Douglas,

    If I understand you correctly, you just want to set up an environment  as you lost an old equipment.

    1) CC vs CCS

    I assume you are looking for "Code Composer (CC)", and not "Code Composer Studio (CCS)". CC predates the entire CCS line. The last version of CC was released in 1997. After that, it was replaced by CCSv1.

    Since you mentioned you used CCS earlier, can you please confirm?

    My understanding is C40 is not supported by CCS but on CC.

    CCS is free, but CC is not. Do you still have your license information?

    2) Yes, Spectrum Digital XDS510PP should work. I searched and found this:

    http://www.spectrumdigital.com/xds510pp-plus-jtag-emulator-with-code-composer-for-the-tms320vc33-c4x/

    If this is a new design, I would suggest you move on to new version of DSPs.

    best regards,

    David Zhou

  • David,

    The existing test procedure specifically refers to "Code Composer Studio".  The earliest documentation we have for the product dates from 2014, but I would guess that the design predates that.

    After the RUN button is clicked, the application appears to be able to write to the "stdout" window and get user input via dialog boxes with ""standard input dialog box" as their caption.  I'm assuming that the debug libraries have the capability of asking for user input via CCS dialog boxes?  Do all versions of CCS support this?  Would the CCS version need to match the versions of the I/O libraries that the target application is compiled/linked with?

    For the JTAG emulator, the XDS510PP uses a parallel port, which we'd rather avoid.  Searching the Spectrum Digital web site for "TMS320C40", which should be compatible with the SMJ320C40GFM50, brings up their XDS200 emulator, which connects to the host PC via a USB port, and is much less expensive.  I don't know if this is supported by the version of Code Composer that is compatible with what we're trying to do.

    Regards,

    Doug Allen

  • Doug,

    Does your test procedure mentioned the version number of "Code Composer Studio" and emulator used earlier?

    From TI only "Code Composer" supports 320C40 and CCv4.1x is the last version to support C4x.

    What is the version of CC or CCS you are using now to flash? Can you provide some screenshots for "CCS dialog box"?

    For emulator: TI XDS510 ISA card is supported. The XDS510PP would also work.

    https://www.ti.com/lit/ug/spnu070c/spnu070c.pdf

    I am not sure about XDS200 though from the data search that I performed on 320C40.

    Best regards,

    David Zhou

  • Hi Doug,

    Douglas Allen14 said:
    The existing test procedure specifically refers to "Code Composer Studio".  The earliest documentation we have for the product dates from 2014, but I would guess that the design predates that.

    No version of "Code Composer Studio" ever supported the C4x. David is correct in that you are likely looking for "Code Composer", which predates the "Code Composer Studio" line. The last version of Code Composer ever released was CCv4.1x. This is likely the version that you need

    Douglas Allen14 said:
    After the RUN button is clicked, the application appears to be able to write to the "stdout" window and get user input via dialog boxes with ""standard input dialog box" as their caption.  I'm assuming that the debug libraries have the capability of asking for user input via CCS dialog boxes?  Do all versions of CCS support this?  Would the CCS version need to match the versions of the I/O libraries that the target application is compiled/linked with?

    If you can post what these dialog boxes look like, that would be helpful. I am going to guess that these are the GEL dialogs which was supported in most CC and CCS versions

    Douglas Allen14 said:
    For the JTAG emulator, the XDS510PP uses a parallel port, which we'd rather avoid.  Searching the Spectrum Digital web site for "TMS320C40", which should be compatible with the SMJ320C40GFM50, brings up their XDS200 emulator, which connects to the host PC via a USB port, and is much less expensive.  I don't know if this is supported by the version of Code Composer that is compatible with what we're trying to do.

    That was be some error with Spectrum Digital's website. the XDS200 does not support C4x. It also only supports later versions of Code Composer Studio. It never supported the old Code Composer line.

    Your emulator options are limited to the XDS510PP or the old XDS510 ISA:

    https://www.ti.com/lit/ug/spnu070c/spnu070c.pdf

    You would also need a PC with Windows XP-32 or earlier. It is very unlikely that the old CC tools will run on any OS later than that.

    ki 

  • Ki and David,

    I've attached a screen shot of the "Standard Input Dialog Box" from the test procedure.  The stdout window can also be seen (displaying a table and the text "Please enter the target Flash Manufacturing ID ->").

    I'm guessing that the target application can be linked with I/O libraries that "know" how to interact with CC/CCS to display text and input dialog boxes in the UI.

    Regards,

    Doug

  • Douglas Allen14 said:

    I've attached a screen shot of the "Standard Input Dialog Box" from the test procedure.  The stdout window can also be seen (displaying a table and the text "Please enter the target Flash Manufacturing ID ->").

    I'm guessing that the target application can be linked with I/O libraries that "know" how to interact with CC/CCS to display text and input dialog boxes in the UI.

    It kind of looks like a GEL input dialog, but I'm not 100% sure. Talking to some folks here, I think the old CC handed IO input through that dialog. I need to find someone to confirm. Not too many people left who remember since this was over 20 years ago...

  • The "TMS320C3x/C4x Optimizing C Compiler User's Guide" appendix B.1 seems to answer the question about the I/O (dialogs and stdout window) between the target CPU and the CC UI:

    "The C I/O functions make it possible to access the host’s operating system to
    perform I/O (using the debugger). For example, printf statements executed in
    a program appear in the debugger command window. When used in
    conjunction with the debugging tools, the capability to perform I/O on the host
    gives you more options when debugging and testing code."

    Anyway, I think I know what I need now.

    Thanks,

    Doug