This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

VCP auto-connection problem

Other Parts Discussed in Thread: TMDSCNCD28035ISO

Hello,

I am struggling with the VCP auto-connection problem already mentioned several times in this forum.

In short: I get the message "VCP auto-connection is enabled for this interface, but there was a problem retrieving COM ports from your system. This may be due to a WMI corruption."
 when starting any sample program for my motor development kits with a kit connected. I followed all the suggested solutions in other posts. However, everything looked fine. The device "Texas Instruments XDS100+RS232 V1.0" contains all required functions (TI XDS100 Channel A, TI XDS100 Channel B, USB Serial Port (COM3), USB Composite Device), updating the XDS100 drivers for channel A or B with the TI drivers as suggested by an older post leads to the windows message that the current driver is the same and up to date (FTDI driver from March 18 2011, version 2.8.14.0 with correct windows signature). Furthermore, for XDS100 Channel B, VCP is activated, but not for Channel A, as described in other posts.
The virtual COM3 is configured as follows: 9600 bos, 8 data bits, no parity, 1 stop bit, no flow control.

The only , that the device manager lists "BCM20702A0" as unknown device. However, I do not know if this is a TI device or related to it.
What do you suggest?

Many thanks,
Stefan

  • Hi Stefan,

    Stefan Goetz said:
    The only , that the device manager lists "BCM20702A0" as unknown device. However, I do not know if this is a TI device or related to it.
    What do you suggest?

    The above unknown device is Broadcom Bluetooth device and not of any TI products. Secondly, this is the window you're able to observe right?

    Regards,

    Gautam

  • Gautam,

    Thanks a lot for your quick reply. In my device manager, both TI XDS100 Channel A and TI XDS100 Channel B are among the USB Controllers and are not marked as unknown or with any driver issues. Thus, everything looks absolutely perfect.
    That is exactly, what makes me nervous.

    Best,
    Stefan
  • That's kinda odd! So, when you enable VCP connection, you get a virtual comport COMxx or not?
  • Gautam,

    Yes, indeed. COM3 is my FTDI USB interface, also listed as working interface in the device manager. In the device manager the check box activate VCP is only checked for XDS100 Chennel B. Although I do not understand the difference between channels A and B yet, this was to my understanding from older posts how it should be.

    Best,
    Stefan
  • Stefan, just for confirmation: did you check this thread?
    e2e.ti.com/.../919485

    Regards,
    Gautam
  • Gautam,

    Thanks a lot. I tried to flash the code as suggested. However, I fail when I try to connect to the target:
    "Error connecting to the target: (Error -1135 @ 0x0) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation (Emulator package 5.1.450.0)"

    Interestingly, testing the target configuration (TI XDS100v1 with a F28035) fails with 83% success on the memory test:

    "[Start: Texas Instruments XDS100v1 USB Emulator_0]

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

    [Result]


    -----[Print the board config pathname(s)]------------------------------------

    C:\Users\p\AppData\Local\TEXASI~1\
    CCS\TI\0\0\BrdDat\testBoard.dat

    -----[Print the reset-command software log-file]-----------------------------

    This utility has selected a 100- or 510-class product.
    This utility will load the adapter 'jioserdesusb.dll'.
    The library build date was 'Mar 9 2014'.
    The library build time was '22:27:48'.
    The library package version is '5.1.450.0'.
    The library component version is '35.34.40.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '4' (0x00000004).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller.
    This utility has successfully reset the controller.

    -----[Print the reset-command hardware log-file]-----------------------------

    The scan-path will be reset by toggling the JTAG TRST signal.
    The controller is the FTDI FT2232 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for FTDI FT2232 features.
    The controller cannot monitor the value on the EMU[0] pin.
    The controller cannot monitor the value on the EMU[1] pin.
    The controller cannot control the timing on output pins.
    The controller cannot control the timing on input pins.
    The scan-path link-delay has been set to exactly '0' (0x0000).

    -----[The log-file for the JTAG TCLK output generated from the PLL]----------

    There is no hardware for programming the JTAG TCLK frequency.

    -----[Measure the source and frequency of the final JTAG TCLKR input]--------

    There is no hardware for measuring the JTAG TCLK frequency.

    -----[Perform the standard path-length test on the JTAG IR and DR]-----------

    This path-length test uses blocks of 512 32-bit words.

    The test for the JTAG IR instruction path-length failed.
    The JTAG IR instruction scan-path is stuck-at-ones.

    The test for the JTAG DR bypass path-length failed.
    The JTAG DR bypass scan-path is stuck-at-ones.

    -----[Perform the Integrity scan-test on the JTAG IR]------------------------

    This test will use blocks of 512 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    The details of the first 8 errors have been provided.
    The utility will now report only the count of failed tests.
    Scan tests: 2, skipped: 0, failed: 1
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 2
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 3
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 4
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 5
    Some of the values were corrupted - 83.3 percent.

    The JTAG IR Integrity scan-test has failed.

    -----[Perform the Integrity scan-test on the JTAG DR]------------------------

    This test will use blocks of 512 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    The details of the first 8 errors have been provided.
    The utility will now report only the count of failed tests.
    Scan tests: 2, skipped: 0, failed: 1
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 2
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 3
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 4
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 5
    Some of the values were corrupted - 83.3 percent.

    The JTAG DR Integrity scan-test has failed.

    [End: Texas Instruments XDS100v1 USB Emulator_0]
    "

    Best,
    Stefan
  • Hello Stefan,

    I can help you get your kit working with the on-card emulator.  Since you have not mentioned your hardware setup, I am assuming that you have one of the DRV-C2 kits (with a TMDSCNCD28035ISO as the controlCARD).

    1) Make sure you've gotten the target configuration correct - looks like you've got this correct.
    2) Make sure the SW3 on the controlCARD is switched toward the 'ON' position.
    3) Make sure that the controlCARD is being power twice.  If everything is correct LD1 and LD4 should both be powered.
    [a] via the mini-USB cable on the left side of the controlCARD (powers the emulator circuitry)
    [b] via power from the baseboard (this powers the F28035 chip).

    ---

    Note that if flashing the MCU doesn't fix your GUI issue (which it may), I think I might suspect the GUI itself.  I will ask others on my team if they have any other thoughts.  Based on what you've described, I think the hardware is working correctly and Windows is finding the correct drivers (FYI: channel A of the xds100v1 is used for the JTAG connection, channel B does the VCP connection). 


    Thank you,
    Brett

  • Hello,

    Is there any news on this matter? I have been trying to run the GUI with the TMDSHVMTRPFCKIT (F28035 controlCARD) and I have the exact same behavior described by Stefan: "VCP auto-connection is enabled for this interface, but there was a problem retrieving COM ports from your system. This may be due to a WMI corruption." I followed the steps described in the Quick Start Guide on 2 different computers, it does not work. I flashed the MCU again, but nothing changes. Found this and another post on TI website but there's no solution. Is there a problem with the GUI as suggested by Brett on his last message?

    Thanks,

    Michel
  • Hi Michel,

    First of all, thanks for listing what hardware you're using :).

    I cannot fully comment.  The GUI utilized works based on Crosshairs, whom we do not work with anymore.  The link between their GUI and the PC would be fully in their domain.

    Assuming you have a R1.1 board, I have 2 suggestions:

    1. Once the Crosshairs GUI provides you the error message, the GUI window still pops up.  You can then click "Connection->Start Connection Wizard" and you may be able to get things working from there.
    2. Eventually you'll need to move to CCS in order to delve more deeply into the kit.  The HowToRunGuide is written like a lab document, and it shouldn't be too difficult to get started using this path.



    Thank you,
    Brett