Post Go back to editing

Not compatible No-OS branch with vcu118

Thread Summary

The user encountered build errors while using the ADRV9026 project on VCU118 with the 2023_r2 Patch1 release and Vivado 2023.2. The issue is a type desynchronization in the `adrv9025_spi_read` function between `adrv9025.c` and `adrv9025.h`. The final solution suggests either switching to the main branch and Vitis 2025.1, or manually changing the type from `unsigned int` to `uint32_t` in the 2023_r2 branch. The user should also ensure all submodules are updated using `git submodule update --init --recursive`.
AI Generated Content
Category: Software
Product Number: adrv9026

Hi,

I'm using the ADRV9026 project on VCU118 with the 2023_r2 Patch1 release and Vivado 2023.2.

I generated the XSA from the HDL 2023_r2 branch, but when I build the corresponding no-OS project, I run into build errors.

Could you please clarify which exact branches/tags/commits should be checked out for HDL and no-OS for the ADRV9026 project on VCU118?

Specifically, could you tell me:

  • Which HDL branch/tag/commit you used?

  • Which no-OS branch/tag/commit you used?

  • Which checkout commands you use for the no-OS repository?

  • Whether an XSA generated from the HDL 2023_r2 branch with Vivado 2023.2 is expected to work directly with the no-OS 2023_r2 branch for ADRV9026 on VCU118?

For example, are you using something like:

git clone github.com/.../no-OS.git
cd no-OS
git checkout 2023_r2

or a specific tag/commit instead?

I'm trying to make sure all repositories are aligned with the correct release and tool versions.

Thank you.

Edit Notes

adrv9026
[edited by: HIRONEGAR at 5:05 AM (GMT -4) on 25 Jun 2026]

Thread Notes

Parents Reply Children
No Data