[C.CC USERS] Almost there with Ubuntu

[Omer Kilic]

Hi Dennis,

I have been using 9.10 without a problem for months and I installed the 
Lucid Beta 2 on a fresh VM earlier. Following the same steps I was able 
to see the FTDI device in lsusb output.

Couple of things:
   - On the bottom toolbar, under the USB icon do you see a tick next to 
the FTDI device when the VM is running?
   - When you start your VM do you hear the 'device unplugged' sound, 
i.e: Does the VirtualBox USB filter driver take over? (this can be 
observed within the Device Manager)

That's all I can think of I'm afraid, could you install a fresh VM and 
try again if possible? As the release of Lucid is imminent (and it fixes 
the autoconf troubles) it might be worth giving the beta a go...


Cheers,
Omer.


Dennis Meade wrote the following on/at 22/04/2010 02:18:
> 
> Omer,
> 
> Thanks for your help.
> 
> I did as you suggested and added a filter for the USB in the VirtualBox 
> settings. The VM says it's active and lists it as FTDI FT232R UART 
> (0600), but Ubuntu 9.10 doesn't see it..
> 
> lsusb is the same as before:
> 
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> 
> fdisk - l is:
> 
>    Device Boot      Start         End      Blocks   Id  System
> /dev/sda1   *           1         993     7976241   83  Linux
> /dev/sda2             994        1044      409657+   5  Extended
> /dev/sda5             994        1044      409626   82  Linux swap / 
> Solaris
> 
> I've looked at the Ubuntu documentation about mounting a USB port, but 
> didn't find anything that would seem to help. I did find the VirtualBox 
> USB documentation that said to do exactly as you suggested, BTW.
> 
> I'll keep trying, but would still be very grateful for any pointers.
> 
> Dennis
> 
> On 4/19/2010 8:31 PM, Omer Kilic wrote:
>>
>> Hello Dennis,
>>
>> Dennis Meade wrote the following on/at 20/04/2010 01:11:
>>> ... but "make upload" fails with the following.
>>>
>>> avr-objcopy -O ihex -R .eeprom tvm-arduino tvm-arduino.hex
>>> ./reset-arduino /dev/ttyUSB0
>>> Traceback (most recent call last):
>>>   File "./reset-arduino", line 7, in <module>
>>>     ser = serial.Serial(sys.argv[1], 57600)
>>>   File "/usr/lib/python2.6/dist-packages/serial/serialutil.py", line 
>>> 166, in __init__
>>>     self.open()
>>>   File "/usr/lib/python2.6/dist-packages/serial/serialposix.py", line 
>>> 175, in open
>>>     raise SerialException("could not open port %s: %s" % (self._port, 
>>> msg))
>>> serial.serialutil.SerialException: could not open port /dev/ttyUSB0: 
>>> [Errno 2] No such file or directory: '/dev/ttyUSB0'
>>> make: *** [upload] Error 1
>>
>> The upload script is looking for '/dev/ttyUSB0' and as it is not 
>> present in your system (judging by the `lsusb` output you have 
>> provided) it fails.
>>
>>
>>> In the Windows Device Manager everything looks ok with the USB port 
>>> masquerading as COM3.
>>
>>   - Right click on your VM instance within the Virtualbox window and 
>> select 'Settings'
>>   - Go to the USB tab and click the 'Add filter from device' button, 
>> the one with a USB plug and a green plus symbol
>>   - Select 'FTDI FT232R UART' from the list and press OK
>>
>> Now, when you start your VM you will see that the FTDI VCP driver will 
>> stop working (COM3 will disappear) and it will be replaced by the 
>> 'VirtualBox USB' driver, the filter driver for the USB devices.
>>
>> Try doing `lsusb` after those and hopefully you should see the FTDI 
>> device under /dev/ttyUSBx.
>>
>>
>> Hope this helps,
>> Omer.
>>
> 
> 
> _______________________________________________
> users mailing list
> users at concurrency.cc
> http://unhosting.org/mailman/listinfo/users