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.

Problem with cc2540 usb dongle

Other Parts Discussed in Thread: CC2540

Hi,

I have recently bought a CC2540DK-MINI and I have tried to follow the basics that is described in the user's guide but when I tried to connect the usb dongle to the pc it don't sees it at all.

I have searched some solutions that tell me to flash the hex file CC2540_USBDongle_HostTestRelease_All.hex, but it doesn't seem to make anything. The usb dongle just have a green led and it switch to red and disconnects when I press one of the buttons. I have tried too to flash an old hex file, from version 1.1. With that the pc sees the dongle and I can connect to BTool, but it has always a red led turn on and the data that it shows on BTool isn't correct.

Can someone help me please? Is that some issue from version 1.3?

  • Hello Jorges,

    Have you tried compiling the hostTestRelease project found in the project folder and loading that into your Dongle?  I don't recall offhand having a problem when I used that method with BLE v1.3.

    Thanks,

  • Hi,

    I have a similar problem. My CC2540-MINI-DK was purchased 1.5 year ago and was working well with v1.1 and v1.2. Today I loaded the v1.3 HostTestRelease to the dongle but my PC could not recognize the dongle (no virtual COM port in device manager). I tried to compile the project as well as debug via IAR and also load the hex file directly via CC debugger, but I still could not see the virtual COM port in device manager. I am thinking there might be some problem with the HostTestRelease project in v1.3 since v1.2 was working perfectly on my PC.

    Thank you.

  • Hello Jun,

    I have only used BLE v1.3 running on WinXP with IAR 8.10.  There have been no issues.  If you are running another version and Windows 7, there are some post in the forum that helped resolve any issues.

    http://e2e.ti.com/support/low_power_rf/f/538/t/163044.aspx

    Thanks,

  • Thank you! It is working now.

    I first load the v1.2 hex file and update the driver to the latest one downloaded from another post (http://e2e.ti.com/support/low_power_rf/f/538/p/243424/901341.aspx#901341), then I I load the v1.3 hex file again. After rebooting and changing to another USB port, I finally can see the virtual COM port in device manager.

  • Hi Jun,

    I tried your way and it worked after a few retries. Thank you all guys.