I'm using the most recent TI BT stack with MFi support running on the STM eval board, and also ported to our custom STM platform. We have used multiple versions of the SS1/TI stack on multiple platforms over the last two years, and we've always had consistent behavior creating Windows 7 virtual COM ports for connecting to our BT devices: We create an SPP server port on our (slave) BT device, use "Just works" secure simple pairing. When we pair with the device on Windows, it reliably creates a COM port which we then use to communicate with the BT device.
However, the TI BT stack's API for implementing SPP while also supporting MFi has changed something. We can communicate with the BT device using iOS and Android RFCOMM, but Windows 7 cannot create a virtual COM port as long as we use the MFi API. Is there something about the MFI-modified SDP record format that interferes with identifying the BT SPP server port as being SPP compatible?
Thanks!
