Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Doubling up BIN files to burn to EPROM

734 views
Skip to first unread message

Nama

unread,
Aug 3, 2009, 4:05:29 AM8/3/09
to
I need to burn an EPROM of Toolkit II for my QL. I was told it needs
to be burnt to a 27128 EPROM, however I don't have any at this size. I
do have a large pile of 27256's which are pin compatible.

My question is simple. How can I double up the .bin file so that I can
burn it to 27256 instead of a 27128.

Thanks in advance

Phil

Andrew Halliwell

unread,
Aug 3, 2009, 4:30:02 AM8/3/09
to

Would you need to double up the bin file?
Shirely just disabling the high address pin on the chip would do the trick,
turning it into a 128?

Not sure whether you'd need to burn it to the top or bottom half of the
memory space though?

Are address lines active high or active low on those things?
--
| spi...@freenet.co.uk | |
| Andrew Halliwell BSc | "The day Microsoft makes something that doesn't |
| in | suck is probably the day they start making |
| Computer science | vacuum cleaners" - Ernst Jan Plugge |

Matthew Westcott

unread,
Aug 3, 2009, 6:51:22 AM8/3/09
to

Assuming the .bin file is just a raw binary image that's exactly the
right size for the smaller eprom, then in UNIX:
cat single_rom.bin single_rom.bin > double_rom.bin

At a Windows / DOS command prompt, from memory:
copy \b single_rom.bin + single_rom.bin double_rom.bin
- or if that doesn't work, it might be
copy \b single_rom.bin + single_rom.bin > double_rom.bin

Andrew Halliwell

unread,
Aug 3, 2009, 7:23:37 AM8/3/09
to
Matthew Westcott <gas...@raww.org> wrote:
> Nama wrote:
>> I need to burn an EPROM of Toolkit II for my QL. I was told it needs
>> to be burnt to a 27128 EPROM, however I don't have any at this size. I
>> do have a large pile of 27256's which are pin compatible.
>>
>> My question is simple. How can I double up the .bin file so that I can
>> burn it to 27256 instead of a 27128.
>
> Assuming the .bin file is just a raw binary image that's exactly the
> right size for the smaller eprom, then in UNIX:
> cat single_rom.bin single_rom.bin > double_rom.bin

Not quite. You'd want to ensure that the bin file is EXACTLY the correct
size first. If it was a few bytes short, you'd end up with the second one
offset from the page boundary (if you know what I mean).

ls -l the file first, find the difference in size from what you need, and
create a zero filled file that's the size difference.
say, the file is 15,596 bytes long rather than 16,383 for example.
You'd create a file to pad out the end with...
dd if=/dev/zero of=padfile count=787
then cat single_rom.bin padfile single_rom.bin > doublerom.bin


--
| |What to do if you find yourself stuck in a crack|
| spi...@freenet.co.uk |in the ground beneath a giant boulder, which you|
| |can't move, with no hope of rescue. |
| Andrew Halliwell BSc |Consider how lucky you are that life has been |
| in |good to you so far... |
| Computer Science | -The BOOK, Hitch-hiker's guide to the galaxy.|

John Elliott

unread,
Aug 3, 2009, 2:20:39 PM8/3/09
to
Sinclair PC200 512k (V1.5) on 3 August 2009
Loading Matthew Westcott <gas...@raww.org>.SYS.....
: At a Windows / DOS command prompt, from memory:

: copy \b single_rom.bin + single_rom.bin double_rom.bin
: - or if that doesn't work, it might be
: copy \b single_rom.bin + single_rom.bin > double_rom.bin

The first one was (nearly) right.

copy /b single.bin+single.bin double.bin

--
--------------------------- ,@@.o ,@@. SPELL SUCCEEDS
John Elliott | @@@@ @@@@ n \_O_
CHAOS in a sig... | '||` '||` Hr \I `
--------------------------- JL JL I\ /\\

Guesser

unread,
Aug 3, 2009, 3:51:49 PM8/3/09
to
Andrew Halliwell wrote:
> Nama <forum...@mac.com> wrote:
>> I need to burn an EPROM of Toolkit II for my QL. I was told it needs
>> to be burnt to a 27128 EPROM, however I don't have any at this size. I
>> do have a large pile of 27256's which are pin compatible.
>>
>> My question is simple. How can I double up the .bin file so that I can
>> burn it to 27256 instead of a 27128.
>
> Not sure whether you'd need to burn it to the top or bottom half of the
> memory space though?
>
> Are address lines active high or active low on those things?

this should work fine, blow the rom to the bottom half of the chip, and
lift the pin for the MSB and tie it to ground with a bit of wire
soldered on.

also check the circuit diagram or board because that pin on the socket
might not be connected to anything (in which case you don't need to bend
the pin up, just put the wire bridge across to GND) or it might be
connected to ground anyway, in which case you don't need to do anything
at all to the eprom

Guesser

Paul E Collins

unread,
Aug 3, 2009, 5:02:29 PM8/3/09
to
"John Elliott" <j...@seasip.demon.co.uk> wrote:

> Loading Matthew Westcott <gas...@raww.org>.SYS.....
> : At a Windows / DOS command prompt, from memory:
> : copy \b single_rom.bin + single_rom.bin double_rom.bin
> : - or if that doesn't work, it might be
> : copy \b single_rom.bin + single_rom.bin > double_rom.bin
>
> The first one was (nearly) right.
> copy /b single.bin+single.bin double.bin

Yes. Windows only uses the backslashes in paths, and for precisely this
reason (that forward slashes were already being used for command-line
switches like /b).

Eq.


Nama

unread,
Aug 5, 2009, 8:14:46 PM8/5/09
to
On Aug 4, 6:02 am, "Paul E Collins" <find_my_real_addr...@CL4.org>
wrote:

Well, thanks guys. I haven't had time to try anything out yet, so I'm
still not sure which direction I'll try, but I'm guessing it'll be the
simplest route for sure ;-)

Thanks again.

Philip

0 new messages