1. CONFIDENTIAL AND PROPRIETARY 13 October 2010
Ideas on the Move
ID 212C: Bluetooth Wireless Connectivity for Renesas Products
13 October 2010

2. CONFIDENTIAL AND PROPRIETARY
Introduction
We enable low cost and low power Bluetooth connectivity for consumer, medical and industrial applications.
Founded in 2005
Brookline, MA
Arkady Pittel
CEO

3. Agenda
Why Bluetooth ? What do I need to implement Bluetooth ? How Bluetooth works ? Features and advantages of using dotstack Where to start ? Licensing and Support

4. Key Takeaways
Importance of Bluetooth in my next design Flexibility of using dotstack already integrated with my Renesas processor Dotstack is an easy and inexpensive way to implement Bluetooth in many applications Development roadmap supported by CandleDragon and Renesas

5. What drives Bluetooth applications ?
Mobile handsets have been the “killer app” for Bluetooth ... penetration in handsets has grown to ~ 50% in ‘07. As the mobile phone market has grown, so has the Bluetooth technology and brand recognition. [IDC] Bluetooth smartphones shipped [IMS] 2009 – 121M 2015 – 548M Bluetooth Technology Chosen as Continua Health Alliance, open industry coalition of leading health care and technology companies, has selected Bluetooth low energy wireless technology. [Continua Health Alliance Announcement]

6. Why Bluetooth ?
Bluetooth represents the next big opportunity to innovate and differentiate my next product ! Price of Bluetooth silicon is dropping ! Inexpensive Bluetooth stack, dotstack runs on Renesas platforms of my choice ! Inexpensive pilot license to jump start my project is available !

7. CONFIDENTIAL AND PROPRIETARY
Applications
Smartphones Headsets Automotive Medical Consumer Industrial
Application for industrial use: technician with a smart phone and Bluetooth application can save time servicing and troubleshooting, reflashing equipment and appliances in the field, that are equipped with Bluetooth connectivity. 7

8. Bluetooth Realization
CONFIDENTIAL AND PROPRIETARY
Bluetooth Realization
+ RX62N =
Wireless connectivity for
Industrial
Medical
Factory & Building Automation
Currently HS7216 platform is available, RX62N , RX610 and others, including NEC platforms will be implemented.

9. CONFIDENTIAL AND PROPRIETARY
Old Approach
Bluetooth Module
Processor
AT Commands
Chip antenna
stack
controller RF
controller
Minimum change of embedded application.
AT commands control Bluetooth.
Module Integrated with Stack
Limited number of profiles available: usually SPP
High price 10k
This is the easiest approach to building your Bluetooth solution, but certainly not recommended for high volume, low cost, low power. Not much choice of Bluetoooth profiles. Less flexibility.

10. CandleDragon Solution
CONFIDENTIAL AND PROPRIETARY
CandleDragon Solution
RX62N
UART
RF controller
Application
Chip antenna
Bluetooth solution
Functions to be implemented in application:
Timers
Non volatile storage pairing info
Send/receive
Variety of profiles
Lower Cost even at 10k:
dotstack <= $1 ea
HCI Bluetooth module $5-10
Highest saving with a discrete RF controller at $1-2
Low Power
Higher Baud Rate
In addition to UART, the transport can be also realized via USB, PCM (for audio especially high bandwidth), SPI.

11. CONFIDENTIAL AND PROPRIETARY
Architecture
Dotstack supports multiple devices

12. How it works …
dotstack uses a set of abstractions for timers, storage, and other OS services
integration code needs to expose that functionality by implementing certain functions declared by the stack
dotstack has no dependencies on any particular OS or platform. (runs on FreeRTOS)

13. CONFIDENTIAL AND PROPRIETARY
Features
Bluetooth Standard Version compliance V2.0, V2.1, +EDR
Bluetooth SIG Certification Yes
Memory Foot Print (typical for SPP) 3-4KB RAM
30KB FLASH
Baud Rate Up to 1.5 MBPS
Processing power requirement < 1MIPS

14. Profiles and Protocols Supported
CONFIDENTIAL AND PROPRIETARY
Profiles and Protocols Supported
Profiles
Service Port Profile (SPP)
Human Interface Device Profile (HID)
Generic Access Profile (GAP)
Headset Profile (HSP)
Health Device Profile (HDP)
Hands-Free Profile (HFP)
Secure Simple Paring (SSP)
                                       
Protocols
RFCOMM
L2CAP
eL2CAP
MCAP
Service Discovery (SDP)
Object Exchange (OBEX)
HFP – ensures safe phone handling in the car by allowing more complete control over phone functions, enables car kits to handle enhanced call control functions such as hold and call waiting. Phone status and signal strength indications are communicated for display by the car kit, while audio quality is also enhanced.
Secure Simple Pairing improves the BT user experience by simplifying two difficult steps for average consumer: finding the companion device and entering a passcode to establish a secure connection. With SSP, the user’s device finds only the device with which the user wishes to pair. SSP also handles passcode entry automatically ensuring the use of the longest, most secure passcode for each connection. The user simply presses a button confirming both devices are giving the same unique indication, and SSP establishes a robust connection.
Headset Profile - defines the requirements for Bluetooth devices necessary to support the Headset use case.
The HID profile defines the protocols, procedures and features to be used by Bluetooth HID (Human Interface Devices) such as keyboards, pointing devices, gaming devices and remote monitoring devices.
RFCOMM is a simple set of transport protocols, made on top of the L2CAP protocol, providing emulated RS-232 serial ports.
L2CAP passes packets to either the Host Controller Interface (HCI) or on a hostless system.
OBEX facilitates the exchange of binary objects between devices, and a foundation for many higher-layer profiles, i.e. FTP.

