dev.nlited.com

>>

Second Pass

<<<< prev
next >>>>

2016-04-19 16:46:14 chip Page 1672 📢 PUBLIC

April 19 2016

The first layout pass exposed some problems with the schematic and I spent a couple days fixing them and improving the design, especially around the power selection. Today's task is to renew the layout and continue.

It appears I lost some of the net class information in the schematic. To avoid hitting this dialog every time I renew the layout from the schematic, I need to update the net classes in the schematic to match the layout.

CtrlMtr net classes. 

I created several new nets in the schematic without assigning any class to them.

NetClass
MTR_GNDPWR_MTR
PWR_3VPWR_DATA
PWR_5VPWR_DATA
PWR_JTAG_CTRLPWR_DATA
PWR_JTAG_EZFETPWR_DATA
VCC_5VPWR_DATA

I renewed the layout. The A3967 circuits didn't change much so that work was preserved.

Renewed layout 

After about 90 minutes I have a rough draft of the JTAG connection to the 5529. I am using the THERMAL plane for power and ground connections. It is a tight squeeze to the TagConnect pads, even though the connector takes up a huge amount of board space due to the space requirements. The extra space is needed to have room to squeeze the TagConnect hardware to disengage the retaining hooks. And this design has two of them. Once I am confident the ezFET works, I can remove the TagConnect to the 5529.

MSP430F5529 layout 

The power select headers are going to be tricky, since J507:IN1 is connected to the 5528 TagConnect, J507:IN2 is connected to the 5529 TagConnect, and J507:OUT goes to J508 next to the power converter. There will be some long-distance traces involved.

I am replicating the TagConnect and JTAG connections to the 5528, just rotating it by 180°.


Mistake icon

My first step after exporting the schematic to layout should have been to group all the components into functional blocks. This is where numbering the components by sheet number pays off. If all the components for the ezFET are near each other, the auto-place and auto-route does a much better job. Trying to sort out the components after the auto-router involves endlessly deleting traces that stretch across the board.




WebV7 (C)2018 nlited | Rendered by tikope in 115.869ms | 18.225.72.181