I want to reach out to you with for a very specific query around the NXP FRDM-KW41Z platform Bluetooth Host interface
- Linux supports BlueZ stack that can communicate with the Bluetooth modules and communicates over HCI interface
- We are currently exploring the possibility if the NXP FRDM-KW41Z module support standard HCI interface so that it can be directly attached to any Linux System over UART and provide the BLE interface to the system
What we tried so far
- While exploring the above-mentioned point, we came across the following topics at NXP forum
- Based on this we were able to flash the “hci_black_box” application on the FRDM-KW41Z module.
- We are able to perform a “$ hciattach /dev/ttyACM0 any” command successful. This command ensures that the FRDM-KW41Z module is attached to the system as an HCI device
- We are also able to perform a low energy scan using the following command and the list of available LE devices is getting populated
- $ sudo hcitool lescan
- We are not able to perform the standard Bluetooth Scan with the application using the following command
- $ sudo hcitool scan
- We are not able to locate the "device name" (Linux system) in BLE scanner applications even when the settings say that the device is visible.
- Can NXPs KW41Z chipset be used a Bluetooth NCP (network coprocessor) over HCI interface?
- Are there any other details available regarding the HCI interface supported by the FRDM-KW41Z module?