On Thu, 14 Oct 2010 10:10:38 -0500, Mike Crowe <[email protected]> wrote: > On Thu, 2010-10-14 at 03:57 +0200, Yann Guidon wrote: >> Jakob Eriksson wrote: >> > I have followed this list for some time, and can't but help believe >> > there must be some simpler way to communicate with GHDL besides shared >> > memory or environment variables. >> Each communication channel has its strengths and weaknesses, >> hence a recommended use or application. > Any references that might steer me into using the best interface?
good question :-) I can only speak about what I know well : - environment variables are obviously for the cases where there is one or a few parameters to pass to the simulator. In fact it was designed for the framebuffer code so the user could direct the code to a specific framebuffer file name. Generally, it can be used to provide elaboration-time informations such as the length of a vector or things like that. It's for one-way communication obviously, for small chunks of data. - static linking with C code is a fantastic feature that allows things like the framebuffer access or things like that. it is generally great for interfaces to exotic ports. it is probably the fastest and the lowest latency but it depends on the GRT to be run at the correct time. It can't access everything either, only the signals and variables of the module(s) it is called from. - the rest (VPI etc.) : i'll let the others voice out :-) yg _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
