Forum Discussion
Altera_Forum
Honored Contributor
14 years agoThanks. Filed the bug report, and figured out at least that the reason I have two entries is that I have a MM avalon slave in the custom instruction, and the
# define "INSTANCE_NAME"_SYNCHRONOUS 0 goes away if I remove the avalon slave. The # define SYNCRONOUS 0 is associated with the custom instruction. Having separate entries for the custom instruction and avalon slave makes sense, but there needs to be a prefix on the custom instruction parameter name so I can have multiple instances. Haven't tried the workaround yet as I'm working on other things and it's not blocking me at the moment, but will let you know if I run into problems.