I was working on a PCB and wanted to print a negative image for photoresist
but found out that despite most of PCB had been covered with a region,
negative still had a thick border. Diving into the code I found out that
this border (margin) is hard coded to be 5mm. I thought it might be good to
It is obvious that there can be only one physical pin as SCH_PIN which
in turn however can be referenced in a multitude of functionalities. A
very simple solution below.
There is a
class SCH_PIN ...
and there is
/// A container for several SCH_PIN items
typedef std::vector SCH_PINS;
As
Hello Ian,
I can see your point, and it has merit. But its a design choice. As is
the design choice to lay out the schematic by function. For complex
MCU's (and lets face it, these days all MCU's are complex with regard to
functionality). I think that really they should just be defined as
Unfortunately, no I don't agree that the grouping should be by peripheral.
The purpose of a schematic is to capture the electrical connections of a
circuit, and allow the designer to reason about it. On most chips, the
electrical specifications of the same peripheral type can differ between
4 matches
Mail list logo
