-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Netlisting changes wire names #323
Comments
Nets without names are auto-named by xschem when netlisting. If you want a consistent naming generate a netlist before saving the file. Also do not set names directly in wires. (like doing a 'q' on a wire and changing the 'lab' attribute). The netlister assigns names to the unnamed nets and will probably overwrite your setting. |
There are some functions to control the symbol appearance, as shown here. floaters.mp4 |
Is it possible to hide only some of the attributes, not all of them? |
Nets without names are auto-named by xschem when netlisting. If you want a consistent naming generate a netlist before saving the file. Not sure what this means. It seems you have to have a saved file before it is possible to generate a netlist? So one needs a file; then needs to netlist, and then needs to save the file a second time? Nets without a label are not guaranteed to retain their names, especially if the circuit is changed. Also do not set names directly in wires. (like doing a 'q' on a wire and changing the 'lab' attribute). If I understand correctly, doing a q on a wire and changing the 'lab' attribute is not considered to be naming a net; to name a net, one must add a lab_pin.sym or a lab_wire.sym. Thank you, I did not know this. Does doing a q on a wire and changing the 'lab' attribute have any effect? |
Some symbol attributes may have the |
Sandbox
sandbox unzips into a single directory called sandbox. >cd sandbox; xschem
The sandbox is self contained (as tested).
The schematic to open is std_lib/km_tb_lib/sch/TST_DIG.sch
Note:
N 120 40 180 40 {lab=A1A}
is labeled A1AOpen schematic, select wire after first inverter, >q, and note it is named A1A
view netlist (A), change to spice netlist option, netlist circuit, note in netlist (stored in sandbox/netlists:
The wire A1A is now called net1, and A1B is now called net2. If the wire in the schematic is examined, it is now called: #net1.
If the schematic is first saved, and then std_lib/km_tb_lib/sch/TST_DIG.sch is examined,
the relevant lines are now:
A link to the new schematic file is: TST_DIG.sch. I'm guessing the problem is somewhere in netlist.c. maybe around: wirecheck() or name_attached_nets(). If you could tell me how to get gdb attached to trace netlisting, I can try and track it down (do I need to add a loop somewhere to allow for attaching and after attaching breaking out for tracing - where should I place such a loop?).
Somewhat related (more likely a new issue). In schematics, the symbol properties (example: "name=INV1 MODEL=DG_INV1_1X1 spiceprefix=X") are included in lines such as:
inside curly braces. It's similar for specifying wire labels. In both cases, it would be nice to be able to control visibility, font size, attachment point, etc. A possible approach would be to make the {} parameter specification hierarchical. For example, when the defaults are not desired, an additional sub-parameter can be included, such as:
This shouldn't break any existing data bases, as it would only be added when desired. Just a thought. Let me know if you think it is worth a discussion (on discord? or sorceforge?).
Overall, a very nice schematic capture program, Thanks.
The text was updated successfully, but these errors were encountered: