Datasheet

Description

Per instance client driver for Android device. Called by USB host stack from the client driver table.

Remarks

This is a internal API only. This should not be called by anything other than the USB host stack via the client driver table

Preconditions

None

Parameters

Parameters Description

BYTE address the address of the device that is being initialized

DWORD flags the initialization flags for the device

BYTE clientDriverID the clientDriverID for the device

Return Values

Return Values Description

TRUE initialized successfully

FALSE does not support this device

Function

BOOL AndroidAppInitialize( BYTE address, DWORD flags, BYTE clientDriverID )

5.5 Events

Macros

Name Description

EVENT_ANDROID_ATTACH ( see page 33) This event is thrown when an Android device is

attached and successfully entered into accessory

mode already. The data portion of this event is the

handle that is required to communicate to the device

and should be saved so that it can be passed to all of

the transfer functions. Always use this definition in

the code and never put a static value as the value of

this event may change based on various build

options.

EVENT_ANDROID_DETACH ( see page 33) This event is thrown when an Android device is

removed. The data portion of the event is the handle

of the device that has been removed. Always use

this definition in the code and never put a static value

as the value of this event may change based on

various build options.

EVENT_ANDROID_HID_REGISTRATION_COMPLETE

( see page 33)

This event is thrown after a HID report is successfully

registered. That report is now available for use by the

application

EVENT_ANDROID_HID_SEND_EVENT_COMPLETE

( see page 33)

The requested report has been sent to the requested

device.

Microchip's Accessory Framework for Android(tm) 32