1.Which KW36 SDK example can use OTA updates, from OTA phone to BLE Master ?
2.Which KW36 SDK example can use OTA updates, from BLE Master to BLE Slave ?
3. If the OTA can go from BLE Master to BLE Slave, which example that can update four BLE slaves at once?
Organize your reply：
chapter 5.19 of the BLE Demo Applications User Guide,
There are only two OTA: Test Tool to Board and IOT toolbox to Board
1. OTA update from OTA phone to BLE Master
Ans: Yes, KW36 support it ?
Use ATT / l2cap.srec from BLE OTAP sever to BLE OTAP Client board via OTA,
2. OTA update from BLE Master to BLE Slave
Ans: Yes, KW36 supported it ?
Which two SDK example( Master、Slave) can be implemented? Give me example path.
3. BLE Master update four BLE slaves
Ans: Yes, KW36 supporte it ?
Need to modify gAppMaxConnections_c,
Which SDK example is to be modified?
Hope can be explained in order, because I don't know which example corresponds to each of the 3 questions?
I need your detailed description
To better explain myself, and to answer your questions:
The OTA Client examples (otac_att and otac_l2cap) configure a KW36 device as the receiver of the OTA update, which can be transferred to the device by an OTA Server in the form of a mobile phone, or a KW36 programmed with the OTAP Server (otas) example, connected to a computer.
Please let me know if you need any more information.
Hi Daniel, I hope you're doing well!
There's three different OTA SDK examples available within the package, each implementing different functionality:
The two OTAP Client examples each implement different OTAP transfer methods, either using ATT or L2CAP CoC, and the OTAP Server example opens a connection from the board to a PC, and essentially works as a middleman between the Test Tool running in the computer and the OTAP Client device.
Depending on the transfer method that's going to be implemented, the receiving OTAP Client device should be programmed with the corresponding example.
As for the OTAP Server, the Test Tool has some configurations available to change settings such as transfer speed and method.
The current implementation allows the OTAP Server device to be connected to only one peripheral device at a given time, established by the way it was coded, and the following macro definition:
/*! Maximum number of connections supported for this application */ #define gAppMaxConnections_c 1
Thus, updating 4 devices at once would require considerable modification of the OTAP Server SDK example.
The Test Tool is available to download from our website here.
More detailed information about the OTAP example applications can be found in chapter 5.19 of the BLE Demo Applications User Guide, included in the SDK package in the following path:
<…\SDK_2.2.2_FRDM-KW36 - MCUXpresso\docs\wireless\Bluetooth\Bluetooth Low Energy Demo Applications User Guide.pdf>
Please let me know if you need any other information.