BM70 static device configuration settings are stored in a separate non-volatile storage in the module. When the device powers up or resets, these settings are read into the device.
Configuration settings can change the behavior of the device, for example:
- Connection intervals
- GPIO functions, etc.
This page provides a brief introduction to the UI Configuration Tool: A Windows® PC-based utility used to edit a "configuration text file", then program the settings into the configuration memory of the device.
Dynamic module configuration is achieved via specially formatted command/response packets exchanged over the UART interface.
This lab requires a BM70 PICtail with version 1.06 of the firmware. Visit the BM70 Firmware Upgrade page to learn how to verify/update module firmware.
Be sure to install the MCP2200 USB drivers before starting. Also, download/extract the User Interface (UI) Tool to your PC using the link above.
The UART RX and TX lines are used to communicate between the Host MCU and the BM70.
Connect to BM70
Connect the BM70 PICtail™ to your PC. Ensure the jumpers are set as shown.
Place the module in Test Mode by setting SW7 in the ON position, then press SW5 (reset) to reset the module.
The module's basic operating mode (Test/Application) is sampled and established on a module reset condition. We recommend pressing the Reset (SW5) push-button whenever SW7 is first changed, or when you want to be sure that SW7 is sampled and applied by the module.
With jumper JP8 shorted, LED0 will be lit (BLUE) indicating the module is in Test Mode, as shown above.
Launch the User Interface Configuration Tool
After extracting files from the User Interface (UI) Configuration Tool .zip file, double click on the application file called IS187x_102_BLEDK3_UI v100.132.exe to launch the utility.
Immediately after launch, the Start Menu window will pop up. Before we can do anything with this tool, we must load a UI parameter table. One way to load the UI parameters is using an existing UI text file.
Click on Load in the Start Menu window.
Edit Text File
Once the text file has been loaded, the edit button will be enabled. Click on Edit.
When you press the edit button to start editing UI parameters, the Main Feature window will pop up. This window is where the user will select the target application. BLEDK3 supports all BLE operations, while the Beacon mode is used for non-connectable advertising only. If BeaconThings is selected, the module will support both BLEDK and Beacon operations.
For the purposes of this demo, we will only select BLEDK 0x00: BM70 and then click OK.
System Setup Window
Immediately after we click OK, we will see the Function Settings window pop up. It is in this window that most module parameters can be configured. As we can see, there are a few different tabs, each with different settings we can change. The first tab, System Setup, is where we find all the system configurations. We can change our device’s name, change the UART’s settings, select between Manual and Auto Pattern Modes, change security settings, etc.
In the second tab, System Setup2, we find the GPIO Configuration table as well as more system configuration settings. The I/O pins on the BM70 can be configured as either a control or an indication signal. The GPIO Configuration table shown on the System Setup2 tab provides configurable I/O pin assignment details for the control and indication signals of the BM70 BLEDK3 application.
Feel free to browse to the tabs and explore the different settings that can be configured to best fit your application. Below is a brief explanation of the rest of the tabs.
- LE Mode Setup: This tab contains the LE mode settings.
- GATT Service Table: In this tab, the user can build their own GATT service table.
- LED Setup: This tab is the P0_2/LED0 configuration page. This is a fixed function status output in BLEDK3, and it indicates what state the module is currently in via the LED flash pattern.
- Beacon Setup: This tab contains all the iBeacon configurations.
Usually the first setting customers choose to change is the Name Fragment under the Device Information section. This allows you to easily identify your device. In this case we chose to name the module DeveloperHelp.
The Name Fragment identifier becomes the module's GAP Service Device Name characteristic.
UART RX IND
Another important setting on this tool is the UART RX_IND. In order to reduce current consumption, BLEDK3 will automatically enter Low-Power mode if UART RX_IND is enabled and UART_RX_IND pin is assigned. When in normal power mode of operation, the module runs a 16 MHz clock; in Low-Power mode, the module runs a 32KHz clock. The Low-Power operation mode also disables the module UART section and thus the host MCU has no way to communicate with the module. If the host MCU needs to send/receive data/commands to the module, then the only way to do it is to pull the UART_RX_IND pin low. By default, the UART_RX_IND pin is enabled, but for the purposes of this lab we will disable it, therefore preventing the module from entering Low-Power mode.
If you are using the Manual Pattern Tool with the BM-70-PICTail board, we recommend disabling UART_RX_IND function, so that the utility is able to communicate with the module. In your final application, we recommend enabling this function to facilitate lower power consumption.
Using this UI Tool the user can also select whether the BM70 will operate on Auto Pattern Mode or Manual Pattern Mode. Refer to the Operating Modes page to learn more about Auto and Manual Pattern modes.
Go ahead and select the mode you wish to use.
After we have made all the desired changes, we need to write these new configuration settings into our module. Click on Finish.
After that window closes, select Save on the Start Menu to save the configuration settings to a text file on your computer. You will now have a starting point for further editing of your static parameters.
The settings have now been saved to the separate non-volatile storage. Next time the device powers up or resets, these settings will be read into the device.