Originally Posted by ah_kap
DanBa, thanks for the explanation.
I will upload a dmesg log file from my international S3 later when i get a chance to load a stock kernel on my S3.
here is the dmesg log for a stock kernel LF1
There is the same error (i.e. 62 ETIME) than with Siyah kernel.
<7>[ 18.896475] c0 s5p-ohci s5p-ohci: urb f1c14200 path 1 ep0in 5ec20000 cc 5 --> status -62
A (same?) problem:
<7>[49289.147493] ohci_hcd 0000:00:0a.0: urb cf384e60 path 1 ep1in 5c160000 cc 5 --> status -62
"Regarding your query, indeed, there are some our clients reported that their USB devices sometimes could not work on EBOX-3300, but when they connected their devices to EBOX-3300 via an USB hub, the fault disappeared.
We have found that the fault is caused by the USB 2.0 PHY. It will
lead to USB 2.0 PHY and some devices sometimes miss commands when they are handshaking."
Could you use a powered USB 2.0 (i.e. high speed / full speed) hub (S3>>high speed>powered hub>full speed>>Pico) just for testing purposes?
Another example of a USB 2.0 hub fixing some hardware bug:
"There seems to be a bug in the Touch hardware that prevents async from working properly when running at full speed. In this case you need the USB 2.0 hub which talks to the Touch at high speed, but talks to the DAC at full speed. This gets around the bug in the Touch. This is only needed for an async full speed DAC. An adaptive full speed DAC or a high speed DAC of any type can be used without the hub. Thus if your DAC is a full speed only DAC (ie has a maximum sample rate of 96KHz) and you get ticks and pops, it is probably running using async mode and will need the hub to work properly."