15. CONFIDENTIAL AND PROPRIETARY
Interoperability
Bluetooth Chipset (RF controller) 
CSR
Broadcom
Texas Instruments
MAC
Interoperability Testing
Microsoft
Toshiba
Widcomm
MAC
BlueZ
BlueCore

16. Advantages of CandleDragon’s Solution
CONFIDENTIAL AND PROPRIETARY
Advantages of CandleDragon’s Solution
Low Cost Wide choice of Profiles Readily available on Renesas platforms One year of free technical support Help with your application, embedded or smartphone
Bluetooth adapter plugs into Renesas development kit. The adapter can carry Bluetooth modules from Roving Networks (CSR BlueCore 04) or Bluegiga (CSR BlueCore 06).

17. Services from CandleDragon
CONFIDENTIAL AND PROPRIETARY
Services from CandleDragon
Embedded Application development
Mobile Application development
Android, Blackberry, Win Mobile, WinCE, Symbian, Linux

18. What’s next from CandleDragon ?
CONFIDENTIAL AND PROPRIETARY
What’s next from CandleDragon ?
Bluetooth Profiles
Advanced Audio Distribution Profile - A2DP
Phone Book Access Profile – PBAP
Bluetooth Low Energy (BLE) - v4.0
Bluetooth High Speed (24Mbps) – v3.0
Advanced Audio Distribution Profile - A2DP
Lets music players stream high-fidelity audio to a set of wireless headphones, a wireless music player docking station, or a car stereo system; increasingly common in phones, can be added to existing MP3 players.
Phone Book Access Profile – PBAP
Enables user to download and browse the entire phone book from any mobile phone or PDA; allowing speed-dial from the car kit and contacts stored on mobile phone.
BLE had been adopted by Continua Alliance as a wireless platform for medical devices.
Dual mode silicon: BT (Bluetooth) and BLE or only BLE.

19. Roadmap to Customer Bluetooth Solution
CONFIDENTIAL AND PROPRIETARY
Roadmap to Customer Bluetooth Solution
Get a RX62N kit that comes along with Bluetooth module based on CSR BC04 or BC06 RF controller via adapter board with SPP profile in object code Sample Application with a source code from CandleDragon Development Tools from Renesas (RDKSH7216 or RDKRX62N) Integrated Debugger

20. Renesas Bluetooth Engagement
CONFIDENTIAL AND PROPRIETARY
Renesas Bluetooth Engagement
SH7216 available RX62N coming soon

21. Licensing and Services by CandleDragon
CONFIDENTIAL AND PROPRIETARY
Licensing and Services by CandleDragon
Licensing Model – NO upfront fees, pricing starts at $1/unit up with a sliding scale.
Pilot License units of dotstack license with application source codes, API and support, all for only $1,500. Development hardware kit provided by Renesas.
Embedded and Mobile Application Development

22. Questions

23. Contact Information
Arkady Pittel, CEO
CandleDragon, Inc.
101 Winthrop Road, Suite 1
Brookline, MA 02445

24. Extra Slides

25. FAQ
Q: Does your software have some platform dependant layers that require customization?
A: All platform dependent functionality required by the stack is abstracted into a set of functions that have to be implemented for the particular platform/board.  
Here is a list of functions that integration code has to provide to the stack:
   - Timers (very low resolution - 50 ms)
   - Non volatile storage for saving link keys (pairing information)
 - Send/receive over UART

26. FAQ - continued
Q: Do you provide those functions ? A: If we have them already on the platform you use, we will provide you with the source code of those functions. Q: Does Candle Dragon provide support in customization and integrating the code into embedded applications and particular platforms, OS ? A: Yes, each particular case is treated separately based on SOW.

27. FAQ - continued Q: What is the tool chain you use?
A: We will compile the stack with whatever compiler you choose
Q: What are the system requirements for your stack to run on our processor ? 
Q: Static RAM allocation?
A: All RAM is statically allocated.  A configuration with only SPP profile will take about 3-4 KB.
Q: Max RAM usage for stack calls?
A: Required stack size is 512 bytes

28. FAQ - continued
Q: Does your dotstack need multiple threads? A: The stack assumes all its functions are called from one thread. Q: FLASH space? A: Program code will take approximately KB for SPP profile (depends on profile) Q: Non volatile storage? A: Each paired device requires 26 bytes of non volatile storage. The number of paired devices is configurable.

29. FAQ - continued
Q: Need certain I/O pins (UART / Interrupt pins) ? A: The following connections to the BT module are required: TX, RX, RTS, CTS, RESET Q: default UART baud rate for HCI interface? A: The Bluetooth module starts at 115,200 kbps. Then it can be configured to any standard (and probably non-standard) baud rate. Q: What is the highest baud rate you tested the dotstack at ? A: 1.5Mbps with EDR

30. FAQ - continued
Q: How the power management and sleep modes are realized between the embedded processor and Bluetooth RF controller ? A: The Bluetooth controller tells the host when it is going to a sleep mode so that the host can also enter a low power mode. When the controller needs to awake the host it uses the CTS line to trigger an interrupt. All described power saving scenarios is applicable to this solution. The wake up time for the host processor is very flexible. During the wake up procedure, after generating the interrupt condition on the CTS line, the controller periodically send a wake up packet to the host and waits for an acknowledgment packet back from it.