Post Go back to editing

no-OS code of AD9379A?

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
  • Hi, I have met an interesting problem.

    When I download and debug the ADI reference design (hdl and no-os projiect), sometimes the LD light is on, sometimes it isn't. Besides, sometimes the chip_id of ad9739a can be read successfully, sometimes it can't. But the DLL of ad9739a always can't be locked. I'm sure I'm using the same code and the jumper jumps to FMC source.

Children
No Data