Hi @ all,
because of the low TX current, I want to use the BTLC1000 in an existing project. Basically I want to replace a Nordic nRF8001, which is a BLE link controller that requires an external MCU and is interfaced via SPI. According to the datasheet the BTLC1000 can also be used as link controller (without its internal M0) controlled by an external MCU.
I am missing documentation about the low level interfacing of the BTLC1000 and an external MCU. When going through Atmel's API, the interesting functions seem to end up in precompiled libraries.
I need to know about the low-level configuration, to be able to use the existing project's MCU without Atmel's API. (I only need broadcasting and to alter advertise data, no callbacks or event calls).
I discovered the simple broadcaster example, and monitored all wires of the BTLC1000-Xplained with a logic analyzer to get more insights.
@ 1: UART_RX and _TX (115200Bd) seem to show the same data (around 40 bytes on TX), even when parameters like device name were changed.
@ 2: On MISO line (SPI_MISO according to data sheet) an UART protocol signal transfers a huge amount of data with 115200Bd.
@ 3: On CS (SPI_SSN according to data sheet) and MISO some bytes are exchanged (UART 115200Bd). Here parameters like ADV_UUID_DATA, ADV_DATA_APPEARANCE_DATA, ADV_DATA_NAME_DATA and ADV_DATA_MANUFACTURER_DATA seem to be exchanged.
Does anyone know, if the M0 of the BTLC1000 is used in the Atmel examples, or is the SAM on the Xplained board used to program it (i.e. in step 2)?
In the example, UART is set as BLE link controller interface, so I expected all the configuration data to appear on UART line. Or is MISO and CS used as UART between M0 and BLE link controller? In this case, controlling and programming the M0 of the BTLE1000 is implicitely done by the Atmel API....
Is it possible to generally send some configuration bytes to the BTLC1000 to make it start broadcasting without the huge data transfers shown above?
Thanks in advance for help:-)