"does it have any influence on flow of program if com int has already occured and no write in mcomp has been done?"
let's assume 1 has been written in MCOMP and directly after this write access overflow of mtim occurs, what leads to right shift of MCOMP (MCOMP>>1 equal 0). 0 is not allowed in mcomp!!!
Let's have a look on Z capture and underflow event. We see the bar with "Compute MCOMP". for a hardware commutation it could be ok, but what about sim commutation. if com int has already occured and no access in mcomp has been done. occurres z capture with mtim underflow what calculates some value and leads to next com int. but i don't need this value, i need exactly mine. I suppose it should be notice for this bar "only for hardware commutation".
Retrieving data ...