How to configure MegaflashRom SCC+ SD extension on openMSX?

Page 2/3
1 | | 3

By bakoulis

Master (166)

bakoulis's picture

23-05-2016, 13:22

Thank you mate.
Smile

By Manuel

Ascended (14738)

Manuel's picture

23-05-2016, 20:27

Basically, on openMSX and real hardware, you use exactly the same ROM images and procedure. There's no difference!

By Eugeny_Brychkov

Paragon (1035)

Eugeny_Brychkov's picture

17-10-2018, 10:09

Apologies for reviving this thread, but I can not make MFR working properly. I need to put flushed ROM from real MFR into it (I have got image and need to try it), and edit config file to point to this ROM. However it seems openMSX does not read config file at all - when I put garbage before "msxconfig" tag it says error parsing, but if I arbitrarily put garbage inside this tag, no error, openMSX starts and no MFR in there. Files seem to be created in persistent directory, thus there's something going on. What do I miss here?

Edit: no, it seems it reads the config file (when I remove "rom/" it asks for it), but does not throw error if there's something wrong in there. It just does not work...

I need more or less complete working configuration file where I can put into my data sources - of sram image and ROM contents.

P.S. It seems I do not knoiw how it works. I have put MFR section into the machine's config file (rather than having it as extension), and not it seems gives appropriate errors. Now I have machine started, and instead of ROM I see RAM in respective slot. I guess to start MFR contents it needs to run its ROM first? Also config file says mem base of 0-10000, does it mean that ROM starts with 0? While I clearly see it should start at 4000.

By Manuel

Ascended (14738)

Manuel's picture

18-10-2018, 00:16

The extension by default has an empty flash ROM. That means it doesn't do anything, so it is as if it doesn't work.
There is a sha1sum in its config though, and it will try to load the ROM specified by that sha1sum at first start up, i.e. when there is no SRAM file (the file that contains the flash ROM content).

So, perhaps that's causing the confusion?

Note that the mem range of 0-10000 is correct. It's not just for the ROM, it means the extension uses all memory space of the Z80. This range just tells openMSX which memory range the extension can access.

By Eugeny_Brychkov

Paragon (1035)

Eugeny_Brychkov's picture

18-10-2018, 07:11

Can you please give me proper syntax to set up existing ROM and SRAM file? I have read manual, it is relatively clear, but I can not make it working. Again, for some reason RAM appears in the MFR slot instead of ROM (even empty ROM with all FFs). I can not understand what is going on and how it should work. I asked Manuel Pazos, waiting for his answer.

By Eugeny_Brychkov

Paragon (1035)

Eugeny_Brychkov's picture

18-10-2018, 08:57

First issue: debugger does not understand that MFR expands the primary slot. That's why I thought there's RAM only. Indeede, RAM is placed into slot 2, with debugger stating "2" for banks 1-3. However SSSR is present, and I can change subslots properly. First time machie comes to reading address 4000 into subslot 0, which must correspond to MFR's ROM. I see FFs in there, however having the following configuration in the machine's file:

<primary slot="2">
        <ROM id="MegaFlashRom SCC+ SD">
          <mem base="0x0000" size="0x10000"/>
          <sound>
            <volume>9000</volume>
          </sound>
		  <rom><filename>c:/xxx/kernel.dat</filename></rom>
          <sdcard1>
            <filename>SDcard1.sdc</filename>
            <size>8</size>
          </sdcard1>
          <sdcard2>
            <filename>SDcard2.sdc</filename>
            <size>100</size>
          </sdcard2>
          <sramname>megaflashromsccplussd.sram</sramname>
          <mappertype>MegaFlashRomSccPlusSD</mappertype>
          <hasmemorymapper>true</hasmemorymapper>
        </ROM>
      </primary>

I have tried with existing files in persistent directory, and after their deletion without any difference - ROM space shows FFs. Target file contains the needed code (not empty or FF).

Edit: if I put inexistent file name into <filename> tag, no error is generated, and I conclude that <filename> tag is not the one which must be used to point to the ROM image? If I change <rom> tag to <roms> it complains that it requires <rom> tag. Further, if I change <filename> tag (within <rom> tag) to <shit> I get no error too! WTF... I expect openMSX not to start with invalid tags/information within its configuration files, or at least throw the warning.

By karloch

Paragon (2025)

karloch's picture

18-10-2018, 10:00

Eugeny, I see you are using the ROM tag in the XML, but MFR doesn't work that way in openMSX. Here is my working XML file: https://gist.github.com/cmilanf/1d21f6a5e0a43b1d8dc31eb47c2d91a3

The actual ROM is present in the megaflashromsccplussd.sram file. For flashing it, boot openMSX with both, MFR and other IDE storage solution with MSXDOS.SYS, COMMAND.COM, OPFXSD.COM and Nextor ROM for MFR (rename to NEXTOR.ROM o something 8+3), and the run OPFXSD NEXTOR.ROM /I. The emulation should be ready to start.

By Eugeny_Brychkov

Paragon (1035)

Eugeny_Brychkov's picture

18-10-2018, 10:24

karloch wrote:

For flashing it

Emulation exists to make things easier, right? Smile

My goal here is:
1. "download" all the possible ROM/RAM contents from the real MFR;
2. set up openMSX with these ROM/RAM contents;
3. execute it so that I am able to reproduce here the issue we see in the field.

It seems steps 1 and 2 are a big hassle. Downloading ROMs must use SAVEROM.COM, and for this I must know exact locations and configurations of MFR ROMs (and relatively advanced knowledge of how it works - thanks to Manuel, we just had chat about it where he explained how it works and what should I do). Then, I must assemble this "megaflashromsccplussd.sram" file from ROM pieces - and this is what you talk about I guess. I would expect I can "insert" the respective ROMs (or better: data images) in respective locatons of MFR in openMSX, but it seems it is not possible?

By karloch

Paragon (2025)

karloch's picture

18-10-2018, 15:37

Well, that's indeed a question for Manuel; I only know how to make it work, but that specific use and building of the sram file is a question for him.

By Guillian

Prophet (3178)

Guillian's picture

18-10-2018, 16:04

Building that ROM is quite easy:

Quote:

incbin "recovery.rom"
incbin "dskrom.rom"
ds #700000 - (32 * 1024)
incbin "nextor.rom"
incbin "romdisk.dsk"

In the MegaFlashROM SCC+ area (ds #700000 - (32 * 1024)) you should insert the content of the real cartridge.

Page 2/3
1 | | 3
My MSX profile