Shop OBEX P1 Docs P2 Docs Learn Events
BST not detect propeller — Parallax Forums

BST not detect propeller

HisNameIsRobertPaulsonHisNameIsRobertPaulson Posts: 5
edited 2013-03-26 23:25 in General Discussion
I am currently running BST on LinuxMint. I cannot get BST to detect my propeller. After I get a message that says "Propeller not found", I get a choice to use a file path to find the port. I don't know where to go from here. Previously, I used the Propeller Tool on a Windows OS on the same computer and I was able to connect very easily.

Comments

  • SRLMSRLM Posts: 5,045
    edited 2013-03-26 01:40
    - Do you have the FTDI drivers installed?
    - What is the output of the following command: 
    ls /dev
    - What Propeller board are you using?
    - Does your Propeller have power?
  • HisNameIsRobertPaulsonHisNameIsRobertPaulson Posts: 5
    edited 2013-03-26 14:19
    I installed the drivers that were linked from the BST download page. I am using the propeller proffesional development board. The board has power.
    							alarm            loop-control        sda2      tty25  tty58      ttyS31
ashmem           mapper              sda5      tty26  tty59      ttyS4
autofs           mcelog              sdb       tty27  tty6       ttyS5
binder           mem                 sdb1      tty28  tty60      ttyS6
block            net                 sdb2      tty29  tty61      ttyS7
bsg              network_latency     sdb5      tty3   tty62      ttyS8
btrfs-control    network_throughput  sdb6      tty30  tty63      ttyS9
bus              null                sg0       tty31  tty7       uinput
cdrom            oldmem              sg1       tty32  tty8       urandom
cdrw             port                sg2       tty33  tty9       v4l
char             ppp                 shm       tty34  ttyprintk  vboxdrv
console          psaux               snapshot  tty35  ttyS0      vboxnetctl
core             ptmx                snd       tty36  ttyS1      vboxusb
cpu              pts                 sr0       tty37  ttyS10     vcs
cpu_dma_latency  ram0                stderr    tty38  ttyS11     vcs1
disk             ram1                stdin     tty39  ttyS12     vcs2
dri              ram10               stdout    tty4   ttyS13     vcs3
dvd              ram11               tty       tty40  ttyS14     vcs4
dvdrw            ram12               tty0      tty41  ttyS15     vcs5
ecryptfs         ram13               tty1      tty42  ttyS16     vcs6
fb0              ram14               tty10     tty43  ttyS17     vcs63
fd               ram15               tty11     tty44  ttyS18     vcs8
full             ram2                tty12     tty45  ttyS19     vcsa
fuse             ram3                tty13     tty46  ttyS2      vcsa1
hpet             ram4                tty14     tty47  ttyS20     vcsa2
input            ram5                tty15     tty48  ttyS21     vcsa3
kmsg             ram6                tty16     tty49  ttyS22     vcsa4
log              ram7                tty17     tty5   ttyS23     vcsa5
loop0            ram8                tty18     tty50  ttyS24     vcsa6
loop1            ram9                tty19     tty51  ttyS25     vcsa63
loop2            random              tty2      tty52  ttyS26     vcsa8
loop3            rfkill              tty20     tty53  ttyS27     vga_arbiter
loop4            rtc                 tty21     tty54  ttyS28     vhost-net
loop5            rtc0                tty22     tty55  ttyS29     video0
loop6            sda                 tty23     tty56  ttyS3      zero
loop7            sda1                tty24     tty57  ttyS30
  • SRLMSRLM Posts: 5,045
    edited 2013-03-26 16:18
    The output of "ls /dev" on my computer (Ubuntu) is: 
    autofs           fd       loop2               oldmem  ram5    sdf2      snd     tty19  tty34  tty5   tty8       ttyS21  ttyS9    vcs5
