Post Go back to editing

AD9081 Evaluation Board HMC7044 Configuration Errors

Category: Software
Product Number: AD9081-FMCA-EBZ, AD9081
Software Version: ACE 1.30.3369.1491

I am trying to use the AD9081-FMCA-EBZ evaluation board to test a few JESD204C configurations. However, when I try to do any chip view configurations, I receive Error Code: -14 and a notice is displayed that there is a problem with configuring the HMC7044. I am using the on-board LVDS mode reference crystal of 100 MHz for HMC7044 reference clocking (CCPD33CB 100M) and requesting a 234.375 MHz frequency out of the HMC7044. We have verified this is possible on the HMC7044 standalone evaluation board.

When I apply a board preset configuration it goes from Figure 1 to Figure 2 and no error pop-up windows appear.

Figure 1: ACE AD9081 Board View Before Applying Settings Figure 2: ACE AD9081 Board View After Applying Settings

However, when I apply a chip view custom configuration, it goes from Figure 3 to Figure 4, displaying two pop-up windows relating to clock configuration errors.

Figure 3: ACE AD9081 Chip View Before Applying Settings Figure 4: ACE AD9081 Chip View After Attempting to Apply Settings

These same errors occurred for this configuration (JESD204C TX=24 RX=26 DCM=2 interp=8) when providing a reference clock to the HMC7044 instead of the on-board VCXO. A board preset was configured first to ensure this was not a reference clocking setup issue.

I also attempted to use an external clock and bypass the HMC7044. Similar results followed, the board level presets worked but the chip view configurations did not. The following errors show up when trying to use an external clock instead of the HMC7044. In chip view, I tried using 100 MHz and 234.375 MHz reference signals and changed the chip ref clock setting accordingly. The following errors and the clock configuration setting for the 234.375 MHz value are shown below (the tool automatically rounds up to 234.38 MHz). I tried both clock values with and without the Enable On-Chip PLL setting enabled.

Figure 5: First transaction error when applying chip configurations Figure 6: Second transaction error when applying chip configurations Figure 7: Clock source options

One additional note is that regardless of clocking scheme, if I configure successfully using board view, then configure using chip view and it fails, I cannot configure successfully from board view without restarting ACE. This makes me think that configuring with chip view modifies extra registers somewhere (HMC7044, AD9081, etc.) 

So I have a few main questions: first, is there a resource that lists all of the error codes that one can encounter in ACE? I have done some searching online, but been unsuccessful. Second, I am guessing that there is a problem with how the AD9081 is trying to configure the HMC7044 when I try to use it for clocking or some internal PLL issue when I try using the direct clocking method. Does anyone have ideas/knowledge of what the ConfigureTRX or ConfigureHMC7044 errors indicate or how to solve them? Also is it possible there is some error with the HMC7044 frequency convergence that is preventing us from being able to use this frequency output from the HMC7044?

  • Hi, could you share the ACE session file used for Fig 3 and 4? We'll get back to you on other details.

    -YH

  • The failed session is attached here. Let me know if you need any further information.

    AD9081_FailedSession.zip

  • Following up on this, I realize the HMC7044 issue is due to a clock error where the ACE software rounds to the nearest 0.01 MHz, therefore 234.375 MHz is not allowed as a reference clock. Instead I found a similar setting that uses a 235.5 MHz clock and does not have the HMC7044 error, however still faces a ConfigureTRX error. I am attaching the session file and the log file. Thanks in advance for any help!7-14-2025.zip

  • Thank you for additional information. We'll get back to you either today or tomorrow. We are looking into how your profile can be configued with 100 MHz VCXO into HMC7044. 

  • Firstly, one setting needs to be changed in your configuration as below : the full bandwidth mode should be disabled and set to DDC ON mode.

    With this change based on your latest session file using 235.5 MHz clock from HMC7044, the ADC path seems to be fine, but not sure about DAC path. I have some issue in my platform, so it may be different in your platform. Please try and let me know.

    And also I want to confirm your target configuration. The HMC7044 can generate all of 234.375, 234.38, and 235.5 MHz from 100 MHz VCXO, but somehow I got partial success with 235.5 MHz only, which came from your session file. I'll look into it and will let you know. So is your target configuration 234.375 MHz or 235.5 MHz works for you?

  • Hello yhkim,

    Thanks for taking a look! I have been trying different things with the setup and have resolved some of the previous issues. Due to the rounding of ACE, using a configuration that requires 234.375 MHz with the HMC7044 does not seem possible and throws an HMC7044 error. However, 235.5 MHz works for my applications and I have been using that. Additionally, I did catch the DDC On dropdown offline and that has resolved the ConfigureTRX error. I am still seeing a red light on the ACE chip view dashboard for RX ILAS ERROR and was wondering if this could cause any issues/if there is a clear problem with the setup. Additionally, when trying to perform data captures in the analysis view, a ConfigureChannels error occurs preventing data collection. Do you have any advice on this issue? Thanks!

  • Hello jwilcox,

    Good to hear that we are on the same page. I also assume that the issue of ACE with 234.375 MHz is due to rounding, and probably not hard to overcome if we write C/Python application based on API, but needs further verification. 

    In my platform, I see an issue in DAC path but no issue in ADC path, so I am able to capture the signal with your profile as shown below. I've seen this behaviour before - sometimes power cycling or resitting the FMC card resolve the issue especially at high sample rate configuraiton. And also typically C application running on ADS9 may be more stable so you may want to write C application with API. Please let me know if you need help on this.

    Hope this helps

  • Hello,

    I've tried power cycling the board without success in achieving the RX capture. Do you have any advice on resitting the FMC card or configuring the ADS9 with the C API? Thanks for your help!

  • Hello, I'll try to write a C application using C API and share it with you when working. In the mean time, please take a look at the following document in your API installation folder and try some existing configurations.

    And also, you may want to try Linux/No-OS solution provided by ADI for few popular carrier boards as shown below. 

    https://wiki.analog.com/resources/eval/user-guides/ad9081_fmca_ebz/quickstart

    Hope that helps