My programs of AD9371 did not pass Tx_QEC_INIT term,but others of terms passed, why?
please, thanks a lot.
Can you share the init cal status? Use below API
Are you using eval platform?
Thank you !
I use the platform of our design, and not use AD9528. When my programs run TX_QEC_INIT term, the function of MYKONOS_waitArmCmdStatus does not pass always, my program stays in do-while and does not go on. //////
My program passes the fuction of MYKONOS_readArmCmdStatusByte occasionally, and the retVAL of MYKONOS_getInitCalStatus is MYKONOS_ERR_OK. The information of UART displays below:
AD9371 ARM version 5.1.1
Unknown error was encountered.
Additionally,our design only uses SPI to control AD9371 without any GPIO.
When you run MYKONOS_waitInitCals() try increasing time out and try?
What is the LO frequency you are running?
Try running lower LO freq(1G,2G)
Thank you !
I have done that as your ways above, and tried running low LO freg(1G)with increasing time out, but it seems ineffective.
Are you using a custom board and which s/w build of API?
Is it Linux driver or No-OS?
How do you get these UART logs. Are you printing this?
You need to figure out what unknown error its mentioning.
Can you check with MYKONOS_abortInitCals() what cals completed . What is the output of MYKONOS_waitInitCals.
Check the output from below sequence.
Thank you very much.
The question of TX_QEC_INIT_cals has been solved,and the cause is that some parameter of DAC is wrong. My board runs No-OS now,but it will run Linux-os.
By the way, AD9371 can run 245.76MHz IQ sample rate with single main RX channel ? if it can, how to set RXframer and JESD204B？
Program TES GUI with your desired configuration and generate a 'C' script which will have all the required initializations including Framer and JESD.
If this configuration is not valid, GUI will show appropriate reason. Make sure you are connected to board while generating a 'C' code.
Retrieving data ...