Topic: FMC176 - Command wormhole map address  (Read 3104 times)

angelasalom April 03, 2014, 03:54 PM

  • Member
  • *
  • Posts: 5
Hi,
I have just started playing with FMC176 and I would like to plug this board in a perseus uTCA carrier.
I have been looking at the code of the vc707_fmc176 example and I would like to know if it would be possible to have the map address of the wormhole commands for this example.
Thank you very much in advance for your help,
Angela

arnaudNL April 04, 2014, 04:22 AM (#1)

  • 4DSP Staff (EU)
  • Administrator
  • Member
  • *****
  • Posts: 7110
Dear Angela,


There is star documentation with the register mapping of all the stars. As soon you generate your design in StellarIP you will obtain a .h file containing the constellation address for every stars.


Best Regards,
Arnaud

angelasalom April 07, 2014, 02:34 AM (#2)

  • Member
  • *
  • Posts: 5
Hi Arnaud,Thank you very much for your reply, I didnt know that. Anyway, here we can only see the base address for each main component of the project, but if it is possible, I would like to know as well the detailed map address of the FMC local devices. I mean, the start address of the FMC176 in this project is 0x2404, but then for example, there are three different start address to configure the AD9250 described in file fmc176_if_v7.vhd--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------constant START_ADDR_AD9250_PHY   : std_logic_vector(27 downto 0) := START_ADDR + x"0000010";constant STOP_ADDR_AD9250_PHY    : std_logic_vector(27 downto 0) := START_ADDR + x"00000FF"; --min. range 16#0010constant START_ADDR_AD9250_CTRL0 : std_logic_vector(27 downto 0) := START_ADDR + x"0000100";constant STOP_ADDR_AD9250_CTRL0  : std_logic_vector(27 downto 0) := START_ADDR + x"0000200"; --min. range 16#0011constant START_ADDR_AD9250_CTRL1 : std_logic_vector(27 downto 0) := START_ADDR + x"0000300";constant STOP_ADDR_AD9250_CTRL1  : std_logic_vector(27 downto 0) := START_ADDR + x"0000400"; --min. range 16#0011--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------What are these different addresses for? According to AD9520 datasheet, the settings map address of this ADC only needs 0xFF addresses at most. I guess you use different base address for different AD9520 settings? So, which AD9250 settings are programmed in each of the ADDR_AD9250_PHY, ADDR_AD9250_CTRL0 and ADDR_AD9250_CTRL1  addresses?For the AD9129, it is the same. The settings map address of these DACs only requires 0x7F addresss, but there are more available addresses in the fmc176_if_v7.vhd file. Could you please tell me which settings are programmed in each of the ADDR_AD9129_PHY0 and ADDR_AD9129_CTRL0?Thank you very much in advance for your help,Angela

arnaudNL April 07, 2014, 03:01 PM (#3)

  • 4DSP Staff (EU)
  • Administrator
  • Member
  • *****
  • Posts: 7110
Dear Angela,


I am attaching the FMC176 star documentation, I assume the register map section will make some sense.


There you will see that there are several devices mapped to the the star range.


Generally, the reference design does exercise all this by configuring the whole chip set during run time.


A good way to get insights on the design would be adding a chipscope peripheral and capture some waveforms!


Best Regards,
Arnaud

angelasalom April 07, 2014, 03:49 PM (#4)

  • Member
  • *
  • Posts: 5
Hi Arnaud,
Thank you very much for the information. I didnt know this file was available. I am still getting used to the documentation of the board. I have seen there are other pdf files that will help me to understand better how this board works,
I think with this I can continue working,
Thanks again,
Angela

arnaudNL April 07, 2014, 04:15 PM (#5)

  • 4DSP Staff (EU)
  • Administrator
  • Member
  • *****
  • Posts: 7110
This topic is being closed because the issue is considered as resolved by 4DSP. Feel free to create a new topic for any further inquiries.

arnaudNL June 16, 2014, 04:42 AM (#6)

  • 4DSP Staff (EU)
  • Administrator
  • Member
  • *****
  • Posts: 7110
This topic is being closed because the issue is considered as resolved by 4DSP. Feel free to create a new topic for any further inquiries.