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.

RDK-S2E JTAG

Other Parts Discussed in Thread: LM3S6432

I am trying to interface the following:

  • RDK-S2E with 10 pin JTAG connection
  • Spectrum Digital XDS510PP Plus
  • CCS V4

The RDK-S2E comes with an ARM JTAG 10-20P Adapter, but the XDS510PP Plus has a 14-pin connector.  What is needed to connect the two together?

I posted this question on the Luminary Micro forum, and got the response back about the post "Using XDS 510 with DK-LM3S9B96"; however, the DK-LM3SB96 has a different 20 pin connection than the ARM JTAG 10-20P Adapter.

  • As mentioned in this wiki article, you need a 20-pin ARM to 14-pin TI Emulation Adapter to connect with the XDS510PP plus:
    http://processors.wiki.ti.com/index.php/JTAG_configuration_for_CCS_and_Stellaris

    So you would need the 10 to 20 pin ARM JTAG adapter that comes with the kit and then the 20-pin ARM to 14-pin TI adapter on top of it. Note that in addition to the adapter, you would also need to short Pin 9 and Pin 11 together as mentioned in that page.

    Also a full licensed CCS (or free eval license) will be needed to debug the RDKs.

     

  • Currently, we have made our own 20-pin ARM to 14-pin TI emulation adapter to verify proof-of-concept.  Pins 9 and 11 of the 14-pin TI connector are shorted to tie the TCK and TCK return together.

    I have a licensed copy of CCS V4.

    I have setup the target connection to: Spectrum Digital XDS510 Parallel Port-PCI  Emulator and the Board or Device to: Stellaris LM3S6432

    When I try to debug in CCS4, I get the following error message:

    Error connecting to the target:
    Error 0x80000240/-1063
    Fatal Error during: Initialization, OCS,
    Bad Target Silicon Revision Number
    Please check your multi-processor configuration.
    The number of devices in the JTAG scan path
    must be correct for the silicon revision to be read.
    Or, you may have selected the wrong DSP device driver.

    However, if I run SDConfigEx v4, I get the following results:

    ** Checking for a valid emulator/eZdsp

      $$ You are connected to:
      $$ EmuProductName=XDS510PP_PLUS
      $$ EmuPortAddr=0x378
      $$ EmuPortMode=SPP8
      $$ ProductId=10
      $$ ProductVersion=02

    ** Checking for a valid emulator/eZdsp

      $$ You are connected to:
      $$ EmuProductName=XDS510PP_PLUS
      $$ EmuPortAddr=0x378
      $$ EmuPortMode=SPP8
      $$ ProductId=10
      $$ ProductVersion=02


    ** Checking emulator/eZdsp scan connection

    ** Emulator Test **

     $$ EmuProductName=XDS510PP_PLUS

     $$ EmuPortAddr=0x378

     $$ EmuPortMode=SPP8

     $$ ProductId=10

     $$ ProductVersion=02

     ** Emulator Scan Test

       -- Found JTAG IR length of 4

       -- Found 1 JTAG device(s) in the scan chain

     **Emulator is reset

    So it appears that the JTAG connection is working; otherwise a device wouldn't be found.

    Is it possible that something is set wrong in CCS4?

  • Here is the version of Code Composer Studio that I am using:

     

    Version: 4.2.0.10017

    Is it possible I have an old device on my RDK?

    Here is the info from the device:

    LM3S6432
    1BZ50A2SD
    $9-02P069H
     ARM    G1

     

    -Nelson

  • It works with the following version of Code Composer Studio:

     

    Version: 4.1.0.02006

    Why doesn't it work with the latest version of CCS4?

  • I can connect to the RDK-S2E with a Spectrum Digital XDS510USB with CCS 4.1.3 but not with CCS 4.2. I am having trouble connecting with XDS510PP plus with either version of CCS. I will try to contact Spectrum Digital and see if they can shed more light on this.

  • Nelson,

    I found out that there were changes made in CCS 4.1.3 and higher that require the following change to make Stellaris devices work with xds510 emulators:
    Open the target configuration (.ccxml) file, go to the 'Advanced' tab and make sure 'Access Port Designator' option for Cortex M3 is set to 0x02000000.

    The TI default is 0x02000003 which could result in a bad target silicon revision number error when you try to connect to a LM3S device.

  • I changed the Access Port Designator to 0x02000000 and CCS 4.2 is now working.  Thanks!!!