linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Dieter Schneider" <dieter.schneider@berghof.com>
To: "'linux embedded forum'" <linuxppc-embedded@ozlabs.org>
Subject: FW: Mpc5200 and ISP1106/1107 USB transceivers
Date: Fri, 5 Aug 2005 13:00:52 +0200	[thread overview]
Message-ID: <000f01c599ac$f2f36830$33f1ff0a@beint.local> (raw)

[-- Attachment #1: Type: text/plain, Size: 263 bytes --]



Mit freundlichen Grüßen
Berghof Automationstechnik GmbH

i.A. Dieter Schneider
- Entwicklungsingenieur -
http://www.berghof.com
mailto:dieter.schneider@berghof.com
Phone: +49 7121 894-129
Fax:   +49 7121 894-100
Adresse:
Harretstr.1  72800 Eningen
Deutschland


[-- Attachment #2: Type: message/rfc822, Size: 1580 bytes --]

From: "Dieter Schneider" <dieter.schneider@berghof.com>
To: <Martin.Krause@tqs.de>
Subject: Mpc5200 and ISP1106/1107 USB transceivers
Date: Thu, 4 Aug 2005 17:14:44 +0200

Hello Mr.Krause,

i made an investigation with Philips 1106/1107 USB transceivers not working
with low speed devices and mpc5200:
-usb 1.1 specification gives a rise/fall time for low speed devices in range
75ns to 300ns.
-"working" devices like Philips PDIUSBP11 have a rise/fall time of aprox.
120ns
-isp1106 / 1107 are in range of 180ns, that's inside usb 1.1 spec, but not
working with mpc5200

So its a problem of mpc5200, not philips 1106/1107 transceivers, who are
inside usb 1.1 spec. Setting transceiver speed pin konstant to High(=high
speed device) let the isp1106/1107 work also with low speed devices, but of
course with high speed rise/fall times (7..20ns). By the way, Phillips
PDIUSBP11 is obsolet. Giving the USB D+/D- an additional capacitive load
(for example 120pF, thats inside usb 1.1 spec ) makes an working Phillips
PDIUSBP11 not working.

Mit freundlichen Grüßen
Berghof Automationstechnik GmbH

i.A. Dieter Schneider
- Entwicklungsingenieur -
http://www.berghof.com
mailto:dieter.schneider@berghof.com
Phone: +49 7121 894-129
Fax:   +49 7121 894-100
Adresse:
Harretstr.1  72800 Eningen
Deutschland

                 reply	other threads:[~2005-08-05 11:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='000f01c599ac$f2f36830$33f1ff0a@beint.local' \
    --to=dieter.schneider@berghof.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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).