Hi, I am working on lpc2148. I need a sample code for interfacing lpc2148 with eeprom device(at24c04). Its very urgent please help me out...
Thanks in advance....
Regards, Kiranmai G
Hi everyone, I need a sample code for interfacing at24c04 (eeprom) with lpc2148. Its very urgent please help me out...
Thanks in advance.........
catb.org/.../smart-questions.html
#include "LPC2148.h" #include "AT24c04.h" void main ( void ) { LPC2148_SetInterface(AT24c04); }
That was a toughy.
When are your school assignment due?
Its not my school assignment... I am working in a company...I am trying to interface AT24c04 with LPC2148 for my development board... So its very urgent i have to close my project as early as possible...
In other words, you are being paid to do this, but you want the forum to give it to you for free?!
If you don't have the in-house capabilities to do this, then you need to hire-in the expertise - see: http://www.keil.com/condb/search.asp
From my side i have tried...I wrote the code, writing is working fine but while reading i am facing the problem..Thats why i am taking help from forums...so that i can get some idea and implement in my code...Thats all...I am not taking any code freely from the forum...I know that i am paid to do this work...
So now it's time for you to Debug what you wrote!
Debugging is an inherent part of software development; ie, it is an inherent part of your job - it is what you are being paid to do!
"writing is working fine but while reading i am facing the problem"
Your first step is to identify what problem, exactly, is happening. Then you will be able to consider ways to fix that problem...
For debugging tips, see: www.8052.com/.../169331 - the approach is entirely generic, and not at all specific to just the 8052.
How do you know that the writing is fine? A requirement for knowing that the write operations works is that the read operations are able to pick up the information written to the EEPROM.
"A requirement for knowing that the write operations works is that the read operations are able to pick up the information written to the EEPROM."
Not necessarily: he might have some independent way to verify that the data has been written - but that should be clearly stated, and not left to guesswork...
Yes. If the EEPROM is socketed, it is easy to move it to a different platform and read out the data. And some chip programmers also supports reading/writing a number of EEPROM.
But I'm of the opinion that when testing software/hardware, the general view should be guilty until proven working. It is much too easy to write some code, and assume it working just because there are no error codes popping up.