The OCM-PLD Pack v3.3 is out

By mtn

Master (247)

13-03-2017, 10:55

Nice!! Big thanks to KDL and everyone involved.

By Sebbeug

Master (190)

13-03-2017, 11:51

A really nice release.
After first tests, a few games run better
Thank you KdL !

By KdL

Paragon (1121)

13-03-2017, 16:09

Thanks ro! Please also tag this post to Zemmix Neo.

PS. my nick KdL is with a lowcase 'd' eheh

By ro

Guardian (4005)

13-03-2017, 16:27

KdL wrote:

Thanks ro! Please also tag this post to Zemmix Neo.

yer welcome! But uhm, tagging wot?

KdL wrote:

PS. my nick KdL is with a lowcase 'd' eheh

Fixed, my bad

By KdL

Paragon (1121)

13-03-2017, 17:06

The package OCM-PLD is for 1chipMSX and Zemmix Neo.

Topic: Challenges
Tags: OCM, Firmware, 1chipMSX, Zemmix Neo

By Grauw

Enlighted (7405)

13-03-2017, 18:39

Nice work KdL and contributors!

By KdL

Paragon (1121)

13-03-2017, 20:04

Thanks Grauw! In June 2016 I sent you a email with a possible fix of H-SYNC for the VGMPLAY.

ELSIF(
   ((REG_R9_Y_DOTS = '0') AND (VDPR9PALMODE = '0') AND (PREDOTCOUNTER_YP_V = 236)) OR
   ((REG_R9_Y_DOTS = '1') AND (VDPR9PALMODE = '0') AND (PREDOTCOUNTER_YP_V = 246)) OR
   ((REG_R9_Y_DOTS = '0') AND (VDPR9PALMODE = '1') AND (PREDOTCOUNTER_YP_V = 260)) OR
   ((REG_R9_Y_DOTS = '1') AND (VDPR9PALMODE = '1') AND (PREDOTCOUNTER_YP_V = 270)) )THEN
PREWINDOW_Y_HS <= '0';

Do you have time to test this fix?
20170313_esemsx3_vgmplay_fix_v1_for_testing_purposes_only.7z

@ro: thanks for editing the tags!

By ro

Guardian (4005)

13-03-2017, 20:23

KdL wrote:

The package OCM-PLD is for 1chipMSX and Zemmix Neo.

Topic: Challenges
Tags: OCM, Firmware, 1chipMSX, Zemmix Neo

Check

By Grauw

Enlighted (7405)

13-03-2017, 22:05

KdL wrote:

Thanks Grauw! In June 2016 I sent you a email with a possible fix of H-SYNC for the VGMPLAY.

Do you have time to test this fix?
20170313_esemsx3_vgmplay_fix_v1_for_testing_purposes_only.7z

Ah KdL, sorry for forgetting about that! I’ve just tested it:

At 60 Hz, it plays at the correct tempo now. At 60 Hz VGMPlay generates interrupts on lines 0, 52, 104, 156 and 208. Screen 0 has 192 lines by default, so it does seem to generate interrupts in vblank now.

At 50 Hz, it still has problems, it’s playing too slow and the tempo is also very irregular. At 50 Hz VGMPlay generates interrupts on lines 0, 51, 102, 153, 204 and 255.

The irregular tempo at 50 Hz is new, suggesting that one out of six interrupts is sometimes-fired, sometimes-not. I’m guessing it has problems with the interrupt at line 255, perhaps it is either not always firing somehow, or maybe it is reset or the flag is masked when it reaches the next line so that it’s easy to miss? Just some guesses…

(Background info: VGMPlay’s OCM workaround option /o switches to 60 Hz and enables 212 lines mode in screen 0 temporarily, so that it can catch that interrupt on line 208.)

By doctorxyz

Supporter (7)

13-03-2017, 21:47

KdL, Thanks a lot for this release... Keep up with your great and precious work! BR,

By KdL

Paragon (1121)

13-03-2017, 23:17

Grauw wrote:

KdL wrote:

Thanks Grauw! In June 2016 I sent you a email with a possible fix of H-SYNC for the VGMPLAY.

