pic and android ...

[jeanninemtv]

hello,

i want to know if anybody already tried microcontroller interfacing with android using the accesory framework for android ? ...
I'm buying 'brick by brick' all the necessary to work (not the official development board but something diy ...


look for example the microchip sample and not-so-cheap-in-europe board ...(aprox 150E from farnell and even from microxip ...)  anyway i'll try using the provided data ....

http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en553673

[Parmin]

You are right, the microchip development board is very expensive for what it provides.

On the other hand, have you ever try to write to Microchip?
tell them that you are s student, provide them with your student ID., and ask them for a discount.
Microchip is a fairly decent company, and they seems to be willing to work things out with their users.

[SuperDrive]

US$ 79.9 both at Digikey and Microchip Direct, note that it includes Pickit3.

[jeanninemtv]

sound a good offer, because my reference was farnell.fr and they spit me with >150E (transport usa, shipping and whatever ).  ah! and no pickit included

[SuperDrive]

I have one, playing with it a little - just trying the demo.

Works with HTC Wildfire S, doesn't work with Samsung Galaxy Y.

Edit: I meant Galaxy Pocket, haven't tried the Y.

[bigtoy]

I realise you were asking about PIC, but this might be another Android interfacing option for you. FTDI has a chip and example software for interfacing to Android:

http://www.ftdichip.com/Android.htm

[jeanninemtv]

seems to be a good usb otg option...

btw, in the android side, how can i do an osciloscope like interface?  is there something faster (and free ^^) than bmp methods?

[violentic]

Hi! I was working in a project that needs to connect a pic to an android phone but i have by now this development stopped.
I have seen that "android accessory dev kit" but this was useless for me because the android version that I need to communicate with is 2.2 (froyo). The "accessory" option in android is available only from 2.3 and above; such as FTDI that requires 3.1 and above.

There are some implementations that can give you an ADB connection in android versions 1.5 (or 1.6) and above! I cannot test this by now (because I need to translate them to PIC32). They are:

IOIO:
https://www.sparkfun.com/products/10748
https://github.com/ytai/ioio/wiki

Microbridge (there are versions for AVR and PIC24F):
http://code.google.com/p/microbridge/
http://code.google.com/p/microbridge-pic/ << I have downloaded the code before they removed it temporally from the page, ask if you need it.

When I have time to port some of this ones to PIC32, I will post this here, but by the time I am with another project :S

[jeanninemtv]

hello again,
finally i found some spare components to test (because they were free ^^ )  so i get a pic24FJ64Gb002 and a pickit3

i downloaded the mplabX demo project from microchips and the apk to install on my nexus S.

In fact , i can see that mplabX configs are like a nightmare ...

I havenn't found the configs for my device so i did it by myself.  then a lot of file path on the includes appeared,  i wrote each path correctly and it compiled,  but ...
aparently the board hangs on the usb port ( my cellphone recognise a usb device plugged into it) but nothing more happen !!!

what could be causing this mess???
(i haven't change the ids or names of the board on the demo)
i'll upload my folder later.


thanks in advance

[Ichan]

What apk is that?

I download Android Basic Accessories demo from Google Play Store using Galaxy Notes, the demo board is run just out of the box.

-ichan

[jeanninemtv]

exactly the same apk you mentioned,
i plug the cable to my nexus S (with android 4X version) and it detects a device but the app doesnt recognize anything  ...  i'll re compile and check all my includes again ... btw is kinda difficult to make it work without warnings about 'file not detected' even when i put manually the full path with #include ....

[jeanninemtv]

hi again,

i solved the #includes problem.  the solution is on the project properties in the compilers options ... i had to indicate the folders that XC16 need...  and include with the source code some usbhost.c and androidv1.c and .h, then the main c compiled quickly

but the main problem now concerns the android OS ( aka jellybean ),  because microshit updated they framework up to 3.2x version ( "+" ) in august but for example my googlephone updated itself automatically to 4.1 version, reading two posts on microchip forum i changed the 1 to 2 inn the version indicators, and the board is recognised by my cellphone, and the demo app downloaded from the web says "device connected",

buuuut ... no led turn on or off with i press a screen button... i did a test to check if some data came into the pic by turning on a led after the device recognition event (i mean when you press any button on the screen's demo apk)  and it responses!!  but no explicit command recognition...

any suggestion???

[TucoRamirez]

recompile the source of the adk after installing the latest adk packages in eclipse. 

after that it must work ...

[Ichan]

I use the demo board with stock hex - PIC24FJ256GB110 on it. Perhaps you have to compare your schematic to the original demo board.

Trying another android device will be good, not all device has "Accessories Library" included - there is compatible device list on microchip website.

-ichan