VOGONS


First post, by keenerb

User metadata
Rank Oldbie
Rank
Oldbie

I've got a handful of 28C256 chips, and I need a 28C64 for a board.

From looking at the datasheet I see the pinouts are basically the same, except 28C256's A13 and A14 are NC/not connected on the 28C64 part.

I assume that those signals would be used to select addresses > 8kb? Addressing reads to the first 8kb shouldn't use those pins, so the 28c256 part should work well, I'll just be wasting the additional space.

My programmer seems to bear this out; I can read the first 8kb of a 28C256 by specifying 28C64 as the chip type, but I'd like some validation that this will work reliably.

Reply 1 of 2, by keropi

User metadata
Rank l33t++
Rank
l33t++

Yes it is possible for the eeproms you mention... I recommend to fill the C256 eeprom completely with the C64 data:

copy /b C64.BIN + C64.BIN + C64.BIN + C64.BIN C256.BIN

the above command assumes your original 28C64 dump is called "C64.BIN" and C256.BIN is the output file to be written on the 28C256 eeprom

🎵 🎧 SoundVision PRO,MK1869 , PCMIDI MPU , OrpheusII , Megacard and 🎶GoldLib soundcard website
💾💾💾 Looking for a full version of LIST ENHANCED 2.4y1 by V. Buerg, message me if you have it for sale! 💾💾💾

Reply 2 of 2, by SSTV2

User metadata
Rank Oldbie
Rank
Oldbie
keenerb wrote:

From looking at the datasheet I see the pinouts are basically the same, except 28C256's A13 and A14 are NC/not connected on the 28C64 part.

I assume that those signals would be used to select addresses > 8kb? Addressing reads to the first 8kb shouldn't use those pins, so the 28c256 part should work well, I'll just be wasting the additional space.

You are correct. If you wish to substitute a smaller capacity eeprom with a larger, you have to write your binary data to the last 8kb space of the 28c256, starting from: 32768-8192=24576 or 6000H. Keropi's suggestion would solve such problem.