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.

  • Resolved

USB-CTM-MINIDK-EVM: Windows 64 bit USB driver does not support CC2540 USB Dongle (MINIDK)

Intellectual 650 points

Replies: 3

Views: 342

Part Number: USB-CTM-MINIDK-EVM

Hi all,

I bought CC2540 USB Dongle (MINIDK) rev. 1.0.1 and I can't find working driver for Windows x64.

I did search a lot of threads here and neither of answers could provide a solution.

If CC2540 USB Dongle is connected to Windows 10, it is installed as COM port with Microsoft driver. In this case I cannot use BT packet sniffer, coz device is not recognized.

I did USB trace on Win 10 and this device: device descriptor cleary states USB VID and PID:

  •  idVendor  Texas Instruments 0x0451
  •  idProduct 0x16AA


I did check that Setup_SmartRF_Studio_7-2.10.0.exe installs cebal driver, where USB PIDs are the following:


cebal2_x64.inf
;******************************************************************************
; Models section (specifies the supported device's hardware ID)
;------------------------------------------------------------------------------
; x64-based systems
[_Models.ntamd64]
%S_DeviceDesc1%  = _Install_1,  USB\VID_11A0&PID_DB20           ; CC2430DB
%S_DeviceDesc2%  = _Install_2,  USB\VID_11A0&PID_EB20           ; SmartRF04EB
%S_DeviceDesc3%  = _Install_3,  USB\VID_0451&PID_16A0           ; SmartRF05EB
%S_DeviceDesc4%  = _Install_4,  USB\VID_0451&PID_16A2           ; CC Debugger
%S_DeviceDesc5%  = _Install_5,  USB\VID_0451&PID_16AB           ; CC2511 USB dongle
%S_DeviceDesc6%  = _Install_6,  USB\VID_0451&PID_16AC           ; CC2511 USB nano dongle
%S_DeviceDesc7%  = _Install_7,  USB\VID_0451&PID_16AD           ; CC1111 USB dongle
%S_DeviceDesc8%  = _Install_8,  USB\VID_0451&PID_16AE           ; CC2531 USB dongle
%S_DeviceDesc9%  = _Install_9,  USB\VID_0451&PID_16B2           ; Generic CCxxxx USB dongle
%S_DeviceDesc10% = _Install_10, USB\VID_0451&PID_16B3           ; CC2540 USB dongle
%S_DeviceDesc11% = _Install_11, USB\VID_0451&PID_16B5           ; SmartRFTrxEB
%S_DeviceDesc12% = _Install_12, USB\VID_0451&PID_16B8           ; Generic CCxxxx evaluation board
%S_DeviceDesc13% = _Install_13, USB\VID_0451&PID_16C6           ; CC2544 USB dongle
%S_DeviceDesc14% = _Install_14, USB\VID_0451&PID_16CB           ; CC2538EM


In swrc212a.zip package driver has even less PIDs defined.

It is obvious that no driver found for such a dongle with PID 0x16AA.

Could anyone at TI explain

1. why was USB PID changed for already existing product thus creating headache for all developers?

2. Where is the 64bit USB driver for devices with PID 0x16AA for CC2540 USB Dongle (MINIDK) rev. 1.0.1 ?

3. Is there any different FW version for CC2540 USB Dongle (MINIDK), so USB PID would be as in the driver? What is the version number and where is it stored?

  • Expert 7185 points
    Dear Alexey,

    We will look into this and get back to you.

    Best Regards,
    Reidar
  • In reply to R.M:

    Hi Alexey,

    Your are right, it would be a headache if we should change the PID.

    I think the problem is  that the dongle comes with FW that is not compatible with the packet sniffer (Prepared for the BTool I think). 

    The dongle needs to be reprogrammed with FW that follows the packet sniffer. See Chapter 1.2 Hardware platforms for instruction on where to find the correct FW for the CC2540 Dongle. User manual for the Packet sniffer: www.ti.com/.../swru187

    The user guide of the MINIDK kit contains information on how to use the flash programmer together with the CC Debugger. I guess you have already figured that out.

    With the correct FW on the dongle you should see the correct PID and it should be working on Windows 10 64 bit. That is what I'm using myself.

    Regards,

    Øyvind

  • In reply to Øyvind K:

    Hi,

    Yes, in order to use packet sniffer app I had to flash a specific FW version from SmartRF Tools which has a different USB PID and then driver matching works ok.
    I think TI documentation for wireless connectivity dev kit cc2541dk-mini is a bit confusing, so it took me a while to sort it out.

    Regards,
    Alexey

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.