Hi Billy On 18 March 2011 19:50, William Mallard <w...@llard.net> wrote:
> On 03/18/2011 06:39 AM, Andrew Martens wrote: > > Just updated my libraries and opened a design and have found that all > > 'To Processor' Software Registers now have an extra input (sim_reg_in) > > and output (reg_in). This does not affect 'From Processor' Software > > Registers. > > > > Could someone explain the idea behind this? Are we trying to make > > Shared Registers bi-directional? If so, why only the 'To Processor' > > Software Register? > > That's a bug, not a feature. If you change it back to 'From Processor' > and then to 'To Processor' again, it fixes itself. > This does work but is rather painful. Dragging a fresh software register into a design and changing IO Direction to 'To Processor' also produces this error. I don't understand why it happens. The script does not seem to offer an option where both sets of ports are generated. The only explanation seems to be that the mechanism by which it automatically deletes other/existing blocks does not get activated properly the first time the script is run. I am not sure if this is because no part of the existing circuit is used in this case i.e the set of existing stuff and new stuff has no intersection. Is this possibly just an error in my setup? I am assuming this happens for other people too...? Regards Andrew
