- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Execution time measured on vertex 5
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
05-03-2012 08:58 AM
I have simulated my vhdl program and the time needed is 80 us. Now when i run this program on board Virtex 5 ,then how will i know about the execution time ? i have assigned the clock frequency at 100 MHz. i think there will be difference in software simulation time and hardware simulation time.. Please help .
Re: Execution time measured on vertex 5
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
05-03-2012 10:47 AM
technovlsi wrote:
I have simulated my vhdl program and the time needed is 80 us. Now when i run this program on board Virtex 5 ,then how will i know about the execution time ? i have assigned the clock frequency at 100 MHz. i think there will be difference in software simulation time and hardware simulation time.. Please help .
VHDL is NOT A PROGRAMMING LANGUAGE.
You are NOT WRITING A SEQUENTIALLY-EXECUTED COMPUTER PROGRAM.
----------------------------------------------------------------
Yes, I do this for a living.
Re: Execution time measured on vertex 5
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
05-03-2012 11:16 AM
You are developing hardware that will run constantly, so the execution time is until the board is powered off.
Hardware timing is usually referred to as latency for a data flow design. Data will be present at the inputs of the design and it will take some numbers of clock cycles before it is full processed and presented on the outptus of the design. The total number of clock cycles is the latency. In most data flow designs, the next output will appear on the outputs the next clock cycle. Taking the number of clock cycles and multipling it by the clock period will give you the real time between the input and output time.
Have you tried typing your question into Google? If not you should before posting.
Too many results? Try adding site:www.xilinx.com











