Automation Of Bluetooth Firmware Validation

Abstract

Wireless ad hoc networks are rapidly developing into an area of intense research. Prior to taking full advantage of the benefits offered by such networks, meaningful applications have to be devised in order to prove the suitability of the backbone technologies to real - life situations and developed mainly as a cable replaced device. Bluetooth is a well-known, short-range technology for Wireless Personal Area networks (WPAN) that allows virtually any digital device telecommunications, personal computing, networking automotive, and consumer electronic to communicate without wrestling with numerous cords or cables Bluetooth wireless technology is set to revolutionize the way communicate and how to connect device. Cables become a thing of the past thanks to the robust, low-cost Bluetooth chips.

Bluetooth SIG is to make wireless connections easy and simple to use. To ensure the best possible customer Bluetooth experience as well as interoperability with other Bluetooth devices, the Bluetooth SIG is developed a logo program, which validates compliance with the published Bluetooth speciation as well as interoperability with other Bluetooth devices. Bluetooth devices that successfully complete the Bluetooth testing criteria have the right to bear the official Bluetooth logo. In this thesis discus about testing of that Bluetooth device is important thing in Research and development department. Moreover testing person is required and he is able to do all testing. In place of reliable on tester ability, it should be done automatically all the testing. Also representing checking quality of receiving audio data when Voice data transmit on Bluetooth is one of the major parts of Bluetooth verification. Mean Opinion Score (MOS) is the parameter for checking quality of audio data. If MOS score value is less than 4 then it is not acceptable. Ellisys is the one more software for taking Air and sniffer log. Automation for taking log is required when Bluetooth is under testing. Device may request for increase or decrease of the other device transmits power level by measuring its Receiver Signal Strength Indicator (RSSI). If device support Legancy Power Control (LPC) then it directly increase to maximum or decrease to minimum power, where as in Enhance Power Control (EPC) it increase or decrease step by step. So, it will not reach to maximum power or minimum power. The audio data transferred over the SCO channel can be provided via the normal Host Controller Interface (HCI) hardware driver and physical bus (UART, USB) or via a PCM back-channel. In case of a desktop computer, the HCI will be used. In case of an embedded device (for example a mobile phone), the SCO channel will be directly connected via a PCM interface to the main audio codec. For testing of Audio Data coming from HOST (SCO over HCI), Audio data should be in Packet format at HOST.