Quote:

What is the worst possible situation while using this EMSX_TOP_20080426_005 version? Risk of shortcircuit or something like this?

(1) Sprite below might become non-display from 192 lines due to this bug.
(2) Operation might become unstable. (For instance, it doesn't run in 10MHz mode. )

Why QuartusII did not put out the error is understood.

Quote:

BodyHammeR: MSX 20th Anniversary demo (by Abyss) work fine with OCM-PLD v2.2b (VGA + Z80 at 3,58MHz) www.webalice.it/gnogni

It does indeed - bar some minor graphical glitches. I think I'll keep this update for Outline!

New update PLD:
http://www5d.biglobe.ne.jp/~hra/note/onechipmsx/files/emsx_top_20080501_001.zip

Updates:
(1) 10MHz mode bug fixed.
(2) "Critical Warnning" fixed.
(3) Timing analizer setting fixed for 10MHz mode.

Bug Memo:
(1) Laydock2 is not playable.
(2) MSX2+ Logo is abnormal.
(3) V-Killer sprite blinking.

A fatal bug of 20080426_005 was fixed.
This version gave priority to a fatal bug patch and the stability operation.
Hereafter, the problem of "Bug Memo" will be investigated.

@HRA!: can you explain me, please why the 'OCM VDP ENGINE' is faster than the original? It's because of some tech
limit?

Contents of genuine VDP are not seen.
ESE-VDP is an emulator by hardware.

A part of processing method is different.
For instance, CPU and VDP access one DRAM chip.
The real thing uses three DRAM chips. (CPUx1,VDPx2)
There is a complex mechanism to conceal this difference.

It is very difficult to make it to the same speed.

It is helpful when there is a means to measure the speed.

New update PLD:
http://www5d.biglobe.ne.jp/~hra/note/onechipmsx/files/emsx_top_20080501_002.zip

Updates:
(1) H-SYNC timing fixed.
(2) [F12] key CPU clock toggle added.

Memo:
Laydock2 playable.

Bug Memo:
(1) Sprite undisplay at Y=1.
(2) Player on "arkanoah" undisplay.
(3) MSX2+ Logo is abnormal.
(4) V-Killer sprite blinking.
(5) VDP Command is faster than real VDP. (unconfirmed)

@HRA!, Good work!
Do you know what is the behaviuor of OCM if, during a vdp command the cpu writes on port 0x98?
On the real thing no problems occour, the data is transferred as if there is no vdp command active.
If you want to test on OCM i can send a test program (.COM)

Quote:

If you want to test on OCM i can send a test program (.COM)

Please send it to me.

mail address:
http://www5d.biglobe.ne.jp/~hra/image/address.gif

New update PLD:
http://www5d.biglobe.ne.jp/~hra/note/onechipmsx/files/emsx_top_20080502_001.zip

Update:
(1) H-SCROLL synchronize timing fixed.
--> MSX2+ logo fixed
--> The display of "F1 Spirit 3D Special" has been improved.

Bug Memo:
(1) Sprite undisplay at Y=1.
(2) Player on "arkanoah" undisplay.
(3) V-Killer sprite blinking.
(4) VDP Command is faster than real VDP. (unconfirmed)

New update PLD:
http://www5d.biglobe.ne.jp/~hra/note/onechipmsx/files/emsx_top_20080502_002.zip

Updates:
(1) The bug to which Line#1 of Sprite is not displayed is corrected.
(2) In 212 line mode, the bug to which sprite is not displayed below 196 lines is corrected.
--> [The bug added from 20080502_001]

Bug Memo:
(1) Player on "arkanoah" undisplay.
(2) V-Killer sprite blinking.
(3) VDP Command is faster than real VDP. (unconfirmed)

Alex Wulms should know about the VDP command engine... as he wrote it

Quote:

Alex Wulms should know about the VDP command engine... as he wrote it

I confirm that the VDP command engine in the OCM is faster then in the real MSX. Getting the timing exactly the same is difficult. Ideally, I would need to measure at bus level how the real VDP behaves so that I can build a better model for the state machine but for that I would need to connect a digital scope to my real MSX. Unfortunately I don't have a digital scope so this path to further analyze the timing is not possible for me.

Though, an alternative is to read status register 8 during command execution (it contains the tmpSX value used to keep track of the source-x coordinate during copy commands). By analyzing how this one changes (with screen on or off, with sprites on or off, etc) it should be possible to build a better timing model and improve the OCM accordingly.

It is still on my to-do list to make the test programs and analyze the results.

Kind regards,
Alex

SystemTimer(TurboR compatible I/O port E6h, E7h) is installed in EMSX_TOP_20080502_002.ZIP.
I made the bench mark of HMMM by using it.

HMMM(Sprite ON) of OCM was about genuine twice velocity.

It is difficult to match it completely.
However, it is possible to bring it close a little more

I will add a high-speed mode and the real mode to VDP.

bench mark
http://www5d.biglobe.ne.jp/~hra/note/onechipmsx/files/vdpcmd.zip

FS-A1ST(turbo mode): 18948
BlueMSX turboR emulation: 18872
EMSX_TOP_20080502(3.58MHz mode): 9867

(*)The smaller the value is, the more high-speed.

I want various bench marks.
I want someone to make it

New update PLD:
http://www5d.biglobe.ne.jp/~hra/note/onechipmsx/files/emsx_top_20080502_003.zip

Updates:
1) VDP Command speed fixed.
2) [F12]+[SHIFT] key toggle VDP Command speed added. (Normal/High speed)

Memo:
The speed of the Normal mode of 95% against the real thing. It is a little slow.
The speed of a high-speed mode of 500% against the real thing. It is considerably fast