Developer Resources
Board support packages
Foundry27 projects
Forums
Home
Developer Resources
Technical Articles

QNX Technical Articles

QNX® Software Development Platform 7.0— Screen (7.0 BuildID 758): Release Notes

Date of this edition: June 7, 2021

Note: Changes to these notes since May 9, 2018 are highlighted below with this icon: New:

This update provides:

  • Fixes and updates to Screen functionality
  • Updates to Screen documentation
  • Board Support for the following:
    • Renesas R-Car H3 Starter
    • ASRock BeeBox-S 6200U
    • Intel Gordon Ridge
    • Intel NUC6i5SYK
    • Renesas R-Car V3M
    • Renesas R-Car M3-W/M3-N
    • NXP S32V234 EVB revisions:
      • NXP S32V234 EVB (SCH_28899 REV D)
      • NXP S32V234 EVB2 (SCH_29288 REV B2)

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

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 QNX SDP 7.0 Screen package.

Packaging structure changes

You'll see updates to the structure of QNX SDP 7.0 Screen.

Prior to installing this update, you would see the following under QNX SDP 7.0 Screen:

  • QNX SDP 7.0 DejaVu Fonts
  • QNX SDP 7.0 Font Engine
  • QNX SDP 7.0 Device Input
  • QNX SDP 7.0 Screen Image Codecs
  • QNX SDP 7.0 Screen Video Capture
  • All Screen board packages that are supported by the installed version of QNX SDP 7.0 Screen

After installing this update, you now see the following under QNX SDP 7.0 Screen:

  • QNX SDP 7.0 Screen Documentation
  • QNX SDP 7.0 Fonts, Device Input and Image Codecs
    • QNX SDP 7.0 DejaVu Fonts
    • QNX SDP 7.0 Font Engine
    • QNX SDP 7.0 Device Input
    • QNX SDP 7.0 Image Codecs
  • QNX SDP 7.0 Graphics Implementation
    • QNX SDP 7.0 Screen Base Graphics
    • QNX SDP 7.0 Device Input Utilities
    • QNX SDP 7.0 Screen Video Capture

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, 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 H3
  • QNX SDP 7.0 Screen Board Support S32V
  • QNX SDP 7.0 Screen Board Support R-Car V3M
  • QNX SDP 7.0 Screen Board Support R-Car M3-N HW
  • QNX SDP 7.0 Screen Board Support R-Car M3-W HW
Caution:

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

Screen API updates

The API changes introduced by this update are as follows:

  • A new SCREEN_DISPLAY_TYPE_DSI connection type that's used to identify a MIPI DSI connection to the display is now supported.
  • A new SCREEN_INVALID_ID definition is introduced to indicate an invalid or uninitialized value for SCREEN_PROPERTY_ID.
  • A new SCREEN_USAGE_PHYSICAL usage flag is now supported. Use this flag to suggest to Screen that your buffer should be physically contiguous and the physical address should be provided.
  • New SCREEN_ACQUIRE_AND_RELEASE_OTHERS and SCREEN_ACQUIRE_DONT_BLOCK flags are now supported for the function screen_acquire_buffer().
  • A new function screen_create_window_from_class() that supports the ability to create a window whose properties will be based on a class that you've defined in your graphics configuration file.
  • New functions screen_register_window_manager() and screen_unregister_window_manager() that supports the abilities for a context to register and unregister itself as the window manager of a display.
  • A new SCREEN_FORMAT_NV16 pixel format that's used to identify a format with 8-bit Y plane, 2x1-subsampled, and interleaved U and V planes is now supported.

Functionality updates

