No-os: Issue with Custom LVDS Profiles on Custom ADRV9002 Board Using TES Application

We are experiencing an issue with custom LVDS profiles generated using the TES application on our custom ADRV9002 board. Here are the details:

1. Setup:

   • We have successfully booted both our custom ADRV9002 board and the ADRV9002 evaluation board using the default LVDS profile and stream supplied with the No-OS application.
   • However, when we generate a custom profile and stream using the TES application (tested with versions 0.24.1 through 0.26), the custom board fails during the initial steps, while the evaluation board starts up without issues.

2. Observations:

   • Each run on the custom board with a custom profile returns a different error.
   • When comparing the profile.json files generated by TES for the default and custom profiles, the only significant difference observed is the "lna_type".
   • The failure occurs inconsistently during initialization—sometimes during the RX phase, other times in different steps of the startup sequence.
   • The main reason for this investigation is that our custom board works successfully with Petalinux 2021.1 based on the ADI Kernel v5.10. However, we aim to migrate to Petalinux 2023.1 using the latest ADI kernel, where this behavior was first noticed.

3. Question:

   • Could the "lna_type" or other hidden factors in the profile.json be causing this inconsistency on the custom board?
   • Are there known differences between kernel versions or Petalinux environments (2021.1 vs. 2023.1) that could contribute to this behavior?
   • Are there any recommended debugging steps or specific configurations to address this issue during the kernel and Petalinux migration?

Your insights or suggestions on resolving this discrepancy would be greatly appreciated.