Do you have time to test this fix?
20170313_esemsx3_vgmplay_fix_v1_for_testing_purposes_only.7z

Ah KdL, sorry for forgetting about that! I’ve just tested it:

At 60 Hz, it plays at the correct tempo now. At 60 Hz VGMPlay generates interrupts on lines 0, 52, 104, 156 and 208. Screen 0 has 192 lines by default, so it does seem to generate interrupts in vblank now.

At 50 Hz, it still has problems, it’s playing too slow and the tempo is also very irregular. At 50 Hz VGMPlay generates interrupts on lines 0, 51, 102, 153, 204 and 255.

The irregular tempo at 50 Hz is new, suggesting that one out of six interrupts is sometimes-fired, sometimes-not. I’m guessing it has problems with the interrupt at line 255, perhaps it is either not always firing somehow, or maybe it is reset or the flag is masked when it reaches the next line so that it’s easy to miss? Just some guesses…

(Background info: VGMPlay’s OCM workaround option /o switches to 60 Hz and enables 212 lines mode in screen 0 temporarily, so that it can catch that interrupt on line 208.)

Ok. Are you sure on these limits?
60Hz 192lines => (PREDOTCOUNTER_YP_V = 236)
60Hz 212lines => (PREDOTCOUNTER_YP_V = 246)
50Hz 192lines => (PREDOTCOUNTER_YP_V = 260)
50Hz 212lines => (PREDOTCOUNTER_YP_V = 270)

By Grauw

Enlighted (7405)

14-03-2017, 01:21

Yes, looking at appendix 7-2 and 7-3 of the V9938 application manual, those seem correct, those are the number of lines between the first display line and the first top border line.

Anyway, I’m a dummy in VHDL, but maybe I found a few possible problem spots:

-- HSYNC INTERRUPT
HSYNCINT_N  <=  '1' WHEN( ( REG_R0_HSYNC_INT_EN = '0' ) OR ( ENAHSYNC = '0' ) )ELSE
                REQ_HSYNC_INT_N;

Why is that OR ( ENAHSYNC = '0' ) there? If I understand it correctly, when PREDOTCOUNTER_YP_V reaches the end value, ENAHSYNC will reset for a while (to sync with the VGA field?), and because of this /IRQ will go high too...? I think /IRQ should only reset when the status register is read, there should not be a “gap” in the IRQ signal.

IF( CLR_HSYNC_INT = '1' OR ( ( W_VSYNC_INTR_TIMING = '1' ) AND ( V_BLANKING_START = '1' ) ) )THEN
    -- H-BLANKING INTERRUPT CLEAR
    FF_HSYNC_INT_N <= '1';

If I read this correctly, this clears the h-blanking interrupt automatically when v-blanking starts. I don’t think that’s supposed to happen. This might also be the problem.

Note that in VGMPlay, when I set the interrupt to occur at line 255, at 50 Hz 192 lines it occurs on the 9th line of the top erase time of the next field, and at 50 Hz 212 lines it occurs on the 2nd line of the synchronise signal. And because the BIOS ISR also occurs, there can be some delay before I’m actually handling the interrupt, so it is important that it stays active until it’s cleared.

Side note: one other oddity of the V9938 I know about, is that the FH flag behaves differently depending on whether IE1 is set. When IE1 is not set, FH goes up at the start of the right border of IL and goes down at the start of the next left border. But this has nothing to do with VGMPlay’s issue, and it’s probably not so important to emulate, just fyi.

By KdL

Paragon (1121)

14-03-2017, 12:45

ok... I write to you in pvt for the next test.

By KdL

Paragon (1121)

14-03-2017, 20:16

Grauw wrote:

At 50 Hz, it still has problems, it’s playing too slow and the tempo is also very irregular. At 50 Hz VGMPlay generates interrupts on lines 0, 51, 102, 153, 204 and 255.

All turbo-cpu modes are ok at 50Hz with VGMPLAY. Only at 3.58MHz it plays irregularly.
I think it could be a slow response by the Altera Cyclone I.
A nice idea could be test this fix on a board with Altera Cyclone II.

