BL654PA Series Long Range Bluetooth Module
Building on Laird Connectivity’s expertise with Nordic from the BL654 series comes the most powerful yet - the BL654PA series! It provides OEMs with the maximum design flexibility and performance. A complete multi-protocol embedded wireless offering with exceptional processing capability, all with extended PA/LNA support for even greater range.
Powered by Nordic’s nRF52840 silicon, the small form factor BL654PA modules and DVKs provide for a secure, robust Bluetooth Low Energy (LE) and Cortex-M4F CPU for any OEM’s product design. The BL654 provides you with maximum development flexibility with programming options for a simple, intuitive AT Command Set, as well as Laird Connectivity’s own smartBASIC environment.
- Bluetooth 5.1 Low Energy (LE) + NFC
- Integrated Skyworks Power Amplifier - Up to +18 dBm output
- Ultra-small footprint - 22 mm x 10 mm x 2.2 mm
- 2 Mbps and LE Long Range
More power so you can go farther.
The BL654PA features an onboard power amplifier that doubles the output power to as high as 18 dBm, over twice the power of the original BL654 Series. High output power and LE Long Range mean roughly double the range for your Bluetooth applications.
- Utilizes Skyworks part # SKY66112-11
- Provides + 10dBm more than standard BL654 (part # 451-0001 / 451-00002)
- Range of external antennas certified
- Complete power control with onboard smartBASIC FW image
Unboxing the BL654PA Development Kit
|Part Number||Additional Description||Antenna Options||Antenna Type||Bulk or Single||Chipset (Wireless)||Frequency Range (Max)||Frequency Range (Min)||Frequency Range 2 (Max)||Frequency Range 2 (Min)||Logical Interfaces||OS/Software||Product Type||System Architecture||Technology|
Recommended for New Design (RND)Buy Now
|Internal||Bulk - Tape and Reel||Nordic nRF52840||2480 MHz||2402 MHz||13.56 MHz||13.56 MHz||Serial, GPIO, ADC, I2C, SPI, PCM, I2S, NFC, PWM, USB||Nordic SDK, smartBASIC, AT Commands, Zephyr||Embedded Module||Hostless||Bluetooth 5.1, Single Mode (BLE), NFC, 802.15.4 / Thread / Zigbee|
Recommended for New Design (RND)Buy Now
|IPEX MHF4 Connector||External||Bulk - Tape and Reel||Nordic nRF52840||2480 MHz||2402 MHz||13.56 MHz||13.56 MHz||Serial, GPIO, ADC, I2C, SPI, PCM, I2S, NFC, PWM, USB||Nordic SDK, smartBASIC, AT Commands, Zephyr||Embedded Module||Hostless||Bluetooth 5.1, Single Mode (BLE), NFC, 802.15.4 / Thread / Zigbee|
Recommended for New Design (RND)Buy Now
|Internal||Bulk - Cut Tape||Nordic nRF52840||2480 MHz||2402 MHz||13.56 MHz||13.56 MHz||Serial, GPIO, ADC, I2C, SPI, PCM, I2S, NFC, PWM, USB||Nordic SDK, smartBASIC, AT Commands, Zephyr||Embedded Module||Hostless||Bluetooth 5.1, Single Mode (BLE), NFC, 802.15.4 / Thread / Zigbee|
Recommended for New Design (RND)Buy Now
|IPEX MHF4 Connector||External||Bulk - Cut Tape||Nordic nRF52840||2480 MHz||2402 MHz||13.56 MHz||13.56 MHz||Serial, GPIO, ADC, I2C, SPI, PCM, I2S, NFC, PWM, USB||Nordic SDK, smartBASIC, AT Commands, Zephyr||Embedded Module||Hostless||Bluetooth 5.1, Single Mode (BLE), NFC, 802.15.4 / Thread / Zigbee|
Recommended for New Design (RND)Buy Now
|Internal||Nordic nRF52840||2480 MHz||2402 MHz||13.56 MHz||13.56 MHz||Serial, GPIO, ADC, I2C, SPI, PCM, I2S, NFC, PWM, USB||Nordic SDK, smartBASIC, AT Commands, Zephyr||Development Kit||Hostless||Bluetooth 5.1, Single Mode (BLE), NFC, 802.15.4 / Thread / Zigbee|
Recommended for New Design (RND)Buy Now
|IPEX MHF4 Connector||External||Nordic nRF52840||2480 MHz||2402 MHz||13.56 MHz||13.56 MHz||Serial, GPIO, ADC, I2C, SPI, PCM, I2S, NFC, PWM, USB||Nordic SDK, smartBASIC, AT Commands, Zephyr||Development Kit||Hostless||Bluetooth 5.1, Single Mode (BLE), NFC, 802.15.4 / Thread / Zigbee|
|Buy Now||USB-SWD Programming Kit: Includes mainboard, TC2050-IDC Tag Connect cable, 10-pin flat IDC cable, 1.2 m USB cable, and 2-pin jumper|
EFA2400A3S-10MH4LmFlexPIFA Flexible Adhesive-Backed PIFA Internal Antenna
001-0022FlexPIFA / FlexPIFA 6E Flexible Adhesive-Backed PIFA Internal Antennas
When working with AT Interface why am I not able to get the module down to 2uA low power mode documented in the Lower Power Mode Application Note?
The Low Power Mode referenced in the following Application Notes are based on running the lp.low.power.deep.sleep.sb sample application which is written specifically for achieving the lowest possible power state of the BL65x module. All of the LEDs on the DVK-BL65x are set to digital out low, the temperature sensor is disabled, and the UART is closed before going into the waitevent. When running the sample application referenced in the document the BL65x module will enter into enter Deep Sleep or Low Power Doze Mode (at waitevent) and achieve the stated low power levels.
Low Power Modes - BL654 v1 1.pdf
Application Note - Low Power Modes - BL654PA
Application Note - BL653 Low Power Modes
Application Note - BL653µ Series - Low Power Modes
BL652 Low Power Modes.pdf
However, if you reference section 3.8 of the AT Interface User Guide you will better understand the nature of the AT Interface application, and why the current consumption is higher even when you are sitting at a waitevent, not entering commands. The Lpuart variant of the AT.Interface smartBASIC application ($autorun$.AT.interface.BL65x.lpuart.sb) can be used to operate the module in doze mode (with the UART closed most of the time) so that the total current consumption can be as low as sub 10 microamps.
Can I pair in vSP Mode with AT Interface Application
Is it possible to bond devices in vSP mode when using the AT Interface application.
In order to enable the devices to pair and bond in vSP mode, when working with the AT Interface sample application, you must make the initial connection in non-vSP mode, using the command, AT+LCON
Once the devices have connected you can pair using the command, AT+PAIR hdlx
command to pair. The pairing will automatically be stored in the
bonding database., Then disconnect the devices and you can now reconnect
in vSP mode using the command ATD
See example with comments following // below:
ati 0 //Calls Device name
ati 3 //Calls the firmware version on the module
ati 4 //Calls the BT ADDR of the module
ati 2009 //Calls number of devices in Bonding Database
at+lcon 01D1C4A981E5E7 //Connects in non-vsp mode with specified BT ADDR
at+pair 1 //Pairs with connection handle created when devices connected
PI:1, 0, 0, 5, 3
at+ldsc 1 //Disconnects the devices
ati 2009 //Confirms one device is stored in the bonding database
at+bndt 01D1C4A981E5E7 //Confirms the BT_ADDR specified is bonded and stored in database
atd 01D1C4A981E5E7 //Connects in vSP Mode (encrypted)
CONNECT 0, 01D1C4A981E5E7,15000,6000000,0
Do I have to use hardware RTS/CTS handshake with the Laird BLE modules?
We advice to use RTS/CTS hardware handshake on all of our SmartBASIC modules. This will avoid UART buffer overflow and loss of data.
However, if e.g. no hardware handshake signals are available on your host system, you might want to try
- Using XON/XOFF software handshake instead.
- Use not handshake at all but lowering the baud rate significantly. This can prevent buffer overflow to a certain extend but actually depends on your particular application and whether other tasks active on the module would consume processing power.
Make sure to always use the latest SmartBASIC firmware version and check the SmartBASIC and module documentation.
If not using SmartBASIC but implementing an own application with nRF Connect SDK or Zephyr, you are free to not use hardware handshake and implement a proper protocol to avoid buffer overflow on application side.
What are the hardware design recommendations for the BL653/BL654 USB interface if not used?
The BL653/BL654 provides an USB 2.0 full-speed (12 Mbps) interface which is compliant to the Universal Serial Bus Specification Revision 2.0. We recommend connecting VBUS to GND and leaving both D+ and D- data pins unconnected if developers do not need or want to implement the USB interface in their hardware designs. Please note that smartBASIC does not support USB functionality, so for software and application development you would need to either use Zephyr or the Nordic SDK.
Why does my BLE module have an extra 01 in front of its MAC address?
For example in SmartBasic Interactive mode
10 4 01 EFA44957769F
BLE devices can have multiple mac addresses and if the mac address begins 01 as above it signifies it is a random static address which is assigned during manufacture. While its random nature means its not unique the number of possible random static addresses is 2^(48-2)-2 a very large number so it is very unlikely you will ever see a duplicate, let alone in the same place at the same time.
Other MAC address types include
- 00 IEEE assigned public address, the same as used by BT classic devices
- 01 Random static, generated at manufacture
- 02 Random private resolvable with IRK. resolvable by other devices already known
- 03 Random private non resolvable
To address privacy concerns, there are four types of Bluetooth addresses in a BLE device which can change as often as required. For example, an iPhone regularly changes its BLE Bluetooth address and it always exposes only its resolvable random address. This feature is known as LE privacy. It allows the Bluetooth address within advertising packets to be replaced with a random value that can change at different time intervals. Malicious devices are not able to track your device as it actually looks like a series of different devices. To manage this, the usual six-octet Bluetooth address is qualified on-air by a single bit which qualifies the Bluetooth address as public or random: ▪ Public – The format is as defined by the IEEE organisation. ▪ Random – The format can be up to three types and this qualification is done using the upper two bits of the most significant byte of the random Bluetooth address.
On Laird Connectivity SmartBasic module, the address type can be set using the function BleSetAddressTypeEx(). On the other hand, Sysinfo$(4) can be used to retrieve the Bluetooth address if it is public or random static. Due to LE privacy 1.2, if the address type is random resolvable or random non-resolvable, it cannot be retrieved by the application layer since it is fully controlled by the baseband layer.
Note: The Bluetooth address portion in smartBASIC is always in big endian format. If you sniff on-air packets, the same six packets appear in little endian format, hence reverse order – and you do not see seven bytes, but a bit in the packet somewhere which specifies it to be public or random.
Does laird Connectivity support Nordic Enhanced Shock Burst (ESB)?
Yes, but software support should be sought direct from the Nordic Devzone as from Lairds point of view we provide only the hardware not the protocol.
Enhanced Shockburst (ESB) is a proprietary simple packet protocol for use in the Nordic modules. It is simple and easy to use and can give very low latency applications compared to BLE.
However, there is no encryption employed in ESB and ESB operates on a single frequency channel so there is no frequency immunity. You can implement your own encryption in upper layers though.
Also see Gazell (GZLL), which is another proprietary protocol from Nordic that builds on ESB.
Can I stop the BL65x firmware upgrade batch file from closing?
Smartbasic firmware is normally flashed to a BL65x module using a Windows batch file but the batch file command window will automatically close on completion. To keep this window open, to view what has happened add the following to the end of the batch file in question.
if "%1" == "nopause" goto :end
Should I use nRFConnect SDK or nRF5 SDK with the Laird BL65x modules?
Nordic nRFConnect SDK, also known as NCS is based on the Zephyr RTOS with support for Laird modules based on nRF52 and nRF53
Nordic nRF5 SDK is a legacy bare metal SDK with support for Laird modules based on nRF51 and nRF52
You can choose either SDK but need to know that nRF5 SDK will not be supporting new features going forward. So if starting a new BL65x or BL5340 project then it is recomended to choose nRFConnect SDK.
See nRF Connect SDK and nRF5 SDK statement - Blogs - Nordic Blog - Nordic DevZone (nordicsemi.com) for more details
Do you support Bluetooth features like BLE Mesh, AoA (Angle of Arrival) and/or Angle of Departure (AoD) in your own AT Command Set Interface implementation?
No. There is no software support for BLE Mesh, AoA (Angle of Arrival) and Angle of Departure (AoD) in our current AT Command Set Interface implementation. Please feel free to build and develop your own BLE Mesh, AoA or AoD application in C by using the Bluetooth SDK and tools from Silicon Labs. In this case, as a starting point, we highly recommend the Simplicity Studio 5 IDE which offers a rich set / collection of example projects and templates.
Bluetooth Mesh is a wireless mesh topology and standard which enables many-to-many (m:m) device communication for an enormous number of local BLE devices. It supports large-scale node networks without the need of an ordinary BLE gateway infrastructure. Refer to https://www.lairdconnect.com/making-bluetooth-mesh-simple and https://www.bluetooth.com/learn-about-bluetooth/recent-enhancements/mesh for additional information.
Angle of Arrival (AoA) and Angle of Departure (AoD) are two concepts for location positioning and direction finding. Without going into too much detail and to keep things very simple: One of the two BLE devices must have at least two antennas or more, so that the data received from those antennas then can be used to identify the direction and angular position of the location where the Bluetooth signals come from. Please find further information available at https://www.lairdconnect.com/resources/blog/magic-bluetooth-aoaaod-direction-finding and https://www.bluetooth.com/blog/new-aoa-aod-bluetooth-capabilities.
Why is SWDIO/SWCLK shorted to GND on my board?
According to the Nordic DevZone there are mainly two potential issues leading to a short on one of the SWD signals:
- ESD issue, likely when connecting an SWD programmer to the SWD signals.
- Connecting an SWD programmer while the target board is not connected to supply voltage.
Please make sure proper ESD precautions are taken into account (ESD wrist-strap, ESD base/mat) as well as make sure to first connect the supply voltage and then the SWD programmer.
Is it possible to clear or reset a table in smartBASIC?
Tables provide associative array (or in other words lookup type) functionality within smartBASIC programs. They are typically used to allow lookup features to be implemented efficiently so that, for example, parsers can be implemented.
There does not exist a function to delete particular entries from a table, but it's possible to overwrite existing elements with TableAdd(). TableLookup() will then return the new element. However, the elements are not actually being overwritten, but marked deleted and added newly to the table, hence the table memory consumption will increase.
To fully clear a table it's possible to simply call TableInit() again.
Can I read a file in SmartBASIC Interactive Mode with an AT Command?
While it's possible to open/write/close files from SmartBASIC Interactive Mode (AT+FOW, FWR, FCL) to e.g., enter configuration information for a SmartBASIC application, there is no AT command available to display the content of a file from the flash file system.
A workaround would be adding another SmartBASIC application to a device which can be started in Interactive Mode (AT+RUN or just the name) and opens the (config) file and prints the content to the console. Below is an example application.
Does the BL65x or BL5430 support Matter?
Matter can be supported on the BL5340 (nRF52840) and the BL654 when using the Nordic nRF Connect SDK. However, due to the memory requirements of Matter it can not be used on the BL653, BL652 nor the BL651 given their flash and RAM memory footprint.The BL653 (nRF52833) has 512K of Flash and 128K of RAM and BL652 and BL651 has less than that.
There are instructions on how to reduce the memory footprint for Matter in the documentation on the nRF Connect SDK Main branch, Memory footprint optimization » Matter, but even using this you will not be able to get it down to a size fitting on the nRF52833. With the steps from the optimization page with the light bulb sample the size was reduced to approximately 730 kB of flash and 170 kB of RAM when building for nRF52840, which is still way too high for the nRF52833. Additionally, there are possibilities that the Matter flash usage will grow more before the official release, as more bug fixes and things from the Matter specification will be added.
Why can’t I Re-open the UART when it closes when running AT Interface LPUART App?
The LPUART AT Interface app allows users to close down the UART port when entering low power Doze mode for additional power savings. The UART when it is open can consume as much as 350uA. The AT Interface LPUART app provides a cross-compile switch that allows the UART to close most of the time when there is no activity and the Tx/Rx buffers are empty. A “Keep UART Open” is implemented by using a GPIO that when low allows the UART to close after a low power operation timer has expired. When this Keep UART Open GPIO signal is high the UART will not close automatically.
The AT Interface Application sets the default GPIO used for this function to SIO_24. An application can chose any pin other than the default by writing the desired SIO port number to Sreg 109.
The BL65x EVK connects SIO_24 to Button 3. However, if running the AT Interface LPUART application on the EVK the UART will close automatically as soon as the low power timer expires (default set to 5 seconds). The UART can not be re-opened in the case. To reduce power the application configures the Keep UART Open GPIO to input pulldown. However, to operate properly Button 3 when pressed will pull the signal to ground which results in an Event interrupt. Since the GPIO uses an input pulldown it is already low and no Event occurs leaving the UART closed.
A simple change in $LIB$.AT.interface can be made to configure Keep UART Open GPIO to input pullup. This keeps the GPIO high at all times and the UART open. When Button 3 is pressed long enough for the low power time to expire the UART is closed. To re-open the UART Button 3 is pressed again which causes an Event which will re-open the UART.
Change the following line in InitGpio() function in $LIB$.AT.interface:
rc = GpioSetFunc(vspCmdModePin, SIOTYPE_DIN, INPUT_PULL_DOWN)
rc = GpioSetFunc(vspCmdModePin, SIOTYPE_DIN, INPUT_PULL_UP)
Also to change the functionality so once the UART is closed is remains closed until the next button press also change the next line in InitGpio().
rc = GpioAssignEvent(0, vspCmdModePin, 0)
rc = GpioAssignEvent(0, vspCmdModePin, 1)
How to avoid/disable module reset on UART break with SmartBASIC?
The default behaviour of the SmartBASIC driven BLE modules is entering deep sleep mode when a UART break condition is being detected and wake up through reset when released. While this is a convenient way to reset a module without having access to the reset line e.g., during development when connected with UwTerminalX, it might be unintended in the final application environment.
For the more recent SmartBASIC BLE modules like BL652, BL653, BL654, BL654PA the behaviour when detecting a UART break is configurable when opening the UART with UartOpen(). Character 9 in the stOptions string specifies the behaviour and it's possible to chose from entering deep sleep / reset, ignore the break or send an event EVUARTBREAK to the SmartBASIC application. See below table:
The default behaviour is entering deep sleep, hence you would have to close the uart and re-open it at the beginning of your application to apply changes to the behaviour.
See the SmartBASIC Extensions User Guides for each module for more details.
The BT900 dual-mode BT/BLE module does not offer configurability of the UART break behaviour and will always go to deep sleep and wake up through a reset.
How can I read out the MAC address from a BLE module during test/production?
A fast and convenient way to read out the MAC address of each module during a test/production process would be through SWD from FICR (Factory information configuration registers) registers DEVICEADDR and DEVICEADDR. The following command will read the MAC address from our BLE modules:
nrfjprog --memrd 0x100000A4 --w 8 --n 6
Please note that reading from memory through SWD will halt the CPU. If you need your application firmware to start afterwards (like for performing some test sequence) you would have to run the CPU with
More information on FICR registers are available in the respective data sheets, like this for nRF52840 / BL654.
What is the battery recommendation if need to use battery to power up BL654PA?
The power input in data sheet is 3.0v~5.5v, and at least need to have 2.8v to make the internal LDO work.
Li-ion, Li-poly nominal battery voltage is 3.6V fully charged, and are recommended to power BL654PA. 3*AAA battery is also recommended as well.
TX power of 1M and 2M in BL654PA is able to achieve 18dBm, and why TX power of LE CODED limit to 14dBm?
This is due to the PSD (power spectrum density) limitation in FCC and IC.
Do I still have to list/qualify my product with the BT SIG even if I don't use the BT logo?
Yes, you need to qualify/list any product that uses BT SIG intellectual property, even if you do not use the logo or require interoperability with other BT devices. see here for more details. Qualify Your Product | Bluetooth® Technology Website
How can a enable/disable particular BLE channels used for advertising/scanning or when in a connection?
The smartBASIC language provides functions for setting a specific set of channels to be used for BLE advertising/scanning or a BLE connection.
- BleChannelMap(chanMap$) enables or disables data channel usage when in a connection.
- BleAdvSetCreate(nSetId, nAdvProperties, nPriSecPhy, nFilterPolicy, peerAddr$, chanMask$) can set BLE advert channels.
- BleScanStartEx(scanTimeoutMs, nPriPhyScan, chanMask$, nFilterHandle) can set channels used for BLE scanning.
The channel map/mask has to be entered as a 5 byte long string for each of the functions and due to the little-endian architecture of the underlying ARM core its composition can be confusing. The below example will show the actual assignment of channel within that string. Furthermore the meaning of a set bit differs among the above functions.
- BleChannelMap() -> a set bit means channel is enabled!
- BleAdvSetCreate() and BleScanStartEx() -> a set bit means channel is disabled!
Now let's “visualize” the channel mapping into the five byte string:
00000000|11111100|22221111|33222222|xxx33333 76543210|54321098|32109876|10987654|xxx65432 \byte 0/ \byte 1/ \byte 2/ \byte 3/ \byte 4/
So for enabling e.g., channels 9+10 only you would set the yellow bits:
00000000|11111100|22221111|33222222|xxx33333 76543210|54321098|32109876|10987654|xxx65432 \byte 0/ \byte 1/ \byte 2/ \byte 3/ \byte 4/ 0x00 0x06 0x00 0x00 0x00
giving “0006000000” as string.
For disabling channel only 35, i.e. active channels are 0-34 and 36, it would be:
00000000|11111100|22221111|33222222|xxx33333 76543210|54321098|32109876|10987654|xxx65432 \byte 0/ \byte 1/ \byte 2/ \byte 3/ \byte 4/ 0xFF 0xFF 0xFF 0xFF 0x17
giving “FFFFFFFF17” as string.
Further detail is given in the smartBASIC Extension Guides in the documentation section of the product page for each BLE module at Bluetooth Module Portfolio.
Does Laird have example code for a Windows Demo App which enables scanning and connecting to Bluetooth Low Energy peripheral IoT devices?
Unfortunately, we do not have an example of a Windows Bluetooth Low Energy application. If you require assistance with developing a Windows Bluetooth Low Energy application please contact one of our Sales Experts and let them know you are interested in a Design Services engagement and we will be happy to discuss your application requirements and provide a quote.
What factors influence the actual TX rate of the controller?
The actual TX rate is influenced by the PDU and MTU sizes along with the Connection Intervals and Slave Latency.
Where can I find the appropriate arguments/parameters to use with the BleAttrMetadata() function used in many examples in the BL65x User Guide, as I only see BleAttrMetadataEx() listed which appears to have different arguments/parameters?
The BLEATTRMETADATA () function is intentionally not documented in the BL65x Extension User Guides for our BL65x series smartBASIC modules, as it is preferred that the ‘EX’ variant BLEATTRMETADATAEX () is used going forward. The two functions are primarily the same, however, the EX version enables more functionality with the nFlags argument as compared to the FlsVariableLen argument in the deprecated BLEATTRMETADATA () function. The non-EX version is still supported to ensure old apps using it still work, including the code examples referred to in the user guide.
If you are looking for specifics about the BLEATTRMETADATA () function, such as the arguments and returns specific to that function these can still be found in the BT900 smartBASIC Extensions User Guide (pg 228), or BL600 smartBASIC Extensions User Guide (pg 110).
Can Pullups or Pulldowns be Disabled on Default UART Pins
The BL65x is delivered with the smartBASIC runtime FW loaded and no smartBASIC application. In this configuration the module will boot into smartBASIC Interactive mode and the default pins for the UART at startup are set as per:
- RTS: digital out, no pull, default high
- TXD: digital out, no pull, default high
- CTS: digital in, pull down
- RXD: digital in, pull up
Startup flow is as follows:
- sB engine starts
- If there is no autorun application - UART is opened (default parameters)
- If there is an autorun application - UART is not opened
- If the autorun application uses print - UART is opened (default parameters)
- If the autorun application uses UARTOPEN - UART is opened (custom parameters)
The pull up/down options can be changed in the smartBASIC application only when the UART is not open. If the $autorun application has opened the UART by using a print statement or calling UARTOPEN() then the UART must first be closed by calling the UARTCLOSE() function.
In the smartBASIC application when the UART port has been closed the code can call GpioSetFunc() to configure the desired GPIO parameters.
The smartBASIC application can use UARTOPEN() function to now enable the UART port. UARTOPEN() does not configure GPIO pull up/down configurations keeping the desired GPIO configurations intact.
How Can I Change the BL65x Tx Power Setting
The BL65x is delivered with the smartBASIC runtime FW loaded and no smartBASIC application. The BL65x will boot up in interactive mode and can be configured via AT Commands. In this mode the TX Power for both advertisements and connections is controlled via Config Register 109. This register is read from or written to via the AT+CFG AT command as is described in the BL654 smartBASIC Extensions Users Guide. However, Config register 109 is valid for Tx Power adjustment when Virtual Serial Port services is enabled.
If Virtual Serial Port Services is not enabled TX Power is configured via the BleTxPowerSet() function within a users smartBASIC application code. In this mode the current setting of Tx Power can be obtained from ATI register 2008 as described in the BL654 smartBASIC Extensions Users Guide
How many SPI Interfaces does the BL65x support
The BL654 Data sheet lists four SPI Interfaces (up to 8 Mbps) are supported. The data sheet is provided as a hardware guide and refers to the hardware itself. The Nordic nRF52840 MCU supports up to 4 SPI instances. However, the actual number of SPI interfaces depends on what SW is used for application development. If using smartBASIC for development there is one SPI instance that can be configured as SPI master.
The SPI port is opened via smartBASIC function SPIOPEN(). This function includes parameters that allow configuration of SPI Mode, SPI Clock Rate and SPI Flags. SPI pins cannot be configured and use the pins that are specified in the BL65x Data Sheet. Refer to smartBASIC Core Functionality Specification. SPI_CS is not controlled in smartBASIC firmware and must be controlled by the application through use of SIO pins.
For applications developed using Nordic SDK or Nordic Zephyr SDK the nRF528xx MCU supports up to 4 SPI Instances. There can be up to 4 SPI Master interfaces (SPIM Master) and up to 3 SPI Slave interfaces (SPIS) but not all at once. There are four total SPI interfaces and master/slave combinations are shared across those four instances. The nRF528xx also contains two I2C Instances which are shared with the two lower SPI instances via TWI. Refer to the latest nRF52xx data sheet for details.
How many I2C ports does the BL65x support
The BL65x Data sheet lists two I2C controllers (up to 400 Kbps) are supported. The data sheet is provided as a hardware guide and refers to the hardware itself. The Nordic nRF528xx BLE mcu’s support multiple I2C controllers. However, the actual number of I2C interfaces depends on what SW is used for application development. If using smartBASIC for development there is one I2C instance and that instance is a master, there is no slave support.
Referring to the smartBASIC Extensions guide for the various BL65x modules it states:
Note I2COpenEx() allows for SCL and SDA to be routed to other GPIO pins.
This function uses the same I2C instance but allows changing the pins it is operating on. The smartBASIC I2C driver does not support a second instance. The intent of this function is so multiple devices with the same I2C address can be used. Some devices support a single address, some have multiple addresses they can use. If a sensor with 2 possible addresses is used then a third cannot be added on the same bus because the address of 2 devices will clash, but it can be used on different pins. Another example is if one sensor only supports 100KHz mode but another that supports 250KHz. Different busses would need to be used so that the 250KHz signals do not cause undefined operation for the 100KHz sensor
For applications developed using Nordic SDK or Nordic Zephyr SDK then I2C interfaces supported by the particular nRF528xx BLE MCU can be used. Both master and/or slave operation is also supported. Refer to the nRF828xx data sheet for details.
Why is the data I am sending in an advertisement PDU seem to be received as converted ASCII data?
When sending extended or normal advertisements by setting AD Elements for scan or advertise response PDU’s using AT+AARA tag,<payload> or At+ASRA tag, <payload> the parser is expecting the payload to be a string enclosed by quotes.
However, how do you differentiate between a normal text string and a string of ASCII hex?
Is FF 0x46 0x46
Or is it
For example if the data added in the response packet is:
T+AARA tag, “BEEF”
The parser interprets this as a four byte string of 0x42, 0x45, 0x45, 0x46
If the command is changed to:
At+AARA tag, “\BE\EF” the parser would interpret this as a two byte string of 0xBE, 0xEF. The slash interprets the following two characters as ONE hex byte.
How many bytes can BL65x modules support for Extended Advertising using smartBASIC?
BL65x modules can support up to 255 Bytes when using extended advertising. This equates to an advertisement packet being sent on one secondary channel.
Extended Advertisement were introduced in Bluetooth SIG v5.0 specification. Advertisement channels 37, 38 and 39 are now qualified as Primary Advertisement Channels with channels 0 to 36 now qualified for use as Secondary Advertisement Channels. Each secondary channel can have up to 255 bytes of payload and the v5.0 specification allows for chaining up to 6 packets for up to 1650 bytes total. However, receiving all of those chained packets may be unreliable resulting in many stack vendors not offering the full chaining capacity.
How can I update and send Extended or Normal Advertisement data using AT Interface application?
In AT Interface there are just a few commands for modifying and sending Extended or Normal Advertisement data. Extended Advertisement Data is provided from the Server to the Scanner via Scan Request and Response PDU’s. An AD Element needs to be created to add the AD report that is returned after a scan request is received. To add AD Elements to the Advert Report use AT Command:
Tag refers to the Data Type Value specified in the Bluetooth SIG Generic Access Profile document. Using a tag of Data Type Value of 0xFF <Manufacturing Specific Data> the command will look like:
AT+AARA 0xFF “payload”
AT+AARA 255 “payload”
Once the AD Report is updated it must be committed using:
To begin Extended Advertisements use AT Command:
AT+EADV <advProp>,<advIntvlMs>,<maxCount>,<priSecPhy>,<peerAddr>, <chanMask>
Refer to AT Interface Guide for more details of parameters.
For now the key parameter is <advProp>. <advProp> is a bitmask where bit 0 is set for connectable adverts, bit 1 is set for scannable adverts, bit 2 for directed adverts and in that case ‘peerAddr’ must be a valid 14 hex digit string and bit 3 is set for extended adverts. For this example AT Command:
This command will begin sending non-connectable Extended Advertisements using default values for remaining fields which are taken from their corresponding S Registers.
To clear AD Elements when new advertisement data needs to be sent use AT Commands:
This will clear existing AD Elements. If the need to maintain current AD Elements for the Advert report but additional AD Elements need to be added to the Advert Report then simply continue adding AD Elements using
What influence does the client have when it comes to notifications?
The Client must initiate the ability of the Server to send Notifications by writing to the CCCD descriptor for the Notified Characteristic on the Server.
Why are multiple EMPTY_PDU are being sent from the Master per connection interval?
The communications protocol for Bluetooth is a ping pong type style, so every connection event begins with the Master sending the slave a packet and the Slave then responds to that packet with any data it may have. Therefore, when the Master has no data to transmit it will send an EMPTY_PDU to the Server and the Server, if it has data to send, will send back the data in response. You can see this readily where there is no data transmissions, the Master and Slave ping pong EMPTY_PDU’s back and forth on every connection event, if Slave Latency was incorporated then during these periods of no data transmissions you would see Master send EMPTY_PDU and no response from Slave because it has no data to send and was allowed to skip the connection event because of it.
Error received when flashing custom Nordic application to DVK-BL65x: SVCALL(SD_SOFTDEVICE_ENABLE, uint32_t, sd_softdevice_enable(nrf_clock_lf_cfg_t const * p_clock_lf_cfg, nrf_fault_handler_t fault_handler)); Programming custom Nordic App to DVK-BL65x
This error indicates and issue with the clock source referenced in your code. We recommend referencing the appropriate Application Note for Using the DVK-BL65x and Nordic SDK linked below:
- Application Note - Using the DVK-BL652 and Nordic SDK
- Application Note - Using the DVK-BL653 and Nordic SDK
- Application Note - Using the DVK-BL654 and Nordic SDK
As noted in the Application Note, by default the DVK-BL65x uses the on-chip RC oscillator as its clock source, as opposed to Nordic's development kit or dongle which use an external crystal. The difference in oscillator source should therefore be reflected in the SDK as shown Application Note. Alternatively, you can connect an external crystal as per BL65x DVK User Guide
Can the BL5340 or BL65x use a different stack to support a hosted application?
Theoretically as long as whoever 3rd party BLE stack is used is tested and supported on Nordic nRF5340 or nRF528xx used on BL65x modules.
Laird would not have tested anything other than Zepher/nRF SDK.
A 3rd party CODEC could be used as well as long as it is targeted for nRF5340. However, licensing would need to be considered.
What is the maximum number of characteristics that can be supported using smartBASIC?
The maximum number of characteristics is not a limitation in smartBASIC but a limitation in the underlying Nordic SoftDevice SDK. The SoftDevice has a maximum RAM allowance of 64KB, adding more characteristics will increase RAM usage and depending on other configuration, will determine how many characteristics can be supported within the 64KB allowed RAM space.
The maximum number of characteristics supported in smartBASIC is roughly 24. This is a product of the combination of the total RAM allowance of 64K for SoftDevice, GATT Table configuration as well as the GATT Table size as is specified in Configuration Key 204 (refer to BL654 smartBASIC Extension Guide). The default GATT table size is 1792 bytes (Config 204)) which will allow for roughly 11 characteristics.
If using the AT Interface application the maximum number of characteristics is set to 24 by default. The default configuration can be found in $autorun$.AT.interface.BL654._.sb file:
//This defines the maximum number of characteristics we can manage
#define MAX_CHARACTERISTICS 24
As mentioned previously this is the max number of characteristics that can be supported but Out of Box the GATT table size is 1792 bytes resulting in roughly 11 characteristics.
How to open multiple BLE connection simultaneously with the SmartBASIC AT interface?
While it is not possible to open multiple virtual serial port (VSP) connection at a time, it is possible to open more than one regular BLE connection.
The SmartBASIC AT interface application provides configuration S registers for setting certain BLE parameters, which are accessible by the ATS command. The default configuration is optimized for establishing one VSP connection with high throughput between two BLE modules. Given this, certain S register have to be modified to accomodate for different applications.
The default configuration has set bit 3 in S register 100 (Start-up Flags), which gives max bidirectional throughput of about 127kbps. As a consequence the number of simultaneous BLE connections is being limited to 1. If you want to use more than one non-VSP BLE connections, bit 3 in S register 100 needs to be cleared and then max connections in S register 126 can be increased.
- ATS 100=1 (if you want to keep the VSP service being active)
- ATS 100=0 (if you want to disable the VSP service)
If you need to set other bits in S register 100, like data length extension or phy rate, add them as required. You can use ATS 100? to retrieve the current settings before changing.
Now the number of simultaneous BLE connections can be set in S register 126.
- ATS 126=8 (set max connections to eight or some other value, the actual maximum number might depend on your particular BLE module)
Then make sure to save and apply the new settings.
- AT&W (this will store S register settings permanently)
- ATZ (does a soft reset and apply changed settings of S registers)
After the soft reset the new settings are active and you can open several BLE connections simultaneously with AT+LCON command.
See BL65x AT Interface User Guide for more information on S register settings and AT commands.
Is achieving the theoretical throughput of 2 Mbps possible with BLE radio with 2M PHY?
Unfortunately, no. At the time of this writing, even with 2M PHY enabled, BLE 5.x radios have a limitation of 1.2 - 1.5 Mbps due to the packet format. In order to achieve throughput of 2Mbps or higher you would have to use a different RF Technology, such as Wi-Fi.
Please see the Application Note for Throughput Testing with Bluetooth 5 LE 2M PHY Feature for the BL65x module.
- Throughput Testing with BT 5 - LE 2M PHY Feature v1 0.pdf
- Throughput Testing with Bluetooth 5 - LE 2M PHY Feature - BL652.pdf
(Note: The above Application Notes have not yet been added to the BL653 or BL654PA Product Pages, however, they do apply to those modules as well. The only difference is the DVK setup.)
Is it possible to have multiple connections as a peripheral device on the BL65x modules?
Multiple connections as a peripheral device is currently not supported in smartBASIC on the BL65x modules. This functionality is supported in Nordic SDK beginning with SoftDevice S132 v.4.0.0.
However, as of the writing of this FAQ, this functionality has been brought out as an experimental feature in the smartBASIC firmware for the BL654/BL654PA only, as per the Release Notes for the v18.104.22.168.0 fw It is not documented in the smartBASIC Extensions User Guide at this time due to it being an experimental feature, and no additional support is currently available for this functionality.
If interested in testing with this experimental feature, the below test can be performed using two/three mobile devices (tablets/phones) as the central devices to demonstrate that two (or more) central role devices can connect to the BL654 configured as a peripheral at the same time. (This does not test GATT functionality or anything else.) While in interactive command mode:
at+cfg 205? // Query the current MAX number of peripheral role connections (User Guide still indicates the MAX this can be set to is 1) at+cfg 206? // Query the current MAX number of central role connections 27 0x00000001 (1) //Response to MAX Peripheral role connections 00 27 0x0000000F (15) //Response to MAX Central role connections 00 Increase the MAX Peripheral role connections and decrease the MAX Peripheral role connections and then reset the module for the settings to take effect: at+cfg 205 3 //Configure Max Peripheral to 3 at+cfg 206 3 //Configure Max Central to 3 atz //Reset
In our testing we used the cmd.manager.sb sample application available from the BL654 Sample Application Repository on GitHub. After setting the MAX connection parameters and resetting the device load and run the cmd.manager.sb sample application.
The commands and parameters for cmd.manager are found in the comments section of the code: To simplify this for testing purposes enter the following command to start adverts:
advert undirected 250 30000 0
Explanation of the command from the code:
advert undirected #INTintervalms# #INTtimeoutms# #INTfilterpolicy#
// - Use this to start adverts of type ADV_IND using the parameters specified
// - #INTfilterpolicy# is 0=no filtering, otherwise set 1 to 4 which is the
// - whitelist handle created using the 'whitelist' command
This will start adverts for 30 seconds, adjust the INTtimeoutms setting if you want to advertise for longer. Then while it is advertising, connect to it using your phones/tablets (central role devices). If the advert times out before you connect the additional devices you can restart it with the advert
undirected 250 30000 0 command.
Is there a way to extend the shelf life of Laird modules?? If the shelf life cannot be extended in any way, what are the consequences of using modules after shelf life?
The shelf life statements are essentially to prevent mishandling of the product and not storing it properly. If the modules are still sealed in the package, stored at the proper temperature and have not been exposed to moisture they should be fine. However, when working with modules beyond their shelf life you MUST bake the modules before populating the them to your board. Failure to bake the modules could result in the yield rate dropping down lower than expectation due to popcorn or de-lamination on the modules. It is recommended that you follow IPC/JEDEC J-STD-033 which is the general standard for the handling, packing, shipping and use of moisture/reflow sensitive surface mount devices.
Our main concern is around the castellation/pads which solder the module to the board. It is imperative those pads do not get tarnished, as this would cause soldering issues. Humidity can affect solderability as well, as if there is any excess moisture in the solder on the module, during reflow of the module to the board, steam balls can essentially explode the solder and sometimes result in an open circuit (or possibly a short circuit).
As long as all of the moisture handling and temperature guidelines are being followed you will likely have no issues. It is further recommended that when you do the build with modules that have exceeded their shelf life that you start with a handful to perform a test run and do a final test to make sure all is working as expected. As long as there are no issues with the initial test run we would expect that you will not experience any problems.
What does the Bluetooth message "advertised data length corrected" indicate?
This is effectively a Bluetooth SPAM message. It indicates the advert data being parsed is less than a full advert record can be, in other words trailing zeroes were removed.
How do I select the 32.768kHz Low Power Clock Source in the new nRF Connect SDK
Customers using the new nRF Connect SDK from Nordic will need to change the low power 32kHz clock source when working with the BL65x family of products.
To do this in the new SDK using the Segger IDE follow the instructions here;
- In Segger Embedded Studio select Project --> Configure nRF Connect SDK Project
- Filter the list for 'osc' or drill down in the list to the Device Drivers --> Hardware clock controller support --> NRF Clock controller support --> 32KHz clock source
- Select the clock source based on your configuration/design:
- Without the optional external 32khz xtal, default configuration for our modules, select 'RC Oscillator'
- With the external 32Khz xtal connected to the module, select 'Crystal Oscillator'
With the correct value selected your code should build with the right clock source configuration and your application should run smoothly.
Can I use Windows to scan for my BLE Peripheral and Connect to it?
Laird does not provide a Windows utility for scanning and connecting to BLE devices. We are also not aware of any existing third party apps to do this either. Android and iOS are the best options for scanning for and connecting to BLE radios.
Getting ERROR: JLinkARM DLL not found. Please reinstall latest JLinkARM when trying to flash BL65x module via the JTAG interface. How can this be resolved?
If you are getting
ERROR: JLinkARM DLL not found. Please reinstall latest JLinkARM, you will need to download and install the updated Segger drivers for the J-Link.
Segger J-Link Drivers
What could be causing additional power draw when in standby doze state?
There are several functions within an application that can increase current consumption above the measurement indicated in the Datasheet for standby doze, low power mode.
- GPIOs held in an asserted state
- Nested functions - which keep the module from entering the standby doze state
- UART (when open)
What are the production programming options for the BL65x modules when using smartBASIC?
For production programming we recommend the following options:
- FLASH cloning: Instructions for FLASH cloning can be found in the firmware Zip files, which can be downloaded from the BL65x Product Page. There are two README files contained in the "Firmware" folder of the files, as well as the utilities required to create the cloned image. The first option, ____READ_ME_TO_CLONE_FILESYSTEM___, captures only the flash file and data system and does not include the firmware. The second option, READ_ME_TO CLONE FIRMWARE_&_APP__, clones the flash file and data system as well as the firmware. When possible, we recommend cloning the firmware as well as the flash and data systems.
- MultideviceLoader, which is a command-line application for Windows, Linux and Mac that can be used to XCompile an application (Windows only) and download it to multiple Laird devices at the same time and provides options for: renaming the file, running it after download and other functions. This is a companion application for UwTerminalX and is mostly suited to production/end-stage testing purposes. Command line arguments are available in the Wiki on the GitHub repository.
Note: UwFlashx and Uwflash_embed are for firmware upgrades, and cannot be used to program smartBASIC applications.
How do I program BL65x modules in production or in the field (Tag-Connect)?
Consider using a PCB pad layout with support for Tag-Connect for JTAG which allows for easy, low cost programming in production or in the field.
Note: Laird recommends you use JTAG (2-wire interface) to handle future BL65x module firmware upgrades. You MUST wire out the JTAG (2-wire interface) on your host design , where four lines should be wired out, namely SWDIO, SWDCLK, GND and VCC. Firmware upgrades can still be performed over the BL65x UART interface, but this is slower (60 seconds using UART vs. 10 seconds when using JTAG) than using the BL65x JTAG (2-wire interface).
Is it possible to use Nordic's UART Serial Port Service when a BL65x module is configured for UART Bridge Mode rather than using Laird's Virtual Serial Port Service?
Yes, if config key 112 set to 1, via the AT+CFG 112 command then the service UUIDs for the UART serial port service is as per Nordic’s implementation. Any other value will use the service UUIDs for Laird’s custom service - vSP (Virtual Serial Port).
Please reference the Virtual Serial Port Service Managed section in the smartBASIC Extensions User Guide of the BL65x module you are working with for additional information.
Issues with Flashing custom firmware to BL65x using Segger Embedded Studios IDE
The BL652, BL653, and BL654 modules come preloaded with our smartBASIC firmware. When flashing custom firmware using Segger IDE it is necessary to do a full erase of the Laird BL65x module before programming the module. This can be accomplished using the NRFJPROG command line tool to send the command
How can I connect a Bluetooth Low Energy Device to a PC?
Bluetooth Low Energy uses Services as opposed to the set of standardized profiles that exists for Classic Bluetooth. While some Bluetooth Low Energy services have been standardized by the Bluetooth SIG, the development of custom services is allowed to meet custom application requirements.
Because Bluetooth Low Energy uses a completely different protocol than Classic Bluetooth and supports custom services, Bluetooth Low Energy devices cannot connect to a computer through the typical Bluetooth configuration of a computer. Therefore, connecting to a PC requires writing and running a Bluetooth Low Energy Central Role/Client application to collect the data sent from the Bluetooth Low Energy peripheral modules. Application development for PCs and Mobile devices is outside the scope of our support. Alternatively, a BL654 USB dongle could be used as a BLE Central Role device, to collect the BLE data and pass it to the PC over a COM Port. However, you would still need an application to view and process the data received over that COM Port.
We generally recommend customers who are new to Bluetooth Low Energy obtain a copy of Getting Started with Bluetooth Low Energy to help them understand the Bluetooth Low Energy protocol and the GATT table. There are also many resources available online which explain this.
When Bluetooth Low Energy was first introduced and we launched our BL6xx product line (predecessors to the BL65x series) we produced the BL600 and BL620 smartBASIC Application Walkthrough document, which provides an overview of how Bluetooth Low Energy works and how a GATT table is constructed.
How do you change the BAUD rate in the AT Interface Application for BL65x smartBASIC modules?
The default baud rate in the AT Interface application is 115200. In order to change the baud rate within the AT Interface code there are two modifications required in the AT Interface files as shown below:
- Locate the following settings within the $autorun$.AT.Interface.BL652._.sb file which sets the baud to 115200 (highlighted):
#define SREGINIT_VAL32_0 "\4C\1D\00\00\98\3A\00\00\00\C2\01\00\00\20\00\00\01\20\00\00"
#define SREGINIT_MIN32_0 "\4C\1D\00\00\4C\1D\00\00\B0\04\00\00\01\00\00\00\01\00\00\00"
#define SREGINIT_MAX32_0 "\1E\04\3D\00\1E\04\3D\00\40\42\0F\00\FF\FF\00\00\FF\FF\00\00"
Modify the settings to set the Hex value for the desired BAUD rate in little endian format
The example below will set it to 9600 baud (0x00 0x00 0x25 0x80) as shown below (highlighted)
#define SREGINIT_VAL32_0 "\4C\1D\00\00\98\3A\00\00\80\25\00\00\00\20\00\00\01\20\00\00"
#define SREGINIT_MIN32_0 "\4C\1D\00\00\4C\1D\00\00\B0\04\00\00\01\00\00\00\01\00\00\00"
#define SREGINIT_MAX32_0 "\1E\04\3D\00\1E\04\3D\00\40\42\0F\00\FF\FF\00\00\FF\FF\00\00"
- Locate the settings for S Register 302 in the $LIB$.SRegInterface.sb file: Modify the settings in
#cmpif 0x00010000 : rc=BleEncode32(SregCache32$,115200,offset)to set the baud rate to the desired baud rate.
Do BL65x modules support Boundary Scan function?
Unfortunately, we do not offer Boundary Scan functionality on the BL65x modules.
We do understand it is harder to place and recommend during development the use of an X-ray or some other means to verify to soldering process.
Do you have a smartBASIC example for Android or iOS devices such as smartphones or tablets?
smartBASIC is a programming language developed for our BT900 and BL6xx modules to simplify the code required for programming them. It is not used for developing Android or iOS device applications. BLE applications for Android and iOS devices would need to written in code specific to the Android or iOS platform.
Our, Laird Toolkit Application available for iOS and Android is currently in the process of being updated for Android and iOS to work with newer OS platforms.
Once it is complete we expect to make the source code available, to customers working with our smartBASIC modules, for reference when developing Apps for these platforms.
As of the writing of this FAQ the current version of the Laird Toolkit is still available on the App store for iOS and Google Play for Android, however, it may not work with newer versions of iOS or Android until the updates have been made.
Google Play Store
An alternate resource, the Nordic nRF Toolbox is also available from the iOS App Store and Google Play. The source code for this application is available from Nordic's Website.
Is there protection from Hacking when using smartBASIC modules?
Our Bluetooth 5.0 smartBASIC modules (BL652, BL653, BL654) have the capability of supporting LE Secure Connections Pairing as well as encryption. LE Secure Connection is an enhanced security feature introduced in Bluetooth v4.2. It uses a Federal Information Processing Standards (FIPS) compliant algorithm called Elliptic Curve Diffie Hellman (ECDH) for key generation.
LE Secure Connections, supports four association models:
- Just Works
- Numeric Comparison (Only for LE Secure Connections)
- Passkey Entry
- Out of Band (OOB)
Additional information about LE Secure Connections and the models can be found here: www.bluetooth.com.
Our Bluetooth 4.0 smartBASIC modules (BT900 /BL600 /BL620) support Simple Secure Pairing and Encryption
Additional information about Simple Secure Pairing can be found here:
We recommend reviewing the Pairing, Bonding and Security Manager functions in the BL6xx/BT900 smartBASIC Extensions User Guides. The full security of the Bluetooth/Bluetooth Low Energy connection will depend largely on how the smartBASIC application is written, and what the input/output capabilities are of the devices that are connecting. If either device will not have any input/output capabilities then pairing will have to default to Just Works, which is the least secure pairing method. However there are additional layers of security that can be added to increase protection from hacking when the Just Works pairing model is used.
With Bluetooth Low Energy, to further secure the connection, it is recommended that the metadata for the characteristic attributes are configured for Encryption with man-in-the-middle protection for characteristic value access. This will prevent anyone from accessing data on the module without proper encryption keys. (See
BleAttrMetadataEx in the BL6xx/BT900 smartBASIC Extensions User Guides.) Additionally, when using Just Works pairing, or any time additional security is required, we recommend adding a challenge/response question to the application layer, with a timer, which expects the connecting device to respond to the challenge question in a specified period of time after a connection has occurred. If the correct response is not received within that time period the application would force a disconnection. Finally, whisper mode pairing can be used during the pairing process as an additional layer of security. This is accomplished by reducing the Tx power while pairing using
BleTxPwrWhilePairing as per the BL6xx/BT900 smartBASIC Extensions User Guide, which will reduce the radius which a hacker would need to breach in order to capture or spoof the encryption procedure.
How do I set parity on the BL65x?
Setting parity is not possible using smartBASIC on the BL652 and BL654. However, setting parity is supported when working with the Nordic SDK. Therefore, if parity setting is required, the module will have to be programmed using the Nordic SDK and the Nordic examples instead of Laird's smartBASIC examples.
Please refer to the Using the DVK-BL652 and Nordic SDK v14.0.0 with Eclipse & GCC or the Using the BL654 and Nordic SDK v16.0.0 with Eclipse and GCC application note for assistance in setting up the BL652-DVK or BL654-DVK using the Nordic SDK. Please note that Nordic examples work with the external crystal as the clock source. The DVK-BL652 uses the internal RC Oscillator as the clock source, therefore if you will not be fitting the low frequency external crystal please be sure to modify the Nordic examples as explained in the above application note. You may also wish to refer to the BL652 Dev Kit User Guide or the BL654-DVK User Guide & Quick Start Guide
Can I write/encode an NFC tag using the BL65x?
The NFC capability of the BL652 is NFC-A Listen Mode, Type 2. It is exposed as a passive interface. Therefore, the BL652 NFC functionality currently allows for read-only (type 2) tags which can be read from an Active NFC reader, such as a smartphone or Arduino-based shield. It is not able to write or encode external tags.
More information on NFC capability on the BL652 can be found in section 7.1, "Near Field Communication (NFC) on page 314 of the BL652 smartBASIC Extensions User Guide
For the BL654, more information can be found in section 6.1 on page 344 of the BL654 smartBASIC Extensions User Guide
Can a BL65x firmware be updated OTA?
OTA firmware updates are not available for the BL65x modules. While smartBASIC programs (e.g. hello.world.sb) can be uploaded OTA, Laird firmware version (e.g. v22.214.171.124) updates can only be done over JTAG or UART.
I've loaded a Nordic SDK application to the BL654PA and it isn't transmitting anything, why is that?
There is a Skyworks 66112-11 front-end module external to the nRF52840 and control over PA (TX) and LNA (RX) must be included in your application. Please see Application Note - Nordic SDK-Based Application Development - BL654PA for more details on how to utilize the Nordic soft device to control the PA and LNA of the Skyworks front-end module.
Do I have to use the Segger branded debugger to program over the 2-wire SWD interface (JTAG) of the Nordic-based modules?
Yes, any programmer/debugger that supports the SWD 2-wire interface and the Cortex M4F processor should work with the Nordic-based modules. You can find information about the memory map in the nRF5xxxx Product Specification under the Memory and NVMC sections.
How can BL65x module or dongle be used to receive data from a custom service running on another device?
Several Sample Applications are available from the corresponding BL65x-Applications folder on Laird Connectivity's GitHub repository, including an AT Interface sample application. The AT Interface sample application enables a quick way to configure a smartBASIC BL65x module using the commands available in the AT Interface User Guide to scan, connect, read the GATT table and receive data from the connecting device via the appropriate UUID for the custom service. We recommend referencing the AT Interface Quick Start Guide v1 0.pdf to get started with the AT Interface Application, which walks you through loading the application and a few of the basic commands, including initiating a vSP connection, (vSP is Laird's custom Serial UART application.) A non-vSP connection can be established using AT+LCON as per page 21 of the AT Interface User Guide.
Alternatively, a custom smartBASIC central application could be developed and loaded to the dongle to connect with the custom service by referencing the Core Functionality smartBASIC and modular Extension User Guides available on the corresponding Product Page for the module, for example:
User Guide - smartBASIC Core Functionality v3.4
BL654 smartBASIC Extensions Guide v126.96.36.199
Please note: the BL654 dongle comes in two variants, smartBASIC variant (451-00003) and Nordic/Zephyr variant (451-00004). If electing to work with the smartBASIC firmware and example applications available on the GitHub repository it will be necessary to purchase the 451-00003 smartBASIC variant, as smartBASIC applications cannot be loaded to the 451-00004 Nordic/Zephyr variant.
What is Laird Connectivity's product lifecycle EOL and PCN policy?
Laird Connectivity is committed to the long-term supply of all its standard embedded wireless modules and packaged products. Laird Connectivity’s products are specifically designed to meet the needs of the industrial and medical markets, which typically require 7 – 10 years product lifecycle. Although Laird Connectivity can’t guarantee that a component used in our products will not be obsoleted and cannot be reasonably substituted, Laird Connectivity can assure customers we will continue to sell our product when we have customer demand and can obtain the necessary components to build our products.
Can I XCompile a smartBASIC script without a module attached to UWTerminalX?
There exist three solutions:
Using the offline XCompiler
- Copy the relvant version of XCompiler (found in the firmware zip file for your relevant firmware version) to the folder that contains your smartBASIC application.
- Say, your XCompiler is called xcomp_bl652_1234_5678.exe and your smartBASIC app is called jenniferRocks.sb. Then open a command prompt window in that folder and issue the command xcomp_bl652_1234_5678.exe jenniferRocks.sb and if there are no errors you will see a file called jenniferRocks.uwc being created which is what gets downloaded to the module by UwTerminal.
- In the file name xcomp_bl652_1234_5678.exe The ?bl652? comes from the AT I 0 response and the ?1234_5678? comes from the AT I 13 response
Using the online XCompiler
- Lairds online XCompiler is available at http://uwterminalx.no-ip.org/
- You can upload a SmartBASIC source code file and when successfully compiled, the browser will automatically download the compiled .uwc file.
- Note that compiling with the online XCompiler is limted to a single source code file (#include statements are not supported)
Using the Online XCompiler Tool
- The Online XCompiler Tool is a frontend for our online XCompiler and supports multiple source code files through #include statements. You can select a source code file and the tool automatically compiles it and stores the .uwc locally.
What is the easiest way to change the advertised Device Name in a smartBASIC Application?
Changing the advertised device name is accomplished using three different functions prior to calling the BleAdvertStart () function.
First, the BleGapSvcInit () function is used to change the device name from the default, Laird [BL600 | BT900], to the desired device name.
Next, the BleAdvRptInit () funtion must be called to create and initialize the advert report with the new device name.
Finally, the BleAdvRptsCommit () function must be called to commit the changes.
Below is an example of a simplified smartBASIC app which changes the default device name to "My Device":
// Laird Connectivity
// Rikki Horrigan
//Global Variable Definitions
dim rc //result code
// Initialize Global Variable
nameWritable = 0 //The device name will not be writable by peer.
nAppearance = 1091 //Device will apear as Walking sensor on hip (org.bluetooth.characteristic.gap.appearance.)
nMinConnInterval = 500000 // must be smaller than nMaxConnInterval.
nMaxConnInterval = 1000000 //must be larger than nMinConnInterval
nSupervisionTout = 4000000 //Range is between 100000 to 32000000 microseconds (rounded to the nearest 10000 microseconds)
nSlaveLatency = 0 //value must be smaller than (nSupervisionTimeout/nMaxConnInterval)-1
//Functions & Subroutines
SUB assertRC(rc, line)
IF rc != 0 THEN
PRINT "\nError on line ";line;", code: ";INTEGER.H'rc
// Change Device Name
print "Default Device Name: "; BleGetDeviceName$ ();"\n"
dim deviceName$ //declare variable for DEVICENAME
deviceName$= "My Device" //Set new DEVICENAME
rc = BleGapSvcInit (deviceName$, nameWritable, nAppearance, nMinConnInterval, nMaxConnInterval, nSupervisionTout, nSlaveLatency )
print "\n New Device Name: "; BleGetDeviceName$ (); "\n"
//Create and Initializing the Advert Report (not advertised until BLEADVRPTSCOMMIT is called)
dim adRpt$ //advert report
adRpt$ = ""
rc = BleAdvRptInit(adRpt$, 2, 0, 16)
//Commit the advert report
dim scRpt$ //scan report
scRpt$ = ""
rc = BleAdvRptsCommit(adRpt$,scRpt$)
addr$ = ""
rc = BleAdvertStart(0,addr$,100,0,0)
ENDFUNC 1 // Remain in WAITEVENT
//Equivalent to Main() in C
rc = OnStartup()
Become a Laird Connectivity Customer and Gain Exclusive Access to Our Design Services Team
- Antenna Scans
- Antenna selection and placement
- Custom antenna design
- Worldwide EMC testing / certifications
- Embedded RF hardware / firmware design
- Cloud architecture and integration
- Mobile application development
- Product & Industrial Design
|Decca Corp||453-00020C||3281||EMEA||Buy Now|
|NetroFlash||453-00020C||1225||North America||Buy Now|
|J3||453-00020C||120||North America||Buy Now|
|Avnet||453-00020C||0||North America||Buy Now|
|Digi-Key||453-00020C||0||North America||Buy Now|
|Future Electronics||453-00020C||0||North America||Buy Now|
|Mouser||453-00020C||0||North America||Buy Now|
|Symmetry Electronics||453-00020C||0||North America||Buy Now|
|NetroFlash||453-00020R||3253||North America||Buy Now|
|Avnet||453-00020R||0||North America||Buy Now|
|Digi-Key||453-00020R||0||North America||Buy Now|
|Future Electronics||453-00020R||0||North America||Buy Now|
|Symmetry Electronics||453-00020R||0||North America||Buy Now|
|Avnet||453-00021C||0||North America||Buy Now|
|Digi-Key||453-00021C||0||North America||Buy Now|
|Future Electronics||453-00021C||0||North America||Buy Now|
|Mouser||453-00021C||0||North America||Buy Now|
|Symmetry Electronics||453-00021C||0||North America||Buy Now|
|Decca Corp||453-00021R||4624||EMEA||Buy Now|
|NetroFlash||453-00021R||1725||North America||Buy Now|
|J3||453-00021R||300||North America||Buy Now|
|Avnet||453-00021R||0||North America||Buy Now|
|Digi-Key||453-00021R||0||North America||Buy Now|
|Future Electronics||453-00021R||0||North America||Buy Now|
|Symmetry Electronics||453-00021R||0||North America||Buy Now|
|Mouser||453-00062-K1||16||North America||Buy Now|
|Digi-Key||453-00062-K1||15||North America||Buy Now|
|Avnet Europe||453-00062-K1||5||EMEA||Buy Now|
|Avnet||453-00062-K1||0||North America||Buy Now|
|Symmetry Electronics||453-00062-K1||0||North America||Buy Now|
|Digi-Key||455-00022||25||North America||Buy Now|
|Mouser||455-00022||10||North America||Buy Now|
|Classic Components||455-00022||2||North America||Buy Now|
|Newark||455-00022||2||North America||Buy Now|
|element14 APAC||455-00022||2||APAC||Buy Now|
|Avnet||455-00022||0||North America||Buy Now|
|Future Electronics||455-00022||0||North America||Buy Now|
|Symmetry Electronics||455-00022||0||North America||Buy Now|
|Mouser||455-00023||6||North America||Buy Now|
|Digi-Key||455-00023||5||North America||Buy Now|
|Classic Components||455-00023||2||North America||Buy Now|
|Newark||455-00023||2||North America||Buy Now|
|element14 APAC||455-00023||2||APAC||Buy Now|
|Avnet||455-00023||0||North America||Buy Now|
|Future Electronics||455-00023||0||North America||Buy Now|
|Symmetry Electronics||455-00023||0||North America||Buy Now|
|Alpha Micro UK Only||+44 1256-851770
+44 2039 365486
|APAC, North America, South America, EMEA||Website|
+44 1628 512900
|APAC, North America, South America, EMEA||Website|
||North America, South America, APAC, EMEA||Website|
|Farlink Technology||+86 13266922199
+44 3447 11 11 22
|North America, South America, APAC, EMEA||Website|
|Jetronic China, Hong Kong and Taiwan||852-27636806
+44 1628 858941
|North America, South America, APAC, EMEA||Website|
|Martinsson||+46 8 7440300
|McCoy South East Asia||+65 6515 2988
+44 1494 427500
|North America, South America, APAC, EMEA||Website|
|North America, South America, APAC, EMEA||Website|
|Supreme Components International|| +65 6848-1178
||North America, South America, APAC, EMEA||Website|
|Tekdis Australia and New Zealand||+61 3 8669 1210
|Telsys||+972 3 7657666