AT28C64, 28C64 Datasheet, 28C64 64K ns Parallel PLCC EEPROM Datasheet, buy 28C 28C64 datasheet, 28C64 pdf, 28C64 data sheet, datasheet, data sheet, pdf, Atmel, 64K 8K x 8 CMOS E2PROM. 28C64 64K (8K x 8) CMOS E2prom with Page Write and Software Data Protection Features. Fast Read Access Time ns Automatic Page Write Operation.
|Published (Last):||10 May 2017|
|PDF File Size:||18.42 Mb|
|ePub File Size:||12.41 Mb|
|Price:||Free* [*Free Regsitration Required]|
Here is my code, sorry if it seems too cluttered:. The device 28cc64 13 address pins, which should specify an address in binary from 0x to 0x1FFF. You have not indicated that you are doing anything with them?
The same diagram shows CE being asserted followed by OE for a datasheeet cycle. Home Questions Tags Users Unanswered. Sign up or log in Sign up using Google. When the timer expires, an internal write cycle is triggered and additional writes before it completes. I understand the benefits of separating the code into subroutines and will probably do this, but for now I am just trying to get the byte write working. Any help would be much appreciated. Thanks for the info. PeterJ 16k 20 42 That will make the remainder of your code much more readable.
Initializing pins for write I don’t really like the design, but my guess is that it was trying to be compatible with an earlier part where one could write locations one at a time and just wait after each one. Mar 27 ’13 at I’d recommend following that same sequence and also change your write sequence to follow the diagram datashete the following page.
Sign up using Facebook.
28C64 Datasheet pdf – 64K 8K x 8 CMOS E2PROM – Atmel
All behave the same. Looking at the datasheet on page 12 it shows a timing diagram and Chip Enable Access Time can be up to nS. I added ms delays between every control pin change and made sure the order was consistent with the datasheet, but still no luck.
Since I am only using the first three address pins, the rest are tied low. Here is my code, sorry if it seems too cluttered: Sign up using Email and Password.
One thing that is missing is on page 7 of the datasheet, it states that you need to write a sequence of codes to disable write-protection. I have edited my question. Email Required, but never shown.
That might help things.
Also, I would suggest that you should write a writebyte procedure which sets all address and data wires to output and puts proper values on them, ensures WE and OE are deasserted, asserts CE, asserts and release WE, and releases CE, and a readbyte procedure which sets all address wires to output and puts proper values on them, sets all data wires to input, asserts CE and OE, samples all the data wires, and releases CE and OE.
If it has, you’ll need to wire up all your address wires in order to disable it. I am using the Xicor 28C64AP chip datasheet. Thanks for dattasheet response, supercat.
Datasneet have tied the top 10 address bits low and am only using the first 3 for now. The chips are new, and I actually have two from two different manufacturers.
BTW, if the chips are equipment pulls as opposed to new parts, it’s possible that the “software protection” feature has previously been enabled. Post as a guest Name.
I wrote a program for the Arduino Uno that writes data to the first 4 addresses and then reads the data back. I have tested an earlier version of the above program with a static RAM chip and everything works great.
Mar 26 ’13 at