digital-logicmicrocontrollerproteusrom;
Trying to load a .bin file into a 2732 ROM chip in Proteus.
Having trouble finding the exact layout of code I need for the .BIN file.
So far i have tried writing the following in notepad and saving it as .bin
00000001
00000000
00000001
00000001
and outputting the data at the first 4 address spaces but i doesnt seem to have 'loaded' in the data I entered.
Maybe iam missing something like a header or some other key words in my .BIN file.
Thanks in advance
This is a two step problem.
First Step:
Combine your 2k x 8 ROMs into a 2k X 32 ROM (requires 4 x 2k x 8 ROM ICs per 2k x 32 unit)). The address inputs will be common and need to be connected in parallel. The data outputs are kept separate to for the 32 lines required. Don't forget there are also control lines, usually a chip enable and a read line (usually active LOW) but check the specs.
Second Step
This involves combining four "2k x 32 bit" ROM units. The input ADDRESS LINES (A0 - A10) are connected together in parallel. The OUTPUT DATA lines are also connected together in parallel. This just leaves the problem of the CONTROL LINES. The READ line is simply commoned as you want the ROM to output the data with a single 'read' signal. The CHIP ENABLE lines are used as an extra ADDRESS signal to ensure that only ONE 2k x 32 bit block is addressed at any given time. We have input addresses A11 and A12 to give the full 8K address for the ROM. We need to add a 2 to 4 line decoder to convert these address lines to CHIP ENABLE selections.
That depends on the rom used, it should be written in the datasheet. I'd say that \$D_0\$ is the LSB and \$D_3\$ is the MSB, but that's just a guess based on the fact that \$D_0\$ represents \$2^0\$, \$D_1\$ represents \$2^1\$ and so on.
Best Answer
A ".bin" file would clearly be a binary one, while you seem to be creating a text file containing something else, perhaps a printable hex dump.
Depending on what your source material is, you may be able to have the a tool specific to that flow translate to a binary output, for example with a gcc-style toolchain you can use
objcopyfor this.Or you can find various "hex editor" tools which will let you edit in a format not unlike what you depict, but then save to a raw binary format.
If there is some organization to the file beyond flat binary, that would be something imposed by whatever is going to read your EPROM, not by the chip itself. So it is not something which could be determined from information in your question. Most commonly however, for systems which use single byte-wide storage devices there is not.