Forums - USB-C Display on RB5

1 post / 0 new
USB-C Display on RB5
daryl1
Join Date: 24 Aug 22
Posts: 1
Posted: Mon, 2022-08-29 11:33

Has anyone managed to connect a USB-C display to the RB5 Dev kit? The moment I plug a display into the OTG port the board appears to crash. The display works with other sources (a MacBook and a Linux PC). I thought it may have been a power issue, so I've powered the display independantly to no avail.

Immediatly after connecting the display, the system stops responding.  On the USB debug port the following is dumped:

Format: Log Type - Time(microsec) - Message - Optional Info

Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.XF.3.2-00354-SM8250-1
S - IMAGE_VARIANT_STRING=Soc8250LAA
S - OEM_IMAGE_VERSION_STRING=crm-ubuntu54
S - Boot Interface: UFS
S - Secure Boot: Off
S - Boot Config @ 0x00786070 = 0x00000001
S - JTAG ID @ 0x00786130 = 0x0015a0e1
S - OEM ID @ 0x00786138 = 0x00000000
S - Serial Number @ 0x00786134 = 0x5b98e663
S - OEM Config Row 0 @ 0x007841e0 = 0x0000000000000000
S - OEM Config Row 1 @ 0x007841e8 = 0x0000000000000000
S - Feature Config Row 0 @ 0x007841f8 = 0x0040200000000400
S - Feature Config Row 1 @ 0x00784200 = 0xc000000000000000
S - Core 0 Frequency, 1516 MHz
S - PBL Patch Ver: 5
S - PBL freq: 600 MHZ
D -      6209 - pbl_apps_init_timestamp
D -     37039 - bootable_media_detect_timestamp
D -       918 - bl_elf_metadata_loading_timestamp
D -       713 - bl_hash_seg_auth_timestamp
D -      6149 - bl_elf_loadable_segment_loading_timestamp
D -      5524 - bl_elf_segs_hash_verify_timestamp
D -      7019 - bl_sec_hash_seg_auth_timestamp
D -       819 - bl_sec_segs_hash_verify_timestamp
D -        33 - pbl_populate_shared_data_and_exit_timestamp
S -     64423 - PBL, End
B -     78537 - SBL1, Start
B -    193705 - SBL1 BUILD @ 23:33:45 on Aug 17 2021
B -    197853 - usb: usb_shared_hs_phy_init: hs phy cfg size , 0xc
D -     10583 - sbl1_hw_init
D -         0 - boot_flash_init
B -    311740 - UFS INQUIRY ID: SKhynix HN8T05BZGKX015  A002
B -    313784 - UFS Boot LUN: 1
D -       884 - Auth Metadata
D -    118035 - sbl1_xblconfig_init
D -         0 - boot_config_data_table_default_init
D -       183 - boot_config_data_table_init
B -    337787 - CDT Version:3,Platform ID:11,Major ID:1,Minor ID:0,Subtype:3
D -      9730 - sbl1_hw_platform_pre_ddr
D -        31 - devcfg init
B -    360540 - PM: PM 0=0x8000024000020080:0x0 
B -    360601 - PM: PM 1=0x8000014000010040:0x0 
B -    365085 - PM: PM 2=0x8000014000010020:0x0 
B -    369568 - PM: PM 5=0x8000014000010040:0x0 
B -    374021 - PM: WARM reset by PS_HOLD
B -    381372 - PM: PMA_2 PON:KPD WR:PS ON:WARM POFF:PS OFF:POFF
B -    387990 - PM: PMA_3 PON:KPD WR:PS ON:WARM POFF:PS OFF:POFF
B -    493764 - PM: SET_VAL:Skip
B -    494313 - PM: PSI: b0x00_v0x53
B -    500352 - PM: Device Init # SPMI Transn: 5316
B -    509777 - PM: Driver Init # SPMI Transn: 558
B -    522709 - PM: battery Id: 7530
B -    522739 - PM: Debug Board detected
D -    173606 - pmic XBL init
D -     28548 - vsense_railway_cpr init
D -    209657 - sbl1_hw_pre_ddr_init
D -         0 - boot_dload_handle_forced_dload_timeout
D -       122 - sbl1_ddr_set_params
B -    570655 - PASS1 Cookie =  0xcafe1111
B -    573827 - HAL_DDR_SDI_Recover() start:  DBG PDC Tr = 0x1, First Pass expire = 0x0, First Pass complete = 0x1 , BIMC Alt ARES  = 0x0 , PASS2 Cookie = 0xcafecab0 
B -    589168 - SHRM run state = 0x1, SHRM stall state = 0x0 
B -    592859 - HAL_DDR_SDI_Recover() end : DBG PDC Tr = 0x1, First Pass expire = 0x0, First Pass complete = 0x1 , BIMC Alt ARES  = 0x0 , PASS2 Cookie = 0xcafebabe 
B -    609817 - SHRM run state = 0x1, SHRM stall state = 0x0 
D -     42944 - sbl1_ddr_init
D -        31 - boot_pre_ddi_entry
B -    621620 - do_ddr_training, Start
D -         0 - do_ddr_training, Delta
D -      6802 - sbl1_do_ddr_training
D -         0 - sbl1_hand_control_to_devprog_ddr
D -        30 - boot_ddi_entry
B -    639859 - Pimem init cmd, entry
D -      3996 - Pimem init cmd, exit
D -      7473 - sbl1_post_ddr_init
D -        30 - sbl1_hw_init_secondary
B -    653615 - APDP Image Load, Start
D -       915 - Auth Metadata
D -       458 - Segments hash check
D -      9699 - APDP Image Loaded, Delta - (8204 Bytes)
B -    666608 - Mem dump cmd, entry
D -       427 - Mem dump cmd, exit
D -      8418 - boot_dload_dump_security_regions
B -    678259 - usb: ser_str_cookie_pid - 85BCE559
B -    682742 - usb: fedl, vbus_low
B -    687348 - TCSR reg value 0x10 
D -         0 - boot_init_for_dload
D -         0 - sbl1_hw_dload_init
D -       549 - xbl_ramdump_configure_header
B -    700585 - XBLRamDump Image Load, Start
D -       946 - Auth Metadata
D -      2440 - Segments hash check
D -     11864 - XBLRamDump Image Loaded, Delta - (354412 Bytes)
B -    721569 - External heap deinit, Start
B -    721599 - External heap init, End
B -    725625 - External heap init, Start
B -    729316 - External heap init, End
B -    734470 - WARNING: unsupported uDDRType=0, use DDR5 as default
 
B -    766617 - DisplayDxe: Resolution 1440x2880 (1 intf)
 
B -   1112365 - Mem dump cmd, entry
D -        31 - Mem dump cmd, exit
B -   1165405 - usb: init start
 
At this point the HDMI output freezes and the debug port stops responding. The system is setup with an extrnal monitor on the HDMI port, a keyboard and mouse connected through a USB hub to one of the USB type A ports, a micro-USB connection to a PC from the debug port and the power cable from the adapter.
 
Is there some board configuration to allow the USB-C OTG port to work with an external display?
 
 
  • Up0
  • Down0

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.