From: "andy pugh" <[email protected]> > > Every "net" command is followed immediately by a signal name. That is, > a name you have chosen yourself, to make sense to you (or to confuse > yourself horribly in the future, if you so choose). > You can uses the same signal name on as many net commands as you like. > But being a signal name it needs to be the first term after the word > "net" > Every "net" command with the same signal name will pass the same value > to every HAL pin listed in the command. And that value will be from > the one, and only one, output pin that appears in one of the net > commands. >
I use the mental model that the "signal" is a wire and the signalname defined after "net" is the heatshrink sleeve printed with its name. The wire loops its way round "pins" (i.e. terminals) but, as the order of writing does not matter, the HAL is essentially a schematic not a wiring diagram. Of course woebetide the person who wires the outputs of more than one totem pole gate (or push-pull amp) together. HAL gives you an error if you try it and this prompts you to include a selector, or "tri-state bus" arrangement on the drivers. As an aside, as many nets are best written on one line, inventing the signal name is tedious. It would suit me to allow a wildcard, "*" or whatever, as signalname and HAL would invent a unique internal name for its own purposes. John Prentice ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
