--- In [email protected], "ayewinoung" <ayewino...@...> wrote: > > Hi all > > I'm trying to create a large pin (> 256 pins) device, FPGA with multiple IO > banks, with libedit, and to simplify schematic entry, I'm doing each IO bank > as "a part" in libedit, such as "Part A, Part B, Part C etc.". > > I'm not sure its the correct way to do things, I just copied someone else > example without really understanding everything ;) > > When I create a pin in each part, I've done with "Edit pin part per part" > clicked (highlighted). And for each pin "Pin Options", "Common to Units", > un-ticked (i.e. a pin can exist only in one part, so to speak). > > Again, I'm not sure its the right or intended way to do things. > > The trouble come, when I do "Test Duplicate Pins" check, the tool ONLY check > the pins within a part, not across multiple parts. What I want the tool to do > is check duplicate pins across all the parts in the symbol. > > I'm confident, I'm not doing things right or not using the tool in what its > intended. > > Could someone point at me how I could check "duplicate pins" across all the > parts ? or any other thing I should do right ? > > Thanks in advance. > > A >
The only good way to do large parts is by scripting the library creation, preferably starting with a text file provided by the part manufacturer. I have some Python code to do this which is not yet ready to release; I think another gentleman has posted on the list that he has made available some Ruby code. But the bottom line is that there is way too much margin for cut and paste error to do this manually. If you figure out a scripting flow that works for you, you will have gained back all your extra time on the second or third part. The file format of the library file is very well documented; the other thing you can do is go to http://kicad.rohrbacher.net/quicklib.php and generate a small part (or even a big part using default names and I/O types) with pins with your names and I/O types. A quick peek at its output will get you started if you know any scripting language at all. Even if you just know C, that's going to be better than using a graphical tool to enter pin names and pin numbers. I use Xilinx FPGAs. The pin number/names are available in text files you can download from their site; alternatively one of their command line tools (forget which one) will output the pin descriptions. You can use these to generate your library part. HTH, Pat
