Yahoo Groups archive

Lpc2000

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

Message

Re: I2C

2006-03-11 by Sutton Mehaffey

Charles,

Using 10K pullups.



Mark,

Yes.  I was afraid I would have to get the scope out.  I was hoping
that it would be straight forward.  Hardware rarely is, I guess.  It
is strange that I am getting back all ACKs, (0x18 and 0x28s) during
the process.  Even to my surprise with the RAM chip not connected....
You know how it is, take a deep breath, sigh, and continue on.  I'll
figure it out.  It's probably something silly I'm missing.



Richard,

I have been using exclusively the LPC2148 user manual flow chart and
state algorithms.  And, I've looked over the sample code.  I am
getting the correct status, but now that I seem to get those status
(with ACKs) with the RAM chip not even connected, it looks like scope
time.

Sutton



--- In lpc2000@yahoogroups.com, "charlesgrenz" <charles.grenz@...> wrote:
>
> Hi Sutton,
> 
>   What size pull-ups do you have and have you tried slowing the clock
> down?
> 
> regards,
> Charles
> 
> --- In lpc2000@yahoogroups.com, "Sutton Mehaffey" <sutton@> wrote:
> >
> > I haven't totally gotten my I2C (LPC2148) to work with my RAMTRON
> > serial RAM yet.  All the status' look good on both writing and reading
> > to RAM, but still get 0xA1 after I write a 0x77.  
> > 
> > However, I noticed that even if I have no power on my RAM and no SDA
> > and SCK lines connected, all the status' are exactly the same and the
> > data is still 0xA1.  It seems as though if the RAM weren't responding
> > at all, you shouldn't get valid codes.  And, I have my ACKs turned on!
> >  Any ideas?
> > 
> > Sutton
> >
>

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.