From: Ned Forrester <nforrester@whoi.edu>
To: Ben Gamari <bgamari.foss@gmail.com>
Cc: beagleboard@googlegroups.com,
spi-devel-general@lists.sourceforge.net,
linux-omap@vger.kernel.org
Subject: Re: [spi-devel-general] SPI troubles
Date: Mon, 15 Mar 2010 16:57:27 -0400 [thread overview]
Message-ID: <4B9E9F37.9030906@whoi.edu> (raw)
In-Reply-To: <4b9e58d3.11435e0a.1736.2cf9@mx.google.com>
On 03/15/2010 11:57 AM, Ben Gamari wrote:
> When measuring the SIMO signal on the expansion connector with my daughterboard
> connected, I noticed that the daughterboard's level shifter appeared to be
> driving the signal higher than it should, to ~2.9 Volts. I then checked the
> 1.8V rail voltage and found that it too was higher than expected, again at 2.9
> volts. When I unplug the daughterboard, the 1.8V rail voltage returns to its
> expected value.
>
> On Mon, 15 Mar 2010 10:38:38 -0400, Ned Forrester <nforrester@whoi.edu> wrote:
>> I'd be happy to check your circuit for you, if it were posted in a more
>> widely used format. How about a PDF of the schematic.
>>
> Certainly, it's a available at http://goldnerlab.physics.umass.edu/~bgamari/schematic.png.
Your problem is likely caused by pulling the THREE STATE pin to 5V. The
spec sheet is explicit (in the Absolute Maximum ratings on page 2, and
in the functional description on page 12 that this pin should be pulled
to VL, not VCC to enable the outputs. Likely by pulling it to 5V the
some part of the chip is biased wrong and may cause OVL1 to be pulled
above VL.
I can't exactly explain the symptoms you report above, based on the
mis-connected pin, but most anything could be happening in the MAX3390
once the absolute maximum ratings have been exceeded. The 10K resistors
on the THREE STATE lines may have saved the circuit from permanent
damage, but they may not save it from improper operation.
Other suggestions, nothing fatal...
1. The pinout of the MAX3390E on the drawing is for the TSSOP package.
Hopefully that is the package you actually used.
2. All uncommitted inputs should be terminated high or low. This
applies to: LS2 pins 4, 5 and 13; LS3 pin 13 and possibly unused pins on
the A/Ds and D/A.
3. The MAX3390E family has extremely low drive capability and slow
response. Is this device really fast enough for your intended clock
rates? Note that the device can only pull down 1ma, and can only pull
up 20ua. If there are any pull-downs or pull-ups on the BeagleBoard,
the MAX3390E might not be able to drive them.
4. I find it curious that the AVDD to the A/D and D/A is fead through a
1ohm resistor that is paralleled by C11 and C12. Likely you meant to
tie one side of each of C11 and C12 (the side now connected to C10
positive) to ground. That connection would make a filter to reduce the
noise on AVDD rather than passing the noise along.
5. Is see on the Maxim site that this series of translators is not
recommended for new design. Likely the suggested alternatives have much
better specifications.
--
Ned Forrester nforrester@whoi.edu
Oceanographic Systems Lab 508-289-2226
Applied Ocean Physics and Engineering Dept.
Woods Hole Oceanographic Institution Woods Hole, MA 02543, USA
http://www.whoi.edu/
http://www.whoi.edu/sbl/liteSite.do?litesiteid=7212
http://www.whoi.edu/hpb/Site.do?id=1532
http://www.whoi.edu/page.do?pid=10079
next prev parent reply other threads:[~2010-03-15 20:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 2:44 SPI troubles Ben Gamari
2010-03-15 2:55 ` [spi-devel-general] " jassi brar
2010-03-15 15:38 ` Ben Gamari
2010-03-15 12:25 ` Philip Balister
2010-03-15 16:01 ` Ben Gamari
[not found] ` <4b9d9f11.9a15f10a.3902.6dc3-ATjtLOhZ0NVl57MIdRCFDg@public.gmane.org>
2010-03-15 14:38 ` Ned Forrester
2010-03-15 15:57 ` [spi-devel-general] " Ben Gamari
2010-03-15 20:57 ` Ned Forrester [this message]
2010-03-16 1:06 ` Ben Gamari
2010-03-16 2:24 ` Ned Forrester
2010-03-15 17:04 ` Tony Lindgren
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=4B9E9F37.9030906@whoi.edu \
--to=nforrester@whoi.edu \
--cc=beagleboard@googlegroups.com \
--cc=bgamari.foss@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.