Why Does a Disconnect Turn Off LED2?

[rvaessen]

I am working with the PCA10028 board, SDK 10.0.0, and s110 8.0.0. I have created a characteristic that is "coupled" to LED2. When a connected central writes a value to the characteristic, my code on the PCA10028 turns LED2 on or off according to the value that was written. The difficulty that I am experiencing is that when the remote central disconnects LED2 is being turned off (not by my code). At this point the LED's state and the value of the characteristic are no longer synchronized. I could fix this by detecting the disconnect (or perhaps the next connect) event and resynchronizing them. But, I would prefer to understand what is happening and, perhaps, prevent it all together. Would someone please give me some insight into what is occurring?

[RK]

you can modify it but you probably don't want to as it will mess up the examples. First job would be to find out what LED2 is being used for (I long since forgot) and ensure that is your problem, it seems likely. Then you could either make a custom board def file which moves LED2 to somewhere which doesn't exist, or see if there's a define in there to turn off the whatever it's doing behaviour.

You're most welcome on RKNRFGO, it doesn't get a whole lot of love these days so if it falls behind softdevice-wise, do tell me. I guess I should make it support the new new chip soon.