icid
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| icid [2020/04/24 14:39] – add intro, background, and database kingkevin | icid [2020/04/24 15:06] – add searches kingkevin | ||
|---|---|---|---|
| Line 21: | Line 21: | ||
| * BSDL: used to do boundary scan electronic testing. This is generally of good quality, but is only provided for micro-controllers which support JTAG. | * BSDL: used to do boundary scan electronic testing. This is generally of good quality, but is only provided for micro-controllers which support JTAG. | ||
| * BXL: a proprietary symbol and footprint library. This is not provided by all vendors and for all parts, but its support is growing and the larger vendors provide BXL files for the most (popular) parts. | * BXL: a proprietary symbol and footprint library. This is not provided by all vendors and for all parts, but its support is growing and the larger vendors provide BXL files for the most (popular) parts. | ||
| + | |||
| + | ====== searching ====== | ||
| + | |||
| + | Here are a couple of tips to improve the search results. | ||
| + | |||
| + | First select the file type. since parts can be described by different models (file types), you might have duplicate parts in the final list: | ||
| + | * if you are looking for a micro-controller which supports JTAG, select only the BSDL file type. This already remove a lot of candidates. The pinout provided in the BSDL models is often good, thus the pins constraints rule can be used precisely. | ||
| + | * if you are look for a micro-controller which does not supports JTAG, not a micro-controller, | ||
| + | * finally, if you did not find any result in BSDL and BXL, you can still try the IBIS file type. IBIS files are also provided for old parts (even before BXL existd), mostly for high-end or analogue parts, but the pinout provided is terrible. Often only some pins are described (the most relevant for an analogue simulation), | ||
| + | |||
| + | writing pins constraint rules: | ||
| + | * the rules are written as conditionals which you often find in programming language: using == (is equal to), != (is not equal to), && (and), and || (or). | ||
| + | * to select pin 1, use '' | ||
| + | * the pin types are: power, ground, input, output, bidir | ||
| + | * instead of writing what a pin type should be, I recommend to write what is can't be. When you see ground connected to a pin, this pin could be an actual ground pin, but it could also be an input, or bi-directional used as input. What it can't be though, is a power pin. | ||
| + | * keep in mind that not all pins are described correctly by the models | ||
| + | |||
| + | results: | ||
| + | * once you select a part, the details of it will be displayed | ||
| + | * this is the complete part information stored in the database | ||
| + | * it is created by parsing the models provided by the vendor | ||
| + | * a link you the source file (e.g. model provided by the vendor) is also available (next to the " | ||
| + | * if you find discrepancies between the " | ||
| ====== sources ====== | ====== sources ====== | ||
icid.txt · Last modified: 2024/01/07 17:49 by 127.0.0.1
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
