PROTOTYPE PREVIEW: FT311D Android Open Accessory IC breakout board

in Prototypes, releases by DP | 17 comments

FTDI announced the FT311D Android Open Accessory IC last week and we designed a breakout board for it. The 7 GPIO pins are broken out, and it has everything necessary for the IC to function. Stuff like:

  • 2 Power supplies: 3.3V for the IC, 5V for the VBUS line
  • Quartz crystal oscillator for stable USB operation
  • Decoupling capacitors, and a choke for noise suppression

Prototype boards will go out soon with any updates. If you have any suggestions please leave a comment below.

This entry was posted in Prototypes, releases and tagged , .

Comments

  1. Mats says:

    Last week…. Hmmm…. So this can’t be the “secret project” that you’ve been blogging about for the last month or so. Dammit! Tell us already! I want to know what it is. Now. :-)

  2. Zach says:

    Ever since you posted about this chip, I have been dying to get my hands on a dev board! I hope you can beat the price of the official FTDI dev board. This thing has a million possibilities!

  3. ken says:

    How is the FTDI better than the PIC32 that’s used for Google’s IOIO board?

    • Gamin Inganela says:

      I too am curious about the differences of this implementation versus IOIO (as an example).
      Apart from one, for me, being the simplicity in the FTDI case of a tiny part interfaced to UART of a microcontroller on one side and to the Android on the other.

      Thanks for bringing this board out (although the FTDI website says supplies of the IC are still not available!)

    • MrCruz says:

      Well, for one you don’t have to rewrite and reprogram software for the PIC by using this IC. You can just select certain signals to select the interface you want.

      It’s a complexity-vs-flexibility issue. Not everyone can reprogram the PIC, but everyone is able to use SPI or UART. If you already prefer the PIC, then by all means the IOIO is perfect for you!

      Also wanted to point out this project. It’s a USB Host shield that’s been able to talk w/ Android for months now. http://www.circuitsathome.com/

  4. Destate9 says:

    Nice board! Kind of related question though, when you made the top plane, did you turn off orphans? I tried to use orphans in a recent design and it made really annoyingly akward orphans inbetween parrallel traces. I noticed your traces from C1 and C2 are running next to each other with a reletively large space between them, yet they are looking spiffy as hell. Is there a way to increase the minimum size of orphans or something?

    • Mats says:

      Destate9: I don’t know of any way of setting the minimum size of orphans. But an almost acceptable method of getting rid of disturbing slivers and “warts” is to draw a polygon of tRestrict (or bRestrict) over the offending parts. This should of course only be done after you’ve finished the routing…

    • vimark says:

      Thanks Destate9, the orphans option were (off) default state when I routed the board. You could play with the polygon’s width to adjust the size of the orphans. In this board the polygon width is set to 12mil.

  5. Garrett Galloway says:

    OH NO! Rounded corners! I hope apple doesn’t come after this…

  6. mitek says:

    One magic word “Android” and all wants it. All who wnats connect android can make it with VNC2 two years ago.

  7. Jacob B says:

    What about adding a connection point somewhere so that the 3.3V voltage regulator could be used if you wanted to run a second IC or sensor without needing another power supply.
    Having the power and usb jacks on the same side would make building this into a project much easier.

Leave a Comment

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Notify me of followup comments via e-mail. You can also subscribe without commenting.