block            full     loop3               port    ram6    sdf5      sr0     tty2   tty35  tty50  tty9       ttyS22  [b]ttyUSB0[/b]  vcs6
bsg              fuse     loop4               ppp     ram7    sdg       stderr  tty20  tty36  tty51  ttyprintk  ttyS23  uinput   vcsa
btrfs-control    fw0      loop5               psaux   ram8    sdh       stdin   tty21  tty37  tty52  ttyS0      ttyS24  urandom  vcsa1
bus              hidraw0  loop6               ptmx    ram9    sdh1      stdout  tty22  tty38  tty53  ttyS1      ttyS25  usb      vcsa2
cdrom            hidraw1  loop7               pts     random  serial    tty     tty23  tty39  tty54  ttyS10     ttyS26  usbmon0  vcsa3
cdrw             hidraw2  loop-control        ram0    rfkill  sg0       tty0    tty24  tty4   tty55  ttyS11     ttyS27  usbmon1  vcsa4
char             hidraw3  mapper              ram1    rtc     sg1       tty1    tty25  tty40  tty56  ttyS12     ttyS28  usbmon2  vcsa5
console          hidraw4  mcelog              ram10   rtc0    sg2       tty10   tty26  tty41  tty57  ttyS13     ttyS29  usbmon3  vcsa6
core             hidraw5  mei                 ram11   sda     sg3       tty11   tty27  tty42  tty58  ttyS14     ttyS3   usbmon4  vga_arbiter
cpu              hidraw6  mem                 ram12   sdb     sg4       tty12   tty28  tty43  tty59  ttyS15     ttyS30  usbmon5  zero
cpu_dma_latency  hpet     net                 ram13   sdc     sg5       tty13   tty29  tty44  tty6   ttyS16     ttyS31  usbmon6
disk             input    network_latency     ram14   sdd     sg6       tty14   tty3   tty45  tty60  ttyS17     ttyS4   vcs
dvd              kmsg     network_throughput  ram15   sde     sg7       tty15   tty30  tty46  tty61  ttyS18     ttyS5   vcs1
dvdrw            log      null                ram2    sde1    sg8       tty16   tty31  tty47  tty62  ttyS19     ttyS6   vcs2
ecryptfs         loop0    nvidia0             ram3    sdf     shm       tty17   tty32  tty48  tty63  ttyS2      ttyS7   vcs3
fb0              loop1    nvidiactl           ram4    sdf1    snapshot  tty18   tty33  tty49  tty7   ttyS20     ttyS8   vcs4

    Notice the emphasis (mine) on ttyUSB0: that's where the FTDI chip is. If you don't have that, then it looks like an FTDI issue: most likely the drivers are not installed correctly. Here is the output of "lsusb" on my computer: 
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 0556:0001 Asahi Kasei Microsystems Co., Ltd AK5370 I/F A/D Converter
Bus 003 Device 003: ID 04f9:0039 Brother Industries, Ltd HL-5340 series
Bus 005 Device 002: ID 03f0:2514 Hewlett-Packard 
Bus 005 Device 003: ID 05f3:0081 PI Engineering, Inc. Kinesis Integrated Hub
Bus 001 Device 006: ID 11b0:6178 ATECH FLASH TECHNOLOGY 
Bus 002 Device 006: ID 046d:c06b Logitech, Inc. G700 Wireless Gaming Mouse
Bus 002 Device 004: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 005 Device 004: ID 046d:c531 Logitech, Inc. 
Bus 005 Device 005: ID 05f3:0007 PI Engineering, Inc. Kinesis Advantage PRO MPC/USB Keyboard
Bus 005 Device 006: ID 0488:0280 Cirque Corp. 
Bus 002 Device 008: ID 22b8:4061 Motorola PCS 
[b]Bus 002 Device 009: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC[/b]
  • frank freedmanfrank freedman Posts: 1,983
    edited 2013-03-26 19:51
    Shoulda done the ls /dev using ls -l /dev |grep SB and then check the ttyUSB0 permissions. Probably will find that the user needs to be also a member of the group dialout. Otherwise that user will not have permission to use that device.

    There are a couple of other possibilities to check as well, google may find them as it's been a while since I had to fight this issue.

    The following boards have worked for me with BST on FCxx through FC17:
    PEK on a breadboard w/ propplug
    GG USB platform (my main backup now)
    Quickstart (on indefinite loan to highschool kid)
    propC3


    Frank
  • SRLMSRLM Posts: 5,045
    edited 2013-03-26 20:01
    frank freedman wrote: »
    Shoulda done the ls /dev using ls -l /dev |grep SB and then check the ttyUSB0 permissions. Probably will find that the user needs to be also a member of the group dialout. Otherwise that user will not have permission to use that device.

    That might come later, but I don't even see the ttyUSBN port in his ls output, so I don't think that's the issue.
  • HisNameIsRobertPaulsonHisNameIsRobertPaulson Posts: 5
    edited 2013-03-26 22:29
    Sorry for the slow response... I reinstalled the driver and still no luck. However, ttyUSB0 now shows up when I run "ls / dev".
    alarm            mapper              sdb       tty27  tty60      ttyS7
