Post Go back to editing

no-OS code of AD9379A?

Thread Summary

The user encountered issues with the AD9739A FMC evaluation board on the Xilinx ZC706, including missing 'spi.h' and 'DAC Core Status errors'. The problem was resolved by using the 2018_R2 branch of no-OS and ensuring the correct clock path (ADCLK914) was enabled. A new issue with inconsistent behavior of the LD light and DLL lock was identified, but the user confirmed the AD9739A is now working.
AI Generated Content

Hello! I'm using the Xilinx ZC706 evaluation board and AD9379A FMC evaluation board.

According to https://wiki.analog.com/resources/fpga/docs/build#windows_environment_setup, I have built a vivado HDL project.

Besides, I have built a no-OS project in SDK according to https://github.com/analogdevicesinc/no-OS/tree/master/ad9739a-fmc-ebz. But the makefile can't  be used because "spi.h" is missed. I'm sure that I used the latest version.

So I add these .c and .h files to SDK project manually. And I have seen that the "spi.h" in https://github.com/analogdevicesinc/no-OS/tree/master/include isn't right and it can be represented by the "platform_drivers.h" in https://github.com/analogdevicesinc/no-OS/tree/master/common_drivers/platform_drivers. So the "include spi.h" in some .c files are modified to "include platform_drivers.h" by myself.

And I found that the "config.h" needs to be modified to meet the corresponding development board. After all the steps are done, I run the debug. But when running to the "dac_setup(&ad9739a_core)", "DAC Core Status errors" is shown in the SDK terminal. I don't know why.

Parents Reply Children