Breaking News
Comments
Oldest First | Newest First | Threaded View
<<   <   Page 3 / 3
DrFPGA
User Rank
Blogger
Re: math links
DrFPGA   12/9/2013 11:02:27 AM
NO RATINGS
Remember when we had to do many of the FPGA tricks by hand? Register retiming, one hot state machines, if then else to mux conversions? Now the synthesis tools do all this for us. Hopefully tricks like the multiply by a constant will get folded in too. Just depends on how common the need is for these tricks I guess.

Maybe there should be a 'list' of tricks that users suggest would be good to put into synthesis tools. Perhaps via a discussion thread on Programmable Logic Design Line?

betajet
User Rank
CEO
Know the limitations of your tools
betajet   12/9/2013 2:20:02 PM
NO RATINGS
I remember the first time I synthesized an FPGA design for a real product.  The synthesizer automatically came up with a one-hot state machine coding.  Everything simulated fine.   Unfortunately, this particular design did not have a well-formed clock when connecting or disconnecting the input signal, which would cause it to lose the one-hot code occasionally when reconnecting.  Switching to a manual state coding that automatically recovered from bad states fixed the problem -- and saved logic cells in this case.

Lesson 1:  Don't trust automatic state assignment.  Some synthesizers make it hard to turn off automatic state assignment, but it's worth the effort.

Lesson 2:  Don't trust simulation.  It only simulates theoretical models, not the real world.

Lessons 1+2 combined and generalized:  Know the limitations of your tools.

DrFPGA
User Rank
Blogger
Re: Know the limitations of your tools
DrFPGA   12/9/2013 2:37:47 PM
NO RATINGS
Very important point and one difficult to do in practice. How many tools actually document (in detail) what the tool will do or not do. I find I need to do small example designs and look over th output of the place and route tool to figure out what is going on. Widh the vendors did this for me!

Anyone else have tools with detailed enough docs that they can tell ahead of time what is being done?

paragdighe
User Rank
Rookie
its fixed point math
paragdighe   12/10/2013 4:45:31 AM
NO RATINGS
1 saves
here's why it works: x/10=x*0.1={2^16*x*0.1}/2^16={x*2^16*0.1}/2^16 =x*1999H/2^16 

<<   <   Page 3 / 3


EE Life
Frankenstein's Fix, Teardowns, Sideshows, Design Contests, Reader Content & More
Max Maxfield

Creating New Faceplates for Antique Analog Meters
Max Maxfield
39 comments
I've currently got a couple of hobby projects on the go that feature the use of antique analog meters. For example, there's my Inamorata Prognostication Engine and its companion, the ...

latest comment Clive "Max" Maxfield @Steve: I'm not worthy! That's the attitude! LOL
EDN Staff

11 Summer Vacation Spots for Engineers
EDN Staff
11 comments
This collection of places from technology history, museums, and modern marvels is a roadmap for an engineering adventure that will take you around the world. Here are just a few spots ...

Glen Chenier

Engineers Solve Analog/Digital Problem, Invent Creative Expletives
Glen Chenier
11 comments
- An analog engineer and a digital engineer join forces, use their respective skills, and pull a few bunnies out of a hat to troubleshoot a system with which they are completely ...

Larry Desjardin

Engineers Should Study Finance: 5 Reasons Why
Larry Desjardin
45 comments
I'm a big proponent of engineers learning financial basics. Why? Because engineers are making decisions all the time, in multiple ways. Having a good financial understanding guides these ...

Flash Poll
Top Comments of the Week
Like Us on Facebook
EE Times on Twitter
EE Times Twitter Feed

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)