Post Go back to editing

How to choose for read FIFO SPI interface for AD6641?

1 How to choose for read FIFO SPI interface for AD6641? In which register of SPI and what values we need to write?

2 How to choose the SPORT interface? In which register of SPI and what values we need to write?

How to initialize a fill command through the SPI port without standby? In which register of SPI and what values we need to write?

4 How to use bits of the register 0x102?

Parents
  • I'm trying to read FIFO SPI interface for AD6641 using AD6641-500EBZ Evaluation Board.  I'm clocking the part at 250MHz.  I followed the exact procedure from this post but it did not work.  After initiating the fill and reading the FIFO status register (0x10A), I get STATUS=0x04 (Over-range).  It doesn't matter when I read the status register, I always get Over-range.  I've never seen it empty or full.  How do I clear the FIFO status?  Do I need to write 0x00 to register 0x10A?

Reply
  • I'm trying to read FIFO SPI interface for AD6641 using AD6641-500EBZ Evaluation Board.  I'm clocking the part at 250MHz.  I followed the exact procedure from this post but it did not work.  After initiating the fill and reading the FIFO status register (0x10A), I get STATUS=0x04 (Over-range).  It doesn't matter when I read the status register, I always get Over-range.  I've never seen it empty or full.  How do I clear the FIFO status?  Do I need to write 0x00 to register 0x10A?

Children
  • Hi, 

    Resetting the FIFO should clear that register: 

    write_reg(0x102, 0x04) // Fill Reset

    Regards, 

    David

  • I executed the example procedure exactly as written on this page except that I read_reg(0x10A) after each write.  As stated previously, the status always comes back 0x04 (Over-range) even immediately after write_reg(0x102, 0x04) // Fill Reset.  The only other thing that might be different about my code is that my write_reg() command contains a read_reg to verify the written value.  Do you expect this to cause problems?  Why else might the status always report over-range?  I'll try using a blindwrite command that doesn't verify the written value and see if that helps.