Published On: October, 10, 2018 By: Eshtaartha Basu | Updated: January 25, 2019 by Cathleen Wicks
The OSD335x C-SiP was designed to reduce the number of external components required for an embedded processing system, minimize the number of Printed Circuit Board (PCB) layers and make the layout process easy. This document will cover important aspects of PCB layout design specific to the OSD335x C-SiP and help designers quickly begin the PCB layout process. First, this document will discuss the layout of the OSD335x C-SiP BGA. Then it will discuss a few common layout scenarios using relevant examples with recommendations on pours for Power, Ground, IO domains, Clamping Circuit and other supporting circuitry.
This document assumes that the reader is already familiar with layout design process and the OSD335x C-SiP (OSD335x C-SiP Data Sheet). It should not be used as a comprehensive layout tutorial or a generic layout design guide.
1.Introduction
2.Revision History of this Document
3. OSD335x C-SiP Layout Specifications
3.1 Background Information
3.2 Ball Function Map
3.3 Footprint Configuration
4. Routing and Vias
4.1 Trace Size Background Information
4.1.1 Example: 6/6 Traces Routed Between Pads of the OSD335x C-SiP
4.2 Via Size Background Information
4.2.1 Example: A 12/24 Via Between 4 Pads of the OSD335x C-SiP
4.2.2 Example: A 12/24 Via and 6/6 Trace Between 4 Pads of the OSD335x C-SiP
4.2.3 Example: Two 10/18 Vias Between 4 Pads of the OSD335x C-SiP
5. OSD335x C-SiP Layout Examples
5.1 Mandatory External Connections
5.2 Signal Pin Fanout
5.3 Power Inputs
5.4 Power Outputs
5.5 Ground Connections
5.6 Clamping Circuit
5.7 IO Voltage Connections
5.8 EEPROM
6. References
A PDF version of this App Note can be found here.
Revision Number | Revision Date | Changes | Author |
---|---|---|---|
1 | 10/4/2018 | Initial Release | E. Basu |
The OSD335x C-SiP Family of System-In-Package (SiP) products are highly integrated building blocks designed to allow easy and cost-effective implementation of TI’s powerful Sitara™ AM335x line of processors. The OSD335x C-SiP integrates the AM335x along with the TI TPS65217C PMIC, the TI TL5209 LDO, up to 1 Gigabyte (GB) of DDR3 Memory, an eMMC for non-volatile storage, a 4 Kilobyte (KB) EEPROM for non-volatile configuration storage, a MEMS oscillator and resistors, capacitors, and inductors into a single 27mm x 27mm design-in-ready package.
This section will introduce important specifications, ball mapping and footprint information of the OSD335x C-SiP.
To understand layout guidelines and methodology used for the recommendations made in this document in more detail, please refer to the following documents:
The Ball function map shown in Figure 1 provides a visual representation of the arrangement of the pins of the OSD335x C-SiP. This can help with the placement and orientation of the OSD335x C-SiP in your design.
The OSD335x C-SiP footprint parameters are shown in Figure 2 and listed in Table 1.
Parameter | Value |
Package Dimension | 27mm x 27mm x 1.5mm |
Number of Balls | 400 |
Ball Grid | 20 rows x 20 columns |
Ball Pitch | 1.27mm (50mils) |
Landing Pad Size | 0.5mm (19.685mils) |
The landing pad size was determined from the IPC-7351A specification. To find more information about IPC-7351A specifications, refer BGA Ball Pad Size section of BGA PCB Design document from Texas Instruments (TI).
For more information on the footprint configuration, please see the Mechanical Dimensions section of the OSD335x C-SiP datasheet.
When pricing a PCB, the size of the traces and vias directly affect the cost to manufacture the board. However, larger traces and vias, while cheaper, can make layout more difficult. Therefore, it is necessary to understand the optimum size of traces and vias for a given design. This section will provide background information on trace and via sizes and discuss layout tradeoffs when designing with the OSD335x C-SiP BGA.
The number of traces that can pass between any two pads of a BGA footprint depends on the trace width and trace spacing. Trace width is the actual width of the trace. Trace spacing is the distance between the edges of any two adjacent traces or a trace and a pad. Trace width and trace spacing are shown pictorially in Figure 3.
In this document, a “x/y trace” indicates a PCB that uses design rules with trace width of x mils and trace spacing of y mils. For example, a 5/6 trace indicates a PCB with trace width of 5mils and trace spacing of 6mils.
The number of traces that can be routed between any two adjacent pads of the BGA can be calculated using the formula (formula assumes all the traces are equal width):
tn tw + (tn + 1) ts <= BP – BD
where,
tn = number of traces
tw = trace width
ts = trace spacing
BP = BGA pitch
BD = BGA ball diameter
For example, to calculate the number of 6/6 traces that can be routed between adjacent pads of the OSD335x C-SiP BGA: tw = 6mils, ts = 6mils, BP = 50mil (1.27mm) and BD = 19.68mil (0.5mm)
Using all this in the above equation:
6tn + 6(tn + 1) <= 30.32
12tn <= 24.32
tn <= 2.026 traces.
This result indicates that two (2) full 6/6 traces can be routed between adjacent balls of the OSD335x C-SiP BGA. Similarly, the number of traces can be calculated for other routing rules, see Table 2. In the OSD335x C-SiP BGA, almost all signal pins are in the first three rows / columns of the BGA. This means to fully escape the BGA, only 2 traces are needed to be routed between each pair of pads. See Section 4.2 for more details on OSD335x C-SiP fanout.
Trace width(mils) / Trace spacing(mils) | Number of traces between two adjacent BGA pads |
Larger than 6/6 | 1 |
6/6 or 5/5 | 2 |
4/4 or smaller | 3 or more |
On all sides, the first three rows of OSD335x C-SiP can be easily accessed using 6/6 traces as shown in Figure 4.
There are two important parameters for vias: drill diameter and annular ring thickness. Drill diameter is the diameter of the actual drilled hole in the PCB. The annular ring thickness is the thickness of the pad that surrounds the drilled hole. These dimensions are shown pictorially in Figure 5.
To determine the diameter of the finished via, use the following formula:
Finished via diameter = Drill diameter + 2 x (Annular ring thickness)
Via spacing is the distance between the edges of any two adjacent vias as shown in Figure 6. When placing vias, make sure the spacing between the vias match the trace spacing design rules that were chosen.
In this document, a “x/y via” indicates a via with drill diameter of x mils and finished via diameter of y mils. For example, a 12/24 via indicates a via with drill diameter of 12mils and finished via diameter of 24mils.
One 12/24 via can be easily placed between four adjacent balls of the BGA as shown in Figure 7.
Figure 8 shows one 12/24 via and one 6/6 trace between four adjacent pads of OSD335x C-SiP.
In case of a tighter design, two 10/18 vias can be placed between four adjacent balls of the BGA as shown in Figure 9.
Once the design rules for traces and vias have been chosen for the PCB, the BGA can now be routed. The following sections provide examples of how to lay out the OSD335x C-SiP.
Figure 10 shows one configuration of the twenty external connections (defined in the Minimum connections section of the OSD335x C-SiP datasheet) that are mandatory for the normal operation of the OSD335x C-SiP. The I2C interface and PMIC control and status sections of the OSD335x Power Management article has more information about these connections.
Figure 11 shows the fanout of all pads of the OSD335x C-SiP using 6/6 traces.
Power to the three input power rails (VIN_AC, VIN_USB and VIN_BAT) can be connected to the OSD335x C-SiP through copper pours as shown in Figure 12.
In space constrained designs, smaller input power pours can be used as shown in Figure 13.
Power from the output power rails of the OSD335x C-SiP can be connected to the rest of the PCB using copper pours as shown in Figure 14.
The ground pins of the OSD335x C-SiP can be connected to ground plane using copper pours as shown in Figure 15. Depending on your thermal needs, the ground pour and the number of vias can be increased.
A clamping circuit may need to be connected between the SYS_RTC_1P8V and SYS_VDD3_3P3V rails in the design. More information about the necessity of using the clamping circuit can be found in the OSD335x Clamping Circuit article.
If used, the clamping circuit can be placed directly below the OSD335x C-SiP on the bottom layer of the PCB. It can be connected to SYS_RTC_1P8V and SYS_VDD3_3P3V through vias as shown in Figure 16. For more detail on placement, download the OSD3358-CSIP-RED Eagle design files.
The OSD335x C-SiP I/O domains can operate at either 1.8VDC or 3.3VDC.
The VDDSHVx signals should be connected to the SYS_VDD3_3P3V output voltage rail to set the I/O domains to operate at 3.3V. This can be done using copper pours as shown in Figure 17.
The VDDSHVx pins can alternately be connected to SYS_VDD_1P8V for 1.8V I/O operation using copper pours as shown in Figure 18.
The VDDSHVx pins can also be connected individually to either SYS_VDD3_3P3V or SYS_VDD_1P8V using copper pours. Figure 19 shows an example where VDDSHV5 is connected to SYS_VDD_1P8V for 1.8V operation while the other VDDSHV pins are connected to SYS_VDD3_3P3V for 3.3V operation.
The write protect pin of the EEPROM (EEPROM_WP) of the OSD335x C-SiP needs to be driven low before information can be written into it. This can be done in a many ways: The EEPROM_WP pin can be driven by another device on the PCB; It can be driven by one of the OSD335x C-SiP pins; It can be routed to a pad to be driven by an external device; It can be routed to a jumper; etc.
Figure 20 shows an example of the EEPROM_WP pin routed to a jumper using 100mil header. The other side of the jumper is connected to GND which allows the EEPROM_WP signal to be easily driven low. This can be a useful layout in prototype designs that are not space constrained.
Octavo Systems LLC all rights reserved
OCTAVO is registered in the U.S. Patent and Trademark Office. OSD, C-SiP, and the Octavo Logo are trademarks of Octavo Systems LLC.
"*" indicates required fields
"*" indicates required fields
"*" indicates required fields
"*" indicates required fields