Post Go back to editing

AD9910 - Loading the RAM data files without Eval-board

Thread Summary

The user seeks to load RAM data files for a frequency sweep from 250 MHz to 350 MHz on an AD9910 device without an evaluation board. The solution involves using SPI to write start and end addresses to RAM Profile registers, selecting the profile via profile pins, and writing 32-bit frequency words to SPI address 0x16. Key clarifications include setting CFR3[15]=1 to bypass the REFCLK divide-by-2 block and verifying RAM data with RAM Enable set to 0 or 1.
AI Generated Content

 Although it would be a fundamental question, let me ask one question. I want to know how to load the RAM data files without evaluation board.

 Above all, I want to introduce my procedures for loading the RAM data files with the evaluation board and software which were provided by Analog Device. Using evauation board and software, I successfully loaded the RAM data files and I could easily generate some ramp signals which I wanted. To be specific, several detailed conditions are mentioned below.

 - Fsystemclk = 1GHz

 - Start frequency = 250 MHz

 - End frequency = 350 MHz

 - frequency step = 0.1 MHz

 => RAM data files : 250MHz, 250.1MHz, 250.2MHz ~ 352 MHz, 352.1 MHz, 352.2 MHz

                                (# of data = 1024, I attached RAM data files which consists of Hex)

 I loaded these RAM data files using RAM I/O Window in the evaluation software. And then, Using Profiles Window, I designated each RA segment by setting Beginning and Final Address, step rate, and mode control.

 

 What I really want to know about is how I can load the RAM data files without Evaluation software and board. I want to know the similar procedure as I loaded attched text files in the RAM I/O Window when I used Eval-software. I think I might have to use SPI control pin such as SDIO, SCLK, I/O_RESET pins. Could you please let me know the detailed process for loading RAM data files?

250_350MHz.txt.zip
Parents
  • First, be aware that in item #1 of your previous post, the 10-bit values are the start and end RAM address locations of the desired RAM segment. Nothing else. They have nothing to do with the frequency values.

    Item #3 is the process for getting your desired frequency words into the desired RAM segment. You have specified 1001 frequency words corresponding to address range 0 to 1000. So, you will be writing 1001 32-b words to SPI address 0x16. The 1st word will be the 32-b value corresponding to 250 MHz and the 1001-th word will be the 32-b word corresponding to 350 MHz. The 2nd through the 1000-th 32-b words are all the other desired frequencies between 250 MHz and 350 MHz. Writing all 1001-words (i.e., frequencies) to the RAM segment effectively defines the frequency sweep.

    Regarding your last question, when you select the profile for the desired RAM segment (Profile 0 in your case), the RAM controller "knows" the start and end address (0 and 1000) because of the profile selection (which you have presumably programmed prior to writing to the portal (SPI address 0x16). Hence, the controller now expects 1001 32-b words via the portal because that is what you programmed for the start and end address values in the selected profile (Profile 0).

Reply
  • First, be aware that in item #1 of your previous post, the 10-bit values are the start and end RAM address locations of the desired RAM segment. Nothing else. They have nothing to do with the frequency values.

    Item #3 is the process for getting your desired frequency words into the desired RAM segment. You have specified 1001 frequency words corresponding to address range 0 to 1000. So, you will be writing 1001 32-b words to SPI address 0x16. The 1st word will be the 32-b value corresponding to 250 MHz and the 1001-th word will be the 32-b word corresponding to 350 MHz. The 2nd through the 1000-th 32-b words are all the other desired frequencies between 250 MHz and 350 MHz. Writing all 1001-words (i.e., frequencies) to the RAM segment effectively defines the frequency sweep.

    Regarding your last question, when you select the profile for the desired RAM segment (Profile 0 in your case), the RAM controller "knows" the start and end address (0 and 1000) because of the profile selection (which you have presumably programmed prior to writing to the portal (SPI address 0x16). Hence, the controller now expects 1001 32-b words via the portal because that is what you programmed for the start and end address values in the selected profile (Profile 0).

Children
No Data