Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-107643

qt.opcua.plugins.open62541: "Endpoint description is invalid because endpoint URL or security policy URL is empty"

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • P2: Important
    • None
    • 5.15.2
    • OpcUA
    • None
    • Integrity

    Description

      I'm trying to run the FA demo on INTEGRITY running on i.MX8qm.

      The application has been built statically because INTEGRITY only allows static libraries.

      *Before building, I applied opcua_fixes.patchto qtopcua directory.

      I'm having this error now when I start up the demo on the board.

      Which is caused in here:

      It has been confirmed that "endpoint.securityPolicy().isEmpty()" is true and yielding this error.

       

       

      [The entire output]

      Connected to /dev/ttyUSB1 (speed 115200)Connected to /dev/ttyUSB1 (speed 115200)Kernel......................................INTEGRITY v19.0.15-r315448BSP..........................Device Tree ARM64: NXP MCIMX8QM-CPU BoardDebug Agent.............................................INDRT2 v2.0.54IP Address.................................................127.0.0.100RAM............................................................6144 MBActive Cores.........................................................6Initial Objects....................................................485Initializing boot modules:    Debug (INDRT)..............................................Success    Start Run-Mode Partner Task................................Success    Resource Manager...........................................Success    System Resources...........................................Success    Driver Debug Stack.........................................Success    GIPC Target................................................Success    i.MX 8 MU SCFW Driver......................................Success    i.MX 8 ESAI Driver.........................................Success    i.MX 8 SAI Driver..........................................Success    i.MX 8 WDOG Driver.........................................Success    i.MX 8 RTC Driver..........................................Success    OSA Helper.................................................Success    Device Tree Connection Exports.............................Success    Device Tree Boot Modules...................................Success    Spectre Variant 2 Workaround...............................Skipped    VASLog EventLogExporter....................................Success    TCP/IP.....................................................Success    File System Client.........................................Success    File System................................................Success    Configure I/O Termination Tasks............................SuccessVFS: Please make sure all filesystems are unmounted    Late KernelRange Clear.....................................SuccessVFS: by doing one of the following just before rebooting orBoot Initialization..........................................CompletedVFS: powering down the system: VFS: a) Run the 'Unmounter' task (if configured), orVFS: b) Unmount all filesystems through application calls to theVFS:    unmount file system call, orVFS: c) Use the unmount or reboot commands in the shell.GALcore+prof 6.2.4.190076 (Aug  6 2021)<ram:128k>autoramroot:a: 256 sectors in 1 cylinders of 1 tracks, 256 sectors 0.1MB in 1 cyl groups (16 c/g, 2.00MB/g, 64 i/g)newfs has completed successfullyVFS: WARNING: File system coming up without a root file systemVFS: File system initialization complete.QEglFSVivIntegration will set environment variable FB_MULTI_BUFFER=2 to enable double buffering and vsync. If this is not desired, you can override this via: export QT_EGLFS_IMX6_NO_FB_MULTI_BUFFER=1[GPU] Using driver: 'imx8_lvds0_dpu0'IT6263 valid display data received (I2C bus: 10). Display reconfigured (1024 x 600)Unable to query physical screen size, defaulting to 100 dpi.To override, set QT_QPA_EGLFS_PHYSICAL_WIDTH and QT_QPA_EGLFS_PHYSICAL_HEIGHT (in millimeters).industrialhmi.qmlclient.screeninfo: Screen information: 1024x600, 100dpi, diagonal 11.8683, device pixel ration 1industrialhmi.qmlclient.languagehandler: Available languages ("de_DE", "en_US", "zh_CN")industrialhmi.qmlclient.languagehandler: Switched language to "de_DE"industrialhmi.qmlclient.qmlclientapplication: Server address defaults to 127.0.0.1industrialhmi.qmlclient.qmlclientapplication: Client port defaults to 4040industrialhmi.qmlclient.qmlclientapplication: Using default ui implementation:  "qtc"QFontDatabase: Cannot find font directory /usr/local/Qt-5.15.2/lib/fonts.Note that Qt no longer ships fonts. Deploy some (from https://dejavu-fonts.github.io/ for example) or switch to fontconfig.industrialhmi.qmlclient.languagehandler: Switched language to "en_US"[     1] Render mode = 0U-Boot 2020.04 (Jan 15 2021 - 15:06:01 +0100)
      CPU:   NXP i.MX8QM RevB A53 at 1200 MHz at 33C
      Model: NXP i.MX8QM MEKBoard: iMX8QM MEKBoot:  SD1DRAM:  6 GiBTCPC:  Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C0 0x51]MMC:   FSL_SDHC: 0, FSL_SDHC: 1Loading Environment from MMC... Run CMD11 1.8V switchOKIn:    serialOut:   serialErr:   serial
       BuildInfo:   - SCFW 0d54291f, SECO-FW d63fdb21, IMX-MKIMAGE 8947fea3, ATF f1d7187  - U-Boot 2020.04 
      Run CMD11 1.8V switchswitch to partitions #0, OKmmc1 is current deviceflash target is MMC:1Run CMD11 1.8V switchNet:   eth0: ethernet@5b040000 [PRIME], eth1: ethernet@5b050000Fastboot: NormalNormal BootHit any key to stop autoboot:  0 64 bytes read in 6 ms (9.8 KiB/s)143873 bytes read in 14 ms (9.8 MiB/s)## Flattened Device Tree blob at bff00000   Booting using the fdt blob at 0xbff00000   Using Device Tree in place at 00000000bff00000, end 00000000bff26fff
      Starting kernel ...
      Kernel......................................INTEGRITY v19.0.15-r315448BSP..........................Device Tree ARM64: NXP MCIMX8QM-CPU BoardDebug Agent.............................................INDRT2 v2.0.54IP Address.................................................127.0.0.100RAM............................................................6144 MBActive Cores.........................................................6Initial Objects....................................................485Initializing boot modules:    Debug (INDRT)..............................................Success    Start Run-Mode Partner Task................................Success    Resource Manager...........................................Success    System Resources...........................................Success    Driver Debug Stack.........................................Success    GIPC Target................................................Success    i.MX 8 MU SCFW Driver......................................Success    i.MX 8 ESAI Driver.........................................Success    i.MX 8 SAI Driver..........................................Success    i.MX 8 WDOG Driver.........................................Success    i.MX 8 RTC Driver..........................................Success    OSA Helper.................................................Success    Device Tree Connection Exports.............................Success    Device Tree Boot Modules...................................Success    Spectre Variant 2 Workaround...............................Skipped    VASLog EventLogExporter....................................Success    TCP/IP.....................................................Success    File System Client.........................................Success    File System................................................Success    Configure I/O Termination Tasks............................SuccessVFS: Please make sure all filesystems are unmounted    Late KernelRange Clear.....................................SuccessVFS: by doing one of the following just before rebooting orBoot Initialization..........................................CompletedVFS: powering down the system: VFS: a) Run the 'Unmounter' task (if configured), orVFS: b) Unmount all filesystems through application calls to theVFS:    unmount file system call, orVFS: c) Use the unmount or reboot commands in the shell.GALcore+prof 6.2.4.190076 (Aug  6 2021)<ram:128k>autoramroot:a: 256 sectors in 1 cylinders of 1 tracks, 256 sectors 0.1MB in 1 cyl groups (16 c/g, 2.00MB/g, 64 i/g)newfs has completed successfullyVFS: WARNING: File system coming up without a root file systemVFS: File system initialization complete.QEglFSVivIntegration will set environment variable FB_MULTI_BUFFER=2 to enable double buffering and vsync. If this is not desired, you can override this via: export QT_EGLFS_IMX6_NO_FB_MULTI_BUFFER=1[GPU] Using driver: 'imx8_lvds0_dpu0'IT6263 valid display data received (I2C bus: 10). Display reconfigured (1024 x 600)Unable to query physical screen size, defaulting to 100 dpi.To override, set QT_QPA_EGLFS_PHYSICAL_WIDTH and QT_QPA_EGLFS_PHYSICAL_HEIGHT (in millimeters).industrialhmi.qmlclient.screeninfo: Screen information: 1024x600, 100dpi, diagonal 11.8683, device pixel ration 1industrialhmi.qmlclient.languagehandler: Available languages ("de_DE", "en_US", "zh_CN")industrialhmi.qmlclient.languagehandler: Switched language to "de_DE"industrialhmi.qmlclient.qmlclientapplication: Server address defaults to 127.0.0.1industrialhmi.qmlclient.qmlclientapplication: Client port defaults to 4040industrialhmi.qmlclient.qmlclientapplication: Using default ui implementation:  "qtc"qt.opcua.plugins.open62541: "Endpoint description is invalid because endpoint URL or security policy URL is empty"QFontDatabase: Cannot find font directory /usr/local/Qt-5.15.2/lib/fonts.Note that Qt no longer ships fonts. Deploy some (from https://dejavu-fonts.github.io/ for example) or switch to fontconfig.industrialhmi.qmlclient.languagehandler: Switched language to "en_US"[     1] Render mode = 0
      

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            fmeerkoetter Frank Meerkötter
            mikio_hirai Mikio Hirai
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes