Are you getting that board printed? If so - I’d advise making a ground plane, then moving all other traces to the top of the board.
If you’re making the board by hand it’s possible to get all traces on the top - It would involve shifting left R2 a bit and running a couple traces underneath it.
nuxie1:
How did you make those blue data bus lines in the schematic?
There is a “bus” button, right next to the “net” button (in EAGLE). Make sure you name the bus appropriately, otherwise the schematic editor won’t let you connect the nets to it.
For example, if you have signals A0, A1, A2, A3, A4, A5, A6, A7, you should name the bus A[0…7]. Then “connect” your nets to the bus the same way you would connect them to a symbol pin.
by the way, the name is simply the signal names seperated by commas so a1,a2,a3 is the same as a[1…3]. You can have a[1…8],cs1,foo if you want. when you connect a net to the bus it will offer up each signal for you to choose.
If you’re going to have a silkscreen on the board… have you looked into the ‘smash’ command? It will allow you to move component names/values around so the board can be much more read-able (ie. LED1 won’t be covered by R2 and C2’s .1uF won’t be on the IC’s pads).
If you’re going to have a silkscreen on the board… have you looked into the ‘smash’ command? It will allow you to move component names/values around so the board can be much more read-able (ie. LED1 won’t be covered by R2 and C2’s .1uF won’t be on the IC’s pads).
Andrew02E:
If you’re going to have a silkscreen on the board… have you looked into the ‘smash’ command? It will allow you to move component names/values around so the board can be much more read-able (ie. LED1 won’t be covered by R2 and C2’s .1uF won’t be on the IC’s pads).
Yeah, I smashed a couple of things in the schematic, but I didn’t plan on producing the board, and therefore slacked on the board…