The functional behavior changes introduced by this update are as follows:

  • The function screen_acquire_buffer() now supports only the following values (or combination of) for its flags argument:
    • 0
    • SCREEN_ACQUIRE_AND_RELEASE_OTHERS
    • SCREEN_ACQUIRE_DONT_BLOCK
  • When you set the SCREEN_PROPERTY_NAME property for groups, it now must be unique within your system and not be prefixed with "__scrn-".
  • When you use the function screen_create_window_group() to create a window group, the name that you choose for your window group now must be unique within your system and not be prefixed with "__scrn-".
  • When you register for notifications of type SCREEN_NOTIFY_EVENT with a NULL object, you'll now receive one notification for each event that's already residing in your context's event queue. Previously, you would receive a notification for only new events arriving in your event queue after your registration.
  • The self-layout parameter is now supported in the class subsection of the graphics configuration file (graphics.conf).

Board support

The following platforms are supported in this update:

Board Supplier Board Name CPU GPU GPU Stack Display Controller Display Interface Number of Displays Display Resolution Monitor Name Touch Video Capture Interface Video Decoder
Renesas

R-CAR H3 Starter (1.2 and 2.0)

R-CAR H3 Salvator X

ARM Quad Cortex-A57 GX6650 ImgTech PowerVR Series6XT VSPD HDMI, LVDS 2 1080p

Lilliput 10.1″ FA1012 (HDMI)

 eGalax N/A N/A
Renesas R-CAR M3-W/M3-N ARM Dual Cortex-A57 GX6250 ImgTech PowerVR Series6XT VSPD HDMI 2 1080p

Lilliput 10.1″ FA1012 (HDMI)

 eGalax N/A N/A
Renesas R-CAR V3M Starter ARM Dual Cortex-A53 GX6650 ImgTech PowerVR Series6XT VSPD HDMI 1 720p

Lilliput 10.1″ FA1012 (HDMI)

 eGalax N/A N/A
NXP S32V234 EVB (Treerunner)

EVB (SCH_28899 REV D)

EVB2 (SCH_29288 REV B2)

 ARM Quad Cortex A53 GC3000 Vivante 6.x 2DACE/DCU LVDS, HDMI 1 (supports both LVDS and HDMI, but only 1 at a time) 1080p

Lilliput 10.1″ FA1012 (HDMI)

Samsung LTL106Jl01 (LCD)

 N/A N/A N/A
ASRock BeeBox-S 6200U i5 Intel HD 520 Intel i915/DRM 4.14.14, Mesa3D 17.3.5 IntelHD DP, HDMI 3 1080p Lilliput 10.1″ FA1012 (HDMI) eGalax N/A N/A
Intel Gordon Ridge Apollo Lake HD Graphics 505 Intel i915/DRM 4.14.14, Mesa3D 17.3.5 IntelHD HDMI 2 1080p Lilliput 10.1" FA1012 (HDMI) N/A N/A N/A
Intel NUC6i5SYK i5 Iris Graphics 540 Intel i915/DRM 4.14.14, Mesa3D 17.3.5 IntelHD DP, HDMI 2

DP:

HDMI: 1080p

 Lilliput 10.1" FA1012 (HDMI) N/A N/A N/A
Note: 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:

