Forums - Displayport problem

21 posts / 0 new
or Register
Last post
Displayport problem
vents.kanders
Join Date: 10 Jun 20
Posts: 8
Posted: Fri, 2021-01-22 06:36
Top

Hi,

Displayport output isn't working. Here's the kernel message log:

[  175.882565] msm-usb-ssphy-qmp 88e8000.ssphy: USB DP QMP PHY: Update TYPEC CTRL(3)
[  175.943243] msm-dwc3 a600000.ssusb: DWC3 exited from low power mode
[  175.946544] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[  175.946685] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 3
[  175.952396] xhci-hcd xhci-hcd.1.auto: hcc params 0x0230ffe5 hci version 0x110 quirks 0x0000000000010010
[  175.952548] xhci-hcd xhci-hcd.1.auto: irq 432, io mem 0x0a600000
[  175.958076] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[  175.958105] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[  175.958131] usb usb3: Product: xHCI Host Controller
[  175.958156] usb usb3: Manufacturer: Linux 4.19.113 xhci-hcd
[  175.958181] usb usb3: SerialNumber: xhci-hcd.1.auto
[  175.965925] hub 3-0:1.0: USB hub found
[  175.966286] hub 3-0:1.0: 1 port detected
[  175.975851] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[  175.975954] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 4
[  175.976004] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.1 Enhanced SuperSpeed
[  175.976518] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[  175.977672] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19
[  175.977689] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[  175.977704] usb usb4: Product: xHCI Host Controller
[  175.977719] usb usb4: Manufacturer: Linux 4.19.113 xhci-hcd
[  175.977733] usb usb4: SerialNumber: xhci-hcd.1.auto
[  175.996724] hub 4-0:1.0: USB hub found
[  175.996895] hub 4-0:1.0: 1 port detected
[  176.065186] usbpd usbpd0: Error (-14) sending VDM command 1
[  176.204867] xhci-hcd xhci-hcd.1.auto: remove, state 4
[  176.204992] usb usb4: USB disconnect, device number 1
[  176.209997] xhci-hcd xhci-hcd.1.auto: USB bus 4 deregistered
[  176.210223] xhci-hcd xhci-hcd.1.auto: remove, state 4
[  176.210329] usb usb3: USB disconnect, device number 1
[  176.217991] xhci-hcd xhci-hcd.1.auto: USB bus 3 deregistered
[  176.221370] msm-dwc3 a600000.ssusb: DWC3 in low power mode
[  176.283801] msm-dwc3 a600000.ssusb: DWC3 exited from low power mode
[  176.285941] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[  176.286032] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 3
[  176.293293] xhci-hcd xhci-hcd.1.auto: hcc params 0x0230ffe5 hci version 0x110 quirks 0x0000000000010010
[  176.293388] xhci-hcd xhci-hcd.1.auto: irq 432, io mem 0x0a600000
[  176.296834] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[  176.296850] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[  176.296865] usb usb3: Product: xHCI Host Controller
[  176.296879] usb usb3: Manufacturer: Linux 4.19.113 xhci-hcd
[  176.296895] usb usb3: SerialNumber: xhci-hcd.1.auto
[  176.301040] hub 3-0:1.0: USB hub found
[  176.301270] hub 3-0:1.0: 1 port detected
[  176.308826] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[  176.308919] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 4
[  176.308973] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.1 Enhanced SuperSpeed
[  176.309459] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[  176.310534] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19
[  176.310550] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[  176.310564] usb usb4: Product: xHCI Host Controller
[  176.310578] usb usb4: Manufacturer: Linux 4.19.113 xhci-hcd
[  176.310592] usb usb4: SerialNumber: xhci-hcd.1.auto
[  176.314422] hub 4-0:1.0: USB hub found
[  176.314612] hub 4-0:1.0: 1 port detected
[  176.324325] i2c_geni 884000.i2c: i2c error :-107
[  176.324585] i2c_geni 884000.i2c: i2c error :-107
[  176.324950] i2c_geni 884000.i2c: i2c error :-107
[  176.325207] i2c_geni 884000.i2c: i2c error :-107
[  176.325234] AUX SBU1/2 switch status is invalid = 0
[  176.325249] [drm:dp_aux_configure_aux_switch][msm-dp-err][1587]failed to configure fsa4480 i2c device (-5)
[  176.325426] [drm:dp_display_host_ready][msm-dp-err][303 ][not initialized]: state (0x8): |CONNECTED|
[  176.325495] [drm:dp_panel_read_dpcd][msm-dp-err][303 ]error reading DP_TRAINING_AUX_RD_INTERVAL
[  176.325509] [drm:dp_panel_read_sink_caps][msm-dp-err][303 ]panel dpcd read failed/incorrect, set default params
[  176.325583] [sde error]EDID read failed
[  176.325597] [drm:dp_panel_read_edid][msm-dp-err][303 ]EDID read failed
[  176.325611] [drm:dp_panel_read_sink_caps][msm-dp-err][303 ]panel edid read failed, set failsafe mode
[  176.325673] [drm:dp_link_parse_sink_count][msm-dp-err][303 ]failed to read sink count
[  176.325734] [drm:dp_link_parse_sink_status_field][msm-dp-err][303 ]DP link status read failed
[  176.325892] [drm:dp_panel_read_mst_cap][msm-dp-err][303 ]dpcd mstm_cap read failed, rlen=-110
[  177.835823] msm-dwc3 a600000.ssusb: DWC3 in low power mode