ashmem           mcelog              sdb1      tty28  tty61      ttyS8
autofs           mem                 sdb2      tty29  tty62      ttyS9
binder           net                 sdb5      tty3   tty63      ttyUSB0
block            network_latency     sdb6      tty30  tty7       uinput
bsg              network_throughput  serial    tty31  tty8       urandom
btrfs-control    null                sg0       tty32  tty9       v4l
bus              oldmem              sg1       tty33  ttyprintk  vboxdrv
cdrom            port                sg2       tty34  ttyS0      vboxnetctl
cdrw             ppp                 shm       tty35  ttyS1      vboxusb
char             psaux               snapshot  tty36  ttyS10     vcs
console          ptmx                snd       tty37  ttyS11     vcs1
core             pts                 sr0       tty38  ttyS12     vcs2
cpu              ram0                stderr    tty39  ttyS13     vcs3
cpu_dma_latency  ram1                stdin     tty4   ttyS14     vcs4
disk             ram10               stdout    tty40  ttyS15     vcs5
dri              ram11               tty       tty41  ttyS16     vcs6
dvd              ram12               tty0      tty42  ttyS17     vcs63
dvdrw            ram13               tty1      tty43  ttyS18     vcs8
ecryptfs         ram14               tty10     tty44  ttyS19     vcsa
fb0              ram15               tty11     tty45  ttyS2      vcsa1
fd               ram2                tty12     tty46  ttyS20     vcsa2
full             ram3                tty13     tty47  ttyS21     vcsa3
fuse             ram4                tty14     tty48  ttyS22     vcsa4
hpet             ram5                tty15     tty49  ttyS23     vcsa5
input            ram6                tty16     tty5   ttyS24     vcsa6
kmsg             ram7                tty17     tty50  ttyS25     vcsa63
log              ram8                tty18     tty51  ttyS26     vcsa8
loop0            ram9                tty19     tty52  ttyS27     vga_arbiter
loop1            random              tty2      tty53  ttyS28     vhost-net
loop2            rfkill              tty20     tty54  ttyS29     video0
loop3            rtc                 tty21     tty55  ttyS3      zero
loop4            rtc0                tty22     tty56  ttyS30
loop5            sda                 tty23     tty57  ttyS31
loop6            sda1                tty24     tty58  ttyS4
loop7            sda2                tty25     tty59  ttyS5
loop-control     sda5                tty26     tty6   ttyS6

    When I run lsusb the following shows up.
    Bus 001 Device 002: ID 04f2:b1aa Chicony Electronics Co., Ltd Webcam-101
Bus 003 Device 002: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader
Bus 005 Device 022: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

    Frank mentioned that I should check the USB permissions. How should I do that? Thanks for your responses!
  • HisNameIsRobertPaulsonHisNameIsRobertPaulson Posts: 5
    edited 2013-03-26 22:32
    Also, I just ran "ls -l /dev |grep SB" and this is the result.
    crw-rw----  1 root dialout   188,   0 Mar 26 22:27 ttyUSB0
  • HisNameIsRobertPaulsonHisNameIsRobertPaulson Posts: 5
    edited 2013-03-26 22:46
    I think I got it! I logged in as root and changed the usb permissions to my username. BST found the propeller. The only problem now is that my touchpad moves the mouse extremely slow when the propeller is connected and turned on. Thanks guys!
  • SRLMSRLM Posts: 5,045
    edited 2013-03-26 23:25
    HisNameIsRobertPaulson wrote: »
    I think I got it! I logged in as root and changed the usb permissions to my username. BST found the propeller. The only problem now is that my touchpad moves the mouse extremely slow when the propeller is connected and turned on. Thanks guys!

    The FTDI chip should not make your mouse move slowly. Maybe try it on a different USB port? In any case, that sounds like a computer problem, not a Propeller issue.

    To add your user to dialout, use the following: 
    sudo adduser $USER dialout
Sign In or Register to comment.