--- Quote Start ---
I will use the generics at least for the time being, until I have some more time to study the configurations a bit deeper.
--- Quote End ---
When you look at configurations, see if you can figure out a way to use a generic to switch between the two examples I gave; editing the code to switch between them seems so ugly :)
--- Quote Start ---
But I'm still thinking about using meaningful names in stead of the place-holder names used in the schematic of the FGPA PCB.
--- Quote End ---
Just write your code in another not-quite-top-level VHDL file, and then instantiate that in your actual top-level entity, i.e., write your code as blink_leds with meaningful pin names, and then just wire it up inside the top-level bemicro_sdk that has the uglier pin names.
In my projects, I organize the source as board/device/project, eg., bemicro_sdk/cyclone4/basic, bemicro_sdk/cyclone4/blink_leds, bemicro_sdk/cyclone4/avalon, etc., each top-level file is identical with regards to its pin assignments. The not-quite-top-level design is often a different source file, named the same as the project folder name.
--- Quote Start ---
I actually saw that the projects were in VHDL93, but the compiler didn't choke on the process( all ) statement.
--- Quote End ---
It (Quartus 10.1) did for me.
--- Quote Start ---
You are right about the TOC and navigation in the Altera Wiki, but is is a place to find stuff to reflect upon. The search in the forum is even a factor 1000 worse.
--- Quote End ---
Good to hear I am not alone in my impressions :)
--- Quote Start ---
Have a nice Sunday,
--- Quote End ---
You too!
Cheers,
Dave
Honored Contributor
