BT860 Series Bluetooth Module

Ezurio did provide breakout boards for our older BL600(EOL) modules but we do not produce breakout boards for any of our current range of Bluetooth modules as of 2024.

This includes all BL65x, BL53xx, BL54xxx, BTxxx, Vela and Lyra modules.

We do provide development kits for all of our module offerings. To learn more, visit any product page on ezurio.com. 

The BT850/BT860 are what is known as a HCI modules, meaning they do not have a BT stack on board and rely on an external host OS (Windows/Linux) or micro with its own stack.

The BT850/BT860 comes preloaded with BT Controller firmware from the factory. 

BT850/BT860 does not come with BT host firmware. It is designed to be used with an external host that has a host stack.

LE Audio introduces the concept of Isochronous channels. The higher layers of the protocol are responsible for controlling the timing of the isochronous channels. For example, if using a pair of earbuds there would be two isochronous channels (Isochronous Group) used to transport left and right audio. These two channels must have a tight timing between them to minimize delay of audio heard between the left and right earbud.

Isochronous channels are part of the Bluetooth controller and are used for the transport of audio data. The BT850 and BT860 Bluetooth controllers do not provide isochronous channels support. Therefore, even though the BlueZ host stack now adds LE Audio support it cannot be used with the BT850 or BT860 Bluetooth controllers.

Yes, it is possible to write a custom Bluetooth address during run time by sending the HCI command, Write_BD_ADDR. You can also use the AIROC Bluetooth Test and Debug tool to select Write_BD_ADDR for setting a custom address.

Note: The Write_BD_ADDR command writes the Bluetooth Address to the chipset's internal RAM, which disappears after a power cycle.

Does the BT860 hardware support 7 concurrent BR/EDR connections?

Yes. The chipset and firmware in the BT860 does not limit the number of concurrent BR/EDR connections. Note that there may be stack or host resource limitations that could limit the number of concurrent connections.

Use of the LC3 codec is included in the Bluetooth product licence when you qualify your product. No additional licence fees are required.

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

 

The actual TX rate is influenced by the PDU and MTU sizes along with the Connection Intervals and Slave Latency.

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.
 

The Cypress CYW20704 A2 chipset, which the BT85x and the BT860 is based on, theoretically supports up to 127 Bluetooth LE connections. However, because the BT860 is an HCI module it is dependent on the Bluetooth stack running on the host therefore, the number of connections will depend on what the host CPU and memory capacity can support.

Additionally, as the number of connections increases, the throughput per each connection will decrease and the processing and memory requirements will increase, which can lead to increased latency. So while 127 is the theoretical limit the actual limit in practical use case would be less than that.

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.

The BT850, BT851 and BT860 are Bluetooth 5 qualified modules. However, these modules do not support any Bluetooth 5 features.
Per the Bluetooth SIG FAQ, "there are no mandatory features that must be claimed to use the Bluetooth 5.0 specification. However, manufacturers are required to implement all interoperability improvements and errata applied to Bluetooth 5 in order to comply with the specification".

In order to prevent a low power glitch that can cause EEPROM corruption (no field fix for this state) in the BT850/ BT860, a 0.1uF capacitor should be placed on the nRESET line of the radio if the nRESET line is connected to something externally.
If the nRESET line is to be left NC (not connected) then the capacitor is not needed. 

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. 

Yes, the following modules share the same pin layout:

BT800 --> BT850
BT830 --> BT860

There are some No Connect (NC) pins on the BT850/860

In general, cleaning the populated modules is strongly discouraged. Residuals under the module cannot be easily removed with any cleaning process. 

• Cleaning with water can lead to capillary effects where water is absorbed into the gap between the host board and the module. The combination of soldering flux residuals and encapsulated water could lead to short circuits between neighboring pads. Water could also damage any stickers or labels.
• Cleaning with alcohol or a similar organic solvent will likely flood soldering flux residuals into the RF shield, which is not accessible for post-washing inspection. The solvent could also damage any stickers or labels.
• Ultrasonic cleaning could damage the module permanently.

However, if water washing is required you will need to use deionized water. We do not recommend chemical cleaning and cannot guarantee it will not damage the modules. If you MUST clean PCB with chemicals it is recommended that you test on one board and then confirm the module still works after the process, prior to adding it to production, while understanding the above affects washing the populated PCBs can have on the module.