From: oller <oleg@elphel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot-xlnx 'master-next' branch: usb not working for microzed
Date: Mon, 14 Oct 2013 11:30:02 -0700 (PDT) [thread overview]
Message-ID: <1381775402172-165384.post@n7.nabble.com> (raw)
Hi,
I've been working with xilinx's microzed board (zynq) recently. The actual
goal is a fsbl-less u-boot.
But even with fsbl - USB is not working in u-boot-xlnx 'master-next' branch.
At the same time it works in the 'master'. Mostly interested in
'master-next'.
Has anyone tried USB in the 'master-next' for microzed/zedboard?
OS: Ubuntu 13.04 x64
board: MicroZed
u-boot-xlnx 'master-next' rev: bbd91fc9ae290c31dc52fd8322f43f67ddd39247
u-boot-xlnx 'master' rev: 0f6dbff16b792a106f52ca37f4503335af30601b
cross-tools: cross compiler built with yocto poky:
> export CROSS_COMPILE=arm-poky-linux-gnueabi-
> export
> PATH=/opt/poky/1.4.2/sysroots/x86_64-pokysdk-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi/:$PATH
incorrect output:
> ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> ehci-pci: EHCI PCI platform driver
correct output:
> 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
Thanks
--
View this message in context: http://u-boot.10912.n7.nabble.com/u-boot-xlnx-master-next-branch-usb-not-working-for-microzed-tp165384.html
Sent from the U-Boot mailing list archive at Nabble.com.
next reply other threads:[~2013-10-14 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 18:30 oller [this message]
2013-10-15 20:52 ` [U-Boot] u-boot-xlnx 'master-next' branch: usb not working for microzed Jagan Teki
2013-10-16 6:18 ` Oleg Dzhimiev
2013-10-16 6:35 ` Michal Simek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1381775402172-165384.post@n7.nabble.com \
--to=oleg@elphel.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox