AD9213 TRIG_X and Source Code

Hi ITRIHW 

Thanks for using AD9213.

Kindly give time for the product owner (jmoreno5 ) to look into this and provide their response.

Hi JAlipio ,

Just a gentle follow-up on this thread.

We wanted to check if there is any update from the product owner (jmoreno5 ) regarding the AD9213 TRIG_x behavior.

This information would be very helpful for our ongoing evaluation and test planning.

Please let us know if any additional details are needed from our side.

Thank you very much for your support.

Hi JAlipio ,

Following up on the AD9213 TRIG_x behavior question.

The customer is progressing with evaluation and test planning, and this clarification would be helpful for their next steps.

Please let us know if there is any update from the product owner (jmoreno5 ), or if additional information is needed from our side.

Thank you for your support.

Hi ITRIHW ,

Apologies for delay response.

To proceed with the fpga reference design code, we need the customer information register to myanalog and email us directly the registered work email address. I'll get back to you regarding your other concern. Thanks.

Hi jmoreno5 ,

Thank you for the update.

I will submit a Technical Support Case using my registered MyAnalog work email address (ITRI) to proceed with the FPGA reference

design code.

Looking forward to your follow-up on the other concern.

Thanks again.

Hi ITRIHW ,

Once we have your information, we will send the reference code thru Secure Software Download, an email link for you to download the code.

As for your other concern, Trig_x is a dedicated differential trigger input used to synchronously command digital event most notably NCO/DDC profile changes and NCO phase sync for fast frequency hopping and multi-chip alignment in. It has no direct impact on ADC sampling process and has no capability on controlling ADC sampling start point, the encode clock has direct impact in ADC sampling process not the Trig_x.

As for the register configuration, the datasheet on p.42 provides step by step in setting up multichannel NCO features including enabling the Trig_x function. I'll get back to you once I could find a sample register writes for NCO features utilizing the trig_x function.

Thanks.

Hi jmoreno5 

Thank you for the detailed explanation.

We understand that TRIG_x is used to synchronously control digital events, such as NCO/DDC profile switching and NCO phase

alignment, and that it does not control the ADC sampling start point, which is determined by the encode clock.

We also understand that SYSREF_x is responsible for establishing and resetting NCO phase coherence.

It would be very helpful if you could share a sample register write sequence or reference procedure for enabling and validating TRIG_x

based NCO channel switching, particularly for a single AD9213 device.

In addition, we would like to ask whether TRIG_x activity or its effect can be observed or confirmed via the ACE Tool, for example through:

• Register status or flags

• Observable NCO/DDC behavior

• Phase continuity or frequency switching behavior

• Any other recommended indicators (ACE or FPGA side)

For your reference, we have already received the confirmation email from Analog Devices Technical Support, and we have replied to that email accordingly.

Thank you very much for your support.

We look forward to your guidance.

Hi jmoreno5 ,

Just a gentle follow-up on our previous question regarding TRIG_x validation on AD9213.

Could you please let us know if there is any update when you have a moment?

Thank you very much for your support.

Hi jmoreno5 ,

Hope you are doing well.

Just a kind follow-up on our TRIG_x validation question for the AD9213. When you have a moment, we would greatly appreciate any

update you may have.

Thank you very much for your support.

Hi jmoreno5 ,

Just checking in on our TRIG_x validation question for the AD9213.

Any update or suggestion when convenient would be greatly appreciated.

Thank you for your support.