Tiny Core Base > Raspberry Pi

libusb not showing devices

<< < (2/4) > >>

curaga:
edit: Seems your rpi's usb could be broken, if the hub alone shows the same behavior. Try another rpi?

kkrpeq:
I added dwc_otg.speed=1 at the end of my cmdline.txt, and now DeviceB is being detected by lsusb. Also, Bus Power was not automatically set to 0x0.
However this parameter limits the usb speed to only 12Mbps, while usb 2.0 can do up to 480Mbps.
Maybe there is a better solution?

References:

https://raspberrypi.stackexchange.com/questions/1886/what-kernel-parameters-are-available-for-fixing-usb-problems

https://www.cl.cam.ac.uk/~atm26/ephemeral/rpi/dwc_otg/doc/html/module%20parameters.html

gadget42:
interesting...good to know...you would think they would have fixed it after so many years...

post from 2020:
https://forums.raspberrypi.com/viewtopic.php?t=262852

post from 2014:
https://ludovicrousseau.blogspot.com/2014/04/usb-issues-with-raspberry-pi.html

post from 2012:
https://raspberrypi.stackexchange.com/questions/1886/what-kernel-parameters-are-available-for-fixing-usb-problems

perhaps for some rest period viewing:
https://www.youtube.com/watch?v=4PoWAsBOsFs
and/or:
https://www.youtube.com/watch?v=613yEF6SrNo

sharing is caring

kkrpeq:
What bugs me the most is that I got DeviceB working on Raspberry OS a few times before, so I thought the problem was a tiny core issue.
But now I tried Raspberry OS again and it shows the same problem.
While setting dwc_otg.speed=1 succeeded in making DeviceB recognizable by lsusb, I am having errors when performing bulk transfers.  :(

Rich:
Hi kkrpeq
I sounds like it may be a power supply issue for the RPi. It could be the power supply is failing and no longer providing
a stable output. Or maybe something on the RPi changed causing it to pull more current than it used to.

Try reducing the power consumption by lowering the CPU frequency. Then see if the USB system behaves any better.

Install cpupower.tcz:

--- Code: ---tce-load -wi cpupower
--- End code ---

Then:
Check the info:

--- Code: ---cpupower frequency-info
--- End code ---

Set the governor to userspace so that we can set the frequency:

--- Code: ---sudo cpupower frequency-set --governor userspace
--- End code ---

Set the maximum frequency:

--- Code: ---sudo cpupower frequency-set --max 600MHz
--- End code ---

Check the info:

--- Code: ---cpupower frequency-info.
--- End code ---
It should say: "Current policy: frequency should be within 600 MHz and 600 MHz."

Found here:
https://raspberrypi.stackexchange.com/a/133666

Navigation

[0] Message Index

[#] Next page

[*] Previous page