I have a fairly large schematic loaded in EAGLE (netlist file is ~2500 lines long) and I want to find out where exactly some pin is connected, given chip name and pin name.
What I'm trying to do:
- I can easily locate chip in question on the zoomed out view, it's not too many of them and they're clearly labelled
- I can more or less quickly locate desired pin by browsing through all the pins of the chip (it's "less quickly" if the chip in question is a CPU with ~600 pins)
- I can trace where the wire goes then by eye, but there are two major obstacles: buses and named nets. Both basically mean that this point connects to the net that can be scattered all around the drawing.
What I already tried:
- "Info" command makes it possible to highlight only one particular instance of the net/bus connected, not highlighting all the rest.
- "Show" command technically does exactly what I want - it highlights all the connected pieces in all instances of the net, but this highlighting stuff is fairly hard to notice (contrast between "highlighted" and "normal" is not so great) and basically it only works on high zoom levels (where there's at most 8-10 inches fit on the screen). Hunting for that "highlighted" pixels on bird's eye view is very tedious task.
find.ulpcan highlight and zoom onto particular element by name, and that works for nets too. But, alas, I can't seem to understand how it works:
- Just asking for net/bus by name (with count=0 by default) yields random piece of that net
- Asking for net/bus by name + count=1000 yields another pretty much random piece of that net, and reports how much of them are available (for example, "9")
- Then asking for net/bus name + count=(1..9) tends to yield various pieces of the net, but sometimes they clearly repeat and the result seems to be pretty much random. How can I make sure that I've browsed through all 9 instances of a given net?
Any tips on how seasoned pros get through this basic navigation stuff? I might guess there's a way to add more contrast to highlighting to make it more obvious, or there's some proper way to use
find.ulp to iterate over every one of the pieces of the net/bus?