1 / 30

13 October 2010

Ideas on the Move. ID 212C: Bluetooth Wireless Connectivity for Renesas Products. 13 October 2010. Introduction. We enable low cost and low power Bluetooth connectivity for consumer, medical and industrial applications. Founded in 2005 Brookline, MA 02445 www.CandleDragon.com

swann
Download Presentation

13 October 2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Introduction We enable low cost and low power Bluetooth connectivity for consumer, medical and industrial applications. Founded in 2005 Brookline, MA 02445 www.CandleDragon.com 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. Applications Smartphones Headsets Automotive Medical Consumer Industrial 7

  8. Bluetooth Realization + RX62N = Wireless connectivity for Industrial Medical Factory & Building Automation

  9. 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 $15-25ea. @ 10k

  10. 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

  11. Architecture

  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. 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 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)

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

  16. 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

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

  18. 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

  19. 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 SH7216 available RX62N coming soon

  21. Licensing and Services by CandleDragon Licensing Model – NO upfront fees, pricing starts at $1/unit up with a sliding scale. Pilot License - 100 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 a.pittel@candledragon.com 857-919-4146 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 32-40 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.

More Related