Replies: 4 comments 5 replies
-
After a quick look at the data sheet, it looks like you could program the M48T08 using the default 28C driver. You just need to set the block size to zero so the code writes a byte at a time instead of doing block writes. In TommyPROM.ino, just comment out the first PromDevice28C declaration and uncomment the second one. This is for the 28C64 chip, but it matches the need of your chips as well. On the hardware side, you have 2 extra pins to deal with. Connect the E2 pin to 5V so it is always enabled. The Interrupt pin is an output and isn't needed, but the data sheet mentions it needing a pull-up resistor, so you may need to look into that. Otherwise, just wire it up like a 28C chip, with the E1, G, and W pins as CE, OE, and WE, respectively. |
Beta Was this translation helpful? Give feedback.
-
Hi Tom, today I had some time to try to program M48T08 using your project. I set-up everything on a breadboard and I am using an Arduino Nano. I have some troubles. Look at the two log file I am attaching at the end of this message. Which may be the problem of such a strange behavior? I have compiled the TommyPROM.ino with the following lines:
Thank you a lot for your assistance! best regards Piero
P00000 37 37 37 INFO: Poke successful
INFO: Poke successful
INFO: Poke successful
TommyPROM 3.3 - 28C series EEPROM Valid commands are: I - Print debug Info
ERROR: Verify failed addr=0x1 read=0x43 expected=0x42
ERROR: Verify failed addr=0x1 read=0x43 expected=0x42
|
Beta Was this translation helpful? Give feedback.
-
Hi Tom, look also at the attached log file. Please note that the last bytes are updated automatically by the clock, which is inside the BBRAM. I first filled all the BBRAM by "22". Then I poke P00000 01. The byte 0x0 was correctly updated, but all other bytes now are (or appear) "23". Best regards Piero |
Beta Was this translation helpful? Give feedback.
-
Pictures are here.
Il Dom 11 Feb 2024, 12:04 Piero Tognolatti ***@***.***> ha
scritto:
… Hi Tommy,
I discovered the problem I had: a socket of ZIF I am using didn't contact
the BBRAM pin 11. I had tested several times the connection between that
socket and the Arduino D2 and the result was OK. But I didn't see that the
ZIF didn't correctly close on that IC's pin.
After a better positioning of the BBRAM on the ZIF, everything is
perfectly working!!! Thank you a lot for your beautiful project and for
your nice support!!!
I am now able to perform any operation of the BBRAM. For example I can
set, start or stop the clock, which appears in the last bytes of the
device. You can see that now is year (20)24, month 02, day 11, week day 1,
hours 11 (here in Rome!), minutes 50, seconds 17
>D 1FF0 1FFF
01ff0: 00 00 00 00 00 00 00 00 00 17 50 11 01 11 02 24 ........
..P....$
Before discovering the fault I also tried to change something in the
arduino sketch. I am now working with PromDevice28C prom(8 * 256L, 0,
10, true);. Can it be OK?
If you like I can send you a picture of the (terrible!) setup I arranged.
You will even see that the BBRAM I am now programming is an old one (got
from Ebay) to which I connected an external CR2032 3V battery.
Let me know if you like me doing some experiment on such a BBRAM.
Best regards
Piero
Il 10/02/2024 19:01, Tom Nisbet ha scritto:
It looks like maybe your connection to data pin zero of the RAM is open or
shorted. The values read seem to follow the last value you've written to
that bit. Double check your wiring between the Arduino and the RAM for the
least significant data bit. I've noticed that the Arduino after reads back
that same value you last wrote if nothing is connected to the data lines,
like when there is no target EEPROM in the burner.
Try poking multiple different values in and I'll bet the LSB will follow
the last value written.
For example,
f 0 f 00
d 0 f
p 0 00 ff
d 0 f
p 0 ff 00
d 0 f
—
Reply to this email directly, view it on GitHub
<#60 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMBTQJLTZTG7QLOIVGST2IDYS6YXNAVCNFSM6AAAAABCOBXG2CVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DIMRYHAZTG>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I would like to use TommyPROM to write a M48T08 BBRAM. It's a 5 V 64 kbit SRAM incorporating a battery and a clock. Has anyone already done it? Can I use an already defined PromDeviceXX class, or I need to create a new one?
Regards
Piero
Beta Was this translation helpful? Give feedback.
All reactions