Hot!Transmission on endpoint 2 failed Error

Page: < 12 Showing page 2 of 2
Author
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 04:22:43 (permalink)
+1 (1)
Could Microchip change this error message ?
Its quite misleading.It makes you think there is something wrong with the board under test.
It really seems to mean the USB between the PC and the ICD-3 is having problems.

*****************************************************
Transmission on endpoint 2 failed
The target circuit may require more power than the debug tool can provide. An external power supply might be necessary.
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.

 
#21
NorvisLM
Super Member
  • Total Posts : 78
  • Reward points : 0
  • Joined: 2015/10/06 07:32:11
  • Location: 0
  • Status: offline
Re:Transmission on endpoint 2 failed Error 2018/08/10 11:49:30 (permalink)
+1 (1)
 
The following are some of the errors I get when the PC to ICD USB connection would goes haywire. None of them had anything to do with the ultimate root cause.
 
You would think that Microchip could write a bulletproof PC to ICD, USB driver that could care less what happens on the target side of the POD.
 

Failed to program the target device 
The debugger could not be started. Terminating debug session. 
No source code lines found at program counter 
ICD3 was unloaded while still busy. Please unplug and reconnect the USB cable before using ICD 3 again. 
Transmission on endpoint 2 failed 
The target circuit may require more power than the debug tool can provide. An external power supply might be necessary.
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. 
Could not connect to tool hardware: ICD3PlatformTool, com.microchip.mplab.mdbcore.ICD3Tool.ICD3DbgToolManager
The debugger could not be started. Terminating debug session. 
Failed reading bulk data (memory type 12, address 1858
Invalid command response (sent 0x61, received 0x3f) 
An internal run error has occurred. It is advised that you restart your debug session. You may continue running but certain run time features may no longer work properly. 
An Error occurred while running 
Reception on endpoint 1 failed
Reception on endpoint 1 failed (err = -121)
 
A communication error with the debug tool has occurred. The tool will attempt to recover momentarily.
 
A tool request has been waiting for more than a second. The debug tool will try to service the request within another second. After that the request will be rejected. 
A tool request has been rejected because it could not be serviced within the two second timeout period.

#22
domble
Senior Member
  • Total Posts : 111
  • Reward points : 0
  • Joined: 2007/01/25 04:11:53
  • Location: 0
  • Status: offline
Re:Transmission on endpoint 2 failed Error 2018/08/14 04:01:48 (permalink)
+2 (2)
It's always seemed odd that errors on the PIC side of the ICD / pickit cause communication errors on the USB connection between PC and ICD.  Surely they should be independent!  Wonder if anyone knows if ICD4 / pickit4 manage to keep ICSP and USB errors seperate?  That would be a good selling point for me - it's annoying having to re-plug the USB.
 
dom.
p.s. forum only works on https so why does it still allow http connections?
#23
KTrenholm
Super Member
  • Total Posts : 558
  • Reward points : 0
  • Joined: 2012/08/08 14:04:23
  • Location: Connecticut, USA
  • Status: offline
Re:Transmission on endpoint 2 failed Error 2018/08/14 06:29:37 (permalink)
0
FaulknerPD
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.



Weird, I'm using the 3.3v version of this chip (PIC24F16KM202) and haven't run across any funny behavior when adding variables to the watchlist while debugging (Using ICD3).
 
Well, at least no more issues than is typical.  Sometimes the "Transmission over Endpoint 2" error just happens for no real reason, but that's the case for any chip.  Usually just disconnecting and reconnecting USB from the ICD3 clears it up for me, but yes it can be annoying.  Some days it just feels like the debug tools and USB driver just sort of work "when they feel like it"
post edited by KTrenholm - 2018/08/14 06:34:56
#24
NorvisLM
Super Member
  • Total Posts : 78
  • Reward points : 0
  • Joined: 2015/10/06 07:32:11
  • Location: 0
  • Status: offline
Re:Transmission on endpoint 2 failed Error 2018/08/14 12:09:23 (permalink)
0
KTrenholm
Weird, I'm using the 3.3v version of this chip (PIC24F16KM202) and haven't run across any funny behavior when adding variables to the watchlist while debugging (Using ICD3).

 
OS, MPLAB X version?
#25
KTrenholm
Super Member
  • Total Posts : 558
  • Reward points : 0
  • Joined: 2012/08/08 14:04:23
  • Location: Connecticut, USA
  • Status: offline
Re:Transmission on endpoint 2 failed Error 2018/08/14 12:11:30 (permalink)
0
FaulknerPD
KTrenholm
Weird, I'm using the 3.3v version of this chip (PIC24F16KM202) and haven't run across any funny behavior when adding variables to the watchlist while debugging (Using ICD3).

 
OS, MPLAB X version?




Windows 7 x64
MPLAB X v4.15
 
#26
NorvisLM
Super Member
  • Total Posts : 78
  • Reward points : 0
  • Joined: 2015/10/06 07:32:11
  • Location: 0
  • Status: offline
Re:Transmission on endpoint 2 failed Error 2018/08/14 18:05:41 (permalink)
0
Perhaps Windows 10 is the culprit.
#27
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/09/12 05:20:05 (permalink)
0
OK two of us in the same office using different computers are getting this now. It seems like some kind of driver mis match because re booting linux seems to sometimes fix this. the error points to the PCB 5V but ITS NOT THAT.
 
This is incredibly disruptive.
Its getting impossible to get work done becayuse of this
 
What has happened to the linux drivers or the firmware in the ICD-3 BECAUSE IT USED TO WORK
#28
Page: < 12 Showing page 2 of 2
Jump to:
© 2018 APG vNext Commercial Version 4.5