Problem to detect probe : SocketException

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Problem to detect probe : SocketException

820 Views
AnthonyJutonENS
Contributor I

On Windows 10, The redlink server doesn't detect the LPC11U35 link probe. There is a connection on the port 3025 and then, we have SocketException Connection Reset.

The board works on all the other computers and this computer doesn't work on any board.

I look on the community but I feel that I am alone with this problem. We reinstall the LPC11U35 driver.

AnthonyJutonENS_0-1602168344940.png

Your propositions and ideas are welcomed.

 

Thank you

 

0 Kudos
Reply
1 Reply

811 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

 

 

 

After much digging it looks like your issue is being triggered by functionality called "HCVI" that is enabled in some versions of Windows 10, but not others (and MS have also changed this functionality in recent builds too).

 

You can check by looking at the following registry key in regedit :

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity

Hello,

You can try the below method, this is from other customers case, he fixed by this way:

 

" The problem occurs when the "Enabled" field has value of 1. To fix, change the value of "Enabled" field of this key to 0, and then reboot.  The LPC DFU driver will then load successfully, and then, after the probe has been booted by the IDE, the LPC-Link driver installs correctly - and then debug the LPCXpresso V1 board successfully.

 

The following article gives more background information on this: 

https://borncity.com/win/2018/07/06/windows-10-v1803-hcvi-causes-driver-error-code-39/

"

 

Regards,

Alice

0 Kudos
Reply