General
  • The units of the SCREEN_PROPERTY_IDLE_TIMEOUT property are now correctly documented in the Screen Library Reference as nanoseconds. (Ref# J2202679)
  • You can now reset the value of the SCREEN_PROPERTY_CLIP_SIZE property back to its original default value. (Ref# J2232661)
  • Screen now notifies the owner of a group with a SCREEN_EVENT_CREATE event when a window of type SCREEN_APPLICATION_WINDOW joins. (Ref# J2242003)
Intel
  • When you specify a display that you didn't configure in your configuration file (graphics.conf) in the -display option of gles2-gears, the gles2-gears application no longer crashes. (Ref# J1628227)
Renesas
  • The correct value for SCREEN_PROPERTY_POWER_MODE is now returned when you call screen_get_display_property_iv() with this property. (Ref# J2235758)
  • On the R-CAR H3 Starter Kit, you should no longer observe issues during video playback (e.g., pinch/zoom corruption). (Ref# J2199966)

Known issues

These are the known issues with this update:

General
  • 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.

  • On some target systems (e.g., NXP SABRE Lite i.MX6Q), you may encounter a timing issue that's related to framebuffer access. Screen may crash because it's attempting to access a framebuffer that's not available. (Ref# J1653526)

    Workaround: In your framebuffer's class subsection of your configuration file, graphics.conf, set the buffer-count to a minimum of 3. 

    ...
begin class framebuffer
    display = 1
    ...
    buffer-count = 3
	...
end class
...

    For more information on how to set configuration parameters, see the "Configuring Screen" chapter in the Screen Developer's Guide.

  • 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.

Renesas
  • You may observe that the resultant blit is drawn incorrectly when you call screen_blit() with a value that's less than 255 for the SCREEN_BLIT_GLOBAL_ALPHA blit attribute. (Ref# J2235760)
  • On the R-CAR V3M Starter, you may observe incorrect rendering (e.g., cache artifacts) on the display. (Ref# J2368471)
  • On the R-CAR M3N, you may observe issues when using transparency with SCREEN_TRANSPARENCY_SOURCE_OVER. (Ref# J2546172)
  • On the R-CAR M3, a race-condition exists that may cause Screen to crash when Screen applications terminate. (Ref# J2546172)
  • In cases where you have one producer stream and multiple consumer streams, you may observe green flashes on the display. (Ref# J2546298)

    Workaround: In the globals subsection of your configuration file, graphics.conf, set the blit-config to use sw as the blitter or compositor. For example, to use sw as a blitter, configure: 

    ...
begin globals
    ...
	blit-config = sw
	...
end globals
...
NXP
  • Not all Khronos GLES 3.0 conformance tests pass. (Ref# J1517912)
  • You may observe flicker on the display when you're running graphics-intensive applications. These applications can create a heavy GPU load and bus congestion that can result in a display controller unit underrun problem. This issue is applicable to both revisions EVB (SCH_28899 REV D) and EVB2 (SCH_29288 REV B2) of the board. (Ref# J2379304)
Intel

Verification issues

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

  • New: Some files in QNX SDP 7.0 Utilities - Base (7.0.0.SGA201702151847) are incompatible with QNX SDP 7.0 Screen Base Graphics (7.0 BuildID 6272) from this update because of a packaging error. (Ref# J2335344)

    The version of each of the following files:
    • display-adjustment
    • display-adjustement.sym
    will result in verification issues if you have QNX SDP 7.0 Utilities - Base (7.0.0.SGA201702151847) already in your installation. You must ensure that the version of each of these files are from the QNX SDP 7.0 Screen Base Graphics (7.0 BuildID 6272) package.

    We recommend that you do the following:

    1. Identify the version of display-adjustment 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/bin/display-adjustment file where cpu_arch is the CPU architecture of your target. For example: 

        # use -i $QNX_TARGET/x86/bin/display-adjustment
      2. From the output of the use command, identify the version of the file in your installation. For example: 
        QNX_BUILDID=(GNU)805c6200cae593088eaad61fac89c90f
NAME=display-adjustment
DESCRIPTION=Composition Manager Debug Client
DATE=2018/04/17-18:07:42-EDT
STATE=stable
HOST=graphics-node-2
USER=builder
VERSION=graphics_release2.1x_be700
TAGID=Graphics_br-21x_be-700-272
PACKAGE=com.qnx.sdp.target.screen.base/7.0.6272.S201804171936
    2. Check that the version of display-adjustment for each of the specified CPU architectures you have installed is compatible with QNX SDP 7.0 Screen Base Graphics (7.0 BuildID 6272).

      If the version of the file is com.qnx.sdp.target.screen.base/7.0.6272.S201804171936, then you may disregard any errors that QNX Software Center still reports on the QNX SDP 7.0 Utilities - Base (7.0.0.SGA201702151847) package that are related to the following files:

      • display-adjustment
      • display-adjustment.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.

      Caution:

      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.base/7.0.6272.S201804171936 of display-adjustment 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 Base Graphics (7.0 BuildID 6272) package (e.g., by typing "screen base" in the Search field).

      If you're unable to locate QNX SDP 7.0 Screen Base Graphics 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 Base Graphics package.

      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 Utilities - Base (7.0.0.SGA201702151847) package that are related to the following files:

      • display-adjustment
      • display-adjustment.sym
      Note: 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.base/7.0.6272.S201804171936 of display-adjustment 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 display-adjustment on your development host, you may proceed to build your target images.

  • New: Some files in QNX SDP 7.0 Screen Board Support Intel are incompatible with QNX SDP 7.0 Screen Base Graphics from Graphics Implementation (7.0 BuildID 8143) update because of a packaging error. (Ref# J2896590)

    The version of each of the following files:
    • drm-probe-displays
    • drm-probe-displays.sym
    • libdrm.so.1
    • libdrm.so.1.sym
    will result in verification issues if you have QNX SDP 7.0 Screen Board Support Intel already in your installation. You must ensure that the version of each of these files are from your QNX SDP 7.0 Screen Board Support Intel package.

    We recommend that you do the following:

    1. Identify the version of each of drm-probe-displays and libdrm.so.1 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 following files:
        • $QNX_TARGET/x86_64/usr/bin/drm-probe-displays
        • $QNX_TARGET/x86_64/usr/lib/libdrm.so.1
        For example: 
        # use -i $QNX_TARGET/x86_64/usr/lib/libdrm.so.1
      2. From the output of the use command, identify the version of the files in your installation. For example: 
        QNX_BUILDID=(GNU)2ac46aeb23ed5ad8b7ad6c64330f5beb
NAME=libdrm.so
DESCRIPTION=Direct Rendering Manager (DRM) client library
DATE=2018/04/17-18:05:29-EDT
STATE=stable
HOST=graphics-node-2
USER=builder
VERSION=graphics_release2.1x_be700
TAGID=Graphics_br-21x_be-700-272
PACKAGE=com.qnx.sdp.target.screen.board.intel/7.0.6272.S201804171936
    2. Check that the version of the files you have installed is compatible with QNX SDP 7.0 Screen Board Support Intel.

      If the version of the each of these files is from your QNX SDP 7.0 Screen Board Support Intel, then you may disregard any errors QNX Software Center still reports on the QNX SDP 7.0 Screen Base Graphics package that are related to the following files:

      • drm-probe-displays
      • drm-probe-displays.sym
      • libdrm.so.1
      • libdrm.so.1.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.

      Caution:

      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.board.intel/7.0.6272.S201804171936 of drm-probe-displays and libdrm.so.1 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 Board Support Intel package (e.g., by typing "screen intel" in the Search field).

      If you're unable to locate the QNX SDP 7.0 Screen Board Support Intel package 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 Board Support Intel package.

      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 Screen Base Graphics package that are related to the following files:

      • drm-probe-displays
      • drm-probe-displays.sym
      • libdrm.so.1
      • libdrm.so.1.sym
      Note: For any other verification issues that QNX Software Center reports, you need to investigate.
    8. Confirm that you now have compatible versions of drm-probe-displays and libdrm.so.1 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 versions of drm-probe-display and libdrm.so.1 on your development host, you may proceed to build your target images.

  • New: Some files in QNX SDP 7.0 Screen Board Support – R-Car H3 (7.0.0.SGA201702151847) are incompatible with QNX SDP 7.0 Screen Board Support – R-car series, 3rd generation, common files (7.0 BuildID 6272) from this update because of a packaging error. (Ref# J2335344)

    The version of each of the following files:
    • screen-roguetq.so
    • screen-roguetq.so.sym
    will result in verification issues if you have QNX SDP 7.0 Screen Board Support – R-Car H3 (7.0.0.SGA201702151847) already in your installation. You must ensure that the version of each of these files are from this QNX SDP 7.0 Screen Board Support – R-car series, 3rd generation, common files (7.0 BuildID 6272) update.

    We recommend that you do the following:

    1. Identify the version of screen-roguetq.so 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/aarch64le/lib/dll/screen-roguetq.so file. For example: 

        # use -i $QNX_TARGET/aarch64le/lib/dll/screen-roguetq.so
      2. From the output of the use command, identify the version of the file in your installation. For example: 
        QNX_BUILDID=(GNU)f05004d5c040e53f20007db9ec351f60
NAME=screen-roguetq.so
DESCRIPTION=Composition Manager Roguetq module
DATE=2018/04/17-18:58:34-EDT
STATE=stable
HOST=graphics-node-2
USER=builder
VERSION=graphics_release2.1x_be700
TAGID=Graphics_br-21x_be-700-272
PACKAGE=com.qnx.sdp.target.screen.board.rcar3.common/7.0.6272.S201804171936
    2. Check that the version of screen-roguetq.so you have installed is compatible with the this QNX SDP 7.0 Screen Board Support – R-car series, 3rd generation, common files (7.0 BuildID 6272) update.

      If the version of the file is com.qnx.sdp.target.screen.base/7.0.6272.S201804171936, then you may disregard any errors that QNX Software Center still reports on the QNX SDP 7.0 Screen Board Support – R-Car H3 (7.0.0.SGA201702151847) package that are related to the following files:

      • screen-roguetq.so
      • screen-roguetq.so.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.

      Caution:

      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.base/7.0.6272.S201804171936 of screen-roguetq.so 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 Board Support – R-car series, 3rd generation, common files (7.0 BuildID 6272) package (e.g., by typing "R-car common" in the Search field).

      If you're unable to locate QNX SDP 7.0 Screen Board Support – R-car series, 3rd generation, common files 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 Board Support – R-car series, 3rd generation, common files package.

      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 Screen Board Support – R-Car H3 (7.0.0.SGA201702151847) package that are related to the following files:

      • screen-roguetq.so
      • screen-roguetq.so.sym
      Note: 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.base/7.0.6272.S201804171936 of screen-roguetq.so 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 screen-roguetq.so on your development host, you may proceed to build your target images.

  • New: Some files in QNX SDP 7.0 Font Engine (7.0.0.SGA201702151847) are incompatible with QNX SDP 7.0 Screen Base Graphics (7.0 BuildID 6272) from this update because of a packaging error. (Ref# J2896590)

    The version of each of the following files:
    • font-freetype
    • bubble.png
    will result in verification issues if you have QNX SDP 7.0 Font Engine (7.0.0.SGA201702151847) already in your installation. You must ensure that the version of each of these files are from your QNX SDP 7.0 Screen Base Graphics (7.0 BuildID 6272) package.

    We recommend that you do the following:

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

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

        # use -i $QNX_TARGET/aarch64le/usr/bin/font-freetype
      1. From the output of the use command, identify the version of the files in your installation. For example: 
        QNX_BUILDID=(GNU)a83000137fc07dd0dc9eebc915a27c4d
NAME=font-freetype
DESCRIPTION=Freetype Font Engine Test
DATE=2018/04/17-19:06:49-EDT
STATE=stable
HOST=graphics-node-2
USER=builder
VERSION=graphics_release2.1x_be700
TAGID=Graphics_br-21x_be-700-272
PACKAGE=com.qnx.sdp.target.screen.base/7.0.6272.S201804171936
    2. Check that the version of the files you have installed is compatible with QNX SDP 7.0 Screen Base Graphics (7.0 BuildID 6272).

      If the version of the each of these files is from your QNX SDP 7.0 Screen Base Graphics (7.0 BuildID 6272), then you may disregard any errors QNX Software Center still reports on the QNX SDP 7.0 Font Engine (7.0.0.SGA201702151847) package that are related to the following files:

      • font-freetype
      • bubble.png

      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.

      Caution:

      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.base/7.0.6272.S201804171936 of font-freetype 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 Base Graphics (7.0 BuildID 6272) package (e.g., by typing "screen base" in the Search field).

      If you're unable to locate the QNX SDP 7.0 Screen Base Graphics package 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 Base Graphics package.

      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 Font Engine (7.0.0.SGA201702151847) package that are related to the following files:

      • font-freetype
      • bubble.png
      Note: 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.base/7.0.6272.S201804171936 of font-freetype 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 font-freetype on your development host, you may proceed to build your target images.

  • New: Some files in Device Input (7.0.0.SGA201702151847) are incompatible with QNX SDP 7.0 Screen Device Input Utilities (7.0 BuildID 6272) 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 the QNX SDP 7.0 Screen Device Input Utilities (7.0 BuildID 6272) package.

    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)7106fa62f8c57347c1b4b6bf3226358c
NAME=calib-touch
DESCRIPTION=mtouch calibration utility for Screen
DATE=2018/04/17-18:08:16-EDT
STATE=stable
HOST=graphics-node-2
USER=builder
VERSION=graphics_release2.1x_be700
TAGID=Graphics_br-21x_be-700-272
PACKAGE=com.qnx.sdp.target.screen.device_input_screen/7.0.6272.S201804171936
    2. Check that the version of calib-touch for each of the specified CPU architectures you have installed is compatible with QNX SDP 7.0 Screen Device Input Utilities (7.0 BuildID 6272).

      If the version of the file is com.qnx.sdp.target.screen.device_input_screen/7.0.6272.S201804171936, then you may disregard any errors that QNX Software Center still reports on the QNX SDP 7.0 Device Input 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.

      Caution:

      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.6272.S201804171936 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 6272) 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
      Note: 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.6272.S201804171936 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.

  • New: The swblit.h file in QNX SDP 7.0 OS Services - Core (7.0.0.SGA201702151847) is incompatible with QNX SDP 7.0 Screen Base Graphics (7.0 BuildID 6272) from this update. (Ref# J2899620)

    The swblit.h file will result in verification issues if you have QNX SDP 7.0 OS Services - Core (7.0.0.SGA201702151847) already in your installation. You must ensure that the version of swblit.h file is from the QNX SDP 7.0 Screen Base Graphics package from this Graphics Implementation (7.0 BuildID 6272) update.

    We recommend that you do the following:

    1. Identify the version of swblit.h that you have installed on your development host by verifying the revision number found at the bottom of the header file.
      1. Open the $QNX_TARGET/usr/include/swblit.h file using your preferred text editor.
      2. Look for the the source revision number for this file. For example: 
        __SRCVERSION("$URL: http://svn.ott.qnx.com/product/graphics/branches/release-2.1.x/lib/swblit/public/swblit/swblit.h $ $Rev: 767926 $")
    2. Check that the version of swblit.h is compatible with QNX SDP 7.0 Screen Base Graphics (7.0 BuildID 6272).

      If the version of the file is http://svn.ott.qnx.com/product/graphics/branches/release-2.1.x/lib/swblit/public/swblit/swblit.h $ $Rev: 767926, then you may disregard any errors that QNX Software Center still reports on the QNX SDP 7.0 OS Services - Core (7.0.0.SGA201702151847) package that are related to swblit.h.

      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.

      Caution:

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

      If you don't have version http://svn.ott.qnx.com/product/graphics/branches/release-2.1.x/lib/swblit/public/swblit/swblit.h $ $Rev: 767926 of swblit.h 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 Base Graphics (7.0 BuildID 6272) package (e.g., by typing "screen base" in the Search field).

      If you're unable to locate QNX SDP 7.0 Screen Base Graphics 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 Base Graphics.

      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 OS Services - Core (7.0.0.SGA201702151847) package that are related to swblit.h.

      Note: For any other verification issues that QNX Software Center reports, you need to investigate.
    8. Confirm that you now have version http://svn.ott.qnx.com/product/graphics/branches/release-2.1.x/lib/swblit/public/swblit/swblit.h $ $Rev: 767926 of swblit.h installed on your development host.

      Do so by executing the verifying the source revision number as described eariler in these procedures.

      Once you've established that you have the compatible version of swblit.h 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.