AnsweredAssumed Answered

AD9371 Multichip Sync Status

Question asked by stevereine Employee on Nov 14, 2016
Latest reply on Nov 16, 2016 by gverma

Hi,

 

This question from a customer, not getting back the expected MCS status, getting 0x0E when 0x0B is expected. Any ideas?

 

thanks,

 

Steve

 

I'm trying to initialize the 9371 and am having some success.  The MYKONOS_initialize() function is returning back success.  Then, trying to follow the procedure outlined in headless.c, I am calling the following

 

uint8_t mcsStatus=0;
// note: if MCS status != 0, then likely a MCS sync error occurred (see mykonos.c)
if( MYKONOS_enableMultichipSync(&mykDevice, 1, &mcsStatus) == MYKONOS_ERR_OK )
{
    printf("MCS ok 0x%x\n", mcsStatus);
}
else
{
    printf("MCS fail 0x%x\n", mcsStatus);
}
// p.34 of Mykonos SW User Guide...pulse SYSREF >=2xs...enableMultichipSync()
if( AD9528_requestSysref(&clockAD9528_, 1) == ADIERR_OK )
{
    printf("pulsed sysref\n");
}
if( AD9528_requestSysref(&clockAD9528_, 1) == ADIERR_OK )
{
    printf("pulsed sysref\n");
}
if( AD9528_requestSysref(&clockAD9528_, 1) == ADIERR_OK )
{
    printf("pulsed sysref\n");
}


if( MYKONOS_enableMultichipSync(&mykDevice, 0, &mcsStatus) == MYKONOS_ERR_OK )
{
    printf("MCS ok 0x%x\n", mcsStatus);
}
else
{
    printf("MCS fail 0x%x\n", mcsStatus);
}

 

From this point, I am printing the mcsStatus from the second MCS call and it is returning back 0x0E.  According to headless.c, this should be returning back 0x0B if the procedure was successful.  Can you provide more details on what may be causing this to return 0x0E instead of 0x0B?

 

Also, we are having trouble getting our JESDB interface up and running.  Would this failure cause the JESDB link not to work properly?

 

Any information you have on this would be appreciated.

Outcomes