Lines Matching refs:accessory
33 <li><a href="#determine-adk">Determine the connected device's accessory mode
36 <li><a href="#start-adk">Attempt to start the device in accessory mode</a></li>
52 …<li><a href="{@docRoot}guide/topics/connectivity/usb/accessory.html">USB Accessory Dev Guide</a></…
60 prototyping platform</a>. The accessory's hardware design files, code that implements the
61 accessory's firmware, and the Android application that interacts with the accessory are provided
81 to develop accessories that support the Android accessory protocol. For more information, see
115 Android USB accessory. The ADK board provides input and output pins that you can implement
137 runs on the ADK board and is written in C++. The sketch calls the Android accessory protocol
142 <li>The Android accessory protocol library, which is located in the
144 enumerate the bus, find a connected Android-powered device that supports accessory mode, and
307 2.3.4 devices that support accessory mode. This library is also forward compatible with Android
308 3.1 or newer devices that support accessory mode. If you only care about Android 3.1 or newer
310 …see the <a href="{@docRoot}guide/topics/connectivity/usb/accessory.html#choosing">USB Accessory</a>
334 power cable to the accessory is plugged in or that the micro-USB port on the accessory is
337 DemoKit application to connect to the accessory. If the prompt does not show up, connect and
338 reconnect the accessory.</li>
349 your own accessory. The files in the <code>arduino_libs/AndroidAccessory</code>
351 Android-powered devices that support accessory mode. Feel free to add debug statements (Arduino
360 your own accessory.</p>
367 reading through how the hardware detects and interacts with devices in accessory mode is still
376 includes most of the logic that will help you implement your own accessory's firmware. It might
381 <a href="#accessory-protocol">Implementing the Android Accessory Protocol</a>.</p>
408 //set the accessory to its default state
414 <h3 id="determine-adk">Determine the connected device's accessory mode support</h3>
416 <p>When a device is connected to the ADK board, it can already be in accessory mode, support
417 accessory mode and is not in that mode, or does not support accessory mode. The
421 device descriptor to figure out if the device is already in accessory mode by calling
423 of the device descriptor. A device in accessory mode has a vendor ID of 0x18D1 and a product ID
424 of 0x2D00 or 0x2D01. If the device is in accessory mode, then the ADK board can <a href=
426 "#start">attempts to start the device in accessory mode</a>.</p>
449 Serial.print("found android accessory device\n");
464 <h3 id="start-adk">Attempt to start the device in accessory mode</h3>
466 <p>If the device is not already in accessory mode, then the ADK board must determine whether or
467 not it supports it by sending control request 51 to check the version of the USB accessory
474 information, and tries to start the device in accessory mode with control request 53. The
499 successful, the device displays itself on the USB bus as being in accessory mode when the ADK board
500 re-enumerates the bus. When the device is in accessory mode, the accessory then <a href=
505 <p>If a device is detected as being in accessory mode, the accessory must find the proper bulk
507 device in accessory mode, it calls the <code>AndroidAccessory::configureAndroid()</code>
583 <p class="note"><strong>Note:</strong> An Android-powered device in accessory mode can
588 to find the appropriate endpoints for your accessory might be different.</p>
642 Serial.println("can't find accessory endpoints");
653 with your USB accessory. Setting this status prevents the device from being re-detected and
698 changes the state of the accessory, such as lighting up or changing the color of the LED