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

QNX Technical Articles

QNX® Software Development Platform 7.0— Graphics Implementation (7.0 BuildID 6299): Release Notes

Date of this edition: June 7, 2021

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

This update provides:

  • Board Support for the Qualcomm Snapdragon target board
Note: This update of Screen is intended to support only the Qualcomm Snapdragon target board.

Note that this Graphics Implementation update has been validated only with QNX SDP 7.0 Screen (7.0 BuildID 758).

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?

This update includes the following packages:

  • QNX SDP 7.0 Screen Base Graphics
  • QNX SDP 7.0 Screen Device Input Utilities
  • QNX SDP 7.0 Screen Video Capture

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

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

Updates

  • Support for the Composite 2D blitter module.

Screen board packages must 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 is validated with only the following the QNX SDP 7.0 Screen Board Support - Qualcomm C2D Blitter package:

Caution:

If you install this update, 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.

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
Qualcomm Snapdragon MSM8996AU A530 Adreno 530 HDMI 4

HDMI 1: 720p

HDMI 2: 720p

HDMI 4: 1080p

 Lilliput 10.1" FA1012 N/A N/A N/A
Note: Screen board support packages previously released with QNX SDP 7.0 haven't been validated with this update of Screen.

Installing this update

To use this installation:

  • You must use QNX Software Center, version 1.3.1 or later. Using earlier versions of QNX Software Center may cause inconsistencies in your installation.
Caution:

You must have already installed QNX SDP 7.0.

You must have already installed QNX SDP 7.0 Screen (7.0 BuildID 758). See issue J2650162 under Known issues.

To run this installation in the QNX Software Center, performing the following steps:
  1. Navigate to QNX SDP 7.0 Graphics Implementation (7.0 BuildID 6299).
  2. Select QNX SDP 7.0 Graphics Implementation (7.0 BuildID 6299) and right-click to select Install.
  3. Ensure that the package is selected and then click Next.
  4. Review the list of packages that QNX Software Center will install and then click Next.
  5. Click Finish.

    After a few minutes, your installation should complete.

  6. Click OK to complete the installation.

Fixed issues

This update has these fixes:

General
  • There is now documentation for drm-intel and drm-probe-displays in the Screen Developer's Guide. (Ref# J2557453)

Known issues

These are the known issues with this update:

General
  • The installation of the Graphics Implementation update doesn't install its dependencies. (Ref# J2650162)

    This update is dependent on QNX SDP 7.0 Screen (7.0 BuildID 758), but when you install the Graphics Implementation update from QNX Software Center, the required dependency isn't automatically installed.

    Workaround: Install the QNX SDP 7.0 Screen (7.0 BuildID 758) update before you install this Graphics Implementation (7.0 BuildID 6299) update.

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

  • New:If you're specifying multiple framebuffer classes in your graphics configuration file, and you use the "usage" parameter to specify different composition modules (e.g., pvr2d) for different classes, you'll see an error logged in slog2info. For example, take the following configuration: 

    …
begin class framebuffer1
  …
  usage = pvr2d
  …
end class

begin class framebuffer3
  …
  usage = gles2blt
  …
end class
…
    In this example, Screen will fail to start and you'll see the following message from the slog2info command: All framebuffers must use the same composition module 'pvr2d' != 'gles2blt'.

    (Ref# J2704977)

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# J2521636)
  • 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
  • When you're running graphics-intensive applications on the Gordon Ridge platform, you may experience GPU lockups. (Ref# J2529205)
  • You can't launch Screen applications as a non-root user. (Ref# J1682025)

    Workaround: Start procnto with the -mL option. For example: 

    procnto-smp-instr -mL

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 Screen Board Support S32V (7.0.6272.S201804171936) are incompatible with QNX SDP 7.0 Screen Base Graphics (7.0 BuildID 6299) from this update because of a packaging error. (Ref# J2896590, J2550850)

    The version of each of the following files:
    • screen-gles2blt.so
    • screen-gles2blt.so.sym
    will result in verification issues if you have QNX SDP 7.0 Screen Board Support S32V (7.0.6272.S201804171936) 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 6299) package from this update.

    We recommend that you do the following:

    1. Identify the version of screen-gles2blt.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-gles2blt.so file For example: 

        # use -i $QNX_TARGET/aarch64le/lib/dll/screen-gles2blt.so
      2. From the output of the use command, identify the version of the file in your installation. For example: 
        $ use -i $QNX_TARGET/aarch64le/lib/dll/screen-gles2blt.so
QNX_BUILDID=(GNU)7f9ee077a3769ef1de2150539d18b752
NAME=screen-gles2blt.so
DESCRIPTION=Screen gles2 blitter module
DATE=2018/06/08-12:55:37-EDT
STATE=stable
HOST=graphics-node-2
USER=builder
VERSION=graphics_release2.1x_be700
TAGID=Graphics_br-21x_be-700-299
PACKAGE=com.qnx.sdp.target.screen.base/7.0.6299.S201806081327
    2. Check that the version of screen-gles2blt.so you have installed is compatible with QNX SDP 7.0 Screen Base Graphics (7.0 BuildID 6299).

      If the version of the file is com.qnx.sdp.target.screen.base/7.0.6299.S201806081327, then you may disregard any errors that QNX Software Center still reports on the QNX SDP 7.0 Screen Board Support S32V package that are related to the following files:

      • screen-gles2blt.so
      • screen-gles2blt.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.6299.S201806081327 of screen-gles2blt.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 Base Graphics package (7.0 BuildID 6299) (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 Screen Board Support S32V (7.0.6272.S201804171936) package that are related to the following files:

      • screen-gles2blt.so
      • screen-gles2blt.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.6299.S201806081327 of screen-gles2blt.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-gles2blt.so on your development host, you may proceed to build your target images.

  • 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 6299) 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 6299) package from this update.

    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)edacc941f363ecb60b1e52ee457aac80
NAME=display-adjustment
DESCRIPTION=Composition Manager Debug Client
DATE=2018/06/08-11:45:55-EDT
STATE=stable
HOST=graphics-node-2
USER=builder
VERSION=graphics_release2.1x_be700
TAGID=Graphics_br-21x_be-700-299
PACKAGE=com.qnx.sdp.target.screen.base/7.0.6299.S201806081327
    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 6299).

      If the version of the file is com.qnx.sdp.target.screen.base/7.0.6299.S201806081327, then you may disregard any errors that QNX Software Center still reports on the QNX SDP 7.0 Utilities - Base 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.6299.S201806081327 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 package (7.0 BuildID 6299) (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 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.6299.S201806081327 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 Font Engine (7.0.0.SGA201702151847) are incompatible with QNX SDP 7.0 Screen Base Graphics (7.0 BuildID 6299) 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 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 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)ab3fd23cbeabe3c2d8d184b364b08e0c
NAME=font-freetype
DESCRIPTION=Freetype Font Engine Test
DATE=2018/06/08-12:55:52-EDT
STATE=stable
HOST=graphics-node-2
USER=builder
VERSION=graphics_release2.1x_be700
TAGID=Graphics_br-21x_be-700-299
PACKAGE=com.qnx.sdp.target.screen.base/7.0.6299.S201806081327
    2. Check that the version of the files you have installed is compatible with QNX SDP 7.0 Screen Base Graphics (7.0 BuildID 6299).

      If the version of the each of these files is from QNX SDP 7.0 Screen Base Graphics (7.0 BuildID 6299), 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.6299.S201806081327 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 6299) 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.6299.S201806081327 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 6299) 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 6299) 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)2d041c3bbfc9324f0c040ac91611f047
NAME=calib-touch
DESCRIPTION=mtouch calibration utility for Screen
DATE=2018/06/08-11:46:17-EDT
STATE=stable
HOST=graphics-node-2
USER=builder
VERSION=graphics_release2.1x_be700
TAGID=Graphics_br-21x_be-700-299
PACKAGE=com.qnx.sdp.target.screen.device_input_screen/7.0.6299.S201806081327
    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 6299).

      If the version of the file is com.qnx.sdp.target.screen.device_input_screen/7.0.6299.S201806081327, 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.6299.S201806081327 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 6299) 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.6299.S201806081327 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 6299) from this update because of a packaging error. (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 (7.0 BuildID 6299) package.

    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: 859301 $")
    2. Check that the version of swblit.h is compatible with QNX SDP 7.0 Screen Base Graphics (7.0 BuildID 6299).

      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: 859301, 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: 859301 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 6299) 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: 859301 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.