Parallella Community

Same here, since I enabled devtmpfs, USB seems to work reliably.

HBE

Hi Shodruk, Bikeman

This sounds promising. Prior to enabling this, were you having success with a USB mouse or keyboard? This is my issue - not other USB devices (at this point in time).

I would really like to at least have a response of some sort from the Adapteva team. I would really think that they would be supporting their backers and commit to making some sort of statement. USB should be working out of the box and they need to make it clear what commitment they are going to make to find a solution (if it be that they are relying on your investigation and proving it) and making everyone aware (very clearly) what the final solution is.


Thank you Shodruk and Bikeman

Hi Leon

What USB devices were you able to get working initially?

I think you need to SSH into the board via Ethernet connection - please correct me if I am wrong gurus - to be able to enter the commands.

Follow Steps 5A onwards of this document to SSH into the board (Ethernet connection from your router to the board) : http://www.parallella.org/wp-content/up ... e_rev3.pdf


Let me know if it works please.

Thanks for the clarification, Sean. I'll try your suggestion.

I first tried a direct connection Trust USB keyboard and keyboard - only one at a time, of course, although I had a hub I could have used. I then used a Logitech mk330 wireless mouse and keyboard together. That is probably the most convenient solution.

for me, it is also not working, I usually get error -99 with lsusb. Then I activated tempfs. The next boot took long time. I tried lsusb and a hub was found.I connected another hub, and lsusb outputs the two hubs. Connecting usb-Keyboard (noname) and mouse also worked. So I connected HDMI, booted again, and finally I could log in via gdm the first time... the desktop came on full HD, nice. The mouse could be moved... but then the mouse froze, keyboard showed no reaction anymore (also NumLock did not toggle the led anymore) the hub seemed still be powered... after that no luck with usb anymore...
So my understanding is, that USB is somehow not initialized correctly sometimes (in my case nearly everytime). If lsusb shows correct answer, usb is working, at least for a short time...

Hi, I also have the same problem as ESI and others in this thread. My board does usually not see the USB mouse & keyboard: in such case running lsusb will give the mentioned error message -99 of libusb. I did as suggested in http://elinux.org/Parallella_Speed_Up_Ubuntu, however this did not solve the problem.

After rebooting the board a few times, suddenly the USB was working and in this case lsusb was correctly displaying the connected device. Then after the next reboot I was again unable to get mouse & keyboard working: this persisted for at least ten consecutive reboots until the USB was suddenly working again. I saved the output of dmesg in both cases of USB working/not working and these are the first lines of diff

< ULPI transceiver vendor/product ID 0x0424/0x0007
< Found SMSC USB3320 ULPI transceiver.
< ULPI integrity check: passed.
< xusbps-ehci xusbps-ehci.0: Xilinx PS USB EHCI Host Controller
< xusbps-ehci xusbps-ehci.0: new USB bus registered, assigned bus number 1
< xusbps-ehci xusbps-ehci.0: irq 53, io mem 0x00000000
< xusbps-ehci xusbps-ehci.0: USB 2.0 started, EHCI 1.00
< hub 1-0:1.0: USB hub found
< hub 1-0:1.0: 1 port detected
---
> xusbps-dr e0002000.usb: Unable to init USB phy, missing?

(can post/mail the whole dmesg outputs, please just ask). That reminds me of this thread:

http://www.zedboard.org/content/u-boot- ... ot-working

My 2 cents...

Hi Leon - any success? I will try it on the weekend if the 'lil one gives me a chance - but it would be good to know if you have got it sorted with the proposed fix.

It really surprises me that Adapteva have not responded to this and don't seem to care about fixing this issue for their loyal backers. What many of us had probably hoped for was a stable product given the long delays in delivery... only to have more frustration in trying to fix their problem with the USB.

Thanks to everyone that is spending their time doing this . Please keep us posted on your progress. I am highly confident that we will find a fix - be it without the support of Adapteva