• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 401 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC Debugger and shorted P1 and P2 in 10 pin ribbon

James Guberski
Prodigy 10 points
Other Parts Discussed in Thread: CC2650STK, CC2540, CC2560

I am a more than a month into my project and have zero completed. My management team now thinks I am an idiot. They expected I would be up and running in 3 minutes..just by changing the CC2650STK from Bluetooth to Zigbee to extend the range a bit which is within the CC2650STK capabilities according to the documentation.

As a side note my company is still only supporting Windows 7...so after more frustration I determined why my PC does not recognize any BLE 4.0 devices...so 

I bought a CC2540EMK Packet sniffer that I wanted to use as the interface to the CC2650STK. This seemed possible according to the BLE device monitor Users Guide.

I found out once I got the CC2540EMK that I needed a CC debugger to reprogram the sniffer so I bought a CC debugger.

To make a long and still frustration experience short I eventually found that the small 10 pin ribbon cable that came with the CC debugger is shorted between pins 1 and 2 at one of the connectors. It was not an easy process to identify the short without external meters and an O'scope. I kept thinking I must be doing something wrong. I tried unsuccessfully to get help from support or a replacement cable from TI...after 2 more days I purchased a cable from another source  and paid a $26 premium to get it the next day. I know the cable is now OK but the CC debugger still does not recognize any downstream devices. I am not sure if the CC2540EMK is damaged and or if the CC debugger is damaged. The CC2540 was powered from my PC and when the debugger was connected the green LED went out and the cable became noticeably warm after a short time.  Can you ship me a replacement CC debugger and CC2540EMK and give me an RMA number to return these items. I disposed of the defective cable just so I would not try to use it again. I no longer have the defective cable.

I have purchased a CC2560 development kit...That at least passed the getting started tests.. but after reading a bit I am not sure if the Smart RF06 can be used to connect to the CC2540EMK...

The Sales order number for the CC Debugger is 163067062 that has all my delivery information. I don't have the CC2450EMK sales order number handy so please don't ask for it

Hopefully this won't take many more days... my managements expected 3 minutes completion time is way past due..

  • 0
    TI__Guru** 105180 points
    Hello James,

    I'm sorry for the trouble you have experienced with the CC Debugger cable. As we are unable to process returns on E2E, please find the RMA procedure in the TI eStore FAQ: www.ti.com/.../gencontent.tsp, under "Returns and Refunds".

    For the packet sniffer, you do not need the full CC2540EMK, you can use the CC2540USB dongle, but you do need the CC Debugger to program the dongle with the sniffer firmware.

    To answer your question, yes, you can connect to the CC2650STK (BLE) with any BLE compliant Central device. This includes the CC2540EMK (running Central FW), another CC2650STK or a PC host with BT4.0 capability (Win 8.1+).

    For questions about ZigBee, please see the ZigBee forum.

    Best wishes