AR #32912 - 11.2 ChipScope Analyzer - "ERROR:INTERNAL_ERROR:Portability:basutencodeimp.c:229:1.24"

Search Answers Database


 

11.2 ChipScope Analyzer - "ERROR:INTERNAL_ERROR:Portability:basutencodeimp.c:229:1.24"

AR# 32912
Part SW-Chipscope Pro
Last Modified 2009-06-24 00:00:00.0
Status Active
Keywords Vista, cable, java.io.IOException, Client, communication, thread, failed

Description

Keywords: Vista, cable, java.io.IOException, Client, communication, thread, failed

When I open the ChipScope Analyzer and attempt to connect to my JTAG chain, the following messages appear in the console:

"COMMAND: open_platform_usb_cable FREQUENCY=3000000 PORT=USB21
INFO: Started ChipScope host (localhost:50001)
INFO: Opened socket connection: localhost 50001 localhost/127.0.0.1
ERROR: INTERNAL_ERROR:Portability:basutencodeimp.c:229:1.24 - Number of bytes peeked does not match number of bytes requested. Corrupted file?
INFO: Connecting to cable (Usb Port - USB21).
INFO: Checking cable driver.
INFO: Driver file xusbdfwu.sys found.
INFO: Driver version: src=1027, dest=1027.
INFO: Driver windrvr6.sys version = 8.1.1.0.
INFO: WinDriver v8.11 Jungo (c) 1997 - 2006 Build Date: Oct 16 2006 X86 32bit SYS 12:35:07, version = 811.
ERROR: INTERNAL_ERROR:Portability:basutencodeimp.c:229:1.24 - Number of bytes peeked does not match number of bytes requested. Corrupted file?
ERROR: Client communication thread failed: java.io.IOException: An existing connection was forcibly closed by the remote host
ERROR: Failed to open Xilinx Platform USB Cable. See message(s) above"


I also receive a pop-up message that states the following:

"cse.exe has stopped working."

How do I work around this issue?

Solution

This issue is caused by the User Access Control (UAC) that is enabled on Vista.

Following are some work-arounds:

- Run the Analyzer as Admin on the machine. Browse to the %CHIPSCOPE%/bin/nt; directory -> right-click on the "analyzer.exe" file -> Select "Run as" -> Administrator.

- Disable the User Access Control (UAC). For instructions, please refer to Scenario 3 in the following Microsoft Technical Article:
http://technet2.microsoft.com/WindowsVista/en/library/0d75f774-8514-4c9e-ac08-4c21f5c6c2d91033.mspx?mfr=true

 
 
/csi/footer.htm