My MGR is working very good, so it's long time I don't make an update.
But does the best choice is to update all firmware's files? (kernel, diskrom, romdisk, recovery, etc.)
And in what sequence?
You can update Kernel + ROM Disk from recovery.
- Copy to an *EMPTY* SD card the file KERNEL.DAT (unpack it from the ZIP file)
- Enter recovery mode (holding cursor up while booting)
- Select F4 option
Recovery can be updated using:
OPFXSD RECOVERY.ROM /i34 (just download RECOVERY.ROM and put it on you SD card)
If you need to update the ROM disk:
OPFXSD ROMDISK.DSK /id
By the way, are you aware of any bug on mknexrom?
I am using
MKNEXROM v1.05 - Make a Nextor kernel ROM
By Konamiman, 4/2014
rom is created, but upon boot, msx keeps resetting, and not a single debug message is displayed on screen.
I'm not aware of any bug in MKNEXTOM.
Are you sure your driver works fine? Have you selected the right mapper?
BTW, why do you want to use a different driver?
I am writing a driver for MSXPi.
https://www.msx.org/forum/msx-talk/hardware/msxpi-msx-raspbe...
I am trying to use my megaflashrom to test the driver.
At this stage I don't care I will loose SD and Flash drive access.
About my driver functionality, no, it does not work. Not at this stage.
But i got startup messages that should be displayed during boot, and that is not happening.
I am not passing mapper parameter to mknexrom, my understanding is that it was not necessary in this case.
Megaflasrom = ASCII16
Is that right?
By the way, are you aware of any bug on mknexrom?
I am using
MKNEXROM v1.05 - Make a Nextor kernel ROM
By Konamiman, 4/2014
rom is created, but upon boot, msx keeps resetting, and not a single debug message is displayed on screen.
I'm not aware of any bug in MKNEXTOM.
Are you sure your driver works fine? Have you selected the right mapper?
BTW, why do you want to use a different driver?
I am writing a driver for MSXPi.
https://www.msx.org/forum/msx-talk/hardware/msxpi-msx-raspbe...
I am trying to use my megaflashrom to test the driver.
At this stage I don't care I will loose SD and Flash drive access.
About my driver functionality, no, it does not work. Not at this stage.
But i got startup messages that should be displayed during boot, and that is not happening.
I am not passing mapper parameter to mknexrom, my understanding is that it was not necessary in this case.
Megaflasrom = ASCII16
Is that right?
That is not right. MFR SD (subslot 3) uses an ASCII8 mapper.
Yep, bug is on the man here.
Using ASCII8 mapper file and passing /8:6000 got better results. I can see debug messages on boot.
Wheels moving again, thanks Guillian.
@Guillian: thankyou very much, now cart is updated and I can see the new Recovery menu!
Going to try a dump, now... I will use the "ROM Extractor" utility (from the download section of msx org), but do you suggest me to use other dumping utilities?
Do you know about some good reasons the rom "works" on OpenMSX but not on actual MSX, after flashing the megaflashrom ?
by "work" I mean the debug messages are now being displayed as expected.
I used opfxsd to flash the rom... maybe I should do it using the recovery method?
I am writing a driver for MSXPi.
https://www.msx.org/forum/msx-talk/hardware/msxpi-msx-raspbe...
I am trying to use my megaflashrom to test the driver.
At this stage I don't care I will loose SD and Flash drive access.
About my driver functionality, no, it does not work. Not at this stage.
But i got startup messages that should be displayed during boot, and that is not happening.
I am not passing mapper parameter to mknexrom, my understanding is that it was not necessary in this case.
Megaflasrom = ASCII16
Is that right?
That is not right. MFR SD (subslot 3) uses an ASCII8 mapper.
@enribar MGSAVE or SAVEROM are good tools for dumping cartridges.
@ronivon Are you overwriting MFR SD Nextor kernel (/i) or loading your ROM into the MegaFlashROM SCC+?
I am overwriting MFR SD Nextor kernel (/i)
With the rom I got generated with mknexrom
@ronivon Are you overwriting MFR SD Nextor kernel (/i) or loading your ROM into the MegaFlashROM SCC+?
In that case there will not be conflicts between different Nextor kernels. So if you implement the basic Nextor driver functions it should work fine.