M93C56, M93C 16Kbit, 8Kbit, 4Kbit, 2Kbit and 1Kbit (8-bit or bit wide). MICROWIRE® Serial Access EEPROM. FEATURES SUMMARY. 93C46 Technical Data, x8(1k) Serial CMOS EEPROM Datasheet, buy 93C 93C46 Datasheet, 93C46 1k Serial EEPROM Datasheet, buy 93C
|Published (Last):||21 January 2009|
|PDF File Size:||10.55 Mb|
|ePub File Size:||6.83 Mb|
|Price:||Free* [*Free Regsitration Required]|
These devices are usually used to store user configurable parameters and device serial numbers. They use a serial bus interface, which allows them to be packaged in inexpensive 8 pin packages.
File:EEPROM 93C46 DSC00570 wp.jpg
To you, the system designer, these little chips offer a nifty way to store a small amount of data in non-volatile memory, using only a few of the port pins, and without raising the system’s cost much. They are usually specified to retain the data eeprrom 10 years and to endurewrite operations before failure. They only require a 5 volt power supply some 3V only versions exist too.
Because these chips use a serial interface, they can not be read quickly enough to serve as conventional memory. In addition, a considerable length of time milliseconds is required to perform a write operation. They typically hold less than bytes of memory. Usually, the 3-wire devices require an addition wire beyond the 3 for data transfer for each chip to be used.
I 2 C is a trademard of Philips. As the pressure on engineers to make products smaller has grown, semiconductor manufacturers have introduced several new interfaces, usually aimed at lower a product’s size and cost As a practical matter, the code offered below only works with the Microwire 3 Wire interface, and is specifically intended to work with the 93C46, which is a standard part available from a variety of distributors.
It can be used without much difficulty with a 93C46, by avoiding calls to the routines that manipulate the extended features of the 93CS They have also added example code similar to the code below, as well as 93c446 I 2 C parts they offer.
National Semiconductor has lots of data sheets on-line. I used their 93CS46 data sheet to write the code. Their literature number is MicroChip now has data sheets on-line for most of their products. They offer quite a 39c46 different types of serial eeproms, including of course the 93CS46 and 93C Xicor once had a considerable collection of example code on-line, but eeporm appear to have removed it. There are lots of other distributors too, but Mouser and DigiKey are probably the easiest, since they give out a free catalog What this family code does This code was written to support the 93CS This 3-Wire interface chip actually has 6 wires.
As mentioned above, four wires are actually required, and the 93CS46 has two additional lines that work together with a special write protection register. This code should work “out of the box” with a 93CS46 chip.
Eeprom 93c46, Eeprom 93c46 Suppliers and Manufacturers at
The two extra pins not required for the 93C46 are manipulated by all the routines. To reclaim these pins, remove all the instructions that use ” pe ” and ” pre ” symbols. A simpler approach 93c6 be to set the bit addresses of these bits in the. It’s up to you.
I might make another version of the code specifically for the plain 93C46, if anyone wants it enough to let me know. Please explain the difficulty you have using the code with a 93C46 or the trouble you think you may have.
Early versions of this code worked with the 93C56 and 93C57, which have more memory. Unfortunately, these chips use an 8 bit address field, whereas the 93C46 uses only 6. The code can be adapted to work with these larger chips The early versions are long since gone. The code is basically designed to manipulate a single 93CS46 chip, connected to six of the port pins. Two versions of the code are available, one with a little menu driven user interface via a terminal connected to the UART and the other with only the routines to include in your existing program.
The user interface is simple and shouldn’t need documentation. Reprom routines available for your code are: Valid address range for R0 is 0 to This operation must be performed before a write may be issued.
This applies to both the 93C46 and 93CS Writing must have been enabled using WEN.
Writing takes a considerable length of time milliseconds. This routine just waits for it to finish before returning This disables write operations. It applies to both the 93C46 and 93CS46 chips.
It is advisable to disable writing if no additional write operations are expected soon. In this state, the chip may have better resistance to accidental data loss due to problems on the power supply, noise on signal lines, etc. The next access should be to this register instead of the memory. In addition, WEN may have to have been called, check your data sheet or just do it to be on the safe side.
PREN should only enable use of the protection register for the next access, so it should be called before every protection register access. Of course, WEN must still be called before writing. All memory locations before and including the value in R0 will become write protected. Unprotected memory locations are still subject to WEN and WDSbut protected eeprm are unwritable unless the protection register is changed or cleared.
PRDS Permenantly freeze efprom protection register to its current value. It can never be modified again after this operation.
All protected memory locations will forever be unwritable, but the locations not protected will remain subject to WEN and WDS. The fact that you have frozen the protection register is stored in the non-volatile memory 10 year min retention. There is no way to undo this operation The menu-driven example code includes a copy of these routines and calls esprom properly to allow the user to view efprom edit the values within a 93CS It is not necessary to erase memory locations before writing.
The erase functions provided in the 93C46 are unnecessary for the chips I’ve used, double check your data sheet. The erase functions are not implemented here.
Disclaimer These 93C46 Serial EEPROM devices are used in many commercial products where the data contained within the chip, though only bytes, is considered confidential and proprietary.
This code library may not be used to “break into” the data stored within devices in commerical products.
Use of this code library to modify the behavior of commercial products, without the expressed written authorization of the manufacturer, is also prohibited. This code library is in the public domain. You may use it within commercial for-profit products, without concern of licensing restrictions, copyright, royalties, etc. If you do use it, I hope that you’ll give me some feedback.