Hi
Thank you for your reply.
As you mentioned, I tested single QN9080-DK with NXP Iot toolbox app in an android phone.
First, when using the Private_profile_client example, Bluetooth connection was not established with the phone. This is probably because the phone is set as the client and cannot be changed. So, I set QN9080-DK as the server for Bluetooth connection using Private_profile_server example.
Second, the data rate was measured without changing the code of the Private_profile_server example at all. In this case, 1M Phy was expected to be used, so I set only LE 1M in QPP of the NXP Iot toolbox and set the Request MTU to 247.
At 1M Phy, the measurement result was 47370 Bps.
Third, I changed the code you pointed out in the Private_profile_server example. However, there were some differences in server example from the client example, and the codes I changed are as follows.
In qpps:
1. #define gBleUseHSClock2MbpsPhy_c 1
2. #define gGapConnEventLengthMin_d = 0xFFFF,
3. #define mQppsTxInterval_c (0)
4. #define gConnPhyUpdateReqTxPhySettings_c (gLePhy2MFlag_c)
5. #define gConnPhyUpdateReqRxPhySettings_c (gLePhy2MFlag_c)
6. #if 1//gConnInitiatePhyUpdateRequest_c
if ((mSupportedFeatures & ((uint32_t)gLe2MbPhy_c |(uint32_t)gLeCodedPhy_c)) != 0U)
{(void)Gap_LeSetPhy(FALSE, 0, 0, gLePhy2MFlag_c, gLePhy2MFlag_c, 0);
//(void)Gap_LeSetPhy(FALSE, peerDeviceId, 0, gConnPhyUpdateReqTxPhySettings_c, gConnPhyUpdateReqRxPhySettings_c, gConnPhyUpdateReqPhyOptions_c);
}
In this case, 2M Phy was expected to be used, so I set only LE 2M in QPP of the NXP Iot toolbox and set the Request MTU to 247.
At 2M Phy, the measurement result was 54737 Bps.
Contrary to expectations, switching to 2M Phy did not double the speed.
Is it correct that 2M phy is set normally?
How can I get the speed higher than 1M bps?