Note: I could be enable a "special custom-speed 3.58 MHz" when the PAL-MODE is ON.

By Grauw

Enlighted (7405)

14-03-2017, 23:31

Mmhh, I suspect that in turbo mode the BIOS ISR just completes sooner, winning a race condition and letting the VGMPlay ISR intercept the interrupt in time before it’s lost… this would back up the ENAHSYNC or int clear scenario. Except I’ve tested those builds you sent me where you disabled those and they did not change the outcome .

I emailed you some test results. Tests on my turboR seem to confirm that line interrupts stay active until they’re handled (try VDP(20)=100:VDP(0)=VDP(0) OR 16: crashes). (Also that at 60 Hz line interrupts can only go up to line 234, interesting detail for us programmers.)

By spl

Paragon (1461)

15-03-2017, 11:31

Great news! Thanks very much, KdL! :-)

By KdL

Paragon (1121)

15-03-2017, 12:01

Grauw wrote:

Mmhh, I suspect that in turbo mode the BIOS ISR just completes sooner, winning a race condition and letting the VGMPlay ISR intercept the interrupt in time before it’s lost… this would back up the ENAHSYNC or int clear scenario. Except I’ve tested those builds you sent me where you disabled those and they did not change the outcome .

I emailed you some test results. Tests on my turboR seem to confirm that line interrupts stay active until they’re handled (try VDP(20)=100:VDP(0)=VDP(0) OR 16: crashes). (Also that at 60 Hz line interrupts can only go up to line 234, interesting detail for us programmers.)

a new fix is ready and it seem to be ok now
pls check your inbox, I'll wait your reply

By KdL

Paragon (1121)

16-03-2017, 20:56

OCM-PLD Pack v3.3.1 (2017.03.16) is out!

v3.3.1 [2017.03.16] [KdL's Updates!]

- Updated the scripts to compile and collect the firmwares.
- Fixed the issue of VGMPlay by improving the accuracy of H-SYNC signal, thanks to Grauw.

By spl

Paragon (1461)

17-03-2017, 09:34

KdL wrote:

OCM-PLD Pack v3.3.1 (2017.03.16) is out!

v3.3.1 [2017.03.16] [KdL's Updates!]

- Updated the scripts to compile and collect the firmwares.
- Fixed the issue of VGMPlay by improving the accuracy of H-SYNC signal, thanks to Grauw.

Thanks for your fast fixes :-)

By toughkidCST

Rookie (19)

18-03-2017, 12:48

mglOcm v1.834f [2017.03.03] - 1chipMsx Romfile Loader for KdL's 1chipMSX is out too!

[Download Link here]
https://drive.google.com/file/d/0B9ug5x4XhMb9bWJ1QkpLM084NDQ/view

By KdL

Paragon (1121)

18-03-2017, 15:16

By KdL

Paragon (1121)

18-03-2017, 15:19

toughkidCST wrote:

mglOcm v1.834f [2017.03.03] - 1chipMsx Romfile Loader for KdL's 1chipMSX is out too!

[Download Link here]
https://drive.google.com/file/d/0B9ug5x4XhMb9bWJ1QkpLM084NDQ/view

thanks a lot!! :)

By toughkidCST

Rookie (19)

18-03-2017, 15:23

I always appreciate your great works.
Thanks a lot~~~

By KdL

Paragon (1121)

18-03-2017, 19:47

By KdL

Paragon (1121)

22-03-2017, 02:24

OCM-PLD Pack v3.3.1 (2017.03.22) "REPACKED"
- Zemmix Neo "BR" variants were recompiled.
- Updated the 'history.txt' and 'mglOcm'.

Quote:

Yesterday Marcelo wrote in pvt of video glitches...

Sometimes random glitches on video or other strange issues could be caused by the optimizations.
This is a very old story with Quatus II because the LEs of 1chipMSX are used to the limits of Cyclone.
On my Zemmix Neo "Red Alluminium Limited Edition" the brazilian firmwares 2017.03.16 were okay.
But the same firmwares on Zemmix Neo "Brazilian Edition" is faulty results.

By KdL

Paragon (1121)

23-03-2017, 04:21

