DOCSLIB.ORG

PIC32 Bluetooth® Stack Library Demonstrations

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
PIC32 Bluetooth® Stack Library Demonstrations PIC32 Bluetooth® Stack Library Demonstrations MPLAB® Harmony Integrated Software Framework Copyright (c) 2013-2017 Microchip Technology Inc. All rights reserved. Bluetooth Demonstrations Bluetooth Demonstrations This section provides descriptions of the PIC32 Bluetooth Stack Library demonstrations. MPLAB Harmony is available for download from the Microchip website by visiting: http://www.microchip.com/mplabharmony. Once you are on the site, click the Downloads tab to access the appropriate download for your operating system. For additional information on this demonstration, refer to the “Applications Help” section in the MPLAB Harmony Help. © 2013-2017 Microchip Technology Inc. MPLAB Harmony v2.05.01 2 Bluetooth Demonstrations Introduction Introduction PIC32 Bluetooth Stack Library Demonstration Applications Help. Description This help file contains instructions and associated information about MPLAB Harmony Bluetooth demonstration applications, which are contained in the MPLAB Harmony Library distribution. There are two types of applications: those built using a Bluetooth Driver (currently there are only two, for the BM64), and those using the MPLAB Harmony PIC32 Bluetooth Stack Library (which is not written as a driver). The Bluetooth Stack Library, which is considered the "basic" Bluetooth Stack , includes basic demonstrations that are referred to as Data Demonstrations. This section describes the hardware requirement and procedures to run these Basic Bluetooth Stack firmware projects on Microchip demonstration and development boards. In addition to the Data Demonstrations provided with the PIC32 Bluetooth Basic Stack Library, additional Premium Demonstrations, which are available for purchase, demonstrate the capabilities of the Bluetooth Audio Stack Library. Information is provided in the Premium Demonstrations section on how to obtain, configure, and run these demonstrations. To learn more about MPLAB Harmony stacks and libraries refer to the related documentation in Volume V: MPLAB Harmony Framework Reference. © 2013-2017 Microchip Technology Inc. MPLAB Harmony v2.05.01 3 Bluetooth Demonstrations Demonstrations BM64 Driver Demonstrations Demonstrations This section provides information on the standard Data Demonstrations and demonstration applications built with the BM64 Driver, as well as the purchased Premium Demonstrations. BM64 Driver Demonstrations This section provides instructions about how to run the demonstration applications built using the BM64 Driver. BM64_a2dp_hfp This topic provides information on the supported demonstration boards, how to configure the hardware, and how to run the demonstration. Description In this demonstration application, the BM64 Module Daughter Board, installed on the PIC32 Bluetooth Audio Development Kit (BTADK), is used to stream A2DP audio from a Bluetooth host, such as a smartphone, to a pair of headphones connected to the Audio DAC Daughter Board which comes with the BTADK. The demonstration can also automatically answer a voice call coming in via Hands-Free Protocol (HFP), interrupting (and pausing) any A2DP streaming in progress. Local audio is input using a microphone connected to the MIC IN input of the BM64 Module Daughter Board. When the call is terminated, streaming resumes. Architecture This application runs on the PIC32 Bluetooth Audio Development Kit, which contains a PIC32MX470F512L microcontroller with 512 KB of Flash memory and 128 KB of RAM running at 96 MHz with the following features: • 220x176 color LCD • Six push buttons (SW1-SW6) • Five LEDs • USB Device and Host interfaces • Two X32 sockets, one for Bluetooth module and a second for a codec or DAC 1. The PIC32 Bluetooth Audio Development Kit comes with a BTM805 Bluetooth Daughter Board and an AK4384 Audio DAC Notes: daughter Board; however, you must replace the BTM805 daughter board with the daughter board for the BM64. 2. The USB Device and Host interfaces are not used in this application. Surrounding the PIC32MX470F512L microcontroller are a set of headers, which accept various plug-in modules (PIM), including one for a PIC32MX270F512L PIM as a second configuration for this project. The following figure illustrates the application architecture. The PIC32 microcontroller (MCU) runs the application code, and communicates with the BM64 over a USART interface operating at 115,200 baud. The BM64 module contains its own Bluetooth stack, so it is unnecessary to include a software Bluetooth stack in the PIC32 MCU. The program takes up about 40% of the PIC32MX470F512 microcontroller’s program space, and 27% of its RAM. The interface between the PIC32 MCU and the LCD is an 8-bit parallel master port (PMP). The program uses the MPLAB Harmony v2.0 Graphics Library to draw on the screen. The buttons are also interfaced using GPIO pins. As with any MPLAB Harmony application, the SYS_Initialize function, which is located in the system_init.c source file, makes calls to initialize various subsystems, such as the clock, ports, board support package (BSP), BM64, AK4384 DAC, PMP, timers, graphics, and interrupts. The BM64 and AK4384 drivers, graphics, timers, and the application state machines are all updated through calls located in the SYS_Tasks function in system_tasks.c file. Interrupt handlers in the system_interrupt.c file are used for the four DMA channels (only channels 0 and 1 are used), the USART, and the two timers. The application code is contained in two source files, app.c and audio.c. The former contains the application state machine (APP_Tasks). It first initializes the application, sets up a periodic timing callback, and then waits for the BM64 driver’s internal state machine to complete initialization (indicated by the function DRV_BT_GetPowerStatus returning RV_BT_STATUS_READY ). At that point the application calls a function called audioStart which initiates audio processing. Meanwhile, the audio state machine in audio.c has received a handle to the BM64 driver by calling DRV_BT_Open, and then setting callbacks for two event handlers (AUDIO_BT_RxBufferEventHandler for buffer event handling, and _audioEventHandler for general event handling). After that it gets a handle to the AK4384 driver by calling its DRV_CODEC_Open function with a mode of DRV_IO_INTENT_WRITE. Then it registers an event handler, AUDIO_CODEC_TxBufferEventHandler as a callback with the AK4384 driver. Then, it waits for the application to call audioStart before it makes its first call to DRV_BT_BufferAddRead to request audio samples from the BM64. The event handler callback is given control whenever a buffer has been processed. By default two sets of buffers are used (AUDIO_QUEUE_SIZE = 2), each with 1250 32-bit samples; however, simply by changing the queue size a circular buffer scheme can be used instead. As each buffer is © 2013-2017 Microchip Technology Inc. MPLAB Harmony v2.05.01 4 Bluetooth Demonstrations Demonstrations BM64 Driver Demonstrations handed off to thebe sent to the codec, the other one becomes available to be filled by the BM64. The BM64 and AK4384 drivers interfaces with their respective I2S interfaces via DMA, but this is largely transparent to the application, as it is all taken care of by MPLAB Harmony. Demonstration Features • Uses the BM64 Bluetooth Driver Library to read audio samples from the BM64 • Use of either a “ping-pong” or circular buffer scheme • At a lower level, the BM64 driver uses the USART Driver Library to talk to the BM64 module • Uses the AK4384 Codec Driver Library to write samples to the AK4384 DAC • At a lower level, using the I2S Driver Library between the BM64 and BM64 driver, and the AK4384 Codec Library and the AK4384 DAC • Use of “ping-pong” audio buffers • Sending and receiving characters between the USART of the PIC32 MCU and the BM64 (see USART Driver Library) • Displays graphics on the 220x176 LCD of the PIC32 Bluetooth Audio Development Kit using the MPLAB Harmony Graphics Library (see MPLAB Harmony Graphics Composer Suite) and the Parallel Master Port (see PMP Driver Library) • Processing of button pushes on the PIC32 Bluetooth Audio Development Kit using a state machine for contact debouncing (see Ports Peripheral Library) • Use of two timers: one as a periodic 1 ms timer for the application, and a second used by the BM64 driver (see Timer Driver Library) The following API calls are made to the BM64 Bluetooth driver: • DRV_BT_Status – get a handle to an opened driver instance • DRV_BT_Open – get a handle to an opened BM64 driver instance • DRV_BT_BufferEventHandlerSet – register a callback for a buffer-related event handler • DRV_BT_EventHandlerSet – register a callback for a general event handler • DRV_BT_BufferAddRead – read audio samples from the BM64 • DRV_BT_GetPowerStatus - • DRV_BT_GetLinkStatus - • DRV_BT_GetBDName – get the Bluetooth device name • DRV_BT_GetBDAddress – get the Bluetooth device address • DRV_BT_GetPlayingStatus – get the playing status (paying, paused, etc.) • DRV_BT_PlayPause – toggle the play/pause status of the host device • DRV_BT_FastForward – put the host device into fast forward • DRV_BT_Rewind – put the host device into rewind • DRV_BT_CancelForwardOrRewind – cancel a previous fast forward or rewind request • DRV_BT_PlayPreviousSong – play the previous song of a playlist • DRV_BT_PlayNextSong – play the next song in a playlist • DRV_BT_volumeUp – bump the volume up one increment • DRV_BT_volumeDown – bump the volume down one increment • DRV_BT_EnterBTPairingMode – enter Bluetooth pairing mode • DRV_BT_DisconnectAllLinks – disconnect all links
Load more

