Ok for me,
The target clock was not running and that's why it didn't complete what is a bit disturbing because the reference clock is running I expected to get 0 as result.
Fortunately I see this comment on the online API :
/* Start a measurement cycle and wait for it to complete. If the target
clock is not running, the measurement cycle will remain active
forever, so a timeout may be necessary if the target clock can stop. */
Unfortunately it is not mentionned neither in the user manual neither in the SDK documentation.
Yoann