I tried different adapters, hubs, and displays but the result was the same.

Any ideas what's wrong?

  • Up0
  • Down0
Re: Displayport problem
kevin.dai
Join Date: 21 Oct 20
Posts: 137
Posted: Fri, 2021-01-22 11:00
Top

How to do you use and test displayport? can you list steps?

 

  • Up0
  • Down0
Re: Displayport problem
vents.kanders
Join Date: 10 Jun 20
Posts: 8
Posted: Mon, 2021-01-25 23:35
Top

I tried:

1. System running with HDMI display connected. Then, connecting DP display.

2. System running with no display connected. Then, connecting DP display.

3. Booting system with DP display attached.

4. Booting system with HDMI and DP displays attached.

 

All of this with different cables / usb-c hubs.

Sometimes, after connecting DP display to a running system, the system will free/crash and won't restart/boot unless the DP display is detached and power is recycled.

  • Up0
  • Down0
Re: Displayport problem
kevin.dai
Join Date: 21 Oct 20
Posts: 137
Posted: Tue, 2021-01-26 15:57
Top

We will try your steps

  • Up0
  • Down0
Re: Displayport problem
kevin.dai
Join Date: 21 Oct 20
Posts: 137
Posted: Tue, 2021-02-09 14:02
Top

The test image is ready, get test image from private message

 

 

  • Up0
  • Down0
Re: Displayport problem
vents.kanders
Join Date: 10 Jun 20
Posts: 8
Posted: Tue, 2021-02-23 00:22
Top

Hi Kevin,

I haven't received anything in PM. Can you please resend it?

  • Up0
  • Down0
Re: Displayport problem
vents.kanders
Join Date: 10 Jun 20
Posts: 8
Posted: Tue, 2021-02-23 01:21
Top

Previously you had attached some updated boot.img. We tried it and here's the kernel output after connecting DP: rb5_dmesg_dump_2021-02-23.txt

 

BR,

Vents

  • Up0
  • Down0
Re: Displayport problem
andris.kuciks
Join Date: 22 Jul 20
Posts: 16
Posted: Tue, 2021-02-23 03:02
Top

Hi Kevin,

Another thing, when we flashed the RB5 with the boot.img you provided we're not able to ssh connect to RB5 anymore.
A connection is created but when asking for a password for "root" user,  "oelinux123" doesn't work anymore,  device returns that provided password is incorrect.

  • Up0
  • Down0
Re: Displayport problem
kevin.dai
Join Date: 21 Oct 20
Posts: 137
Posted: Wed, 2021-02-24 10:39
Top

Have you installed or setup somthing on your board beore updating boot.img?

Can you use sdkmanager to update board? after board bootup, fastboot flash boot.img.

Please try it.

 

  • Up0
  • Down0
Re: Displayport problem
andris.kuciks
Join Date: 22 Jul 20
Posts: 16
Posted: Wed, 2021-02-24 23:31
Top

Hi Kevin,

I used sdkmanager to generate new system image. After that I found the original boot image in sdkmanager/QRB5165.1.0.0-201116/full_build/ufs and replaced the original *boot.img  with the one you provided. Afterwards using sdkmanager I flashed the new system image on RB5.

Based on your comments it seems like there is another way to do this. Could you please explain how to do the fastboot flash? There are only two options in the sdkmanager when I select the preferred image :

1 = Download resources and generate system.img with current release
2 = Flash full build (require system.img generation first)

So how to do the board update?

  • Up0
  • Down0
Re: Displayport problem
kevin.dai
Join Date: 21 Oct 20
Posts: 137
Posted: Thu, 2021-02-25 10:09
Top

