Moderators: simonsunnyboy, thothy, Moderator Team
When transferring data from the DSP to the CPU on a stock Falcon you only need synchronization for each DSP word transfer on the DSP side. The CPU is slower so only need to check $FFFFA202 for the first DSP word transferred (if you transfer more than one in one go).Emphii wrote:I think, I have some synchronization. On data movement DSP uses continuously jclr and cpu does btst. The rest time they are doing their own job.
I disabled MMU emulation and took off cycle exacts and got these messages: But this can come as a life saver in some other part. Code: Select all
> profile help
'profile' - profile CPU code
Usage: profile <subcommand> [parameter]
Subcommands:
...
- loops <file> [CPU limit] [DSP limit]
...
Detailed (spin) looping information can be collected by
specifying to which file it should be saved, with optional
limit(s) on how many bytes first and last instruction
address of the loop can differ (0 = no limit).HiEmphii wrote:Eero. Thanks for the pro tip.
Exception 2 (e02cde) at e02cde -> e02ce6!
Exception 2 (e0184e) at e0184e -> e01836!
Exception 2 (e0184e) at e0184e -> e01836!
M68000 Bus Error writing at address $fffffa42 PC=$ad63a.
Exception 2 (ad63a) at ad63a -> ad650!
but screen runs on better speedratio. Still data from DSP is not correct, so it is hard to develop a stuff with this.
But I must say that I appreciate all the work team has done. Without you there probably would not be anything nice like this.
Daniel. That's a good tip. I'll check how much influence it has. Anyway, the amount of data in this mentioned screen does not take that much to transfer. There's still job for CPU to do.
I downloaded files from http://antarctica.no/~hatari/latest/windows/win64/ , except HMSA / debug marked files.czietz wrote:They run fine for me, Windows 10 x64, e.g. hatari-win64-release.exe from http://antarctica.no/~hatari/latest/win ... -r7255.zip.
Please, Emphii, provide more details: Which file exactly(!) from http://antarctica.no/~hatari/latest/ are you trying to run? Which Windows version do you use? What is the exact(!) error message?
It's an invaluable job.I'm not familiar with falcon settings, would need to look at the sources, but isn't horizontal resolution supposed to be a multiple of 16 in falcon video, so 600 is not OK ?Emphii wrote:For the screen, this was tested against - Now it runs without forementioned exceptions, and fiddling with the settings, I can reach the original "slowness" of the screen. Still the data from DSP is incorrect (maybe something to do with the M-register?)
problemo.PNG
In console window you can notice ?-mark - I'm not using VDI screen, why it even wants to initialize it?
Hard to tell for the DSP, as I don't have a real Falcon to check. As this is your code, maybe you have the possibility to create a log file when the demo runs to print the data you received from the DSP, then we could compare with the emulated version and try to see which part of the DSP code could be wrongly emulated ? (assuming it's a bug in the dsp part, it could be somewhere else)And the main problem with the data from the DSP is marked with * . This is crawling problem from right to left - It's not in constant place.
I really do appreciate the work you team do for us - "the consumers"
**Edit: In case you want to know, what is reading instead of "Emulation Paused" it's this:
16MHz/030(PF)/- 4MB Falcon, TOS 4.04, RGB 50 Hz
npomarede wrote:I'm not familiar with falcon settings, would need to look at the sources, but isn't horizontal resolution supposed to be a multiple of 16 in falcon video, so 600 is not OK ?
800 is horizontal size, 600 is vertical size. But this was only curiosity, as I don't have "Use extended VDI screen" marked.I'm doing my code with assembler, so no, no logging. I'll try this with other screens as well, but it takes a little more time as I really need to finish my demo. It runs fine on real hw, so I'm happy so far.npomarede wrote: Hard to tell for the DSP, as I don't have a real Falcon to check. As this is your code, maybe you have the possibility to create a log file when the demo runs to print the data you received from the DSP, then we could compare with the emulated version and try to see which part of the DSP code could be wrongly emulated ? (assuming it's a bug in the dsp part, it could be somewhere else)
Nicolas
) Hatari TOS setup code seems to call VDI mode size checks even if VDI mode isn't enabled. I commited a fix for this, as warning about incorrect size can be thought to indicate VDI mode being enabled.Emphii wrote:npomarede wrote:I'm not familiar with falcon settings, would need to look at the sources, but isn't horizontal resolution supposed to be a multiple of 16 in falcon video, so 600 is not OK ?
