QNX Technical Articles

Date of this edition: June 7, 2021

---

Changes to these notes since July 31, 2019 are highlighted below with this icon:

---

This update provides:

• Fixes and updates to Screen functionality
• Updates to Screen documentation
• Board Support for the following:
  • Renesas R-Car H3 Starter
  • Renesas R-Car D3
  • Renesas R-Car V3M/V3H
  • Renesas R-Car M3-W/M3-N
  • Intel Gordon Ridge
  • Xilinx ZCU102

Target OS: This update is compatible with targets that are running the QNX^® Neutrino^® RTOS 7.0.

Host OS: To apply this update, you must have installed the QNX Software Development Platform 7.0 on one of the following development hosts:

• Microsoft Windows 10 Pro 64-bit, Windows 8.1 Professional 64-bit, or Windows 7 Professional 64-bit
• Linux Red Hat Enterprise Linux 7 64-bit, or Ubuntu Desktop 16.04 LTS 64-bit
• macOS version 10.10, 10.11, 10.12

Contents

• What's in this update?
• Fixed issues
• Known issues
• Verification issues
• Technical support

Throughout this document, you may see reference numbers associated with particular issues, changes, etc. When corresponding with our Technical Support staff about a given issue, please quote the relevant reference number. You might also find the reference numbers useful for tracking issues as they become fixed.

What's in this update?

Packaging

This update includes the following QNX SDP 7.0 Screen packages:

• QNX SDP 7.0 Graphics Implementation
• QNX SDP 7.0 Screen Documentation
• QNX SDP 7.0 Fonts, Device Input and Image Codecs

---

For QNX SDP 7.0 Graphics Implementation (with debug symbols), you will need to separately install the following packages: QNX SDP7 Graphics Implementation (with debug symbols) QNX SDP7 Screen Base Graphics QNX SDP7 Screen Device Input Utilities

---

Screen board packages must now be installed individually. They are located in the QNX Software Center. Navigate to Screen Board Support. When you expand Screen Board Support, you may see a list of several Screen board support packages. However, this update of Screen is currently compatible with only the following board support packages:

• QNX SDP 7.0 Screen Board Support Intel
• QNX SDP 7.0 Screen Board Support R-Car D3
• QNX SDP 7.0 Screen Board Support R-Car H3
• QNX SDP 7.0 Screen Board Support R-Car V3M
• QNX SDP 7.0 Screen Board Support R-Car V3H
• QNX SDP 7.0 Screen Board Support R-Car M3-N HW
• QNX SDP 7.0 Screen Board Support R-Car M3-W HW
• QNX SDP 7.0 Screen Board Support ZCU102

---

If you install this package, note that this update of Screen uninstalls all previously installed Screen board support packages. We recommend that if you are using Screen board support packages for boards other than those supported in this update, use a separate installation to install and use the updated Screen and its new board support packages. For more information on how to add an installation, see myQNX License Manager and QNX Software Center User's Guide.

Files and binaries installed with this update

You can use the QNX Software Center on your development host to see the contents of this package.

To see the contents of the Screen package, do the following:

1. Navigate to QNX SDP 7.0 Screen.
2. Right-click QNX SDP 7.0 Screen and then choose Properties.
3. In the Properties for Screen window, click Package Contents.

To see the contents of a board support package, do the following:

1. Navigate to Screen Board Support.
2. Right-click the appropriate board support package and choose Properties.
3. In the Properties window, click Package Contents.

Updates

• A new configuration parameter, allow-bypass, is now supported to allow client applications to bypass composition when showing a window's content on the display.
• Screen now supports the new SCREEN_PROPERTY_FD property. This property allows client applications to create graphics buffers via screen_buffer_create() and pass them as shared memory file descriptors to Screen.
• A new default interface type (CAPTURE_IF_DEFAULT_TYPE)is supported by the Video Capture library.

Board support

The following platforms are supported in this update:

