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.
Hi,You used make to build the HDL project right?can you do the same for no-OS https://github.com/analogdevicesinc/no-OS/commits/master/ad9739a-fmc-ebz/zc706?According to https://wiki.analog.com/resources/fpga/quick_validation.
Thanks for your reply.
I'm sure that I build the HDL project right. I have followed the steps in https://github.com/analogdevicesinc/no-OS/commits/master/ad9739a-fmc-ebz/zc706?. But when I type "make" and enter in the terminal in the "\no-OS\ad9739a-fmc-ebz\zc706" path, a fatal error happens "../src/ad9739a.h:49:10: fatal error: spi.h: No such file or directory". I don't know why.
I follow your steps above.
Firstly, I extract the .hdf file and get some files. And I run the xsdb terminal.
The following steps are as follows:
I use the ad9739a_zc706.zip file supplied from you.
Hi,Ok. What was the result? UART console.What is the status on the hardware modifications?Andrei
UART console is the same as before.
I haven't do these hardware modifications above. You mean I need to switch to ACLK914 clock path?
Yes and desolder - solder the mentioned components.
I noticed that the pads of the mentioned components are already on the position of the narrow pads closer to the ADCLK914.
After I saw the schematic of the board, I noticed that the output clock of adf4350 is not connected to any ports. Does it mean the adf4350 on the board will not do anything?
After I switch to the ADCLK914, how much input frequency (J3) do I need? Is a random value in 1.6GHz to 2.5GHz okay?
功程292 said:Does it mean the adf4350 on the board will not do anything?
Out of the box, no. adf4350 is there as a second option (enabled by desolder/soldering those capacitors). The reference design considers it as being used.
功程292 said:Is a random value in 1.6GHz to 2.5GHz okay?
From what it can be seen in the datasheet, yes. You can ask more questions regarding the clock in High-Speed DACs forum. Using a 2.5GHz external clock will work with the no-OS reference code, without any modifications.
I thought I seemed to find the problem.
These pictures above are the power supply on AD9739A evaluation board. I have found that there are no connection between JP1 and JP2 on the board. Besides, I have measured the TP12 TP2 TP1 TP3. And there is no voltage on the board! Does it mean I must solder a 0 ohm resistance on JP1 and JP2 pad?
Hi, I've solved the problem and it's working. Thank you for helping me!
Hi, I have a new problem!
I've tried to write the verilog code about spi configuration of the ad9739a evaluation board which has two spi devices (adf4350 and ad9739a). I'm sure that the spi code is working normally because the spi data read from ad9739a is right. But the adf4350 spi doesn't work normally. After I configure the register in adf4350, the LD light on the board isn't on. The debug picture of adf4350 spi are as follows:
the clock frequency of ILA is 200MHz. According to the datasheet of adf4350, the timing is correct.
The data written to r0-r5 register of adf4350 is 0x00320000, 0x00008009, 0x00006e42, 0x00000003, 0x008c823c and 0x00580005.
I don't know why it isn't working.
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.