linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christian Schroeder <christian.schroeder@imms.de>
To: linuxppc-embedded@lists.linuxppc.org
Cc: karsten.pahnke@emsys.de, reklies@mazet.de
Subject: USB hostcontroller for TQM823L boards seems to work
Date: Thu, 06 Jun 2002 12:48:48 +0200 (MEST)	[thread overview]
Message-ID: <1023360528.3cff3e10175e5@imp.imms.de> (raw)


Hi all,

I succeded testing the usb hostcontroller (sources from www.heeltoe.com
written by Brad Parker).

1. Hardware

- TQM823L board with mpc823e (PPC823EZTnnB2)
- connection between X7/7 (Timer 1 output) and X9/16 (/DREQ1) to
  enable the spi/iic microcode patch
- 4 delay gates (74LVT244A) beetwen X32/1 resp. X32/3 (VM/VP outputs
  of the PDIUSBP11A) and X32/2 resp. X32/4 (USBXRM and USBXRP inputs
  of the mpc823e) required , power supply from X3/9 (+3,3V) an X3/3 (GND)
- connection of a high speed device (hub) to the usb connector required
  (low speed devices are only detected behind this hub)

2. Software

- linux-2.4.4 kernel sources from ftp.denx.de
- m8xxhci.c from www.heeltoe.com (added as config option CONFIG_USB_MPC8xx
  and to .../drivers/usb/...)
  #ifdef CONFIG_TQM823L
  #define USE_TIMER1_FOR_SOF
  #define USE_PA4_CLK4
  #undef POLL_FOR_HUB
  #endif
- kernel configuration (.config)
  CONFIG_UCODE_PATH=y
  CONFIG_USB=y
  CONFIG_USB_DEBUG=y
  (for testing)
  CONFIG_USB_MPC8xx=y
  (don't include usb mouse and usb keyboard drivers for testing,
   because the mouse an keyboard drivers claim the interfaces and
   the sample driver cannot see any data transfers)
  CONFIG_INPUT=y
  CONFIG_INPUT_EVDEV=y
  (mousedev and keybdev drivers don't link for ppc - undefined symbols)

3. Testing

- I used the sample usb driver from Alessandro Rubini and Jonathan Corbet
  and plugged it as a module to the running kernel.
  (http://examples.oreilly.com/linuxdrive2/ldd2-samples-1.0.1.tar.gz)
- I plugged a usb mouse and a usb keyboard to the external usb hub, connected to
  the board.
- When I moved the mouse, pressed mouse buttons or keys on the keybord,
  the kernel dumped the results to the console, so I think the host con-
  troller works correctly.

Thanks a lot for all help and comments.

Now I want to check, if I can repeat the results with my FADS823 board,
but I'm not sure if there is a possibility to do the necessary hardware
modifications. Specially I don't have any idea how to insert the delay
gates. Any hints would be greatly appreciated

Christian Schroeder

Dr.-Ing. Christian Schroeder
Institut fuer Mikroelektronik- und Mechatronik-Systeme
Langewiesener Strasse 22
98693 Ilmenau
Telefon: +49 3677 678315
Telefax: +49 3677 678337
Mobil:   +49 173 5789172
e-mail:  christian.schroeder@imms.de
www:     http://www.imms.de/~christi/cs.html
pgp:     finger christi@finger.imms.de


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2002-06-06 10:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-06 10:48 Christian Schroeder [this message]
2002-06-07  4:45 ` USB hostcontroller for TQM823L boards seems to work jari

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=1023360528.3cff3e10175e5@imp.imms.de \
    --to=christian.schroeder@imms.de \
    --cc=karsten.pahnke@emsys.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=reklies@mazet.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;
as well as URLs for NNTP newsgroup(s).