SLVUBO3A April   2019  – October 2020 TPS650330-Q1

 

  1.   Trademarks
  2. 1BOOSTXL-TPS65033 Components and Environment
  3. 2BOOSTXL-TPS65033 Board Information
    1. 2.1 Critical Socketed Board Connections
      1. 2.1.1 Power Switches
    2. 2.2 Jumpers and Test Points
  4. 3Programming GUI Operation
    1. 3.1 Initial Set-up
      1. 3.1.1 Finding the GUI
      2. 3.1.2 Offline Installation
      3. 3.1.3 Flashing the MSP430F5529 LaunchPad
      4. 3.1.4 Flashing the MSP432E401Y Launch Pad
    2. 3.2 Connection Debugging
    3. 3.3 Basic Operation of the GUI
      1. 3.3.1 Home
      2. 3.3.2 Block Diagram
      3. 3.3.3 Registers
      4. 3.3.4 Device Configuration
        1. 3.3.4.1 Using Device Configuration to Define Spin Settings
        2. 3.3.4.2 Configuring the Power Sequence
    4. 3.4 Scripting
  5. 4Recommended Operating Procedure
  6. 5BOOSTXL-TPS65033 Schematic
  7. 6BOOSTXL-TPS65033 Board Layers
  8. 7BOOSTXL-TPS65033 Bill of Materials
  9. 8Revision History

4 Recommended Operating Procedure

  1. Connect the socketed board to the MSP430F5529 LaunchPad by aligning placing the socketed board on top of the LaunchPad, aligning the J1/J3 and J2/J4 headers, and pressing the two boards together. For the MSP432E401Y, align with the J5/J7 and J6/J8 headers.
  2. Ensure S1, S2, and S3 of the socketed board are not asserted (down position), and connect the LaunchPad to the PC using a micro-USB cable. A TPS65032001-Q1 or TPS65033x-Q1 device may be inserted into the socket at any time that S2 is open and proper ESD considerations are observed. Ensure the unit's Pin 1 indicator is aligned with the Pin 1 silkscreen indicator on the lower left corner of the socketed board.
  3. Ensure the Device Selection jumper (J2) matches the generic part number of the device populated in the socket.
  4. If this is the first time using the LaunchPad with the TPS6503xx-Q1 GUI, flash the LaunchPad using the steps outlined in Section 3.1.3 or Section 3.1.4. This will permanently configure the LaunchPad to act as a USB-to-I2C adapter and will not be necessary for subsequent sessions.
  5. Set S2 to the active position. The D1 LED will indicate when power is supplied to the socket.
  6. Verify the connection status of the adapter in the bottom left corner of the GUI window. If Hardware not Connected is displayed, toggle the connection icon once to refresh the adapter connection. With the D1 LED active and the adapter recognized by the GUI, I2C communication should be available to the PMIC. The adapter will disconnect if I2C communication fails. Verify that the I2C pull-up voltage is available (J12 and VIO test point) if the GUI consistently disconnects after read or write attempts.
  7. Navigate to the Register Map or Device Configuration page, and select the Read All Registers button in the top right corner of the GUI window.
  8. The Register Map will populate with the returned values as the PMIC replies to the I2C read requests. The Register Map can directly interact with the PMIC through drop down menus for each register field or by directly writing into the value column for the individual registers. For a graphical representation of common device settings, select the slider icon below the pencil icon in the left toolbar to navigate to the Device Configuration view. These visual indicators are linked directly to the respective bits or bitfields in the register map.
  9. Selecting the tabs at the top of the Device Configuration view will navigate through the categorized register fields.
  10. By default, the Control and Configuration registers of the PMIC are always locked after a re-start event, preventing accidental I2C writes to the device. The check-boxes in the top right corner of the Device Configuration view can verify if critical registers are accepting write instructions from the I2C master. These check boxes can also be used to lock and unlock the associated registers.
  11. By default, certain regulators are dependent on either the status of SEQ (S1), or the status of SEQ and GPIO (S3). All sequencing dependencies are visible in the regulator's respective tab, or by using the Sequencing Overview tab within the Device Configuration view.
  12. When registers are unlocked, any changes to the device registers will take effect immediately.
  13. The PMIC will always return to default settings if a fault occurs that forces a transition to the RESET state.
  14. Register changes will not be stored in EEPROM unless the programming instruction has been sent to the PMIC through the I2C.
  15. The EEPROM is programmed when a hex value of 0x2D is written to register 0x4A. In the GUI, this can be done directly through the register map or by clicking the Flash EEPROM button in the Re-Program PMIC view of the GUI.