Hello Mario,
Thanks for your reply. Your query's answers are as below:
Are you trying to transfer by console or by UART? I tested by my side and it works.
>> I am sending data by console.
What is the SDK version that you are working on?
>> I am using SDK version 2.2.1
Could you please describe step by step the process that you are following?
>> Steps:
1. Import "Bluetooth Wireless UART Baremetal" example code.
2. Set value of "gAppUseBonding_d" and "gAppUsePairing_d" as 1.
3. Build Project. And Upload to KW36 EVM module.
4. Set EVM module as Peripheral.
5. Open IOT application in mobile device and click on Wireless UART.
6. Start advertising on EVM module. IOT application shows bluetooth device on mobile device.
7. Click on it. Application ask for pairing.
8. Enter passkey to pair with EVM module.
9. After successful pairing try to transfer data.
I tried again by importing same example code as per above steps. And I am able to transfer and receive data using console and UART both with Bluetooth versions 4.0, 4.1, 4.2 and 5.0. It means there is no problem right now.
Then we have changed code to run as GAP Peripheral only and it works fine.
Till now we have done basic testing and found no issue. We do more testing on it as per our requirement. And will contact you if found any other problem.
But wants to ask you one thing that, in my previous example code of "Bluetooth Wireless UART Baremetal" I have made some changes as below:
>> Commented SecLib_Init(), RNG_Init(), RNG_SetPseudoRandomNoSeed(NULL) in main_task() of AppMain.c file.
>> Excluded DCDC framework from compilation.
>> Excluded I2C driver file from compilation.
Do these changes will effect on connection?
Kindly give suggestion on this.
Thank you.