CC2540 USB Slave

You will need to rebuild the HostTestRelease application using the "CC2540USB Slave" configuration. Note that the BTool GUI does not directly support slave mode, though you can use the "Adv. Commands" tab to run slave mode commands.

Is there anyway to make it discoverable once it is in slave mode? I have an iPhone 4s and I'm trying to connect to it but I'm not able to find the dongle.

Perhaps you could be interesting in setting the variable initial_advertising_enable set to  

uint8 initial_advertising_enable = TRUE;

Did you manage to achieve what you were hoping back in January? I'm in an analogous position. I'm tasked to develop a BLE App for the iPhone 4S and want something (anything!) to act as a BLE peripheral, just to be sure that the iPhone can see it. If I'd known for sure that the Wahoo Heart Rate Monitor followed the BLE spec in its service, I'd regret not shelling out $80 for one. As it is, I've bought the CC2540 USB Dongle, and then a CC Debugger to reprogram it (all on an old Dell Latitude, running XP), and so I'm out-of-pocket more than the cost of the Wahoo toy. BTool sees the Dongle, but I can't see how to get it into slave mode and advertise something (Generic Access would be nice). The only hex file that seemed available for reprogramming the Dongle was CC2540_USBdongle_HostTestRelease_All (which seems to have replaced some older hex files) and so, based on the "All" part (as opposed to "Master") it seems as though there may be hope that the Dongle can be simply told to be a slave. 

To Willis1: Please see my reply to nrgautama's January post. Any help would be appreciated.

I'll toss in one more question: There is are hex files down there which conceivably might have some application. I imagine CC2540_keyfob_SimpleBLEPeripheral.hex is intended only for the Keyfob (which I don't have). But there's also CC2540MiniDkDemoSlave.hex. Where is that used?