I find it often difficult to make a readable schematic for simple boards that have a microcontroller or FPGA that has lots of connections to some other components, where each connection goes through a small resistor (to avoid smoke in case of programming errors) and also needs a pull-up or pull-down.
Obviously, this is the worst possible way to do it:
An approach I've seen often is to draw the inline resistor near the "central" microcontroller, then place the label behind it, and somewhere else define the pull-up attached to the label, but this leads to a forest of label/pull-up/power rail symbols on some page, which isn't entirely obvious either.
How would you draw a schematic like this, making it clear that the non-inverted signals have pull-down resistors, the inverted signals have pull-up resistors, and all of them have in-line resistors to protect the controller?
Best Answer
I agree with Wesley that you have it drawn well already.
It is necessary to define what is the good schematic versus bad schematics. In my opinion, there're two rules for good schematic (circuit diagram):
You current circuit diagram is readable and understandable, because symbols are arranged logically and in order, and connections for symbols are similar giving understanding why they are there and what involved devices do in the circuit.
You want to know how you can have circuit occupy less space "on paper" without compromising readability. I think you may consider the following points:
Probably this one will make sense to consider (this is an example of drawing, there's no sense in the circuit as is :):