USB-C CC pins are pulled to the GND by AW3512 (VCONN switches) when VCONN is off
#21
(07-16-2020, 05:14 AM)oaklarch Wrote: My apologies if already answered, but:

1) Is the hardware fix applicable to BH phones?
2) If yes, what are the necessary steps to enable OTG on the software side?  After removing the regulators I tried bott the nightly Mobian and PMOS ANX image and only get stuff along the lines of "anx7688 0-0028: read failed (-6)".

I did the hardware mod on my CE Pinephone a few days ago. I haven't fully tested all OTG functions since I don't have a USB-C dock right now, but I was able to get a USB keyboard and mouse working in Mobian after I:
1) Installed the updated anx7688 firmware (for me, this got rid of the anx7688 error message I saw when watching dmesg -w). The process for this is described on the xnux.eu page about the Pinephone hardware bug.
2) Installed pinephone-devtools (I'm not 100% sure if this is required, but I'm pretty sure I was having issues with peripherals still not working until I had installed this)
  Reply
#22
On a side note related to this thread, the new postmarket release is coming with a usb-c dock, does that meant they fixed the hardware bug with the new release? I'd like to know if they'll be selling that main board on the store and if I can swap it out with my ubports version.
  Reply
#23
(07-17-2020, 08:50 AM)vatolsk Wrote: On a side note related to this thread, the new postmarket release is coming with a usb-c dock, does that meant they fixed the hardware bug with the new release? I'd like to know if they'll be selling that main board on the store and if I can swap it out with my ubports version.

Yes, the hardware bug  has been fixed in version 1.2a, see https://www.pine64.org/2020/07/15/july-u...e-version/. They also promised to establish repair shops and help everyone to fix it for their phone.
  Reply
#24
(07-17-2020, 09:58 AM)fsflover Wrote:
(07-17-2020, 08:50 AM)vatolsk Wrote: On a side note related to this thread, the new postmarket release is coming with a usb-c dock, does that meant they fixed the hardware bug with the new release? I'd like to know if they'll be selling that main board on the store and if I can swap it out with my ubports version.

Yes, the hardware bug  has been fixed in version 1.2a, see https://www.pine64.org/2020/07/15/july-u...e-version/. They also promised to establish repair shops and help everyone to fix it for their phone.
Oh nice
  Reply
#25
Can you elaborate on this? I tried doing what was written on xnux (setting a variable in sysfs) but /sys/class/typec is empty. Used Megi's 5.8 kernel and remade the uboot image as per instructions.
  Reply
#26
(07-17-2020, 03:11 PM)oaklarch Wrote: Can you elaborate on this? I tried doing what was written on xnux (setting a variable in sysfs) but /sys/class/typec is empty. Used Megi's 5.8 kernel and remade the uboot image as per instructions.

Try using one of the recent pre-built Mobian images. I just compared fresh installs of a recent nightly build (20200715) I had against an older one (20200707). The older one didn't have anything in /sys/class/typec, but the more recent one did. I was able to use the more recent pre-built image to update the firmware. It looks like the current images should now include the anx7688 driver, so there should be fewer hoops to jump through to get USB peripherals working.

I also double checked whether pinephone-devtools was needed for it, and it looks like it isn't, so scratch that.
  Reply
#27
(07-18-2020, 04:43 AM)jyc88 Wrote: Try using one of the recent pre-built Mobian images. I just compared fresh installs of a recent nightly build (20200715) I had against an older one (20200707). The older one didn't have anything in /sys/class/typec, but the more recent one did. I was able to use the more recent pre-built image to update the firmware. It looks like the current images should now include the anx7688 driver, so there should be fewer hoops to jump through to get USB peripherals working.

I also double checked whether pinephone-devtools was needed for it, and it looks like it isn't, so scratch that.

Tried the mobian images and still get "i2c read failed" and empty /sys/class/typec. I suspect I borked something while desoldering after all.

Thanks for help anywa.
  Reply
#28
Did you install the latest nightly and "apt get update"? For me Mobian just started showing folders in /sys/class/typec "recently" maybe 4 days ago.

Nightly
https://images.mobian-project.org/pinephone/nightly/
  Reply
#29
(07-19-2020, 11:57 PM)Ersatz Wrote: Did you install the latest nightly and "apt get update"? For me Mobian just started showing folders in /sys/class/typec "recently" maybe 4 days ago.

Nightly
https://images.mobian-project.org/pinephone/nightly/

Thanks, didn't do the system update before. Still nothing though.
  Reply
#30
I'd like to plug-in a usb keyboard so thinking about attempting the stupid fix on my braveheart - unless the local workshops idea has become a bit more concrete?
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Kill switches for Wifi/Bluetooth does not work luxgiammi 0 91 10-14-2024, 03:34 PM
Last Post: luxgiammi
  pine64 keyboard pogo 'no-go' pins --- 3 3,125 04-29-2022, 04:59 AM
Last Post: Humid Stylus
  PP v1.2 VCONN question m4xx3d0ut 0 1,000 03-18-2022, 12:26 PM
Last Post: m4xx3d0ut
  what are these pins above modem chip? zetabeta 1 1,900 12-13-2021, 04:38 AM
Last Post: kqlnut
  Pogo pins power clarification - reading schematics bokomaru 48 50,804 06-19-2021, 10:46 AM
Last Post: bokomaru
  Is the PinePhone only Pine-device with hardware switches? harrm 1 2,532 01-23-2021, 12:29 AM
Last Post: KC9UDX
  Where are the HW kill switches located? WaldoTheRanger 11 15,976 10-04-2020, 02:23 AM
Last Post: WaldoTheRanger
  Only enable modem when needed with kill switches sokolgeo 2 4,565 09-20-2020, 04:40 AM
Last Post: sokolgeo
  hardware switch wishlist/discussion - switches on the outside? mypine 7 8,232 04-12-2020, 10:40 AM
Last Post: wibble
  Kill switches blicken 2 4,223 02-08-2020, 03:51 PM
Last Post: wibble

Forum Jump:


Users browsing this thread: 1 Guest(s)