The general timings of Hatari in Falcon mode are quite good and quite aproximatives at the same time

For general emulation, the result is useable (many programs,; music, demos, ...) work correctly.
But in some conditions, the timings are wrong, resulting in music distortion or glithes, freezing of the program (falcamp, ...)
The cpu code manages cache/no cache mechanisms, but the timings are quite wrong.
I started to implement a static table with the 68030 falcon timings, I use it with the new CPU, but it's far from being accurate. (and the static way is probably not the best approch for an emulator).
The problem is that I reach my limits here, but hatari-falcon would benefit a lot of a better cycles timings emulation.
The DSP timings should be OK (in term of cycles) taking into account the inner or external dsp ram access timings.
I've reworked it last year.
But the DSP cycles are given by the cpu cycles (which in hatari is the main clock of the whole emulator).
If the cpu cycles counter is wrong, the dsp will execute a wrong number of cycles and you can have unsynchronizations that don't exist on the real hardware (like sound distortion or programs freezing because they don't transfer datas in synchronisation with the CPU/DSP)
The help of an expert of 68030 cycles and Falcon architecture would be great for Hatari.
But it's still a huge task to do.
Regards
Laurent