Project

General

Profile

Actions

Feature #3419

closed

usbftdi needs to support the BeagleBone

Added by Hans Rosenfeld over 10 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Category:
-
Start date:
2012-12-16
Due date:
% Done:

100%

Estimated time:
Difficulty:
Bite-size
Tags:
Gerrit CR:
External Bug:

Description

The BeagleBone is a small ARM evaluation board with an on-board FTDI2232C chip that provides a JTAG adapter on interface 0 and a serial console on interface 1. The JTAG adapter part is already handled correctly by usb_mid, but usbftdi doesn't currently attach to interface 1.

Usbftdi already supports the 2232C, but it doesn't know about it. The code where it checks the vendor/product IDs must be extended to include the 2232C.

Actions #1

Updated by Hans Rosenfeld over 10 years ago

  • % Done changed from 0 to 100

webrev: http://cr.illumos.org/~webrev/hans/illumos-3419-webrev/

While at it I also eliminated a TODO about the buffer sizes: instead of the minimal default of 64 bytes supported by all usbftdi devices, get the buffer sizes from the endpoints and use them for bulk transfers.

This fixes an issue that I saw when the BeagleBone would output text at the default speed of 115200. The driver would get a buffer overrun, and the cua device had to be closed and reopened to make it work again. Handling of errors like this seems to be missing from the driver and should be added eventually, but that would be a different bug.

Actions #2

Updated by Hans Rosenfeld over 10 years ago

I also tested this with the SheevaPlug JTAG adapter, the only other FTDI device I got. Works like a charm when dumping lots of text on the console at 115200.

Actions #3

Updated by Rich Lowe over 10 years ago

  • Status changed from New to Resolved
  • Tags deleted (needs-triage)

Resolved in 452fab4

Actions

Also available in: Atom PDF