Other Parts Discussed in Thread: BLE-STACK
Hello,
I've searched around for the answer but the threads I found were either very dated or didn't have a clear answer. I've implemented a thin wrapper for the DTM interface on our project over UART. We'd like to avoid having to program a Host Test application during production.
The transmitter test works as expected. I've been trying to verify the receiver test but not having any luck. After I call HCI_LE_TestEndCmd() my application receives the HCI_LE_TEST_END event from the stack. I've tried pulling the packet count out this way, but I'm not sure if this is correct:
case HCI_LE_TEST_END: { uint16_t pktCnt = (uint16_t)command_complete->pReturnParam[1] << 8; pktCnt += command_complete->pReturnParam[2]; appCliDtmEndEvent(status, pktCnt); break; }
I also found this thread, in the last post it looks like he is expected pReturnParam[] bytes 7 and 8 to contain the packet count. I've tried both of these and don't seem to be getting the expected results back. Does anybody know if the packet count is available, and if so how to access it?
I'm running the tests on a custom board with an R2F. I'm using a 2650LP to act as the transmitter when running the receive test on our board. I've triple-checked that both transmitter and receiver are operating on the same channel/freqeuncy (BLE Channel 37 / 2402 MHz). The only other thing I'm unsure of in my test setup is if the "PDU payload length", "Adv. Address" fields, etc. in SmartRF studio matter? Do these have to be configured in a specific way for the device-under-test to actually "count" the packets?
Thanks
Josh