Topic: Noise with FMC151  (Read 23874 times)

tonyku May 30, 2014, 07:08 PM (#45)

  • Administrator
  • Member
  • *****
  • Posts: 196

While it's possible to add delays to the firmware, you'll have to recompile it several times to get the right timing iwth hardware, right?   That's a significant amount of time to spend on it.

Our reference design utilizes software and firmware so that certain things such as delays in the line which may vary amongst different hardware platforms and configurations can be done directly in software without having to recompile firmware.   


samar June 02, 2014, 04:45 PM (#46)

  • Member
  • *
  • Posts: 2
Hi,

I am a collaborator working with Paul on this design. I think it might help to provide some context for this problem.

We are trying to generate a 500 Hz square wave from the DAC, and integrate over part of the response from a circuit. The generation seems to work seamlessly. The integration should be done over 50K samples from the ADC, 0.1 ms after the positive edge, for each period of the generated signal.

We modified the reference VHDL, but during synthesis in ISE, we are having difficulty meeting timing. So, there are two issues:

1. Which signal(s) should we extract from the given design to get the ADC outputs?
2. What tap delay should we use, and how should we insert it directly in the VHDL logic?

Thanks!

tonyku June 02, 2014, 04:51 PM (#47)

  • Administrator
  • Member
  • *****
  • Posts: 196
Please open a new topic on this.   As far as the tap delay, please see the previous posts.  It is designed to sync the lines of the clock and the adc traces to the FPGA's logic.



Hi,

I am a collaborator working with Paul on this design. I think it might help to provide some context for this problem.

We are trying to generate a 500 Hz square wave from the DAC, and integrate over part of the response from a circuit. The generation seems to work seamlessly. The integration should be done over 50K samples from the ADC, 0.1 ms after the positive edge, for each period of the generated signal.

We modified the reference VHDL, but during synthesis in ISE, we are having difficulty meeting timing. So, there are two issues:

1. Which signal(s) should we extract from the given design to get the ADC outputs?
2. What tap delay should we use, and how should we insert it directly in the VHDL logic?

Thanks!

paulleons June 02, 2014, 05:16 PM (#48)

  • Member
  • *
  • Posts: 30
Hello,


Is there a way to fix these problems by slowing down the sampling frequency, let say from 247 MSPS to 10 MSPS.


My application does not require very high sampling rate and hence, I could still work with a slower frequency if that could fix the problem.


Paul

tonyku June 02, 2014, 05:25 PM (#49)

  • Administrator
  • Member
  • *****
  • Posts: 196
Paul,

it does not matter what frequency you use, etc.    This is an inherent issue with any firmware design.   You have an external part that a FPGA is trying to interface - the FPGA compiles and generate a bit file -  and can generate different routes depending on how much has chagned, right?   Those routes changes the delay of the lines to the FPGA.  It's an inherent issue in any FPGA design when interfacing with an external device.   We provide a way to be able to program it with software with the firmware to tune the delay.   There is  plan to do it automatically in firmware in the future.

Anyways, from what we have done, the hardware of your FMC151 is working, it's just the tap delays needed to change from the default value in software.   If you need to change the frequency, you'll need to look at the ADC configuration in software and you'll need to build the software yourself.

We can support you on using our reference software and reference firmware but beyond that you'll need to contact sales@4dsp.com.


Tony





paulleons June 02, 2014, 05:37 PM (#50)

  • Member
  • *
  • Posts: 30
Thanks for the reply.


But I have some more concerns regarding the tap-delay.  I have my own custom Ip which connects to two signals, namely phy_out_data0 and phy_out_data1 (from the reference design) and I observe these values in chipscope.


The was implemented and had met timing. Now, a tap-delay of 0 was observed to be ideal as I got a sine wave similar to untitled.jpg.


However, when I see the same waveform in chipscope, the sine wave seems to be distorted as in image_0.jpg and image_1.jpg.


Is there a possible explanation for this behavior?


Paul
  • « Last Edit: June 02, 2014, 05:39 PM by paulleons »

arnaudNL June 03, 2014, 05:36 AM (#51)

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


I would double check the chipscope sampling clock then.


The fact you get proper data saved to file indicate the reference design is working. Modification on the reference firmware are not supported unless you have a extended technical support contract in place.


Because you indicate you have the proper data saved to file indicate the initial issue is resolved and therefor I am closing this topic.


Best Regards,
Arnaud



arnaudNL June 03, 2014, 05:36 AM (#52)

  • 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.