Mathias /Guys, I got the debug log of the xhci_hcd module, during the communication with the robot kit (Lego brick). Attached are two files: brick-boot.log: The brick is connected to USB port, and press switch ON button. upload.log: The brick is already ON, and start the uploading of an application code from PC -> Brick, the uploading procedure never finished. I don't know so much about usb communications, but seeing these file logs, I didn't see any estrange message. What do you think, can you see some clue there ? Another things that i can do after that, is obtain the messages of the communication with the brick on a PC where all work fine, and compare both. I don't know if this would be useful because, the driver used is ehci-pci. Thanks in advance. Gustavo. On Tue, Dec 16, 2014 at 9:34 AM, Gustavo Duarte <gus.duarte@xxxxxxxxx> wrote: > Ahh, good tip, I'll try it, and let you know the output. > > Thanks. > > On Tue, Dec 16, 2014 at 8:49 AM, Mathias Nyman > <mathias.nyman@xxxxxxxxxxxxxxx> wrote: >> Hi >> >> On 16.12.2014 00:53, Gustavo Duarte wrote: >>> Hi Guys, >>> >>> >>> I'm having troubles for communication between a NXT - Lego Brick >>> device (http://www.lego.com/) and a Notebook with USB 3.0. >>> >>> kernel version: >>> >>> $ uname -r >>> 3.13.0-36-generic >>> $lspci -vvv >>> >>> 00:14.0 USB controller: Intel Corporation ValleyView USB xHCI Host >>> ************************************* >>> Questions >>> ************************************* >>> >>> 1) Do you think this issue could be caused by kernel/xhci_hcd module ? >>> >> >> It's possible Can you upgrade to a more recent kernel and see if it helps? >> There are a lot of xhci changes since 3.13. Current is 3.18 >> >>> 2) I know that without the brick device, replicate this tests for you >>> isn't possible. >>> >>> So i would like to ask you, a guide to debug this problem, what kind >>> of things I can do to try find out, the problem. >>> >> >> what does dmesg say? any xhci related errors? >> >> You can enable more verbose xhci debugging with: >> echo -n 'module xhci_hcd =p' > /sys/kernel/debug/dynamic_debug/control >> >> then start communicating with your device, and show the output of dmesg. >> >> Requires dynamic debug support and debugfs mounted, I think many distributions have them as default. >> >> -Mathias >>
Attachment:
brick-boot.log
Description: Binary data
Attachment:
upload.log
Description: Binary data
