I have that bluetooth module (blue CSR8645, with EEPROM) - but on a different breakout board, where all pins are broken out, and there is only minimal circuitry on board (power-on enable, and mic input paossives).
As thats a nice big image of it I think I can name the pins from where they are connected on that module - the blue board, not the carrier.
If we number the pins from the top left, down, across the bottom, then up the right...
1 = optional antenna, NC.
2 = LED1
3 = LED0
4 = AI0, NC
5 = SPI_MISO
6 = SPI_CS
7 = SPI_CLK
8 = SPI_MOSI
9 = SPI/PCM. - note I2S/PCM is most likely disabled on the ROM, so this pin must be high to enable the SPI port for configuration.
It seems the smaller half pitch holes are indeed for the SPI connection. One would need 7 pins... two for power and ground, 4 for the SPI port, and one to enable the SPI port. I am guessing this is just a config header for use with CSR's USB adapter (there's an open source one that just uses an FT232R, google "csr-spi-ftdi").
As for the naming, you'll have to check which pins are connected to the module
K is connected to pin 6, which is SPI_CS.
E is connected to pin 9, which is SPI/PCM, should be pulled high to IO voltage (1.8V on this module, but you can get away wtih 3.3V via a 10k resistor).
I'm guessing 'I' is input, as this is a slave device, that would me MOSI.
Also guessing 'O' is output.. MISO.
That leaves 'B, which might be clock. Note these are guesses.
As I said you'll have to check with a continuity tester.
Link to pinout of the actual module:
http://www.electrodragon.com/w/File:8645_pin_definition.png