[meta-xilinx] zedboard usb issues

[Simon Vincent]

I pulled in your commit ffa9c0f7425916527c5f75c9e6b9610a9415ca12 but 
that made no difference. What ps7_init files should I be using as it 
looks like for the commit to work I need to make sure the usb phy reset 
is connected correctly?

I then cloned your whole nrossi/next branch and used that. I had to 
upgrade yocto meta and meta-openembedded to dizzy to get rid of some 
error messages. I was still left with some error messages stopping it 
from building.

ERROR: Multiple .bb files are due to be built which each provide glibc 
(/home/simonv/poky/yocto-build/zedboard/xilinx/../../../meta/recipes-core/glibc/glibc_2.20.bb 
/home/simonv/poky/yocto-build/zedboard/xilinx/../../../meta-xilinx2/recipes-core/meta/external-xilinx-toolchain.bb).
  This usually means one provides something the other doesn't and should.
ERROR: Multiple .bb files are due to be built which each provide 
virtual/libc 
(/home/simonv/poky/yocto-build/zedboard/xilinx/../../../meta/recipes-core/glibc/glibc_2.20.bb 
/home/simonv/poky/yocto-build/zedboard/xilinx/../../../meta-xilinx2/recipes-core/meta/external-xilinx-toolchain.bb).
  This usually means one provides something the other doesn't and should.
ERROR: Multiple .bb files are due to be built which each provide 
virtual/arm-xilinx-linux-gnueabi-libc-for-gcc 
(/home/simonv/poky/yocto-build/zedboard/xilinx/../../../meta/recipes-core/glibc/glibc_2.20.bb 
/home/simonv/poky/yocto-build/zedboard/xilinx/../../../meta-xilinx2/recipes-core/meta/external-xilinx-toolchain.bb).
  This usually means one provides something the other doesn't and should.
ERROR: Multiple .bb files are due to be built which each provide 
virtual/libiconv 
(/home/simonv/poky/yocto-build/zedboard/xilinx/../../../meta/recipes-core/glibc/glibc_2.20.bb 
/home/simonv/poky/yocto-build/zedboard/xilinx/../../../meta-xilinx2/recipes-core/meta/external-xilinx-toolchain.bb).
  This usually means one provides something the other doesn't and should.


Simon

On 31/10/14 09:35, Nathan Rossi wrote:
>> -----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.
>
> 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
>
> Regards,
> Nathan
>
>> Thanks
>>
>> Simon
>> --
>> _______________________________________________
>> meta-xilinx mailing list
>> meta-xilinx at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-xilinx