General discussions about V-USB, our firmware-only implementation of a low speed USB device on Atmel's AVR microcontrollers
-
bearing
- Posts: 10
- Joined: Mon Oct 27, 2008 6:06 pm
- Location: Sweden
Post
by bearing » Mon Oct 27, 2008 7:03 pm
I have successfully tried the hid-mouse example under Windows XP; the device is recognized and the mouse pointer starts to move in a big circle.
However, in Ubuntu nothing seems to happen when i plug it in; dmesg says nothing, and no messages are appended in the log files. I'm quite new to both Linux and Ubuntu so i don't really know how to proceed from here.
I activated DEBUG_LEVEL 2. Here is a command log:
Code: Select all
bjn@bjn:~/avr/avrusb-20081022/examples/hid-mouse/firmware$ stty -F /dev/ttyS0 19200
bjn@bjn:~/avr/avrusb-20081022/examples/hid-mouse/firmware$ stty -F /dev/ttyS0
speed 19200 baud; line = 0;
-brkint -imaxbel
bjn@bjn:~/avr/avrusb-20081022/examples/hid-mouse/firmware$ cat /dev/ttyS0
(then I plug it in and get the following:)
�01:
02:
03:
23: c3 00 ff 07 00 cd db
02:
02:
...
Then it just keeps iterating the main loop; "02: <CR> <LF>" is written in a fast rate. (Actually so fast that dmesg shows a bunch of: "[ 4588.651402] ttyS0: 1 input overrun(s)".)
-
bearing
- Posts: 10
- Joined: Mon Oct 27, 2008 6:06 pm
- Location: Sweden
Post
by bearing » Mon Oct 27, 2008 9:00 pm
Problem solved. I am using a USB-hub. After disconnecting the hub and connecting it to a different USB-port everything is working.
Is there a unix command which would make things work without manually disconnecting and changing USB-port?
-
gert
- Rank 1
- Posts: 27
- Joined: Sat Oct 20, 2007 5:58 pm
Post
by gert » Thu Oct 30, 2008 1:50 pm
Hi Bearing
To my knowledge (as a Debian/Ubuntu/OpenWRT user) there is no issue with AVR-USB other than bulk transfer from low speed devices (e.g. CDC).
What you describe sounds more like an electrical problem (i.e. zener diodes).
Best
Gert
-
bearing
- Posts: 10
- Joined: Mon Oct 27, 2008 6:06 pm
- Location: Sweden
Post
by bearing » Thu Oct 30, 2008 6:27 pm
Hi Gert,
I think that when the device (during buggy development
) did something illegal the kernel stopped looking for devices on that USB-port. Later, when the bug was fixed and the device was connected to a different USB-port everything worked as it should.
It is easier to write a command in the terminal than to move the physical connector.
-
Guest
Post
by Guest » Tue Aug 04, 2009 9:39 am
hi all
thank you for your assistance
all things solved and i found the answer