I use ATmega32L and an eeprom AT24C16..Could anyone give me source code to read and write from this eeprom.
PLease mail me at sarvesh.baheti@gmail.com
Thanks!
YES! For which Keil toolchain?
There are small differences between the sources to achieve support for your target MCU depending on the Keil toolchain you are using.
FOR KEIL uvision4
Extraordinary.
You have found Keil uVision4 to support the ATmega32L processor? Please post how you managed that, since Keil doesn't have any official support for the Atmel AVR-family processors.
CONTROLLER = AT89S52
Could anyone give me source code to read and write from this eeprom. why would anyone do that? if you are student, it would be cheating if it is industrial, it would be giving work away for someone else to make money on if you are an amateur, you would learn nothing
Erik
So why did you say "ATmega32L" in your opening post?!
making YOUR (properly formatted and commented) code work.
"if you are an amateur, you would learn nothing"
Looking at professional examples is a great way for a budding amateur to learn.
I do it all the time.
But then you probably look at a lot of varying examples and then take what you learn in small pieces and combine to something new. There is one thing to look for general knowledge and another to just want finished code exactly matching your requirements.
I see that now, when your ability to spam has been severely limited (I know you know what I mean!), you channel your frustrations via other channels. That's cool, and will probably help you stay out of a mental institution for somewhat longer, Steve.
"...your ability to spam has been severely limited..."
What?! They closed down Twitter?
Indeed.
However, there is no shortage of AT24C16 code readily available for study on the web - so it seems unlikely that anyone genuinely interested in learning would need to ask to have it sent direct to their mailbox...
Looking at professional examples is a great way for a budding amateur to learn
if you do not have (developed) the skill to, at least in principle, develop the thing yourself, ANY error/misunderstanding/... will stun you.
The typical example is all the LCD/UART/... "sample codes" that have led to forum posts "why does this code not work for me?" simply because the downloaded code was used with a different clock speed.
There is no excuse for not knowing, at least, the basics before you start.
"... ANY error/misunderstanding/... will stun you."
Seeing code written by (purported) qualified engineers and finding the problems and/or figuring ways to improve things is another fine way to learn.
That initial seed of interest is important too.