A schematic doesn't necessarily represent every circuit element as a bunch of gates or simple flipflops. It's much easier for that civil engineer, over 50, (who, BTW, was required, as an undergraduate, to take a logic circuits course as well as a basic electronics course ... resistors, cap's, Thevenin, Norton, LaPlace, phasors ... etc.) can read a logic diagram just fine, and, in fact, better than most coders under 35, to my experience, since he was taught the difference between a J-K and a D flipflop. If he's the guy in charge of the project, probably because of the stake he holds in the company, he's concerned with the overall function, with details that might have "fallen through the cracks," and things of that sort. He wants to be assured that what he's being sold is what will be delivered. If you enter the entire design in HDL and then let him review a schematic, that certainly doesn't precisely reflect what he's being sold. If he's asked that he be allowed to review what's being delivered, you have to give him what he's asked for. If he wants schematics, you have to use 'em, else he'll find someone who'll do that.


I agree, it's useful for up to, maybe, 250 circuit blocks, whether they're library components, IP blocks, or state machines. The problem is with the software and not with the concept. The latest software set from XILINX has some real issues. Take a look for yourself.

RE