Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: board warranty

2005-11-02 by seangra

I found something disturbing as well, here's the email that I sent.  
Anyone have any thoughts about this?


Dear Olimex Support:

I've got a question about the connection of SD/MMC cards, based on 
the your schematics.  I'm looking at your dev kit for the 
LPC2148/SAM7S64, but I'm worried about the SD connection.

According to the SD spec:
-DAT0-3/CMD/WP should have pullups,
-DAT0-3/CMD/CLK should have caps

However nowhere any on your schematics do you have any caps, and you 
seem to be inconsistent with your use of pullups.  On some 
schematics you leave DAT1/DAT2 floating (which is a direct no-no 
AFAIK) and you don't pull up CMD, and inconsistently pull up DAT0.

The spec says directly that not pulling up DAT1/DAT2 (even though 
they are unused) can cause high current consumption:
  "The `RSV' pins are floating inputs. It is the responsibility of 
the host designer to connect external pullup resistors to those 
lines. Otherwise non-expected high current consumption may occur due 
to the floating inputs."

Additionally since there is an internal pull-up on CS, do you need 
an external one?

Is there something that I don't know here, or is this an error in 
the board design?

Thanks for any insight.



--- In lpc2000@yahoogroups.com, rseku <rseku@p...> wrote:
>
> Dear Olimex support!
> On the CS8900 ethernet board, there significant inconsistencies 
between 
> schematic and board:
> 1. On board label D11 - On schematic no such label
> 2. On schematic R11 installed - on board not
> 3. On schematic connector pins exist as C2.1 -> c2.16, on board 
17 -> 32
> 4. On board only top side has parts labels, bottom parts is you 
secret
> 
> 
> Do You take responsibility for these inconsistencies in case of 
> potential board damage caused by them?
> 
> Regards
> robert seczkowski
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.