---

Screen board support packages previously released with QNX SDP 7.0 may not be compatible with this update of Screen.

---

Fixed issues

This update has these fixes:

• Screen no longer crashes when it encounters a timing issue that's related to framebuffer access. (Ref# J1653526)

Known issues

These are the known issues with this update:

• If your application calls screen_manage_window() and the window manager that's managing the window terminates, your application will hang; slay your application to terminate it. (Ref# J2568255, J2568251)
• An application can call screen_manage_window() only once per window to be managed. (Ref# J2684228)
• An application with a window whose swap interval is non-zero will block or stop updating if Screen composites a second application with a window whose swap interval is zero on the same framebuffer as the first application. (Ref# J2640660)

• The following blitter modules may not report the status of blit operations:

  • inteldrm
  • gles2blt
  (Ref# J2564541, J2657676)

  You may observe incorrect pixel colors or rendering artifacts on your display after you perform a blit operation (e.g., screen_blit()).

• Screen supports only EGL_DEAFULT_DISPLAY as the EGL display connection when you use Khronos rendering APIs (e.g., eglGetDisplay()). (Ref# J2641608)
• Changing the z-order on child windows may affect input focus. (Ref# J2638277)
• A race condition exists such that when you use screen_attach_window_buffers() improperly, Screen may crash. (Ref# J2665185)
• The software blitter doesn't support YUV conversions. (Ref# J2536917)
• The software blitter doesn't support rotation. (Ref# J2551268)
• Screen won't drop root abilities until it loads the blit module. (Ref# J2692247)

  Workaround: Call screen_blit() or screen_fill() to force Screen to load the blit module.

• Applications that call screen_destroy_context() when Screen unexpectedly terminates may result in an infinite loop. (Ref# J2545504 )
• Screen may terminate unexpectedly without providing a core file. (Ref# J2583535 )
• From the QNX Software Center, if you verify the installation of this update, you'll see that it reports issues for the file target/qnx7/aarch64le/lib/dll/screen-gles2blt.so. (Ref# J2550850)

  You can disregard this error.

• YUV windows might not be displayed.

  A window that has all of the following characteristics might not be displayed if it's positioned at the limit of the display’s upper scale range:

  1. Its SCREEN_PROPERTY_FORMAT property is of a YUV format
  2. Its SCREEN_PROPERTY_SOURCE_SIZE property has an odd-numbered width or height
  3. It's on its own pipeline

  (Ref# J1387630)

  Workaround: Set the window's SCREEN_PROPERTY_SOURCE_SIZE property so that both its width and height are even-numbered.

• When screen_create_window_group() is called early in the system's bootup sequence, the window group that's generated by Screen may not be unique. (Ref# J1525054)

  Workaround: If you're calling screen_create_window_group() early in your system's bootup sequence, use a unique static name in the name argument instead of setting it to NULL.

• When you try to start screen after it terminates unexpectedly, it may fail to restart. (Ref# J2734282)

  Workaround: Slay and restart io-hid before trying to restart screen, or reboot your target.

• You may observe artifacts on your display that's associated with a Qualcomm target. (Ref# J2746813)

  When you're using a gles2 compositor (the usage parameter in your graphics.conf is set to gles2) and you change the SCREEN_PROPERTY_DISPLAY property of a window that's visible to move it to a different display, you may get undesirable effects.

  For a Board Support Package (BSP) that supports the Qualcomm target, contact Qualcomm Support.

• If you're using the Fontconfig library (i.e., libfontconfig.so) to configure and customize fonts, you need to provide a font configuration file (/etc/fontconfig/fonts.conf) on your target system. (Ref# J1687221, J1687021)

  See www.fontconfig.org for examples of font configuration files and more information on the Fontconfig software library.

Verification issues

These are the known verification issues that you may encounter when verifying your installation with this update:

• Some files in Device Input (7.0.0.SGA201702151847) are incompatible with QNX SDP 7.0 Screen Device Input Utilities (7.0 BuildID 6529) from this update because of a packaging error. (Ref# J2899620)

  The version of each of the following files:
  • calib-touch
  • calib-touch.sym
  will result in verification issues if you have Device Input (7.0.0.SGA201702151847) already in your installation. You must ensure that the version of each of these files are from QNX SDP 7.0 Screen Device Input Utilities (7.0 BuildID 6529).

  We recommend that you do the following:

  1. Identify the version of calib-touch that you have installed on your development host (it's not necessary to identify versioning on file variants with debug symbols):

     1. Execute the use command with the -i option from your development host for the $QNX_TARGET/cpu_arch/usr/bin/calib-touch file where cpu_arch is the CPU architecture of your target. For example:

        # use -i $QNX_TARGET/x86_64/bin/calib-touch
        							

     2. From the output of the use command, identify the version of the file in your installation. For example:

        QNX_BUILDID=(GNU)f8fce74430bf1ad97acc174344f543dc
        NAME=calib-touch
        DESCRIPTION=mtouch calibration utility for Screen
        DATE=2019/02/07-13:51:08-EST
        STATE=stable
        HOST=graphics-node-1
        USER=builder
        VERSION=graphics_release2.1x_be700
        TAGID=Graphics_br-21x_be-700-529
        PACKAGE=com.qnx.sdp.target.screen.device_input_screen/7.0.6529.S201902071641
        							

  2. Check that the version of calib-touch for each of the specified CPU architectures you have installed is compatible with the QNX SDP 7.0 Screen Base Graphics (7.0 BuildID 6529) update.

     If the version of the file is com.qnx.sdp.target.screen.device_input_screen/7.0.6529.S201902071641, then you may disregard any errors that QNX Software Center still reports on the QNX SDP 7.0 Device Input (7.0.0.SGA201702151847) package that are related to the following files:

     • calib-touch
     • calib-touch.sym

     You may proceed to build your target images on your development host; there's no need for you to continue with any further steps to verify your installation regarding this issue.

     ---

     For any other verification issues that QNX Software Center reports, you need to investigate. If you don't have version com.qnx.sdp.target.screen.device_input_screen/7.0.6529.S201902071641 of calib-touch installed, then you must proceed to the next steps to verify and repair your installation.

     ---

  3. Perform a Verify Installation on your installation.

     See the myQNX License Manager and QNX Software Center User's Guide for more information on how to verify your installation.

  4. Do not select any of the available repair actions on your Installation problems window; simply close this window by selecting Cancel.
  5. Select your Installed tab.
  6. Navigate to the QNX SDP 7.0 Screen Device Input Utilities (7.0 BuildID 6529) package (e.g., by typing "screen input utilities" in the Search field).

     If you're unable to locate QNX SDP 7.0 Screen Device Input Utilities from your Installed tab, select the All tab and look for the package under the Installed: category.

  7. Right-click and select Repair on the QNX SDP 7.0 Screen Device Input Utilities.

     If you perform subsequent Verify Installation actions on your installation, you will still see verification issues. However, since you've performed the repair action, you may disregard any errors QNX Software Center still reports on the QNX SDP 7.0 Device Input (7.0.0.SGA201702151847) package that are related to the following files:

     • calib-touch
     • calib-touch.sym

     ---

     For any other verification issues that QNX Software Center reports, you need to investigate.

     ---

  8. Confirm that you now have version com.qnx.sdp.target.screen.device_input_screen/7.0.6529.S201902071641 of calib-touch installed on your development host.

     Do so by executing the use command with the -i option as described eariler in these procedures.

     Once you've established that you have the compatible version of calib-touch on your development host, you may proceed to build your target images.

Technical support

To obtain technical support for any QNX product, visit the Support area on our website (www.qnx.com). You'll find a wide range of support options, including community forums.