BT900 Setup It’s only necessary to set up a BT900 board if you’re running samples or automated tests that use a BT900 to test the Bluetooth Classic SPP or BLE CYSPP interoperability. Detailed instructions can be found in the documentation section of the BT900 homepage. The information presented on this page is not designed to replace the existing documentation, but to provide a quick walk-through the the steps that are necessary to setup the BT900. Laird BT900 Documentation Update BT900 Firmware It is a good idea to make sure the BT900 is running the latest firmware. Firmware is available at the BT900 product page. UwFlashX UwFlashX is an programming tool developed by Laird Connectivity. Download and Install from GitHub: UwFlashX BT900 Firmware Download the BT900 Firmware Programming BT900 Firmware Follow Instructions to program the BT900 firmware. Install Command Manager Application on BT900 Module Once the core firmware on the BT900 is updated, a user can program a sample application to run on the module. Command Manager is the Laird Connectivity equivalent of Infineon’s EZ-Serial application. Once programmed on the module, the BT900 can communicate with the Vela IF820. UwTerminalX UwTerminalX is an enhanced terminal program developed by Laird Connectivity. Download and Install from GitHub: UwTerminalX Command Manager Application Download the Command Manager App from GitHub: Command Manager App NOTE: You need to download the entire repository. Click the green “Code” button and select “Download ZIP”, or pull the code with git. Install Command Manager Application on BT900 Follow the instructions in this Application Note to install the application. See the section entitled “BT900 Development Kit Setup”. Verify Operation A quick way to check that the firmware is running is to issue a query firmware command “ati 3” as shown in the picture below. A quick way to check that command manager is working is to issue the command “cmd” as shown in the picture below. To exit command mode issue the “exit” command as shown in the picture below. Then query the firmware again to verify command manager is not running.
