Page 7 of 8

Re: Cartridge ROM mapping

Posted: Wed Mar 29, 2023 11:16 am
by kevgal
@username@ wrote:
Tue Mar 28, 2023 11:30 am
ROM image creator.

Knocked up in lunch break - so let me know if you hit any issues.

I took the executive decision to fix the byte at $7223 for BASIC - saves writing and having a panic attack :lol:

Good luck!
Thats Great! Works perfectly, now have all the roms working (including Chopper!).
I like the way it displays the rom layout too. Makes things a bit more obvious.
Great utility.
Thank you .
Kev

Re: Cartridge ROM mapping

Posted: Wed Mar 29, 2023 11:36 am
by kevgal
@username@ wrote:
Mon Mar 27, 2023 3:02 pm
OK - here's a little test utility.

There are two styles in the zip, flat memory $4000->$C000 and romb $8000->$C000 + $4000-$8000.

Hopefully the second one should give what you expect.

Basically each 2K page has a valid program with the address to check in each.

They should be inline, so $4000 == $4000 and so on.

In emulation only the flat one will be successful.

Good luck!
Looks like I'm in 'Flat' land from the results from memcflat.bin.
I've modified the cart to use the upper half of the unused 16k so now have more room.
Thanks again for another great utility.

Re: Cartridge ROM mapping

Posted: Wed Mar 29, 2023 11:53 am
by kevgal
@username@ wrote:
Wed Mar 29, 2023 9:39 am
Scouter3d wrote:
Wed Mar 29, 2023 6:06 am
Can you please provide a small "how to" get a BASIC Program in the right format / cartridgespace for this awesome design?
There is no actual design - more a kind of organic cobbling together :lol:

I've attached the DIY manual and tools - but I will probably update the utility part over time, as I'm sure there will be a wee buggette waiting for me!
For something cobbled together this is awsome! Great explanation too. Now I can add more Basic games to my cart.
The 'Flat' version works for me.
(Am I pushing my luck to ask if 'CRUN' could be run automatically?).
Thanks heaps again.
Kev

Re: Cartridge ROM mapping

Posted: Thu Mar 30, 2023 9:06 am
by @username@
OK - update 1 with AutoCRUN and CR added when LOADING PROGRAM.

Re: Cartridge ROM mapping

Posted: Thu Mar 30, 2023 9:44 am
by Scouter3d
This is sooooo cool! :0)

Cheers, TOM:0)

Re: Cartridge ROM mapping

Posted: Thu Mar 30, 2023 10:35 am
by MADrigal
Gorgeous stuff!

Re: Cartridge ROM mapping

Posted: Thu Mar 30, 2023 1:02 pm
by @username@
:oops: Shameless plug :oops:
The FLAT images will also work on the MegaSDCart with or without extensions!

Re: Cartridge ROM mapping

Posted: Thu Mar 30, 2023 6:55 pm
by @username@
ROMs and how they are loaded, with caveats for those which you can patch or mirror.

4K ROMs
Load directly to $B000

6K ROMs
Tank Attack - 4K to $B000, 2K to $A800
Deep Sea Rescue, Planet Defender, Tennis, TennisD1, TennisD2 - 4K to $B000, 2K to $A000
Note Deep Sea Rescue needs the byte at $B4C8 fixed from $AF to $A7

8K ROMs
Load directly to $A000

10K ROMs
Locomotive - 8K to $A000, 2K to $7000

12K ROMs
Load 8K to $A000, 4K to $7000
Note BASIC82A and BASIC82B change byte at $7223 from $40 to $70

16K ROMs
Load 8K to $A000, 8K to $8000

18K ROMs
Load 8K to $A000, 8K to $8000 and 2K to $7800

Perhaps a better method would be to split the ROMs to the relevant BLOCK sizes and name with extension reflecting the memory page.
This is how TI99 copes with Multipart GROMs and ROMs.

What do you think?

Re: Cartridge ROM mapping

Posted: Fri Mar 31, 2023 3:10 am
by kevgal
@username@ wrote:
Thu Mar 30, 2023 6:55 pm
ROMs and how they are loaded, with caveats for those which you can patch or mirror.

4K ROMs
Load directly to $B000

6K ROMs
Tank Attack - 4K to $B000, 2K to $A800
Deep Sea Rescue, Planet Defender, Tennis, TennisD1, TennisD2 - 4K to $B000, 2K to $A000
Note Deep Sea Rescue needs the byte at $B4C8 fixed from $AF to $A7

8K ROMs
Load directly to $A000

10K ROMs
Locomotive - 8K to $A000, 2K to $7000

12K ROMs
Load 8K to $A000, 4K to $7000
Note BASIC82A and BASIC82B change byte at $7223 from $40 to $70

16K ROMs
Load 8K to $A000, 8K to $8000

18K ROMs
Load 8K to $A000, 8K to $8000 and 2K to $7800

Perhaps a better method would be to split the ROMs to the relevant BLOCK sizes and name with extension reflecting the memory page.
This is how TI99 copes with Multipart GROMs and ROMs.

What do you think?
Yes, I agree would have saved my a lot of head scratching.
E.g. Deep Sea Rescue might be DEEPSEA_R1BB.bin and DEEPSEA_R1BA.bin
Locomotive might be LOCO_R1BA.bin and LOCO_R2B7.bin
This would identify which /ROM# and which Block# they belong in.
Or..
Just make them all 16K GAME_1.bin or GAME_2.bin for which rom they are with empty blocks mirrored (the way the machine 'sees' them) or with unused areas filled with $FF (the way the program requires them and unused areas would be obvious).

Re: Cartridge ROM mapping

Posted: Fri Mar 31, 2023 3:12 am
by kevgal
@username@ wrote:
Thu Mar 30, 2023 9:06 am
OK - update 1 with AutoCRUN and CR added when LOADING PROGRAM.
Awsome again!
Thank you.