The PRoC BLE or PSoC 4 BLE is the main component on the BLE Module. It provides the RF
interface and analog and digital capability. The PRoC BLE or PSoC 4 BLE pins are mapped to the
Bluetooth module headers (see Figure 5-20). For more information, refer to the BLE web page.
Figure 5-20. Schematics and Board Highlight of Bluetooth Module Headers for BLE Pins
The PSoC 4 BLE and PRoC BLE Modules connect to the Pioneer board using the two (20-pin and
24-pin) Bluetooth module headers (Figure 5-21). All GPIOs and power domains are brought out to
these headers. These headers are the counterparts of the connectors in section 5.1.4.
Figure 5-21. Schematics and Board Highlight of Headers
An Antenna Matching Network is required between the BLE device and the antenna to achieve optimum performance (Figure 5-23). The matching network has four main tasks:
■ Transform the balanced output of the radio to an unbalanced connection to the antenna (balun).
■ Transform the output impedance of the ra dio to a 50-ohm antenna.
■ Suppress harmonics to a level below the regulations lev el in TX mod e.
■ Suppress the local oscillator (LO) leakage in RX mode.
Figure 5-23. Schematics and Board Highlight of Antenna Matching Network and Antenna
Module boards include a 24-MHz cryst al and a 32-kHz crysta l, the CMOD and shield (CT ANK) circuit
for CapSense, a SAR bypass capacitor, and adequate decoupling capacitors for all the power
domains, as shown in Figure 5-24.
Figure 5-24. Schematics and Board Highlight of External Crystal, CMOD, CT ANK, Decap s, Jumpers
All power domains are brought out as test points for easy probing.
5.3BLE Dongle Board
See PSoC 4 BLE or PRoC BLE on page 106.
See Wiggle Antenna on page 108.
See Antenna Matching Network on page 109.
See Pioneer Board LEDs on page 101.
See Push Buttons on page 102.
Figure 5-25. Board Highlight
The PSoC 5LP connects to the USB port of a PC through a USB type A plug (Figure 5-27). This plug
can also be used to power the board. A resettable polyfuse is used to protect the computer's USB
ports from shorts and overcurrent. If more than 500 mA is applied to the USB port, the fuse will automatically break the connection until the short or overload is removed. The VBUS, D+, and D– lines
from the USB connector are also protected again st ESD eve n ts using TVS diod es.
Figure 5-27. Schematics and Board Highlight of USB Ty pe A Plug
This chapter describes advanced features of the BLE Pioneer kit as well as the corresponding
projects. It can be used as referenc e to exploit these features for other applications, according to
project requirements.
6.1Using PSoC 5LP as USB-UART Bridge
The PSoC 5LP serves as a USB-UART bridge, which can communicate with the COM terminal
software. This section explains how to create a PSoC 4 BLE code example to communicate with the
COM terminal software.
Users who have a Windows operating system that does not have HyperTerminal can use an
alternative terminal software such as PuTTY.
1. Create a new PSoC 4 BLE project in PSoC Creator, as shown in Figure 6-1. Select an
appropriate location for your project and rename the project as required.
for(;;)
{
/* Get received character or zero if nothing has been received yet
*/
ch = UART_UartGetChar();
if(0u != ch)
{
/* Send the data through UART. This function is blocking and waits until
there is an entry into the TX FIFO. */
UART_UartPutChar(ch);
}
}
}
7. Build the project by clicking Build > Build {Project Name} or [Shift][F6]. After the project is built
without errors and warnings, program (by choosing
Debug > Program) the project to PSoC 4
BLE/PRoC BLE through the PSoC 5LP USB programmer or MiniProg3.
Note: UART RX and UART TX can be rou ted to any digit al p in on PSoC 4 BL E/PRoC BLE based
on the configuration of the UART component. An SCB implementation of UART will route the RX
and TX pins to one of the following subsets: (P0[0], P0[1] or P0[4], P0[5] or P1[4], P1[5] or P3[0],
P3[1] or P3[4], P3[5] or P5[0], P5[1]).
To communicate with the PSoC 4 from the terminal software, follow this procedure:
1. Connect USB mini-B to J13. The kit enumerates as a
KitProg USB-UART and is available in the
Device Manager, Ports (COM & LPT). A communication port is assigned to the
KitProg USB-UART, as shown in Figure 6-8.
3. A new window opens, where the communication port can be selected.
In HyperTerminal, select COMx (or the specific communication port that is assigned to the Kit-
Prog USB-UART) in
COMx in
Serial line to connect to. This code example uses COM12.
Connect using and click OK, as shown in Figure 6-10. In PuTTY enter the
5. Enable Echo typed characters locally in File > Properties > Settings > ASCII Setup, to
display the typed characters on HyperTerminal, as shown in Figure 6-12. In PuTTY, select
on
in T erminal > Line disciplineoptions to display the typed characters on PuTTY, as shown in
Force
Figure 6-13.
Figure 6-12. Enable Echo of Typed Characters in HyperTerminal
Figure 6-13. Enabling Echo of Typed Characters in PuTTY
6. The COM terminal software displays both the typed data and the echoed data from the PSoC 4
BLE or PRoC BLE UART, as shown in Figure 6-14 and Figure 6-15.
The PSoC 5LP serves as a USB-I2C bridge that can be used to communicate with the USB-I2C
software running on the PC. The following step s describe how to use the USB-I
communicate between the BCP and the PSoC 4 BLE/PRoC BLE.
1. Create a new project targeting the PSoC 4 BLE/PRoC BLE dev ice in PSoC Creator, as shown in
10.Open Protocol Configuration from the Tools menu and s elect the appropriate I2C Speed, as
shown in Figure 6-23. Make sure the I
component. Click
OK to close the window.
2
C speed is the same as the one configured in the I2C
Figure 6-23. Opening Protocol Configuration Window in BCP
11. From the BCP, transfer five bytes of data to the I
command shown in Figure 6-24 and press
[Enter] or click the Send button in the BCP. The log
2
C device with slave address 0x08. Type the
shows whether the transaction was successful. A '+' indication after each b yte indicates that the
transaction was successful and a '–' indicates that the transaction was a failure.
12.From the BCP, read five bytes of data from the I2C slave device with slave address 0x08. The log
shows whether the transaction was successful, as shown in Figure 6-25.
Figure 6-25. Read Data Bytes from BCP
Note: Refer to Help Contents under Help in BCP or press [F1] for details of I