Recommended publications
  • The Core Difference in Your Design RX Family Software Solutions
    The Core Difference in Your Design RX Family Software Solutions www.renesas.eu 2014.03 Free software from Renesas – Save time and costs in your embedded-system development project Use our proven software solutions to jump-start your embedded design, freeing up more time to focus on your application code. We offer software libraries and hundreds of sample programs for the microcontrollers in our advanced RX family – code that has been thoroughly developed, debugged, and tested by application engineers. Documentation explains how the code works. See below for a sampling of some of our software solutions. For a complete list, go to: www.renesas.eu/support/software/index.jsp MCU Series Connectivity Software App Note RX100 RX200 RX600 To add Ethernet, USB, or CAN connectivity to your system design, just select an RX600-series TCP/IP (HTTP, FTP, DNS, DHCP) R20AN0051EJ0106 4 MCU and download reliable code for the standard formats LibUSB (simple comm. w/out 4 you need. If it comes to USB only, RX100 and RX200 would be class spec) R01AN0492EJ0200 providing excellent solutions. USB HID (Device) R01AN0401EJ0200 4 USB HID (Host) R01AN0399EJ0200 4 USB MSC (Device) R01AN0514EJ0200 4 USB MSC (Host) R01AN0513EJ0200 4 USB CDC (Device) R01AN0273EJ0200 4 USB CDC (Host) R01AN0275EJ0200 4 CAN API R01AN0339EU0203 4 USB (Device/Host) R01AN1670EJ0100 4 USB MSC (Host) R01AN0624EJ0210 4 USB MSC (Device) R01AN0710EJ0211 4 USB HID (Device) R01AN0546EJ0211 4 USB HID (Host) R01AN0664EJ0211 4 USB CDC (Host) R01AN0643EJ0211 4 USB CDC (Device) R01AN0555EJ0211 4 MCU Series Graphics Software App Note RX100 RX200 RX600 RX600-series MCUs integrate an external DMA 4 controller that enables cost-effective direct-drive Graphics Library *Contact Sales graphics implementations.
    [Show full text]
  • Rii Mini [Bluetooth]
    Ultra Slim Bluetooth keyboard User’s Manual Ver:ZW-53001BT （MWK09）1.1 Contents 1、Introduction 2、Hardware Installation 3、Software Setup Microsoft Windows Mobile OS Google Android OS Symbian OS Windows OS (with IVT Bluetooth Stack) Windows OS (Broadcom Bluetooth Stack) Linux(Ubuntu) 4、Product overview 5、Technical parameters 6、Maintenance 1、Introduction Thank you for purchasing the Ultra Slim Bluetooth Keyboard! You can use it for emails, chat, or to enjoy your favorite games. It is compatible with desktop computers running Windows or Linux but also with handhelds running Android, Windows Mobile Pocket PCs or Symbian S60 Operating systems. It also supports the Sony Playstation3. Use it with your HTPC on your Sofa or browse the internet in the most comfortable fashion. Computer System Requirements Windows 98/ME/2000/XP/Vista/7 Mac OS 10.2.8 or Later Mobile System Requirements Google Android Apple IOS 4 or Later Microsoft Windows Mobile 5.0 or Later Nokia Symbian S60 System Sony Playstation 3 Package Contents: Ultra Slim Bluetooth Keyboard Bluetooth USB Dongle（Optional） Driver CD（Optional） Charging Cable User Manual 2、Hardware Setup Please Note: The battery may be empty when you first unbox the product.Make sure to charge the device before attempting to set it up Paring Mode 1. Turn ON the power swith,the green LED will illuminate for 2 seconds. 2. Click on the “Bluetooth Pair/Connect”button.The green LED will blink intermittently. 3. The Keyboard is now in paring mode and is ready to be paired with your device. Recharging Connect the mini Bluetooth keyboard to your computer by using the included USB charging cable.When connected,the Red LED will illuminate and get dimmer as the battery charge level nears capacity.
    [Show full text]
  • PM0269 Bluetooth LE Stack V3.X Programming Guidelines
    PM0269 Programming manual Bluetooth LE stack v3.x programming guidelines Introduction The main purpose of this document is to provide developers with reference programming guidelines on how to develop a Bluetooth® Low Energy (Bluetooth LE) application using the Bluetooth LE stack v3.x family APIs and related event callbacks. The document describes the Bluetooth LE stack v3.x Bluetooth Low Energy stack library framework, API interfaces and event callbacks allowing access to the Bluetooth Low Energy functions provided by the STMicroelectronics Bluetooth Low Energy devices system-on-chip. The following Bluetooth Low Energy device supports the Bluetooth LE stack v3.x family: • BlueNRG-LP device The document also focuses on the key changes about APIs and the callback interface, Bluetooth LE stack initialization versus the Bluetooth LE stack v2.x family. This programming manual also provides some fundamental concepts about the Bluetooth Low Energy technology in order to associate the Bluetooth LE stack v3.x APIs, parameters, and related event callbacks with the Bluetooth LE protocol stack features. The user is expected to have a basic knowledge of Bluetooth LE technology and its main features. For more information about the supported devices and the Bluetooth Low Energy specifications, refer to Section 5 References at the end of this document. The manual is structured as follows: • Fundamentals of the Bluetooth Low Energy technology • Bluetooth LE stack v3.x library APIs and the event callback overview • How to design an application using the Bluetooth LE stack v3.x library APIs and event callbacks. Note: The document content is valid for all the specified Bluetooth Low Energy devices.
    [Show full text]
  • Iwrap 6.1 Bluetooth® Software
    iWRAP 6.1 Bluetooth® Software May 2015 Topics . iWRAP Bluetooth Stack . New features in iWRAP 6.1 . BGScript for iWRAP . iWRAP Feature Matrix 2 Silicon Labs Confidential iWRAP Bluetooth Stack Host (MCU) APPLICATIONS Application . Cable replacement . Stereo and hands-free audio Bluetooth Module . Smart phone accessories . HID Bluegiga iWRAPTM UART SPP, iAP etc. A2DP, HDP etc. profiles profiles FEATURES Security Generic . A fully featured Bluetooth 3.0 Stack RFCOMM Manager (SM) Access Profile (GAP) . Implements 13 different Bluetooth profiles for data and audio L2CAP . SPP, iAP, OPP, FTP, HID, DUN and HDP . A2DP, AVRCP v.1.5, HFP v.1.6, HSP, PBAP and MAP HCI . Up to 7 simultanous connections and data throughput up to 550kbps A fully featured Bluetooth 3.0A Stack . Apple MFI complaint with iAP1 and iAP2 protocols Bluetooth BR/EDR Radio . Integrated SBC, mSBC, aptX®, aptX® low latency and AAC audio codecs . Easy-to-Use ASCII based API over UART . Field upgradable over UART 3 Bluetooth 3.0 Integrated profiles Easy to use API ProductSilicon Family Labs ConfidentialDirectory New Features in iWRAP6.1 . Audio tone support . Audio tones (files) can be stored in the Bluetooth module’s flash memory Host (MCU) . Playback support for stored files Application Bluetooth Module . Audio tone mixing . Audio tones can be mixed with A2DP or HFP audio output Bluegiga iWRAPTM UART SPP, iAP etc. A2DP, HDP etc. profiles profiles . Enhanced reconnection logic . End user configurable Bluetooth reconnection logic Security Generic RFCOMM Manager (SM) Access Profile (GAP) . Simultanous AVRCP controller and target profiles L2CAP . Improved user experience with latest smart phones HCI .
    [Show full text]
  • BLUEBORNE on ANDROID Exploiting an RCE Over the Air
    BLUEBORNE ON ANDROID Exploiting an RCE Over the Air Ben Seri & Gregory Vishnepolsky BLUEBORNE ON ANDROID – © 2019 ARMIS, INC. Table of Contents Preface 3 Android RCE Vulnerability in BNEP - CVE-2017-0781 3 Exploitation on Android 7.1 5 Target Object Selection 6 Loading the Payload into Memory 10 Grooming the Heap 12 PoC Exploit Code 16 Conclusion 16 BLUEBORNE ON ANDROID — ©​ 2019 ARMIS, INC. — 2 ​ ​ Preface Armis researchers Ben Seri and Gregory Vishnepolsky presented (October 21, 2017) a detailed explanation of the Android Remote Code Execution vulnerabilities related to the BlueBorne attack vector at the Hacktivity conference. This presentation included new information regarding the vulnerability, as well as the exploit code itself. This white paper will elaborate upon the Android RCE vulnerability and its exploitation, which are part of the BlueBorne attack vector, revealed in September 2017. BlueBorne is an attack vector by which ​ ​ hackers can leverage Bluetooth connections to penetrate and take complete control over targeted devices. Armis has identified 8 vulnerabilities related to this attack vector, affecting four operating systems, including Windows, iOS, Linux, and Android. Following Armis discoveries, Google has issued a patch to its Bluetooth stack in Android’s codebase (AOSP). This post contains additional details that were not included in the Blueborne whitepaper and unveils the exploit source code. To fully understand the ​ ​ underlying facilities that allow exploitation of the Android vulnerabilities, it is strongly suggested to read the full technical whitepaper, especially the following sections: Demystifying Discoverability, SMP, SDP and BNEP. Future publications will explore in detail the BlueBorne vulnerabilities on Linux and the “Bluetooth Pineapple” attack which affects both Android & Windows devices.
    [Show full text]
  • Symbianos by Himal Humagain Fall.Ppt
    2 Overview In this chapter we’ll present a brief overview of the different parts of Symbian OS we’re going to talk about in this book. Detailed explanations of how things work will be left to the individual technology chapters, but here we’ll take a quick look at what each area does. First we have something of an aside, but on an important topic – that of binary compatibility (BC). Symbian OS v9.0 introduced a major BC break with versions 8.1 and earlier, due to the introduction of a new (standardized) application binary interface (ABI). Therefore applications compiled against v8.1 and earlier of Symbian OS will not run on v9.1 and later. In addition to this, the platform security model requires some changes to applications using communications functionality. Depending on the application this might be as simple as adding a CAPABILITY statement to the MMP file. To start with we take a quick look at a very high-level model of how a Symbian OS-based phone is constructed in order to see where various components fit in. This isn’t to say every phone looks like this, but it is a good enough model to help understand the different layers that exist within Symbian OS. The signalling stack (also referred to as the ‘baseband’ or ‘cellular modem’) is provided by the manufacturer of the device, so Symbian OS contains a series of adaptation layers to allow standard Symbian OS APIs to be adapted to the specific signalling stack in use. Today, all shipping products use either a 2.5G GSM/GPRS or 3G UMTS (aka W-CDMA, aka 3GSM) signalling stack.
    [Show full text]
  • Application Development for Bluetooth Embedded Systems
    Application Development for Bluetooth Embedded Systems Abu Ahmed Sayeem Reaz, Rajibul Alam, Bakhtiar Kamal and Fakhrul Alam Depparfment of Computer Science and Engineering, North South Univevsiiy 12 Kemal Ataturk Avenue, Banaei, Dhaka-1213, Bangladesh [email protected], [email protected], [email protected], [email protected] Abstract Bluetooth is steadily gaining popularity as time progresses, the importance of application development Blirctooth is a wireless technology thal enables a of Bluetooth is becoming apparent [3]. In this paper an wireless device to communicate in the 2.4 GHz application for Bluetooth embedded system is Industrial. Sccicntijic and Medical (ISM band It has developed while addressing some core requirements been specificully designed as a low cost. low power of software engineering processes. The developed radio technology. which is particularly suited jbr the application intends to create a smart billboard that short rung Personal Area Network (PAN) utilizes the individualism of consumer behavior. The application. In this paper we develop an application essential parts of the development includes the for a Bluetooth system thut will help create a smart Graphical User Interface (GUI) based application that billboard [ha{ utilizes [he individualism of consumer runs on the mobile devices and the application behavior. The essential parts of ihe development equipped with advertisement presentation and includes the Graphical User Interface (GUI) based information exchange capability that reside in the application that runs OH ihe mobile devices and the network. The communication between the two major application equipped wiah advertisement presentation components of the system is based on Bluetooth. The and informarion exchange capability. The Client Application is targeted to run on a Bluetooth communication between the two major components of enabled mobile device, e.g.
    [Show full text]
  • QNX SDK for Bluetooth Connectivity
    PRODUCT BRIEF QNX SDK for Bluetooth Connectivity The advancements in Bluetooth technology over the years have led to explosive growth in Bluetooth and Bluetooth Low Energy devices in a wide range of general embedded markets including medical, industrial, consumer electronics, and automotive. With the surge in numbers of Bluetooth Low Energy (BLE) devices of late, many embedded systems will need to be capable of communicating with both these low energy peripherals as well as traditional Bluetooth devices, over a range of different profiles. The QNX® SDK for Bluetooth® Connectivity, is a reliable and Proven and certified intellectual property (IP), compliant with flexible software offering compliant with the Bluetooth Core latest Bluetooth specification helps guarantee interoperability Specification version 4.2, supporting a broad set of profiles and The QNX SDK for Bluetooth Connectivity is compliant to the latest services. In addition, the SDK includes an optional IEEE 11073 version of the Bluetooth Core Specification, version 4.2. Deploying Personal Health Data (PHD) stack to enable easy interoperability a system with IP that maintains lock-step with the latest adopted with a variety of personal health devices such as pulse oximeters standard helps guarantee maximum interoperability with existing and weight scales, for medical applications. in-field devices. A system built with a 4.2 compliant stack will be compatible with other 4.2 Bluetooth-enabled devices, in addition A flexible Bluetooth Smart Ready® stack – to legacy devices. comprehensive offering, no vendor lock-in Developers are faced with many considerations in selecting Mindtree’s Bluetooth IP, at the heart of the QNX SDK for Bluetooth a Bluetooth host stack for their embedded platforms.
    [Show full text]
  • LBM: a Security Framework for Peripherals Within the Linux Kernel
    LBM: A Security Framework for Peripherals within the Linux Kernel Dave (Jing) Tian∗, Grant Hernandez∗, Joseph I. Choi∗, Vanessa Frost∗, Peter C. Johnsony, Kevin R. B. Butler∗ ∗University of Florida {daveti, grant.hernandez, choijoseph007, vfrost, butler}@ufl.edu yMiddlebury College [email protected] Abstract—Modern computer peripherals are diverse in their However, with this virtually unconstrained functionality capabilities and functionality, ranging from keyboards and print- comes the threat of malicious devices that can compromise ers to smartphones and external GPUs. In recent years, periph- computer systems in myriad ways. The BadUSB attack [62] erals increasingly connect over a small number of standardized communication protocols, including USB, Bluetooth, and NFC. allows attackers to add functionality allowed by the USB pro- The host operating system is responsible for managing these tocol to device firmware with malicious intent. For example, devices; however, malicious peripherals can request additional a BadUSB flash drive presents not only expected behavior functionality from the OS resulting in system compromise, or of a storage device when plugged into a computer, but also can craft data packets to exploit vulnerabilities within OS registers keyboard functionality to allow it to inject malicious software stacks. Defenses against malicious peripherals to date only partially cover the peripheral attack surface and are limited keystrokes with the aim of gaining administrative privilege. to specific protocols (e.g., USB). In this paper, we propose Other examples of malicious USB functionality include charg- Linux (e)BPF Modules (LBM), a general security framework ers that can inject malware into iOS devices [51], or take that provides a unified API for enforcing protection against control of Android devices via AT commands [78].
    [Show full text]
  • Ultro Mini Bluetooth Keyboord with Bocklit
    Ultro Mini Bluetooth Keyboord With Bocklit User'S if,onuol Contents 1. Safety Precautions Satety Matte6 Plea* Bfer to allsfety pre€utions @vered in this usr mnual 1. Safety 2 to prevent injury or damge. 2. lntroduction 3 This pDduc{ @ntahs a rechargeable lithiuGion battery. All sfety 3. Hardware Setup 4 pre€utions should be taken into @nsileEtbn when handling or 4. Software Setup 5 opeEting any type of devi@ that b poweEd by a battery sucfi as this prcduct. Do not dDp, heat, wsh & subrerge this prcduct in Microsoft Windows Mobile os 5 water. Do not opeEte this device in extrere humility, heat or @ld Google Android OS -- 7 envircnrents for long periods of tire. Mbus of this device my @us injury and will voil the devie's wamnty. Symbian OS 7 Windows OS (lVT Bluetooth Stack) -.--- g Atterfion to traffc saftty Windows OS (Broadcom Bluetooth Stack) 8 Do not opemte or attempt to opeEte this device while --- drMng or opeEting any rcving vehide. Linux (Ubuntu) 8 5. Technical parameters I Aircraft Sahty 6. Maintenance 9 Please do nol opeEte or attempt to opeEte thb device while on board an aircEft. that my €u* interferen@ 7- Productoverview 10 with the aimfts opeEtions and @mmni@tions devices Combustible Agents and Chemicals Pl6e tum the device off while around fuel c any @mbustible agents or chemicals. Turn off this dryie in the hospital Please do not optrate q attsrpt io optrate This device in a hospital. Doing s my @us interferene with redftll opeEtions and @mmnications devi@s. As all wireles devices, this prcduc't my interfere with implanted @rdiac pa@mke6, hearing aids and other Medi@l implant devi@s.
    [Show full text]
  • July/August 2021
    July/August 2021 A Straight Path to the FreeBSD Desktop Human Interface Device (HID) Support in FreeBSD 13 The Panfrost Driver Updating FreeBSD from Git ® J O U R N A L LETTER E d i t o r i a l B o a r d from the Foundation John Baldwin FreeBSD Developer and Chair of ne of the myths surrounding FreeBSD is that it • FreeBSD Journal Editorial Board. is only useful in server environments or as the Justin Gibbs Founder of the FreeBSD Foundation, • President of the FreeBSD Foundation, foundation for appliances. The truth is FreeBSD and a Software Engineer at Facebook. O is also a desktop operating system. FreeBSD’s base sys- Daichi Goto Director at BSD Consulting Inc. tem and packages include device drivers for modern • (Tokyo). graphics adapters and input devices. Consistent with Tom Jones FreeBSD Developer, Internet Engineer FreeBSD’s role as a toolkit, FreeBSD supports a variety • and Researcher at the University of Aberdeen. of graphical interfaces ranging from minimalist window managers to full-featured desktop environments. The Dru Lavigne Author of BSD Hacks and • The Best of FreeBSD Basics. first article in this issue walks through several of these Michael W Lucas Author of more than 40 books including options explaining how users can tailor their desktop • Absolute FreeBSD, the FreeBSD to their needs. It also provides pointers to downstream Mastery series, and git commit murder. projects which build an integrated desktop system on Ed Maste Senior Director of Technology, top of FreeBSD. The next two articles dig into the details • FreeBSD Foundation and Member of the FreeBSD Core Team.
    [Show full text]
  • Ndnblue: NDN Over Bluetooth
    NDN, Technical Report NDN-0015, 2013. http://named-data.net/techreports.html Revision 1: November 7, 2013 NDNBlue: NDN over Bluetooth Arjun Attam∗, Ilya Moiseenkoy ∗Indian Institute of Technology, Delhi. [email protected] yUniversity of California, Los Angeles. [email protected] Abstract—Named Data Networking is a network protocol that III. CONFIGURATION in future is able to displace IP protocol from its current role of a dominating inter-networking layer and also to have an edge in The process of establishing a Bluetooth connection to run such areas of networking as PAN (Personal Area Networking) NDN is initiated by devices finding other physically proximate where IP protocol has never been universally used. This project Bluetooth enabled devices. The user needs to decide between looks into the problem of fitting Named Data Networking request- response communication model into constrained Bluetooth net- an incoming connection (server) or an outgoing connection working stack for both mobile and desktop platforms. We provide (client.) a cross platform proxy layer, which works between NDN stack and Bluetooth stack to achieve NDN connectivity over Bluetooth A. Discovering Devices links for multiple platforms. Index Terms—Information-centric networks, named-data net- NDNBlue for Android can discover nearby Bluetooth de- working, bluetooth, device-to-device communication vices to identify the server device for outgoing connections. The process requires that the server be set as discoverable by I. INTRODUCTION other Bluetooth devices. NDNBlue is an endeavor to extend the scope of NDN ap- plications with Bluetooth. The present CCNx software router B. Security caveats [1] implementation for Named Data Networking works with TCP and UDP tunnels and also can be extended with NDNLP It is recommended that the devices should be authenticated [2] — a link level protocol for Ethernet.
    [Show full text]