[meta-xilinx] zedboard usb issues

[Simon Vincent]

I did a build using the nrossi/next branch and I can confirm the USB now 
works.
Many thanks

Simon

On 04/11/14 09:45, Nathan Rossi wrote:
>> -----Original Message-----
>> From: meta-xilinx-bounces at yoctoproject.org [mailto:meta-xilinx-
>> bounces at yoctoproject.org] On Behalf Of Mike Looijmans
>> Sent: Monday, November 03, 2014 4:48 PM
>> To: meta-xilinx at yoctoproject.org
>> Subject: Re: [meta-xilinx] zedboard usb issues
>>
>> On 10/31/2014 10:35 AM, Nathan Rossi wrote:
>> Met vriendelijke groet / kind regards,
>>
>> Mike Looijmans
>> System Expert
>>
>>
>> TOPIC Embedded Systems
>> Eindhovenseweg 32-C, NL-5683 KH Best
>> Postbus 440, NL-5680 AK Best
>> Telefoon: (+31) (0) 499 33 69 79
>> Telefax:  (+31) (0) 499 33 69 70
>> E-mail: mike.looijmans at topic.nl
>> Website: www.topic.nl
>>
>> Please consider the environment before printing this e-mail
>>
>> Topic zoekt gedreven (embedded) software specialisten!
>> http://topic.nl/vacatures/topic-zoekt-software-engineers/
>>
>> -----Original Message-----
>>>> From: meta-xilinx-bounces at yoctoproject.org [mailto:meta-xilinx-
>>>> bounces at yoctoproject.org] On Behalf Of Simon Vincent
>>>> Sent: Friday, October 31, 2014 12:48 AM
>>>> To: meta-xilinx at yoctoproject.org
>>>> Subject: [meta-xilinx] zedboard usb issues
>>>>
>>>> I have build a zedboard image using the latest xilinx-yocto but I am
>>>> having problems with the usb.
>>>>
>>>> I find that 50% of the time I get an error initialising the usb phy:
>>>> root at zedboard-zynq7:~# dmesg|grep -i usb
>>>> [    0.562406] usbcore: registered new interface driver usbfs
>>>> [    0.568243] usbcore: registered new interface driver hub
>>>> [    0.573986] usbcore: registered new device driver usb
>>>> [    1.314762] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI)
>> Driver
>>>> [    1.329453] zynq-dr e0002000.ps7-usb: Unable to init USB phy,
>> missing?
>>>> [    1.336866] usbcore: registered new interface driver usb-storage
>>>> [    1.461775] usbcore: registered new interface driver usbhid
>>>> [    1.469402] usbhid: USB HID core driver
>>>>
>>>> The rest of the time I get the following but no usb devices are
>>>> recognised:
>>>>
>>>> root at zedboard-zynq7:~# dmesg|grep -i usb
>>>> [    0.562418] usbcore: registered new interface driver usbfs
>>>> [    0.568255] usbcore: registered new interface driver hub
>>>> [    0.573981] usbcore: registered new device driver usb
>>>> [    1.314193] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI)
>> Driver
>>>> [    1.331922] Found TI TUSB1210 ULPI transceiver.
>>>> [    1.341299] zynq-ehci zynq-ehci.0: Xilinx Zynq USB EHCI Host
>> Controller
>>>> [    1.348773] zynq-ehci zynq-ehci.0: new USB bus registered, assigned
>>>> bus number 1
>>>> [    1.405684] zynq-ehci zynq-ehci.0: USB 2.0 started, EHCI 1.00
>>>> [    1.418015] hub 1-0:1.0: USB hub found
>>>> [    1.429784] usbcore: registered new interface driver usb-storage
>>>> [    1.560122] usbcore: registered new interface driver usbhid
>>>> [    1.567687] usbhid: USB HID core driver
>>>>
>>>> If I boot using the sdcard image that came with the zedboard the USB
>>>> works every time and recognises usb devices.
>>>>
>>>> Has anyone else had problems with this?
>>> I have seen this before with other boards. It is caused when the USB PHY
>> is not reset properly. I don't see the issue in my testing most likely due
>> to FSBL and or U-Boot resetting the phy.
>>
>> I have been using a patch for that for a while (the PHY reset in FSBL only
>> worked for half the MIO pins). I was waiting for the VBUS patch to make it
>> to
>> Xilinx master-next before submitting that to Xilinx. There's also one in
>> the
>> ADI tree, but it uses much too loose timings for the reset pulse.
>>
>> You can see my code here, this solved the PHY reset on all boards:
>> https://github.com/topic-embedded-
>> products/linux/commit/7fb825c883e744c069a049ca4629c4664d2081af
> This is what I was referring to regarding the kernel being able to reset the PHY. But as it turns out the linux-xlnx kernel only had this in the xlnx_3.8 tree (https://github.com/Xilinx/linux-xlnx/commit/53e868300ad63c52137f47fd762a660071f1fd4e), and the patch was never merged with the newer branches.
>
> That patch looks good Mike, I have ported that change as a patch for the linux-xlnx_3.14 recipe. I have that on the nrossi/next branch, which I intend to merge by the end of the week.
>
> @Simon: I have also resolved that toolchain error you were getting with the newer meta-xilinx with dizzy.
>
> Regards,
> Nathan
>
>>
>>
>>> Linux is able to reset the PHY, and I have a patch on my nrossi/next
>> branch which should fix this issue you are seeing. Would you be able to
>> give it a try and let me know the outcome?, the branch is at:
>>> https://github.com/nathanrossi/meta-xilinx/compare/nrossi/next
>>
>> --
>> _______________________________________________
>> meta-xilinx mailing list
>> meta-xilinx at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-xilinx