CC Debugger - Always RED led when programming CC2540

The ccdebugger is designed to talk directly to the CC2540 chip. You mention a BLE112 Module. I assume that you mean the Bluegiga BLE112 Module.

The CC2540 chip from Factory comes with NO Firmware. It does nothing wen you power it up.
The Bluegiga BLE112 Module has a preprogrammed firmware. I don't know the details, you should contact Bluegiga for this (or at least read their documentation). While they physically use the same CC2540 chip they have their own Firmware and SDK. Supposedly this is to shorten the development cycle. Their customer support is said to be pretty good so please ask there.

You might still be able to Programm the CC2540 chip within the BLE 112 Module, but then (I guess) you won't be able to use Bluegiga BLE stack.

I see at least one big problem for this. For any JTAG interface to work MOSI, MISO and SCLK have to be connected, since these carry the data lines. So please try to figure out where the SPI interface lines go to on your BLE112 Module and connect them.

Latest Version for CCdebugger is 0042, but this should not matter.

Hi Burak and thanks for your response.

Yes, I am referring to bluegiga's module.

I was asking that because I read some articles about using CC debugger and BLE112. Even in Bluegiga's documentation mention that.

Due to I have 6 modules, I was wondering if I was doing anything wrong.

The programming interface is like a JTAG, but not exactly a SPI bus.

I paste you a few links talking about it.

http://blog.bluetooth-smart.com/2012/09/11/programming-the-ble112-with-c-code-using-iar/

http://www.ambientsensors.com/bluetooth-low-energy-projects

Actually just yesterday I have connected a CC1101 chip to the CCdebugger the same way as desribed in that blog, it worked nice.
Here is a short list of things you could check :
1) They seem to use a purple adapter Board. The pinout of the purple adapter board does not necessarily have to match the pinout of the BLE112 module. If you are not using exactly that adapter board please check your pinouts.
2) Check any solder joints and cables. Even better measure from end to end with an ohmmeter.
3) The CCdebugger sometimes does not directly recognise the chip even if the connections to the chip are already in plaace while you connect the USB cable. Press the reset button after you have connected everything ( including usb )
4) Maybe one or another of the power lines are not connected correctly, connect all VCC, VDD, VSS and GND lines apropriately.

If this really works, and I assume it does depending on the blog post you have linked.

Thanks for answering burak.

1)I am using directly a BLE112 module, so I wired directly the pins of the module.

2)I checked the connections with a multimeter and they are ok. I also connected all VCC and GND pins.

3) Checked and rechecked and no luck

4) I have connected all, adn now I am able to discover the module scanning it with a smart phone. So the module is running but not recognized by cc debugger.

I am going to add some capacitors to 3V3 supply and also I will try the pull up and RC filter recommended in cc debugger guide. What do you think?

Could be any level issue on DD or DC lines.?

I attach a picture of my setup with one of the modules.

Burak,

You were right.

I made a simple PCB board to make connections more robust (and also I connected all VDD and GND lines) and it worked!

My purpose was to test this module so quickly so I did not do the connections robust -- my mistake.

thanks for your answers.

Happy I could help you :)