Difference between revisions of "PinePhone v1.2"

From PINE64
Jump to navigation Jump to search
(Added schematics for v1.2a)
Line 5: Line 5:
== Schematics ==
== Schematics ==
* [http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schematic.pdf  Hardware schematic v1.2] (2020-03-10, for CE: UBports)
* [http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schematic.pdf  Hardware schematic v1.2] (2020-03-10, for Community Edition: UBports)
* [http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2a%20Released%20Schematic.pdf  Hardware schematic v1.2a] (2020-06-08, for CE: postmarketOS)        
* [http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2a%20Released%20Schematic.pdf  Hardware schematic v1.2a] (2020-06-08, for Community Edition: postmarketOS)
== Changes from v1.1 ==
== Changes from v1.1 ==

Revision as of 11:57, 12 August 2020

The PinePhone v1.2 is a hardware revision of the PinePhone that shipped in 2020.

This page contains information and resources which are specific to the v1.2 revision of the PinePhone. For other revisions or for resources related to all PinePhone revisions, see PinePhone.


Changes from v1.1

The v1.2 mainboard revision changes the routing of several GPIOs to fix bugs and to improve power management. Therefore, it needs an updated device tree. The state of PL6 at boot can be used to distinguish between v1.1 (it can be pulled high) and v1.2 (it will remain low).

  1. The WiFi module's CHIP_EN input (connected to the kill switch) is now pulled down, so the WiFi will turn off reliably when the switch is off.
  2. PL2 is now connected to the WiFi module's reset pin, allowing the WiFi to be turned off or reset in software.
  3. The magnetometer's DRDY pin is now connected to PB1, allowing interrupt-driven periodic sensor readings.
  4. LINEOUTP is again connected to the speaker amplifier's INP input (like in v1.0), increasing the SNR of the rear speaker.
  5. PH7 is now connected to the modem's AP_READY input (instead of WAKEUP_IN), allowing the modem to buffer URCs (interrupts) while the phone is asleep.
  6. The modem's RI output and DTR input had their GPIOs swapped between PL6 and PB2, so the RI signal can be detected without powering the main pin controller.
  7. Both PL9 and VBUS_CTRL (from the ANX7688) are now connected to N_VBUSEN on the PMIC. This causes the PMIC to automatically stop drawing power from the USB port when supplying power to a USB-OTG peripheral. It also allows the ANX7688 to automatically control the direction of current flowing through the USB port.
  8. As part of the previous change, the ANX7688's reset input was moved to PD6; this pin previously controlled the USB OTG power.
  9. Some of the regulators supplying the ANX7688 were rearranged, to reduce power consumption when the USB port is not connected and not being used to transmit video.
  10. As part of the previous change, PD11 now controls the ANX7688's 1v0 digital power domain.
  11. The modem's STATUS output is now connected to PH9, allowing the modem on/off state to be visible in software (note: this only works while the modem is powered). Since it is no longer connected to PB3, reading STATUS no longer turns the modem on.
  12. The modem no longer has access to the I2C bus containing the sensors.
  13. HBIAS is now connected to the headphone jack.



Backlight LED current regulation depends on gpio0-ldo voltage stability due to feedback voltage from current sensing resistor being modified via SoC's PWM pin and pullup resistor to gpio0-ldo. gpio0-ldo also powers the CTP controller and light/proximity sensor, among other things. When backlight brightness is very low and the CTP controller actively communicates on the I2C bus the backlight blinks heavily. It's not a very good idea to tie boost converter's current regulating feedback circuit to the potential source of noise, especially since the noise will have much larger effect when the backlight LED current is low. It's possible this can be mitigated if C1110 can be raised to 22-47uF range, or by changing the resistor values in the feedback circuit.

PWM duty cycle for the lowest brightness of the backlight is also not very predictable, varying from 7-20% (tested with a small sample size of 2 devices). Therefore it's not possible to come up with a single device tree brightness settings that will work for everyone, requiring per-device calibration.

On PinePhone 1.0, this was not the case, PWM signal was directly fed to the CE pin of the regulator, and lowest brightness setting seems more stable. On the other hand, the lowest achievable brightness was brighter than on 1.1+.


USB-C CC pin issues from BraveHeart are still present in the original 1.2 revision boards, since they were discovered after production of 1.2. Revision 1.2a fixes these.