• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 81 subscribers
  • Views 728 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.

XDS100v2 emulator connection

Gloria Budiman
Intellectual 815 points
Other Parts Discussed in Thread: TMS320F28035

On the TMS320F28035 datasheet, TMS and TDI are not pulled-up. But this document -> http://www.google.com/url?sa=t&rct=j&q=error%20connecting%20to%20the%20target%3Aerror%200x00001200%2F-1041&source=web&cd=1&ved=0CBsQFjAA&url=http%3A%2F%2Fe2e.ti.com%2Fcfs-filesystemfile.ashx%2F__key%2FCommunityServer.Components.PostAttachments%2F00.00.13.90.84%2FI-am-trying-to-connect-to-an-TMS320F2812-with-an-XDS100v2-emulator.pdf&ei=bKa9Tq73McHj0QHd2_GtBA&usg=AFQjCNGE7FXC--N9uQbMyurdWHIA1EBR2Q said otherwise. Which one is correct?

 I'm getting the same error as mentioned in the PDF.

Also, regarding the pin layout on XDS100v2 JTAG header, which one is correct?

1 2

3 4

5 6 <-- blocked, KEY

7 8

9 10

11 12

Or

1 14

2 13

3 12 <-- blocked

4 11

5 10

6 9

7 8

Thanks

  • 0
    TI__Guru 55700 points

    Gloria,

    Please Pg 11 of http://www.ti.com/lit/ds/symlink/tms320f28035.pdf datasheet. Both TDI and TMS have internal pull up.

    Regards,

    Manoj

     

  • 0 in reply to Manoj Santha Mohan
    Intellectual 815 points

    The problem is Parallel Debug Manager can't connect to my bare TMS320F28035, but it can connect to Piccolo ControlStick.

    Error was as follows:

     

    Error connecting to the target:

    Error 0x00001200/-1041

    Error during: OCS, Target, 

    Device driver: Problem with the Emulation Controller.

     

    How do I debug this?

    EDIT: I faithfully follow the schematics on page 109 on the document referred to in your post

  • 0 in reply to Gloria Budiman
    Intellectual 815 points

    Oh, and I just did a DBGJTAG Integrity test with no error:

    -----[Print the reset-command software log-file]-----------------------------

     

    This utility has selected a 100- or 510-class product.

    This utility will load the adapter 'jioserdesusb.dll'.

    The library build date was 'Jun 14 2011'.

    The library build time was '22:23:33'.

    The library package version is '5.0.429.0'.

    The library component version is '35.34.29.0'.

    The controller does not use a programmable FPGA.

    The controller has a version number of '4' (0x00000004).

    The controller has an insertion length of '0' (0x00000000).

    This utility will now attempt to reset the controller.

    This utility has successfully reset the controller.

     

    -----[Print the reset-command hardware log-file]-----------------------------

     

    The scan-path will be reset by toggling the JTAG TRST signal.

    The controller is the FTDI FT2232 with USB interface.

    The link from controller to target is direct (without cable).

    The software is configured for FTDI FT2232 features.

    The controller cannot monitor the value on the EMU[0] pin.

    The controller cannot monitor the value on the EMU[1] pin.

    The controller cannot control the timing on output pins.

    The controller cannot control the timing on input pins.

    The scan-path link-delay has been set to exactly '0' (0x0000).

     

    -----[Perform the Integrity scan-test on the JTAG IR]------------------------

     

    This test will use blocks of 512 32-bit words.

    This test will be applied just once.

     

    Do a test using 0xFFFFFFFF.

    Scan tests: 1, skipped: 0, failed: 0

    Do a test using 0x00000000.

    Scan tests: 2, skipped: 0, failed: 0

    Do a test using 0xFE03E0E2.

    Scan tests: 3, skipped: 0, failed: 0

    Do a test using 0x01FC1F1D.

    Scan tests: 4, skipped: 0, failed: 0

    Do a test using 0x5533CCAA.

    Scan tests: 5, skipped: 0, failed: 0

    Do a test using 0xAACC3355.

    Scan tests: 6, skipped: 0, failed: 0

    All of the values were scanned correctly.

     

    The JTAG IR Integrity scan-test has succeeded.

     

    -----[Perform the Integrity scan-test on the JTAG DR]------------------------

     

    This test will use blocks of 512 32-bit words.

    This test will be applied just once.

     

    Do a test using 0xFFFFFFFF.

    Scan tests: 1, skipped: 0, failed: 0

    Do a test using 0x00000000.

    Scan tests: 2, skipped: 0, failed: 0

    Do a test using 0xFE03E0E2.

    Scan tests: 3, skipped: 0, failed: 0

    Do a test using 0x01FC1F1D.

    Scan tests: 4, skipped: 0, failed: 0

    Do a test using 0x5533CCAA.

    Scan tests: 5, skipped: 0, failed: 0

    Do a test using 0xAACC3355.

    Scan tests: 6, skipped: 0, failed: 0

    All of the values were scanned correctly.

     

    The JTAG DR Integrity scan-test has succeeded.

     

  • 0 in reply to Gloria Budiman
    TI__Guru 55700 points

    This could be a hardware issue (or) CCS issue. Given that you are able to connect control stick to CCS using XDS100 tells that there is something in hardware. Do you have any other emulators you can try? How many devices did you try to connect?

    These links should help you...

    Debugging JTAG Connectivity Problems

    http://processors.wiki.ti.com/index.php/XDS100#Troubleshooting_FAQ

    Regards,

    Manoj

     

  • 0 in reply to Manoj Santha Mohan
    TI__Guru 55700 points

    Try reseting the DSP (or) power cycle your board.

    -Manoj

  • 0 in reply to Manoj Santha Mohan
    Intellectual 815 points

    Actually now that you mentioned CCS issue, I tried again and I could put simple program and run it fine in CCS4.2. CCS 3 (not sure what the subversion number) couldn't connect to it. And yes, it's using the bare MCU, not ControlStick.

    Wonder why that is...

  • 0 in reply to Manoj Santha Mohan
    TI__Guru 55700 points

    It would not be a bad to try reinstalling the CCS as some of our customers have tried reinstalling CCS and everything started working.

    -Manoj

  • 0 in reply to Gloria Budiman
    TI__Guru 55700 points

    XDS100v2 is not supported in CCS3.3.

    -Manoj

  • 0 in reply to Manoj Santha Mohan
    Intellectual 815 points

    I've been prototyping using ControlStick with XDS100v2 for 2 months on CCS 3 prior to receiving the bare MCU. I'm sure that's not the case...