OCM-PLD Pack v3.3.2 (2017.03.23) is out!

- Updated the [msxtools\] folder.
- Video luminance adjustments and other minor fixes.

Notes:
- Sometimes random glitches or other strange issues could be caused by the optimizations of Quartus II.
In these situations you can recompile the project with the 'iplrom.vhd.alternative' file.
- Some games go to black screen using 'ep.com'. I suggest to retry enabling two disk drives via 'eset.com'.

By KdL

Paragon (1121)

23-03-2017, 13:40

Today, the brazilian user Marcelo have confirmed to me that the Zemmix Neo Bazilian is working with regular version 3.3.2 and not working with the alternative version. This test has confirmed that the issues are bypassed with a trick of the optimizations.

The 'iplrom.vhd' can be used to recompile the entire project by yourself in many variants. Just change the two bytes as shown below.

[ iplrom.vhd ]

-- the next two bytes are used to overcome any issues caused by the optimizations of Quartus II
X"84",X"21"

By KdL

Paragon (1121)

23-03-2017, 21:58

By KdL

Paragon (1121)

27-03-2017, 02:15

OCM-PLD Pack v3.3.2 (2017.03.27) "REPACKED"
Fully recompiled using var4128 for better compatibility. Luminance is ok now.
Sorry for any inconvenience caused. ^^'

By spl

Paragon (1461)

30-03-2017, 18:39

Thanks again for your work KdL!

By -Neo-

Champion (365)

25-04-2017, 23:27

Hi KdL, I got it all working fine today on my Zemmix Neo Brazilian. Love it! Thanks for the great job.

I am curious about the notes: You state that the Nextor kernel will be supported by future releases. I assume that means it's not supported in this one? I saw on your twitter account some Nextor versions but that seams quite expirimental.

By KdL

Paragon (1121)

28-04-2017, 00:03

-Neo- wrote:

Hi KdL, I got it all working fine today on my Zemmix Neo Brazilian. Love it! Thanks for the great job.

I am curious about the notes: You state that the Nextor kernel will be supported by future releases. I assume that means it's not supported in this one? I saw on your twitter account some Nextor versions but that seams quite expirimental.

Nextor will be supported from the next release.

By -Neo-

Champion (365)

28-04-2017, 11:02

@KdL That's great! Looking forward to it. Thanks.

By KdL

Paragon (1121)

07-06-2017, 23:52

OCM-PLD Pack v3.3.3 (2017.06.07) is out!

Minor fixes and improvements in this release.
Sorry, the Nextor support will be out from v3.4

By mfeingol

Master (254)

08-06-2017, 06:18

I just saw the note about SDHC support. Does this mean that SDHC cards will now work?

By KdL

Paragon (1121)

08-06-2017, 14:31

mfeingol wrote:

I just saw the note about SDHC support. Does this mean that SDHC cards will now work?

yes

By toughkid

Supporter (14)

08-06-2017, 15:11

Sweet

By WORP3

Paladin (803)

08-06-2017, 17:10

Hi KdL, this is also the version where the switched I/O has been fixed ? Can't find it in the above update description....

By KdL

Paragon (1121)

08-06-2017, 18:32

yes it is...

