• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 56 subscribers
  • Views 5837 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.

"Error Connecting to Target": HVMotorCtrl+PFC kit

Glen Springle
Prodigy 60 points
Other Parts Discussed in Thread: CONTROLSUITE

I am having problems connecting to my HVMTRPFC kit to download and debug a project (from the ControlSuite examples)

The thread link below looked very similar, however even after working through it, I still get some variation of the "Error Connecting to Target" message

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/43494.aspx?PageIndex=1

My setup is as follows:

OS: WIndows 7 64 bit
EVK: HVMTRPFCKIT (F28035)
CCv4.2.4.00033 (first install was 4.1.3 but upgraded as part of this process)
M3-J5 no jumper
Connection: Texas Instruments XDS100v1 USB (also tried v2)
Board or Device: Developers Kit - High Voltage Motor Control and PFC (F28035)
Project: HVACI_Sensorless [F2803x_RAM]  
Device Manager sees TI XDS100 Channel A and B under USB Controllers
Device Manager sees USB Serial Port COM6
I ran the GUI demo which successfully communicated with the kit using COM6
Different combinations of powering down/disconnecting the EVK and re-starting CCv4

I have tried connecting to the target through the project (Debug Active Project) and non-project debug (Launch TI Debugger | Connect Target)

I always get some form of the "Error Connecting to Target" message.

Error connecting to the target:
(Error -1041 @ 0xFFFFFF87)
The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation.
(Release 5.0.429.0)

Error connecting to the target:
(Error -1135 @ 0x0)
The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation.
(Release 5.0.429.0)

I'm not sure what to try next. Any ideas or suggestions are welcome.

Glen

  • 0
    TI__Guru**** 467401 points

    Hi Glen,

    The next thing to try is to take CCS out of the equation and run some JTAG connectivity tests from the command line.

    See: http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems

    Please post the results of these tests.

    Thanks

    ki

     

  • 0 in reply to Ki
    Prodigy 60 points

    Thanks Ki,

    That helped a lot!

    I installed the DBGJTAG GUI utility (http://processors.wiki.ti.com/index.php/DBGJTAG_Graphical_User_Interface).

    It detailed the specific fault as being:

    The explanation is:
    The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
    An attempt to scan the JTAG scan-path has failed.
    The target's JTAG scan-path appears to be broken
    with a stuck-at-ones or stuck-at-zero fault.

    After connecting my oscilloscope and checking the TCK/TDI/TDO lines, the solution is to put a jumper on [Main Board-J9]. This passes TRSTn to the F28035 board.  The DBGJTAG GUI succeed.  Next I need to test it with the HV Project.

    The [Main-J9] description is in the HVMTRPFC Hardware Guide.  I guess I just missed it or mis-interpreted it.

    Thanks again,

    Glen

  • 0 in reply to Glen Springle
    Prodigy 225 points

    Glen,

    I'm having similar issues with my High Voltage Digital Motor Control Kit. That is, any time I try to connect from CCS, I get the error:


    Error connecting to the target:
    (Error -1135 @ 0x0)
    The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation.


    Did putting the jumper on [Main Board-J9] solve your problem? What were your results when you tested this with the HV board? I'm currently in the process of running the JTAG tests that you ran to diagnose the problem.

    EDIT: I ran the JTAG GUI and got the exact same error you did. Putting a jumper on J9 did NOT remedy the problem. 

    Thanks,

    Mike

  • 0 in reply to tvich11
    Prodigy 60 points

    Mike,

    In my case installing the [Main Board-J9] was enough to get it working with the JTAG GUI.  After that, I tried with Code Composer Debug and was successful as well.

    Glen

  • 0 in reply to Glen Springle
    Prodigy 180 points

    Glen, Ki,

    Thank to your discussion I was able to solve my problem (exactly the same as described by Glen).

    Now I'm ready to proceed to the next error!!!

    Thanks again.

     

  • 0 in reply to Riccardo Dell'Oro
    Expert 1240 points

    when i run, DBJTAG, i got following error:

    The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
    An attempt to scan the JTAG scan-path has failed.
    The target's JTAG scan-path appears to be broken
    with a stuck-at-ones or stuck-at-zero fault

    kindly help me pls

  • 0 in reply to Ki
    Prodigy 60 points

    Hi,

    I just got the TMDSHVMTRPFCKIT in our lab. Set it up and try to do the first demo according to the Quick start Guide. Followed the steps and have the GUI successfully connected to the motor with only the DC power on, but once powered on the AC, the PC(Win7 64) can't recognize the driver any more. The COM port disappeared and the X100 A and B turned to unknown. Tried with different PC (win8), same result. If everything turned off and repowered up, with DC power only, the fault will clear and driver will come back to normal, but once AC on, same fault shows. Also tried power everything only with AC rectified power, driver will just be directly unknown in this case. 

    At this stage, it seems the AC power may not be isolated with this USB connection for this particular one we got. I wonder if this is a defect in the hardware for this particular one. Or am I doing anything incorrectly? Desperately need and deeply appreciate some help and guidance right now. 

    Thanks a lot.

    Regards,

    Jian