Post by thread:FRAM/Ramtron info@ramtron.com

> John Johnson Team OS/2 member | spam_OUTjohnsonjTakeThisOuTbga.com | .....johnsonjKILLspam@spam@utdallas.edu John, It's nice to see positive responses about my company's products. > Very little code mod was necessary in my xlinx I assume you are using our FM24C04. This should be completely drop-in compatible with EEPROM I2C 24C04 parts. I am very curious to know exactly what changes were necessary. Were the code changes only to take advantage of the fast write time of FRAM? > I put them to the test overnight and only had 4 > read back errors after 5mil r/w cycles. I realize that this may be good performance for a(n) EEPROM, but you should see ZERO errors in 10 billion cycles with our FRAM products. I'd like to know the details of how you are accessing the FM24C04 (temp, reading/writing pattern, voltage, etc.). Are the 4 errors you've seen hard errors or soft errors? I'll forward your info to our QA department; they're very interested in your experience. CONTACT INFO: NEW!!!! Email: infoKILLspamramtron.com (Since this is new: if there are problems, please bear with us.) Ramtron International Corporation 1850 Ramtron Drive Colorado Springs, CO 80921 (800) 545-FRAM (719) 481-7000 Fax: (719) 488-9095 We're working on anonymous ftp access for our data sheets etc. Right now, the best way to get information is to e-mail or call and ask for our data book. Greg Smith Design Engineer Ramtron Int'l Corp .....gregKILLspam.....ramtron.com

My apologies if the list receives this twice. > John Johnson Team OS/2 member | EraseMEjohnsonjspam_OUTTakeThisOuTbga.com | johnsonjspam_OUTutdallas.edu John, It's nice to see positive responses about my company's products. > Very little code mod was necessary in my xlinx I assume you are using our FM24C04. This should be completely drop-in compatible with EEPROM I2C 24C04 parts. I am very curious to know exactly what changes were necessary. Were the code changes only to take advantage of the fast write time of FRAM? > I put them to the test overnight and only had 4 > read back errors after 5mil r/w cycles. I realize that this may be good performance for a(n) EEPROM, but you should see ZERO errors in 10 billion cycles with our FRAM products. I'd like to know the details of how you are accessing the FM24C04 (temp, reading/writing pattern, voltage, etc.). Are the 4 errors you've seen hard errors or soft errors? I'll forward your info to our QA department; they're very interested in your experience. CONTACT INFO: NEW!!!! Email: @spam@infoKILLspamramtron.com (Since this is new: if there are problems, please bear with us.) Ramtron International Corporation 1850 Ramtron Drive Colorado Springs, CO 80921 (800) 545-FRAM (719) 481-7000 Fax: (719) 488-9095 We're working on anonymous ftp access for our data sheets etc. Right now, the best way to get information is to e-mail or call and ask for our data book. Greg Smith Design Engineer Ramtron Int'l Corp KILLspamgregKILLspamramtron.com

P.S. I am an embedded conrtrol and design engineer but who ever posted that job add. You had better add eskimo to your requirments :) just joke about the great white north. Was up there once in the winter(one week). Nearly froze to death in my hotel with the heater on(good beer though). Came back home to Texas where it was nice and warm. > Very little code mod was necessary in my xlinx > > I assume you are using our FM24C04. This should be completely drop-in > compatible with EEPROM I2C 24C04 parts. I am very curious to know exactly > what changes were necessary. Were the code changes only to take > advantage of the fast write time of FRAM? Nope close though. FM24C16. It maybe with the 24C04 but we used the 93C66 in our original design(tossed now). And the modes were for true I2C compatability. As for timing? yup that was one thing I upped. > > I put them to the test overnight and only had 4 > > read back errors after 5mil r/w cycles. > > I realize that this may be good performance for a(n) EEPROM, but > you should see ZERO errors in 10 billion cycles with our FRAM > products. I'd like to know the details of how you are accessing the > FM24C04 (temp, reading/writing pattern, voltage, etc.). Are the 4 > errors you've seen hard errors or soft errors? I'll forward your info > to our QA department; they're very interested in your experience. oh i took it through hell. I would write the data address then the data, then add then data, add, data till it was full. None of that nice sequential crap :) then did add,read,add,read,add,read until the end. once again no nice sequential(this was pretty messy to do, add,write,read). As for temp? around 100 F or so(not sure what chasis temp range is but that would be a good guess). as for V? 5 solid and even. As for the errors H/S? well it could go either way but most likely hardware. My software took a 20meg file, wrote it to the chip and read it back via a MXI bus. If it was software i think there would have been more.. however... ehh out of how much was written it is possible and I/O error occured. > We're working on anonymous ftp access for our data sheets etc. Right > now, the best way to get information is to e-mail or call and ask for > our data book. God man are you crazy! Dont come into the 21st century yet. For godsake only Harris has this(they used a Web, its really nice but incomplete). :) later John ----------------------------------------------------------------------------- John Johnson Team OS/2 member | RemoveMEjohnsonjTakeThisOuTbga.com | spamBeGonejohnsonjspamBeGoneutdallas.edu ----------------------------------------------------------------------------- And the Seventh version of OS/2 raised into the air its bow of blue steel and cried," It. Is. Done." Around him lay Bill Gates and Microsoft apps. Their evil in this world at an end. Revelations of InfoWorld, Oct 11 1994