Microchip's Accessory Framework for Android(tm)
48
some other reason. Please see the Requirements, Limitations, and Potential Issues ( see page 11) section for other known
issues or limitations.
? Workaround: Since the Read() request never completes resulting in locked resources, a workaround can be implemented
in the application layer. If the accessory and the application implement a command for the application to indicate to the
accessory that the app is closing (or is being paused), then the accessory can respond back with an acknowledge packet.
When the app receives this ACK packet, it knows not to start a new read() (since that read() request will not be able to
terminated once started).
8.6 Why don't all of the features of the demo
work?
The demo application on the Android device was written with the assumption that there were 8 LEDs, 4 push buttons, and a
potentiometer available on the accessory. Not all of these features are available on the supported hardware platforms.
Where these features are not available, these functions do not work.
The Explorer 16 board is an even more complex situation. Even though the base board does include these features, some
processor modules don't have all of these features routed to the processor. Also on some processor modules the features
are routed to the same pin as other features so both can't be used easily in the same demo.
8.7 What if I need more support than what is
here?
There are several options that you can use to get various kinds of help.
? You can try our forums at forum.microchip.com . The answers provided here will be by fellow developers and typically not
from Microchip employees. The forum often provides a way to get answers very quickly to questions that might take
longer for other support routes to answer.
? You can contact your local sales office for support. You can find the local office from www.microchip.com/sales . The local
sales team should be able to direct you to a local support team that can help address some issues.
? You can submit support requests to our support system at support.microchip.com or search through the existing hot
topics.
? You can also contact androidsupport@microchip.com for support.
8.8 Why doesn't my phone work? -or- Does this
phone work?
The OpenAccessory interface was added to the Android OS in versions 2.3.4 and 3.1 of the Android OS. Version 2.3.3 and
earlier devices will not work as well as version 3.0 devices.
The OpenAccessory interface library is also an option library. An Android device manufacturer is not required to include this
library in their device. As a result, not all devices with a capable version of the OS actually have the library. It is up to the
discretion of the manufacturer of the device. Support for this library may also change with an update from the manufacturer
48
8
相关PDF资料
DM300004-2 BOARD DEMO DSPICDEM.NET 2
DM300014 BOARD DEMO DSPICDEM 1.1 GEN PURP
DM300016 BOARD DEMO DSPICDEM STARTER
DM300017 BOARD DEMO DSPICDEM STARTER
DM300020 BOARD DEV DSPICDEM MC1 MOTORCTRL
DM300021 MODULE PWR DSPICDEM MC1H HV 3PHS
DM300022 MODULE PWR DSPICDEM MC1L LV 3PHS
DM320002 BOARD EXPANSION PIC32 I/O
相关代理商/技术参数
DM2410-0AL1 制造商:未知厂家 制造商全称:未知厂家 功能描述:Optoelectronic
DM2410-0BL1 制造商:未知厂家 制造商全称:未知厂家 功能描述:Optoelectronic
DM2410-0CL1 制造商:未知厂家 制造商全称:未知厂家 功能描述:Optoelectronic
DM2410-0DL1 制造商:未知厂家 制造商全称:未知厂家 功能描述:Optoelectronic
DM2410-0GL1 制造商:未知厂家 制造商全称:未知厂家 功能描述:Optoelectronic
DM2410-0HL1 制造商:未知厂家 制造商全称:未知厂家 功能描述:Optoelectronic
DM2410-0SL1 制造商:未知厂家 制造商全称:未知厂家 功能描述:Optoelectronic
DM2410-1AL1 制造商:未知厂家 制造商全称:未知厂家 功能描述:Optoelectronic