Wireless MCUのトピックRe: The KW38 slave cannot be connected by third party software

The KW38 slave cannot be connected by third party software

liTian_one — Tue, 09 Jul 2024 08:31:09 GMT

When the KW38 is a slave, it cannot be connected to third-party software. Can only be used by iot toolbox connection.

sdk:D:\MKW38A512VFT4\SDK_2_6_15_MKW38A512xxx4\boards\frdmkw38\wireless_examples\bluetooth\w_uart\freertos

third-party software: nrf connect

Now I want to use kw38 slave through third-party software. How can I modify it? Look forward to your reply, thank you.

Re: The KW38 slave cannot be connected by third party software

Ricardo_Zamora — Tue, 09 Jul 2024 18:01:41 GMT

Hello,

Hope you are doing well. The Wireless UART example application implements both the GATT client and server for the custom Wireless UART profile and services.

As it is a custom profile, your application has to implement it.

For more information about Wireless UART, please refer to section 5.18 of the Bluetooth Low Energy Demo Applications User's Guide (Path: SDK\docs\wireless\Bluetooth).

Hope this helps.

Regards,

Ricardo

Re: The KW38 slave cannot be connected by third party software

Park123456 — Thu, 11 Jul 2024 03:09:07 GMT

Currently using the w-uart routine can be recognized by nrf connect, but the connection does not work, is it necessary to be specific which routine can achieve nrf connect connection? Or do I need to modify the routines to change which programs and configurations? Or do I have to use NXP's IoT toolbox to connect?
we want to realize the common debugging tools on the market such as nrf connect class BLE debugging tool connection.

Re: The KW38 slave cannot be connected by third party software

Ricardo_Zamora — Fri, 12 Jul 2024 16:01:49 GMT

Hello,

As mentioned, the Wireless UART is a Custom Profile. In your case, your application does not know the profile, and the disconnection occurs. (in code, the Wireless UART example disconnects if the Service Discovery was not found).

Regards,

Ricardo