$adb reboot bootloader

$fastboot flash boot_a boot.img

$fastboot flash boot_b boot.img

  • Up0
  • Down0
Re: Displayport problem
andris.kuciks
Join Date: 22 Jul 20
Posts: 16
Posted: Fri, 2021-02-26 01:33
Top

Hi Kevin,

So I tried to update boot.img by following the commands you provided. It seemed like the bootloader got updated but we are still unable to get any output from DP only on HDMI. Here are DMESG message log.  Hope this helps.

Regards,

Andris

  • Up0
  • Down0
Re: Displayport problem
kevin.dai
Join Date: 21 Oct 20
Posts: 137
Posted: Fri, 2021-02-26 11:20
Top

Thank your log message, I will  study it.

  • Up0
  • Down0
Re: Displayport problem
andris.kuciks
Join Date: 22 Jul 20
Posts: 16
Posted: Mon, 2021-03-01 02:56
Top

Also, since I updated to boot.img I'm not able to connect to the board with ssh. I mean I can connect but when RB5 prompts for root password "oelinux123" does not work. I reflashed RB5 with new image using sdkmanager couple of times but this problem still exists.

  • Up0
  • Down0
Re: Displayport problem
mita.rathod
Join Date: 17 Sep 18
Posts: 59
Posted: Wed, 2021-03-03 08:58
Top

Hi Andris,

Has ssh login been successful before? Is the password wrong or is the connection refused, please use adb to confirm if sshd is running.

Thanks!

  • Up0
  • Down0
Re: Displayport problem
andris.kuciks
Join Date: 22 Jul 20
Posts: 16
Posted: Fri, 2021-03-05 01:35
Top

Hi Mita,

Yes ssh login used to work before. When I try to ssh as root RB5 returns incorrect password all the time, but when I try to login as root to device directly the same password works. adb works as well

  • Up0
  • Down0
Re: Displayport problem
kevin.dai
Join Date: 21 Oct 20
Posts: 137
Posted: Tue, 2021-03-09 14:17
Top

Hi Andris

I did flash boot.mg which I sent you before,  and still can ssh log in device.

make sure PermitRootLogin yes in /etc/ssh/sshd_config

I will get USB-C->DP adator to simulate your enviroment.

I got imformation  about USB-c->DP use case.

connect both HDMI and USB->DP con display, and disconnect HDMI, or plug/unplug HDMI, then USB-DP should work. please try it.

Thanks

 

 

 

  • Up0
  • Down0
Re: Displayport problem
andris.kuciks
Join Date: 22 Jul 20
Posts: 16
Posted: Wed, 2021-03-10 06:10
Top

Hi Kevin,

So the PermitRootLogin was set to "check for password" changed it to "yes" and now the ssh is working again, thanks!

About the DP port we tried the steps you suggested but still we weren't able to get any output on the DP. Here are picture of the log messages from DMESG when DP connected and when disconnected. If you wish I can provide you with plain text log file with those messages visible in the pictures.

Hope you can test this yourself and report back with the results!

Andris

  • Up0
  • Down0
Re: Displayport problem
kevin.dai
Join Date: 21 Oct 20
Posts: 137
Posted: Mon, 2021-03-15 10:56
Top

I  order a new monitor this week, with two monitors I can simulate user case, I will let you know test result.

 

  • Up0
  • Down0
Re: Displayport problem
linux.kernel.noob
Join Date: 20 May 21
Posts: 1
Posted: Thu, 2021-05-20 23:23
Top

Either try rotating the cable or ask vendor for queries as it seems aux switch is not there.

  • Up0
  • Down0
Re: Displayport problem — Best Answer
Mayur
Join Date: 26 Feb 21
Posts: 16
Posted: Mon, 2021-05-24 22:02
Top

Hi vents.kanders,

You can display to RB5 by using following steps 

1. Connect RB5 to Moniter or TV using HDMI cable 

2. Set DIP_SW_0 (PIN4) to OFF

3. Entering to Fastboot 

    a. Press & hold VOL - Key then press power ON to enter to fastboot mode  

     b.   Alternativly "adb reboot bootloader" from the command promot 

      #fastboot oem select-display-panel none 

4. Power OFF & ON the device 

5. Chcek HDMI display after the device boot up: 

      #cd /usr/bin 

      #./modtest -M msm_drm -c 

     #./modtest -M msm_drm -s 29:1920x1080x60x148500vid 

 

Thanks & Regards,

Mayur 

 

 

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.