Hot!Transmission on endpoint 2 failed Error

Page: 12 > Showing page 1 of 2
Author
gtenrreiro
Senior Member
  • Total Posts : 175
  • Reward points : 0
  • Joined: 2008/06/20 08:32:22
  • Status: offline
2014/01/17 11:49:45 (permalink)
5 (1)

Transmission on endpoint 2 failed Error

Hi,
 
What is the solution to this frequent error message while trying to launch the debugger?
 
"Transmission on endpoint 2 failed"
 
This happens constantly, and I need to unplug the ICD 3 or the REAL ICE.
 
Thanks
 
 
#1

27 Replies Related Threads

    RISC
    Super Member
    • Total Posts : 5255
    • Reward points : 0
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2014/01/17 14:15:08 (permalink)
    0
    Hi,
     
    Which version of MPLAB X do you run ?
     
    regards
    #2
    gtenrreiro
    Senior Member
    • Total Posts : 175
    • Reward points : 0
    • Joined: 2008/06/20 08:32:22
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2014/01/17 16:30:27 (permalink)
    +1 (1)
    I am running 1.95, but it has always happened, no matter what version.
    I used to run an ICD 3, and it used to happen all the time. Now I am using a REAL ICE which I just got thinking that would be better? Still the same.
     
    Thanks
    #3
    forrest.hu
    New Member
    • Total Posts : 13
    • Reward points : 0
    • Joined: 2014/07/20 21:29:28
    • Location: 0
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2014/11/05 22:34:50 (permalink)
    +1 (1)
    I have the same issue.
     
    On some board,after finish debugger session, I have to disconnect and reconnect the ICD 3 to the USB cable several times,then I may got ICD3 reconnect to target and debug the program again.
     
    Sometime I find if I use external power supply rather than ICD3 's power,this error will not happen so frequently.It seems to be caused by USB power supply insufficient, or power supply not stable.
     
    Is there anything we should note,so that we could avoid below problem?
     
    *****************************************************
    Transmission on endpoint 2 failed
    Connection Failed.
    If the problem persists, please disconnect and reconnect the ICD 3 to the USB cable. If this does not fix the problem verify that the proper MPLAB X USB drivers have been installed.
    *****************************************************
    #4
    RISC
    Super Member
    • Total Posts : 5255
    • Reward points : 0
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2014/11/06 15:46:59 (permalink)
    0
    Hi Forrest,
    the ICD3 and Real-ICe drivers were improved AFAIK in the latest V2.1X, V2.2x versions.
    Are you running V2.20 or V2.25 ?
    Did you test your tools with the provided small auto-test PCB which enable you to do an auto-test ?
    Can you describe your ICSP circuitry from connector to the PIC ?
    Do you use the original ICSP cable provided with the tool ?
    Regards
    #5
    vipzrx
    New Member
    • Total Posts : 3
    • Reward points : 0
    • Joined: 2014/09/10 20:04:34
    • Location: 0
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2014/11/07 00:42:29 (permalink)
    0
    请检查你的USB线是否正常。
    我遇到了一个和楼主一样的问题,做了两个工作,遇到类似问题可以尝试下:
     
    1 重置ICD3
    2 换一条USB线缆
     
    #6
    forrest.hu
    New Member
    • Total Posts : 13
    • Reward points : 0
    • Joined: 2014/07/20 21:29:28
    • Location: 0
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2014/11/07 02:24:38 (permalink)
    +1 (1)
    Hi RISC:
    I found two way may help to reduce the error.
    1、Stable power,2、change an short USB cable to ICD3
     
    Do you have any other suggestion?Did you meet this issue?
     
    Below is the answer to your question.
    the ICD3 and Real-ICe drivers were improved AFAIK in the latest V2.1X, V2.2x versions.
    Are you running V2.20 or V2.25 ?
    Yes,I have test on V2.10,V2.15,V2.20 and now I am using V2.25.
    Did you test your tools with the provided small auto-test PCB which enable you to do an auto-test ?
    Yes,in fact,I have two ICD3.
    Can you describe your ICSP circuitry from connector to the PIC ?
    When using ICD3 + F1 Evaluation Kit,I have meet this issue too.
    Do you use the original ICSP cable provided with the tool ?
    Yes,and the cable is short too.
     
    Best Regards
    Forrest
    #7
    JuliaDee
    Super Member
    • Total Posts : 173
    • Reward points : 0
    • Joined: 2009/05/04 13:51:40
    • Location: Connecticut
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2017/01/07 12:17:08 (permalink)
    +1 (1)
    I've struggled with this maddening problem for several years, with a number of targets, two different ICD3's, a few versions of the IDE, various USB cables, various USB ports, etc. Two days ago my Asus Win7 PC's hard drive crashed, so I used that as an excuse to buy a new PC, another Asus, this time running Win10. MPLABX and the ICD seem to be operating perfectly now (knock on wood).

    "Given one hour in which to chop down a tree, I'd spend the first 30 minutes sharpening my axe" - Abraham Lincoln
    #8
    rpc48gx
    Super Member
    • Total Posts : 334
    • Reward points : 0
    • Joined: 2003/11/07 12:52:16
    • Location: Brighton, UK
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2018/08/09 04:37:21 (permalink)
    0
    I am getting this now.
    i have shortened the USB lead. Removed any potentially power hungry USB devices.
    It still does not work.
     
    I have not yet thrown an ICD3 at the wall (as someone I know did a few months back) due to this.
     
    But my board has 5V and 3V3. The processor seklected it right.
    Devices I could program with it NOW GET VEROR| POINT 2 all the nti9me
    WHY ?
    WHY?
    Should I upgrade MPLAB ? Every time the stupid thing tries to reconnect it thinks its a `differnt' icd 3, which means may its USB is in a confused state.
     
    WHY? Its been working for years and NOW IT WONT
    WHY?
    #9
    rpc48gx
    Super Member
    • Total Posts : 334
    • Reward points : 0
    • Joined: 2003/11/07 12:52:16
    • Location: Brighton, UK
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2018/08/09 04:47:02 (permalink)
    +1 (1)
    Ok theory.somehow the firmware in the ICD-3 has become corrupted. that kind of explains the cryptic error message. How to get it to read read through. Maybe try and program a different type of device? Even if its not connected?
    #10
    DarioG
    Allmächtig.
    • Total Posts : 54081
    • Reward points : 0
    • Joined: 2006/02/25 08:58:22
    • Location: Oesterreich
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2018/08/09 04:56:15 (permalink)
    +1 (1)
    sometimes corrupted FW leads to "funny" errors: try updating/rewriting it!

    GENOVA :D :D ! GODO
    #11
    rpc48gx
    Super Member
    • Total Posts : 334
    • Reward points : 0
    • Joined: 2003/11/07 12:52:16
    • Location: Brighton, UK
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2018/08/09 05:16:16 (permalink)
    +2 (2)
    rebooted the Linux machine. that probably reset the microchip USB driver. problem somewhere between the ICD-3 and the USB driver. very annoying because the error messages were talking about not being able to power the board under test, which encourages you look in the wrong direction / wrong part of the problem.
    #12
    DarioG
    Allmächtig.
    • Total Posts : 54081
    • Reward points : 0
    • Joined: 2006/02/25 08:58:22
    • Location: Oesterreich
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2018/08/09 05:21:44 (permalink)
    0
    don't tell me.
    on MPLAB X, when you have some hardware problem (for example forgetting to connect all VDD/VSS pins on a PIC for prototype) it says "you're attempting to program Protected Memory" and such...
     
    (reported time ago in X forum, to no avail)

    GENOVA :D :D ! GODO
    #13
    JuliaDee
    Super Member
    • Total Posts : 173
    • Reward points : 0
    • Joined: 2009/05/04 13:51:40
    • Location: Connecticut
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2018/08/09 05:28:28 (permalink)
    0
    Still happening to me occasionally; I just unplug-replug the ICD and move on.

    "Given one hour in which to chop down a tree, I'd spend the first 30 minutes sharpening my axe" - Abraham Lincoln
    #14
    NorvisLM
    Super Member
    • Total Posts : 75
    • Reward points : 0
    • Joined: 2015/10/06 07:32:11
    • Location: 0
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2018/08/09 10:14:04 (permalink)
    +1 (1)
    I get the dreaded Transmission on Endpoint 2 error with some devices whenever I add variables to the MPLAB X IDE Watchlist. Clear the watchlist and the problems go away. Add one or more variables and the problem immediately reappears. 
     
    Don't ask me how this can corrupt the USB drivers but it does. I have to unplug/plug the USB cable many times in a debug session if I am viewing variables. It doesn't matter which version of the IDE I am using. It also doesn't care if I use a PICKIT 3, ICD 3, PICKIT 4 or PKOB. They all exhibit the same behavior. 
    #15
    Jim Nickerson
    User 452 _
    • Total Posts : 5126
    • Reward points : 0
    • Joined: 2003/11/07 12:35:10
    • Location: San Diego, CA
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2018/08/09 10:36:11 (permalink)
    0
    NorvisLM,
    I wonder which OS you are running on which PC ?
    And USB Hub or not, US2 or 3 ?
     
    #16
    NorvisLM
    Super Member
    • Total Posts : 75
    • Reward points : 0
    • Joined: 2015/10/06 07:32:11
    • Location: 0
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2018/08/09 10:43:50 (permalink)
    +1 (1)
    Windows 10, USB 2 and 3.
     
    I have tried numerous cables, at least 4 different PCs, two ICD3's, a PICKIT 3 and PICKIT 4. IT seems to be ICD independent. 
     
    What confuses me is that I am able to view the File Register Window without incident. Wouldn't a few watch variables require a subset of the USB communication necessary to view the entire set of File Registers?
     
     
     
    #17
    Jim Nickerson
    User 452 _
    • Total Posts : 5126
    • Reward points : 0
    • Joined: 2003/11/07 12:35:10
    • Location: San Diego, CA
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2018/08/09 11:20:42 (permalink)
    0
    NorvisLM,
    I have no knowledge of the debug device communications via ICSP.
    The only difference I see is accessing the PIC ram versus the SFR's are likely handled in a different manner.
    There is a small piece of Debug software running on the PIC to manage the communication with the debug tool.
    Each family of PIC has some debug support built into the silicon.
    #18
    NorvisLM
    Super Member
    • Total Posts : 75
    • Reward points : 0
    • Joined: 2015/10/06 07:32:11
    • Location: 0
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2018/08/09 14:55:14 (permalink)
    0
    JANickerson
    Each family of PIC has some debug support built into the silicon.



    And so it goes that the PIC24FJ256GB110 is trouble free while the ICD USB interface goes bonkers with the PIC24FV16KM202, whenever I add variables to the watchlist.
    #19
    rpc48gx
    Super Member
    • Total Posts : 334
    • Reward points : 0
    • Joined: 2003/11/07 12:52:16
    • Location: Brighton, UK
    • Status: offline
    Re:Transmission on endpoint 2 failed Error 2018/08/10 01:57:03 (permalink)
    +1 (1)
    My MPLAB crashed this morning so I xkilled it.
     
    Then on re running mplab_ide from a terminal got following error messages

    libusb couldn't open USB device /dev/bus/usb/002/008: Permission denied.
    libusb requires write access to USB device nodes.
    libusb couldn't open USB device /dev/bus/usb/002/008: Permission denied.
    libusb requires write access to USB device nodes.
    COMM::=MPLABComm-USB-Microchip:=<vid>04D8:=<pid>9009:=<rev>0100:=<man><cannot_open>04D8:9009:=<prod><cannot_open>04D8:9009:=<sn>?:=<drv>x:=<xpt>b:=end
    libusb couldn't open USB device /dev/bus/usb/002/008: Permission denied.
    libusb requires write access to USB device nodes.
    libusb couldn't open USB device /dev/bus/usb/002/008: Permission denied.
    libusb requires write access to USB device nodes.

    sure enough when trying to reprogram he device I got the confusing message about power to the board.
     
    Unplugged the USB, waited, and now its working OK. But this does seem like some sort of misunderstanding between the USB driver and the ICD-3.
     
    #20
    Page: 12 > Showing page 1 of 2
    Jump to:
    © 2018 APG vNext Commercial Version 4.5