Part Number: CC2650
Hi,
We are tyring to certify our product with the Bluetooth SIG. We pass all tests in the PTS tool other than GATT/SR/UNS/BI-01-C.
Test Description:
• Test Procedure
Lower Tester sends an Attribute PDU with the Attribute Opcode field set to a randomly generated request opcode, with the Command Flag set to 0, that is not in the list of ATT Requests supported by the IUT (if the IUT supports all the request opcodes defined by the specification, then the generated opcode will be an RFU value).
If the value of the Authentication Signature Flag is 1, then the Authentication Signature field of the Attribute PDU is set to a random 12-octet value.
The Attribute Parameters field of the Attribute PDU is set to an array of random octets, of size limited by the ATT_MTU and the authentication signature.
• Expected Outcome
Pass verdict
The IUT responds with an ATT Error Response PDU, with the Request Opcode In Error field set to the opcode sent by the Lower Tester, the Attribute Handle In Error field set to 0x0000, and the Error Code field set to 0x06 (Request Not Supported)
According to the PTS documentation, the IUT should respond with ATT_ERR_UNSUPPORTED_REQ, however our device responds with ATT_ERR_INVALID_PDU.
We are using ble_sdk_2_02_02_25 with SNP on the cc2650, controlled by an MSP432. I've searched through all relevant code and have concluded that ATT_ERR_INVALID_PDU is returned from inside the stack, and the ATT opcodes have already been check before any of our functions are called.
So, Im unsure if this version of the stack can pass PTS 7.3.0 when configured as a BLE peripheral. If it can, could you please provide some example code of where we need to make changes to pass this test.
Thanks
