No. No it is not. Is there any way to add OpenAccessory support?
Thank you very much for your help thus far.
On Tuesday, March 31, 2015 at 12:20:10 AM UTC-4, Ytai wrote:
Are you sure your phone supports OpenAccessory? Is it on the supported
devices page?
The lack of AOA support (if that is indeed the problem you're facing) is
either a hardware or a software limitation of the device you're using. If
you have a different Android device, you can check if the IOIO works with
it in order to verify that the rest of the setup is good.
On Tue, Mar 31,
*UPDATE*: I have found the problem related to the non responsive calls of
twi.readWrite() with my custom firmware (V3.x), this was due to some
modifications we did in the i2c.c file commenting all calls of rx_queue.
After uncommenting these lines, the Andrdoid App received the read
acknowledge
You write a piece of software that uses the IOIO API for reading the
samples, as in:
https://github.com/ytai/ioio/wiki/Analog-Input
You probably want the buffered version.
On the hardware side of things, this can be as simple as connecting your
probes between GND and the analog pin, or could get
When you say assert, do you mean assert high or assert low?
On Tuesday, March 31, 2015 at 2:36:24 PM UTC-7, Ytai wrote:
The IOIO decides whether it should be host or device based on whether the
USBID pin is pulled low (host) or left floating (device). On the standard
IOIO board this pin
I got the boot loader flashed and am able to run the blink app...but having
trouble with the Android charging circuit.
Is there a detailed description of the Android charging circuit including
the operation of Q1, Q2 and the VBUS and HOST pins of the PIC? My new
circuit implementation does
