FAQ:  What is the cause of the Target Connection Error 0x80004005 or 0x80044005?

Q:

I occasionally receive the Target Connection Error 0x80004005 or 0x80044005 when trying to connect to my target in the IDDE - what causes this?

 

----------

 

A:

There are a number of problems which may be the root cause of a Target Connection Error.

 

First, ensure that the Session you are connecting to within VisualDSP++ is appropriate to your hardware. Check the target processor(s) and, if appropriate, the Emulator.

 

This error could also be caused by a corrupt Session. To determine if this is the cause, please delete your current session and re-create it from scratch. This can be done via 'Session'->'New Session' or by starting VisualDSP++ while holding the 'CTRL' key and choosing "New Session" when the 'Session List' window appears.

 

You should also check the Device Manager to confirm there are no reported problems with the hardware.

 

Please test your target board to ensure that it is not in a bad state, e.g. stuck in Reset. If you are using a Custom Board we would also recommend that you consult EE-68 for details of the JTAG specification to ensure your board conforms to this standard.

 

For our Emulator Troubleshooting please review either EE-175 or EE-356 and carrying out all troubleshooting techniques described:


 

The EE-Notes are available in our Technical Library.

 

----------

 

This FAQ was generated from the following thread: What is the cause of the Target Connection Error 0x80004005 or 0x80044005?

Comments
Anonymous
    •  Analog Employees 
    in reply to AshokMajee

    Hi Ahok,

    again, I think such questions would be best directed to private support. Or, alternatively you could post any questions in their own thread, rather than on this FAQ.

    Thanks,

    Craig.

  • in reply to ADIApproved

    Hi Craig,

    Thank you for your response .

        In my custom board the reset signal generated by ADM 708 and same reset signal is routed

    to other three ICs and one reset indicator  LED.

      whenever i disconnect the reset signal from one of the IC ,its working fine means target getting connected , again put back problem is showing. But i dont have any other alternate choice to generate reset signal for other ICs, can we get any alternate reset IC from ADI to drive four ICs together ? or alternate reset mechanism for TS 201A processor.

    regards

    ASHOK

    •  Analog Employees 
    in reply to AshokMajee

    Hi Ashok,

    I would recommend following the Emulator Troubleshooting Guide, EE-175, available via the link below:

    http://www.analog.com/ee175

    As it is a custom board, you should also ensure your design fully complies with the JTAG specification detailed in EE-68:

    http://www.analog.com/ee68

    Do you have another emulator available? Does this work with the target?

    If the problem persists, we would have to look at the possibility of the Emulator being faulty. For that, you should go through private support who can offer more thorough troubleshooting guides, and advise of the replacement process:

    http://www.analog.com/processors/support

    Regards,

    Craig.

  • I am getting same error during connecting my custom target board.

    Error Code : 0x80004005

    target : custom ADSP TS201 board.

    platform : Win 7 with vdsp5.00 ,update 8

    previously it is working fine suddenly this error is coming even after so many time trying once is getting connected also.

    emulator: HPUSB-ICE

    I did following steps for getting connected...........

    1) verify the target session.

    2) delete the session and   create new session

    3) from device manager remove the emulator drive rand install again ,showing fine at device tree.

    4) Remove complete vdsp and reinstall again.

    5) change working new emulator and adopter and usb cable.

    6) check processor core and i/o voltage and input clock.

    7) change host pc also.

    Somebody  can tell the where the emulator not getting connected ??

Related