Forum Discussion
Altera_Forum
Honored Contributor
14 years agoThanks for the posts, helped me get things working--with a caveat. I'm passing parameters for a custom instruction, and so I've added the following to my validation callback:
set_module_assignment embeddedsw.CMacro.SYNCHRONOUS [get_parameter_value SYNCHRONOUS] What ends up happening is that the parameter shows up twice in my system.h, once as # define "SOPC_MODULE_NAME"_SYNCHRNOUS 0 which is what I want and expect, and once just as # define SYNCHRONOUS 0 after the custom instruction macros, which I don't expect and is probably bad. Any idea what might be happening? It seems like a bug (I'm using the Web edition of 11.1sp1 in linux). Right now it's not a problem, but if I want to do something like have two custom instructions in the same system, bad things happen (#define SYNCHRONOUS happens twice, bsp generation fails).