Kyu,
I am using ML605 rev D. The steps to reproduce the error are pretty simple.
1) Generate the ISE project using 4DSP's tools.
2) Build the project in ISE 14.1. Program the ML605 using iMPACT.
3) Run the FMC176 app from MS Visual Studio, communicating with the ML605 via Ethernet.
4) Observe the DAC outputs on a scope. If your FMC176 app is (like mine) unmodified, both channels should be outputting a 300MHz sine wave.
5) Set the scope to trigger if the DAC0 output exceeds the normal envelope of the sine wave.
5) Wait and check the scope periodically for a trigger event. On one of my FMC176 boards I did not observe any failures for 30-60 minutes. On the other board it took only 30-60 seconds to see a failure.
I can provide my modified design which pins out the MMCM locked signals if that is useful to you.
I should also let you know that yesterday I got both of my FMC176 boards to work on the board I am using for my product. I discovered that both MMCMs were in fact staying locked when using my carrier board and that the real problem was that the DLL on the AD9129 was failing to lock. For some reason, turning off the duty-cycle correction on the DLL allows it to lock for certain phase settings. Once it locks, it stays locked and the data output is clean.
Jim