Shop OBEX P1 Docs P2 Docs Learn Events
USB Connection issue -Linux — Parallax Forums

USB Connection issue -Linux

joethumphreyjoethumphrey Posts: 25
edited 2010-12-08 07:37 in Propeller 1
Hello all,

I'm having what seems to be a simple problem. I can't connect to a prop-demo board with usb using a Linux distribution running BST.

Dmesg shows:
console [tty0] enabled
tty_check_change: tty->pgrp == NULL!
usb 6-2: FTDI USB Serial Device converter now attached to ttyUSB0
ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
usb 6-2: FTDI USB Serial Device converter now attached to ttyUSB0

lsusb provides:
Bus 006 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC

lsmod shows :
ftdi_sio 35305 0
usbserial 33093 1 ftdi_sio

Typing the /dev/ttyUSB0 into the BST connection manager give the " No propeller found" error.

"cat /dev/ttyUSB0" gives no return.

Any pointers would be helpful. Thanks,Joe.

Comments

  • icepuckicepuck Posts: 466
    edited 2010-12-01 12:21
    Since you are getting a response back from the ftdi chip goes to show you are at least making it that far. The ftdi chip is powered from the usb port and does not power any thing else.
    Are you running your board from batteries or a power supply?
    Use a voltmeter to check your power source.
    If all else fails use a windows computer to see if it works at all.
    -dan
  • joethumphreyjoethumphrey Posts: 25
    edited 2010-12-01 12:50
    Thanks Dan.

    Just as a note, I'm getting video output from the board plus the p16-p23 lights power on after boot up on the board.

    The video looks like some onscreen buttons.

    WOOF and MEOW?
  • joethumphreyjoethumphrey Posts: 25
    edited 2010-12-02 06:45
    It connects fine with windows.

    There is something with the FTDI chip driver then.

    The linux box sees it, but the nothing seems to be able to talk to the serial line.

    What has everyone else used in this instance?Driver wise/connection setup?
  • LoopyBytelooseLoopyByteloose Posts: 12,537
    edited 2010-12-03 01:47
    Ubuntu Linux works fine with FTDI provided drivers that are included in the Ubuntu distribution. It could be that your distribution of Linux is using older, out-dated FTDI drivers or that how the FTDI driver is interfaced into the Linux is not quite right.

    In sum, you may have to update and patch your particular version of Linux OR you may have to shift to a distribution that keeps up to date. I checked out www.distrowatch.com for a distribution of Linux that keeps regularly up todate before trying to use it for programming micro-controllers...

    You might take a look at what kernel and how Ubuntu is doing things as an example of what needs to be corrected. FTDI may help you with recommendations about Linux installation.
  • avsa242avsa242 Posts: 456
    edited 2010-12-03 13:29
    joethumphrey,

    One thing you might want to check is the permissions on the /dev/ttyUSB0 device node. If you don't have permission, bst doesn't error out as such; it simply states it couldn't find a propeller.

    Cheers,
    Jesse
  • max72max72 Posts: 1,155
    edited 2010-12-03 22:19
    If I remember correctly older versions of Ubuntu had an issue with the FTDI. Probably is cited in BST's discussion.
    As a test grab a live current ubuntu, run it from USB, and test if it works..
  • max72max72 Posts: 1,155
    edited 2010-12-03 22:31
  • joethumphreyjoethumphrey Posts: 25
    edited 2010-12-08 07:37
    Yea that pointed to more checking.

    And my user was not part of the dialout group.

    Added that, no change. Ran as root before so I wasn't imagining that would make a difference.

    Any other thoughts?

    I see the port ../ttyUSB0 being added just unusable by bst.

    EDIT:

    OK got it. Forgot to logout/in after group add. In business now. Thanks everyone.

    So as an answer, if you are seeing the port being added but it inaccessible, run
    ls -la /dev/ttyU*

    Add you that group list in the return to your user you want to run BST with.
    crw-rw---- 1 root dialout 188, 0 2010-02-10 15:05 /dev/ttyUSB0

    Bolded "dialout" was my group. Yours may be different but that location in the return is the group owner of that port.

    And don't forget to reboot or logout/in.
Sign In or Register to comment.