v3.3.3 [2017.06.07] [KdL's Updates!]

- New Hex-files 304kB from OCM-SDBIOS Pack v1.9.2 with MSX3 Final Release and Zemmix Neo logos.
"UK layout with backslash" is the default profile from now.
- New 'pld_collector.cmd' script, a simple collector tool for testing more PLDs.

Directory of A:\PLD333

FLASH.BAT            70 
OCM2P-BR.PLD    524.288 
OCM2P-ES.PLD    524.288 
OCM2P-FR.PLD    524.288 
OCM2P-JP.PLD    524.288 
OCM2P-UK.PLD    524.288 
OCMX3-BR.PLD    524.288 
OCMX3-ES.PLD    524.288 
OCMX3-FR.PLD    524.288 
OCMX3-JP.PLD    524.288 
OCMX3-UK.PLD    524.288 
PLDFLASH.COM      2.304 
ZEMBR-BR.PLD    524.288 
ZEMBR-ES.PLD    524.288 
ZEMBR-FR.PLD    524.288 
ZEMBR-JP.PLD    524.288 
ZEMBR-UK.PLD    524.288 
ZEMKR-BR.PLD    524.288 
ZEMKR-ES.PLD    524.288 
ZEMKR-FR.PLD    524.288 
ZEMKR-JP.PLD    524.288 
ZEMKR-UK.PLD    524.288

- Fixed access to port $40 for external cartridges, thanks to WORP3.
- Enabled "Balanced" and "Extra Effort" synthesis settings to improve compatibility, thanks to Fabio Belavenuto.

Notes:
- The Nextor kernel will be natively supported by future releases.
- Sometimes random glitches or other strange issues could be caused by the optimizations of Quartus II.
In these situations it is suggested to recompile the project by replacing 'iplrom.vhd' with the alternative
'iplrom.vhd.var8421' or by replacing 'emsx_top.qsf' with the alternive 'emsx_top.qsf.area'.
- Some games go to black screen using 'ep.com'. I suggest to enable two disk drives via 'eset.com' and retry.

Some known issues:
- The timings of VDP TH9958 are too fast: the intros of Fray and Space Manbow confirm the issue.
Hint! The most of Microcabin games can run better with the 'runit.com' tool.
- The 'Break' command of ESE-PS2 module do not work during the hard reset or if you unplug the keyboard at warm.
- Sometimes the SD-Card is not detected after a hard reset but you can re-insert it on the fly to solve.

By DamnedAngel

Expert (75)

10-09-2017, 00:53

I missed this annoucement back then, and now KdL's web site announces that "AN IMPRESSIVE UPDATE IS COMING...". Will the update be of the web site itself or of OCM and Zemmix's firmware? Anyone knows about dates?

By KdL

Paragon (1121)

11-09-2017, 11:18

I'm in testing ... please wait a few hours/days.

By DamnedAngel

Expert (75)

13-09-2017, 13:54

Hi KdL,

thanks for the feedback. I am patiently, but excitedly, waiting .

By fernando.collazo.5682

Master (226)

15-09-2017, 21:53

Wow! Less than 24 hours!!!

Maybe Turbo-R will be added?

By Grauw

Enlighted (7405)

15-09-2017, 23:47

Haha, I hadn’t seen the counter on the site, nice tension building KdL .

(@fernando It’s counting up though, so KdL is a bit delayed I think .)

By KdL

Paragon (1121)

16-09-2017, 21:37

I'm sorry... not fully working MSX turbo-R for now but only "MSX-BIOS V4.1 support".
The main intent of the new release is the future evolution of OCM in a compatible MSX turbo-R machine!

By KdL

Paragon (1121)

17-09-2017, 15:42

Testing is finally complete. The new packages will be out in 24/48h.

OCM + MSX-BIOS V4.1: the S1990 and R800 emultation could be not impossible now!

By journey

Champion (276)

19-09-2017, 14:18

KdL wrote:

Testing is finally complete. The new packages will be out in 24/48h.

OCM + MSX-BIOS V4.1: the S1990 and R800 emultation could be not impossible now!

Great work Luca!!

By fernando.collazo.5682

Master (226)

20-09-2017, 01:27

Wow! every new release is a surprise!
I´m looking forward, keep the awesome work KdL

By mtn

Master (247)

21-09-2017, 16:24

Fantastic!!

Or damn, am I dreaming?

KdL: Are you actually implying there will be R800/Turbo-R compatibility in the future?

By KdL

Paragon (1121)

21-09-2017, 19:43

yep, at least I hope so!

By mtn

Master (247)

22-09-2017, 19:10

KdL wrote:

yep, at least I hope so!

I wish for your hopes and dreams to come true!

By KdL

Paragon (1121)

22-09-2017, 20:16

OCM-PLD Pack v3.4.1 (2017.09.22) is out! ;)

By aurix72

Resident (34)

25-09-2017, 13:23

Excellent work
Never tried your releases on my OCM, but i promised myself to trying the releases ASAP.

Keep up the great job you're doing !!!

By -Neo-

Champion (365)

