Menu

How to load 2048 bytes custom ROM at start

Help
dash9
2024-12-01
2024-12-01
  • dash9

    dash9 - 2024-12-01

    I have the following two roms:

    $ ls -l
    total 48
    -rw-r--r--. 1 x x  2048 Sep 29  2023 'CIP-01 (19xx)(Intreprindera Electronica).rom'
    -rw-r--r--. 1 x x 16384 Sep 29  2023 'CIP-03 (19xx)(Intreprindera Electronica).rom'
    

    I can use the 16384 bytes rom just fine, but not the 2048 one:

    $ fuse --rom-48 CIP-03\ \(19xx\)\(Intreprindera\ Electronica\).rom
    $ fuse --rom-48 CIP-01\ \(19xx\)\(Intreprindera\ Electronica\).rom
    [...]
    fuse: error: ROM 'CIP-01 (19xx)(Intreprindera Electronica).rom' is 2048 bytes long; expected 16384 bytes
    fuse: error: couldn't find ROM '48.rom'
    fuse: error initialising -- giving up!
    

    Using version 1.6.0. Is there any way to disable the ROM size check, or to load the ROM with nonstandard size, somehow?

    (The 2048 rom contains basically just the tape loading routine, one has to play the tape each time the system boots to load the BASIC interpreter, or whatever else.)

     
  • dash9

    dash9 - 2024-12-01

    It worked by appending zeroes to the file:

    $ dd if=/dev/zero of=zeroes bs=1 count=$((16384-2048))
    $ cat CIP-01\ \(19xx\)\(Intreprindera\ Electronica\).rom zeroes > CIP.rom
    
     

Log in to post a comment.

MongoDB Logo MongoDB