Hi Arnaud,
Thanks for your reply. I have a KC705 and ML605 to test with in addition to the VC707.
I tried the KC705 first with 253_kc705_fmc126.bit and with Fmc12xApp.exe, but was getting a timeout error around line 345 of main.cpp (see below excerpt) where the code attempts to obtain the sipcid table.
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// Obtain and display the sip_cid informations to the console. This function also check that the constellation ID
// obtained by the firmware match the value passed as argument
rc = cid_init(0);
if(rc<1) {
printf("Could not obtain sipcid table (error %x), exiting\n", rc);
sipif_free();
return -3;
}
I tried running the code and this error was repeatable.
I next tried the ML605 and was able to successfully run Fmc12xApp.exe (see attached screen capture of the cmd window output), and although there were no errors reported by the pattern check after idelay calibration, when I look at the ADC data from the subsequent DMA transfers in Wireshark, it looks like there are patterns other than the flashing 11 (0x7ff) in the chan D (ADC3) data. See attached screen capture of Wireshark for good chan C and bad chan D data. I commented out a small segment of code in lines 337-349 of fmc12x_adc.cpp to keep the ADCs in the flashing 11 test mode for the subsequent DMA transfers, but the code is otherwise the original Fmc12xApp.exe.
I have also attached the screen captures of the cmd window and Wireshark data for the VC707 with FMC126 case, so that you can see the constant pinning of chan D, bit 5 to the high position. I will add these to the next post since the attachment limit is 4 per post.