Published On: December 17, 2025 By: Greg Sheridan
This application note provides detailed information on the power design methodology for the OSD62x-PM System-in-Package. It covers power inputs, sequencing, voltage grouping, and low-power design considerations. For a complete implementation example using the OSD62-PM-BRK reference platform, refer to the OSD62x-PM Example Power Design Application Note.
In this application note, we will cover the following topics:
OSD62x-PM integrates the AM62x SoC, DDR4 high-speed memory, and associated passives. The following high-level block diagram shows how the two main internal components are connected.
The OSD62x-PM exposes the power rails of the AM62x SoC and the DDR4 high-speed memory via BGA balls. This allows for a highly customizable power architecture. All processor – DDR connections are made inside the OSD62x-PM System in Package. The two DDR power inputs are the only required external DDR4 connections.
The following table shows the DDR specifications:
Table 2‑1: OSD62x-PM DDR4 Specifications
| Parameter | Value | |
|---|---|---|
| Interface width | 1GB | x16 |
| 2GB | x16 | |
| Maximum operating frequency | 800MHz (1600MTs) | |
| DDR Supply voltage (VDDS_DDR) | 1.2V nominal | |
| DDR VPP voltage (DDR_VPP) | 2.5V nominal | |
The following figure shows the power inputs to the OSD62x-PM System in Package.
Most power inputs are required and power various subsystems of the SoC and DDR components. However, some power inputs are optional if peripherals such as the CSI Camera Interface (CSIRX0) or USB are not used. As seen in Figure 1, VDDS_DDR of the AM62x and VDD and VDDQ of the DDR4 are connected internally, they form one input power rail for OSD62x-PM.
There are nine (9) IO voltage domain inputs that allow the user to configure the IO voltages of the banks they power (either 1.8V or 3.3V). The associated capacitors (CAP_VDDSx) are integrated within the OSD62x-PM. The USB, and CSIRX0 subsystems have independent power domains to allow for isolation and can be turned off if needed. Additionally, the CANUART subsystem (VDD_CANUART) can be powered independently from all the other power supplies to make use in which only the CANUART domain is operational and the rest of the SoC is turned off.
There are several analog inputs for PLLs that may require external filtering based on use case. Additionally, there are several voltage monitor (VMON) inputs that allow the user to monitor up to three power supplies: SYS, 3.3V, and 1.8V. Lastly, the VPP power input needs to be supplied by a controllable power supply to meet the sequencing requirements when AM62x OTP programming is in progress.
The following table shows the input specifications of each power rail of OSD62x-PM device.
Table 2‑2: OSD62x-PM Power Rail Specifications
| Voltage Rail | Description | Maximum current rating (mA) | Mode | Voltage (V) |
|---|---|---|---|---|
| VDD_CORE | Core supply | 2700 | 0.85V operation 0.75V operation | 0.75 0.85 |
| VDDA_CORE_CSIRX0 | CSIRX0 core supply | |||
| VDDA_CORE_USB | USB core supply | |||
| VDD_CANUART | CANUART core supply | 10 | ||
| VDDR_CORE | SRAM supply | 150 | 0.85 | |
| VDDS_DDR | DDR supply | 800 | 1.2 | |
| VDDS_OSC0 | MCU_OSC0 supply | 5 | 1.8 | |
| VDDA_MCU | RCOSC, POR, POK, and MCU PLL analog supply | 30 | ||
| VDDA_PLL0 | MAIN PLL, DDR PLL, DSS PLL0, and DSS PLL1 analog supply | 150 | ||
| VDDA_PLL1 | PER0 PLL and PER1 PLL analog supply | |||
| VDDA_PLL2 | ARM0 PLL and SMS PLL analog supply | |||
| VDDA_1P8_CSIRX0 | CSIRX0 1.8 V analog supply | |||
| VDDA_1P8_OLDI0 | OLDI0 1.8 V analog supply | |||
| VDDA_1P8_USB | USB0 and USB1 1.8 V analog supply | |||
| VDDA_TEMP | TEMP analog supply | |||
| VPP(1) | OTP ROM programming supply | 400 | During OTP programming(2) | 1.8 |
| Normal operation | 0 | |||
| VMON_1P8_SOC | Voltage monitor input for 1.8V SoC power supply | 1.8 | ||
| VDDA_3P3_USB | USB0 and USB1 3.3 V analog supply | 50 | 3.3 | |
| VMON_3P3_SOC | Voltage monitor input for 3.3V SoC power supply | |||
| VMON_VSYS(3) | Voltage monitor input | |||
| USB0_VBUS(4) USB1_VBUS(4) | VBUS input for USB interface | |||
| VDDSHV_CANUART | IO supply for CANUART | 10 | 1.8V operation 3.3V operation | 1.8 3.3 |
| VDDSHV_MCU | IO supply for MCU | 30 | ||
| VDDSHV0 | IO supply for IO group 0 | 150 | ||
| VDDSHV1 | IO supply for IO group 1 | |||
| VDDSHV2 | IO supply for IO group 2 | |||
| VDDSHV3 | IO supply for IO group 3 | |||
| VDDSHV4 | IO supply for IO group 4 | |||
| VDDSHV6 | IO supply for IO group 6 | |||
| VDDSHV5 | IO supply for IO group 5 | 30 |
The AM62x SoC does not support Dynamic Voltage Scaling (DVS), so VDD_CORE voltage needs to be chosen corresponding to the operating frequency of the core. The following table shows the VDD_CORE voltage setting and corresponding maximum frequency for the A53 cores:
Table 2‑3: VDD_CORE voltage vs A53 core frequency
| Operating Voltage (VDD_CORE) | Maximum A53 Frequency |
|---|---|
| 0.85V | 1.4GHz |
| 0.75V | 1.2GHz |
There are several power rails that have the same voltage specification. Some of these power rails can be grouped together to consolidate the power system for lower cost and area. On the other hand, some of the rails can also be dynamically controlled and need to be individually switchable to make use of AM62x low power modes. So, power architecture of the system must be targeted for the specific application requirements. The maximum current for each rail is also listed in the table above. This specification helps with budgeting power rails and matching them with regulators that have output specifications that match the power rail requirements.
In addition to the above specifications, the AM62x SoC has power rail slew rate requirements. All power rails must have a slew rate of < 18mV/us.
The OSD62x-PM has several IO pins whose function is to interface with the power system or control power and reset sequencing for external devices in the rest of the system. The following table provides a description of these pins along with notes on how to use them.
Table 2‑4: OSD62x-PM Power IO Pins
| OSD62x-PM/AM62x Signal Name | Description | Usage |
|---|---|---|
| PMIC_LPM_EN0 | Dual-function PMIC control output, Low Power Mode (active LOW) or PMIC Enable (active HIGH) | Can be used to signal low power mode enable to the power system |
| EXTINTN | External Interrupt to AM62x SoC | Can be used by the power system to signal faults/events to AM62x SoC |
| MCU_PORZ | MCU Domain cold reset | Main Power on Reset input that must be released after all power rails are stable |
| MCU_RESETZ | MCU Domain warm reset | Can be used to issue a warm reset to the device MCU domain |
| PORZ_OUT | Main Domain POR status output | Can be used to put other devices in RESET while AM62x is in Power on Reset state |
| RESETSTATZ | Main Domain warm reset status output | Can be used to put other devices in RESET while AM62x is in RESET state |
| MCU_RESETSTATZ | MCU Domain warm reset status output | Can be used to put other devices in RESET while AM62x MCU domain is in warm RESET state |
| RESET_REQZ | Main Domain external warm reset request input | Can be used to request a warm reset of the SoC |
| MCU_ERRORN | Error signal output from MCU Domain | Can be used to signal an external device that the SoC has encountered an error |
Depending on the use case, there are power sequencing requirements for the power inputs. The following figure shows the power up sequencing requirements for the OSD62x-PM.
The following table shows the operating voltage for each power input.
Table 2‑5: OSD62x-PM
| Operating Voltage | Power Input |
|---|---|
| 1.8V only | VDDA_MCU, VDDS_OSC0, VDDA_PLL0, VDDA_PLL1, VDDA_PLL2, VDDA_1P8_CSIRX0, VDDA_1P8_USB, VDDA_TEMP0, VDDA_TEMP1 |
| 1.8V or 3.3V | VDDSHV_CANUART, VDDSHV_MCU, VDDSHV0, VDDSHV1, VDDSHV2, VDDSHV3 |
| 3.3V only | VDDA_3P3_USB |
| 1.8V & 3.3V(1) | VDDSHV4, VDDSHV5, VDDSHV6 |
Important things to note regarding power sequencing for the OSD62x-PM:
The only power mode that requires a change in the power sequence is the partial IO power mode. In this mode, VDD_CANUART and VDDSHV_CANUART are supplied with an independent power supply. These power rails need to follow the power up sequencing described above but can remain powered ON when all other rails are turned OFF.
The following figure shows the requirements for the power-down sequence.
Important things to note regarding power-down sequence of OSD62x-PM:
Based on application requirements, some subsystems on AM62x SoC can be turned OFF to save power. See the following table for details on which subsystem can be turned OFF by connecting the corresponding power rails to GND.
Table 2‑6:Recommendations for Unused Power Rails
| Subsystem | Power rails that can be connected to GND if unused |
|---|---|
| USB0 and USB1 | VDDA_CORE_USB, VDDA_1P8_USB, VDDA_3P3_USB |
| CSIRX0 (If boundary scan is not used) | VDDA_CORE_CSIRX0, VDDA_1P8_CSIRX0 |
AM62x SoC contains One-Time Programmable (OTP) registers that can be programmed with information such as security keys. The power supply that provides power to the VPP power input must be controllable by the processor in order to meet the timing and sequencing requirements. The following steps are required from a power sequencing perspective to program the registers and are handled by the software provided by TI:
There are two main ways to design a power system for the OSD62x-PM:
1. Using a Power Management IC (PMIC).
2. Using Discrete Regulators.
Along with guidelines from TI, Octavo Systems provides the following guidelines when selecting discrete regulators for theOSD62x-PM SiP:
1. Power supplies must be configured to the required voltage level of the SiP and must always operate in the Recommended Operating Conditions of the OSD62x-PM SiP power input.
2. Power supplies must follow the power-up and power-down sequencing according to the specifications in Section.
3. Power supplies must meet the slew rate requirements outlined in Section 2.1.3.
4. All power rails must be fully powered up before MCU_PORz reset is released.
5. There must not be any residual voltage (<0.3V) on any power rails before the power supplies are turned ON.
6. MCU_PORz release must be glitch free.
7. Power rails can be grouped based on the operating voltage and power sequencing requirements.
8. Voltage monitor inputs must be connected as specified in Section 2.1.
9. Configure power sequencing/grouping based on whether Partial IO low power mode is used.
10. Power supplies must be able to support the current requirements of the power rail / group of power rails they are powering.
11. Some power supplies, for example a supply powering a UHS-1 SD card interface, must be able to switch between 3.3V and 1.8V and must be IO controlled.
12. The supply powering the VPP voltage input must have controllable voltage output.
TI provides a reference discrete power solution for the AM62x SoC that can also be used for the OSD62x-PM device. The application note describing the solution is located here: https://www.ti.com/lit/an/sluaak2/sluaak2.pdf. This solution may need to be modified based on the user application requirements. For example, VDDSHV_CANUART and VDD_CANUART may need an extra always-ON regulator to support Partial IO power mode. Additionally, current requirements in specific applications may differ based on the power rail grouping. Sequencing of the power rails can be achieved using the PGOOD outputs of regulators, gating logic, RC delay circuits, and SoC IO.
For reference, the block diagram describing this solution is provided below:
A reference design based on discrete power system for AM62x SoC is located here: https://www.ti.com/tool/SK-AM62#design-files. The reference design uses DDR4 memory making the power system compatible with OSD62x-PM based on design requirements.
TI provides the TPS65219 Power Management IC (PMIC) that is a perfect companion for the AM62x SoC and the OSD62x-PM SiP. The TPS65219 PMIC integrates three (3) DC-DC Buck convertors and four (4) LDO regulators and can be used to generate all the voltages needed to power the OSD62x-PM according to specifications. The following table provides an overview of the outputs along with their capabilities:
| TSPS65219 Output | Input Voltage Range | Output Voltage Range | Current Capability |
|---|---|---|---|
| BUCK1 | 2.5 V – 5.5 V | 0.6V – 3.4V | 3.5A |
| BUCK2 | 2A | ||
| BUCK3 | 2A | ||
| LDO1 | 1.5V – 5.5V (LDO/Load switch) 1.5V – 3.3V (Bypass) | 0.6V – 3.4V (LDO) 1.5V – 3.4V (Bypass) | 400mA |
| LDO2 | 400mA | ||
| LDO3 | 2.2V – 5.5V | 1.2V – 3.3V | 300mA |
| LDO4 | 300mA |
The following features of TPS65219 make it a good target to power the OSD62x-PM device:
TPS65219 has four (4) operating states:
Here is the State Diagram from TPS65219 datasheet for reference:
The following are the low power modes the OSD62x-PM supports:
The entire SoC and DDR is OFF except I/O pins in CANUART I/O Bank. This allows wakeup capability from CANUART I/O pins. To support this mode, VDDSHV_CANUART and VDD_CANUART must be powered separately from an always ON regulator. This is the only mode that requires explicit hardware design to support it. The system loses nearly all of its current state as DDR is OFF. Partial I/O is comparable with a Linux “poweroff” state.
In this mode, power supplies stay ON, but all on-chip power domains are shut OFF except for the always on domains. The DDR is put in self-refresh mode. This is the lowest power mode that allows for fast wake-up. The peripheral and MPU context must be saved in the DDR before entering this mode. When a wake-up event is detected, the boot ROM checks whether the device is waking from this mode and initiates a DDR resume process.
In this mode, the state of the SoC is the same as deep sleep except the MCU domain is ON. The DDR is put in self-refresh mode, but the MCU domain can run applications and use MCU domain peripherals. In addition to the wake-up sources for deep sleep mode, the MCU can generate a wake-up condition to the SoC to exit out of this mode.
In this mode, all modules are clock gated except for the GPIO. The DDR is put in self-refresh mode. All power domains are powered ON, but the PLLs may be put in bypass mode. GPIOs can be used to generate an interrupt to the device manager to wake up from this low power mode. If any other peripheral needs to wake up the device from this power mode, the PLL to the peripheral must be kept ON and it must be configured to generate an interrupt to the device manager core.
The following table shows the valid wake-up sources for each low power mode of the OSD62x-PM:
Table 4‑1: AM62x SoC Wake-up Sources
| Wake-up Source | Deep Sleep | MCU-only | Partial IO |
|---|---|---|---|
| Real-Time Clock (RTC) | Yes | Yes | No |
| MCU (WKUP) GPIO | Yes | Yes | No |
| Main I/O Daisy Chain (Main GPIO and Main UART) | Yes | Yes | No |
| USB Wakeup | Yes | Yes | No |
| WKUP UART | Yes | Yes | No |
| MCU IPC (for MCU Only mode) | No | Yes | No |
| CAN UART I/O Daisy Chain | Yes | Yes | Yes |
In addition to the low power modes, the CPU frequency can be used to fine tune power consumption based on the use case. This is done by defining operating performance points (OPPs) at different frequencies for the A53 cores. The table below shows the list of possible CPU frequencies while in the active state. Since, the AM62x SoC does not support dynamic voltage scaling, 1400 MHz can only be achieved by having the device boot with a core voltage of 0.85V.
Table 4‑2: AM62x SoC Frequency Scaling
| VDD_CORE Voltage (V) | A53 Core Frequency (MHz) |
|---|---|
| 0.75 or 0.85 | 200 |
| 400 | |
| 600 | |
| 800 | |
| 1000 | |
| 1250 | |
| 0.85 only | 1400 |
https://www.ti.com/lit/an/sprada6/sprada6.pdf
https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html
https://www.ti.com/lit/an/sluaak2/sluaak2.pdf
https://www.ti.com/lit/an/slvafd0b/slvafd0b.pdf
https://www.ti.com/lit/pdf/SPRSP58
https://www.ti.com/lit/pdf/SPRAD05
https://www.ti.com/lit/pdf/SPRAC76
https://www.ti.com/lit/pdf/SPRAD31
| Revision Number | Revision Date | Changes | Author |
|---|---|---|---|
| 1 | 6/25/2025 | Initial Release | Neeraj Dantu |
| Erik Welsh |
There has been multiple revisions to the OSDZU3-REF and some of the documentation is for specific revisions.
The revision of your OSDZU3-REF is printed under the fan next to the Octavo Systems logo. See the image below.
If there are multiple versions of a document make sure you select the one that matches your revision.