26-09-2017, 18:06

Hi KdL, I flashed my Zemmix Neo Br with the corresponding UK version for it and that succeeded (checked with firminfo). However, although I put NEXTOR.SYS in the root of the SD card, it won't boot Nextor and also the Basic version is still 3.0 whilst I would expect Basic version 4.1. Maybe I should do something with that SDBIOS file I have but I don't know how to use it and can't find a manual about it. It seems Windows stuff but I run linux. Can you help out?

By -Neo-

Champion (365)

26-09-2017, 19:37

I succeeded by getting my old windows laptop but now I run into another issue. I am able to install on a 2GB SD card I have but when I try my 32GB SD it isn't recognized and it boots into basic. The SD card has 8 partitions of 4GB. That should work right?

By -Neo-

Champion (365)

27-09-2017, 01:15

All good now. For if others run into such issues: You need to go into the "make" directory under Windows and run new-sdcard.cmd which will install everything to get you started. You can choose there which options you want, including the expirimental Nextor and Turbo-R bios options. Also make sure you created a FAT16 with a MAX of 4095MB's. After that you can create an extended partition with logical volumes in it. I have now 32GB available for MSX stuff, MODs, MP3 etc.

By KdL

Paragon (1121)

27-09-2017, 14:26

it was not that difficult

By -Neo-

Champion (365)

27-09-2017, 15:31

Haha, indeed, once you figure out that your partitions are 4096 instead of 4095 and you really need to have the OCM-BIOS.DAT file as the first one on the partition.

I wonder though why it works so picky by demanding that you put that OCM-BIOS.DAT file as the first file on the SD card. Is it because the file system (Nextor) is only activated later and the OCM needs to assume that the BIOS is in the first sectors of the partition as it can't read filenames yet?

I must say everything seems to work great till now given the fact that I run the expirimental Turbo R BIOS and Nextor. What do you need to implement more to get Turbo R complete? R800 only?

On your twitter you also mention that you can't flash the PLD with Nextor with PLDFLASH.COM. Will there be a future version of PLDFLASH.COM that will enable you to flash under Nextor?

By KdL

Paragon (1121)

27-09-2017, 20:41

R800 --> I'm sorry, I do not see the future but I will do my best!

In the OCM-SDCREATE, used by 'new-sdcard.cmd', the max lenght for FAT16 partition is assigned by DISKPART: if SDHC lenght > 4GB ( set partsize=4095 ) else ( set partsize=null ).
So 4096 MB? I do not know how this is possible or maybe a bug of DISKPART or your partition tool have it.

SDBIOS is needed for Nextor kernel because SRAM used by EPCS4 is too small and any compression of data will lengthen the boot time of OCM.
The use of 1st file is the best choice for loading fast the SDBIOS (check inside the '.asm' file of IPL-ROM loader for more details).

PLDFLASH: the NEXTOR16.ROM patched by yuukun-OKEI is not fully compatible for now and also other tools for ESE-MEGASD are not working, EP.COM, ESET.COM, etc.
I always fix the issues when they are reported and considering that it is not all done by me, there is no time to rewrite everything.

By Samor

Paragon (1986)

17-02-2018, 19:41

@KdL Nextor indeed boots when I use your script, but if I try to do this process manually (and copying the bios file first) it doesn't? What is the magic part that I am missing?

I format the card in fat 16, copy ocm-bios.dat first, then the system files (msxdos2.sys, nextor.sys, command2.com). The result boots msxdos2, not nextor.

By Sebbeug

Master (190)

17-02-2018, 20:16

Use sdcreate.cmd which is a KdL's script to configure your SD card with OCM-bios.dat
You will have a fully working SD card with tools under Nextor !
(available with OCM-SDBIOS Pack v2.1)

By Samor

Paragon (1986)

18-02-2018, 10:53

Yes, and I use it, but I am curious why I can't get it to work manually.

By KdL

Paragon (1121)

19-02-2018, 03:07

Samor wrote:

Yes, and I use it, but I am curious why I can't get it to work manually.

The script guarantees that the "Volume System Information" folder has been removed.

By Samor

Paragon (1986)