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.

TMDSSK3358: JTAG connection too slow on VirtualBox

Part Number: TMDSSK3358

I tried to connect the target board TMDSSK3358 via JTAG on VirtualBox. But it took more than ten minutes to connect. During connecting, OnTargetConnection() message was displayed as shown in Fig.1 . After connecting, CCS response was too slow to debug.

I can use USB memory or micro SD card via USB-SDcard converter without slow response.

Do you have any idea to fix this problem ?

[ Additional Information]
The attached evm.ccxlm is the target configuration file.
The attached lsusb.txt is the result of lsusb commands.
Fig.2 shows USB settings on VirtualBox. USB 2.0 is selected.

Fig.1

Fig.2

lsusb.txt

7840.lsusb.txt
uegaki@hqr3113:~/ex1/workspace$ lsusb
Bus 001 Device 003: ID 0403:6010 Future Technology Devices International, Ltd FT2232C Dual USB-UART/FIFO IC
Bus 001 Device 002: ID 14cd:168a Super Top 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
uegaki@hqr3113:~/ex1/workspace$ lsusb -v -s1:3

Bus 001 Device 003: ID 0403:6010 Future Technology Devices International, Ltd FT2232C Dual USB-UART/FIFO IC
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0403 Future Technology Devices International, Ltd
  idProduct          0x6010 FT2232C Dual USB-UART/FIFO IC
  bcdDevice            7.00
  iManufacturer           1 FTDI
  iProduct                2 EVM-SK\XDS100V2
  iSerial                 3 FT3NTXUJ
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           55
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2 EVM-SK\XDS100V2
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2 EVM-SK\XDS100V2
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)
uegaki@hqr3113:~/ex1/workspace$ 

  • evm.ccxlm was not be uploaded in previous posting. Then, I re-post it as code insertion. 

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <configurations XML_version="1.2" id="configurations_0">
        <configuration XML_version="1.2" id="Texas Instruments XDS100v2 USB Debug Probe_0">
            <instance XML_version="1.2" desc="Texas Instruments XDS100v2 USB Debug Probe_0" href="connections/TIXDS100v2_Connection.xml" id="Texas Instruments XDS100v2 USB Debug Probe_0" xml="TIXDS100v2_Connection.xml" xmlpath="connections"/>
            <connection XML_version="1.2" id="Texas Instruments XDS100v2 USB Debug Probe_0">
                <instance XML_version="1.2" href="drivers/tixds100v2icepick_d.xml" id="drivers" xml="tixds100v2icepick_d.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds100v2cs_dap.xml" id="drivers" xml="tixds100v2cs_dap.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds100v2cortexM.xml" id="drivers" xml="tixds100v2cortexM.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds100v2cs_child.xml" id="drivers" xml="tixds100v2cs_child.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds100v2cortexA.xml" id="drivers" xml="tixds100v2cortexA.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds100v2csstm.xml" id="drivers" xml="tixds100v2csstm.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds100v2etbcs.xml" id="drivers" xml="tixds100v2etbcs.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds100v2pru.xml" id="drivers" xml="tixds100v2pru.xml" xmlpath="drivers"/>
                <platform XML_version="1.2" id="platform_0">
                    <instance XML_version="1.2" desc="SK_AM3358_0" href="boards/sk_am3358.xml" id="SK_AM3358_0" xml="sk_am3358.xml" xmlpath="boards"/>
                    <board XML_version="1.2" description="AM3358 StarterKit Board" id="SK_AM3358_0">
                        <device HW_revision="1" XML_version="1.2" description="AM33x - Cortex A8 Embedded Processor" id="AM3358_0" partnum="AM3358">
                            <router HW_revision="1.0" XML_version="1.2" description="ICEPick_D Router" id="IcePick_D_0" isa="ICEPICK_D">
                                <subpath id="subpath_11">
                                    <router HW_revision="1.0" XML_version="1.2" description="CS_DAP Router" id="CS_DAP_M3" isa="CS_DAP">
                                        <subpath id="M3_wakeupSS_sp">
                                            <cpu HW_revision="1.0" XML_version="1.2" desc="M3_wakeupSS_0" description="Cortex_M3 CPU" id="M3_wakeupSS" isa="Cortex_M3"/>
                                        </subpath>
                                    </router>
                                </subpath>
                            </router>
                        </device>
                    </board>
                </platform>
            </connection>
        </configuration>
    </configurations>
    

  • Hi Naoto,

    Virtual Machine is slow in general and often has USB connection issues. It is not recommended and not validated with any Sitara platform.

    Please use a real PC to see if the issue still happens.

  • Hello
    I think that you're making sense.
    Actually, I have a real Linux laptop and USB-JTAG speed is enough.

    By the way, I'm trying to create telework environment.
    This means that a member of our company is limited to have a Windows10 laptop for the purpose of telework because of VPN software requirement and security consideration.
    Also, in Japan, government strongly recommends telework because of COVID-19.
    Therefore, I want to be able to use CCS JTAG debug on VirtualBox.

    Any advice would be appreciated.

  • Hi Uegaki-san,

    Though I don't use Windows for development work, but I believe you could install CCS on your (or your team member's) Windows laptop and directly connect to USB-JTAG. Will this setup work for your project?

  • Than you for your advice.
    Good idea. It's one of solutions.

    I've already use CCS on Windows10, and confirmed good USB-JTAG response.
    But USB-JTAG on VirtualBox could provide more seamless debug environment than USB-JTAG on Windows10.
    If USB-JTAG on VirtualBox work smoothly, this is the best solution.

    Anyway, I think that this thread should be checked as resolved.
    If you have additional idea, please keep me informed.