Arch Linux User Repository

@s.f

I have had a bit of a dig into this (never used harmony 3 before), and it looks like the graphics composer ships its own Qt library versions.

plugins/legato/libQt5Network.so.5
plugins/legato/libQt5Xml.so.5

Are both from v5.14.1 where as the rest are from 5.15.2.

As a quick hack I replaced these two files with the versions available in the 5.15.2 from the archlinux package archive (https://archive.archlinux.org/packages/q/qt5-base/qt5-base-5.15.2-5-x86_64.pkg.tar.zst) and the composer then launches just fine (need to extract the two libQt5Network.so.5.15.2 and libQt5Xml.so.5.15.2 files from /usr/lib and then rename and replace the original files).

So basically the legato package is broken, I would guess that it doesn't launch even if you install MPLABX manually so this should be reported to microchip.

Hope that helps

When starting the graphics composer from Harmony3 I get this message in the terminal where I started mplab_ide:

Cannot mix incompatible Qt library (5.14.1) with this library (5.15.2)

Starting the graphics composer stand-alone works. The path is eg.

~/Harmony3/gfx/middleware/legato/composer/linux/composer

They ship their dependencies:

ldd ~/Harmony3/gfx/middleware/legato/composer/linux/composer
linux-vdso.so.1 => linux-vdso.so.1 (0x00007ffedc7db000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x00007fe68e01d000)
libQt5Widgets.so.5 => /home/simeon/Harmony3/gfx/middleware/legato/composer/linux/libQt5Widgets.so.5 (0x00007fe68d600000)
libQt5Gui.so.5 => /home/simeon/Harmony3/gfx/middleware/legato/composer/linux/libQt5Gui.so.5 (0x00007fe68cc00000)
libQt5Core.so.5 => /home/simeon/Harmony3/gfx/middleware/legato/composer/linux/libQt5Core.so.5 (0x00007fe68c400000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007fe68c1c9000)
libm.so.6 => /usr/lib/libm.so.6 (0x00007fe68df35000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007fe68bfe5000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007fe68df30000)
libGL.so.1 => /usr/lib/libGL.so.1 (0x00007fe68deaa000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007fe68de8a000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007fe68de70000)
libicui18n.so.56 => /home/simeon/Harmony3/gfx/middleware/legato/composer/linux/libicui18n.so.56 (0x00007fe68ba00000)
libicuuc.so.56 => /home/simeon/Harmony3/gfx/middleware/legato/composer/linux/libicuuc.so.56 (0x00007fe68b600000)
libicudata.so.56 => /home/simeon/Harmony3/gfx/middleware/legato/composer/linux/libicudata.so.56 (0x00007fe689c00000)
libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x00007fe68de69000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007fe68bea8000)
/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007fe68e1dc000)
libGLdispatch.so.0 => /usr/lib/libGLdispatch.so.0 (0x00007fe68d549000)
libGLX.so.0 => /usr/lib/libGLX.so.0 (0x00007fe68b9ce000)
libpcre.so.1 => /usr/lib/libpcre.so.1 (0x00007fe689b89000)
libX11.so.6 => /usr/lib/libX11.so.6 (0x00007fe689a46000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007fe689a1b000)
libXau.so.6 => /usr/lib/libXau.so.6 (0x00007fe68d544000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007fe68d53c000)

Using export LD_LIBRARY_PATH does not work, it looks like the spawn a new process from within mplab_ide with a clean environment.

Any ideas?

@K4LCIFER

Your issue is with the "java8-openjfx" package, report your issue there.

Wont' build due to errors:

FAILURE: Build failed with an exception.

* What went wrong:
Could not create service of type ScriptPluginFactory using BuildScopeServices.createScriptPluginFactory().
> Could not create service of type PluginResolutionStrategyInternal using BuildScopeServices.createPluginResolutionStrategy().

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 0s
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: java8-openjfx

Hi @danwood76,

After complete deinstall MPLABX and build this package new it works fine now.

It usually pops up a notification in the bottom right hand corner or the IDE when it discovers a programmer.

One thing you may want to check is whether you have any stale microchip libraries or links in /usr/local/lib there shouldn't be any microchip libs (libmchp*) in there but you may have some if you ever installed it directly from the installer.

Hi @danwood76,

any idea how I caan check if MPLABX is detecting the PICKIT? Can I take any logs somewhere?

Are the drivers in the mplabcomm folder? I moved the folder to an other HardDrive.

Best regards, Kevin

Hi @NobodyDBG

I am fairly certain I used a PK3 on my machine with MplabX 6 the other day (try replugging/rebooting). However I mainly use the PK4 or Snap, occasionally when first starting up I have had to replug my programmers for them to be recognised but I thought that was my dodgy USB leads. Unfortunately my PicKit 3s are at the office so I cannot double check until next week.

Kind regards, Danny

Hello,

After upgrade my PICKIT3 would'nt be detected. Is PICKIT3 compatible with MPLABX 6.0? I read that PICKIT3 is not longer supported.

It works now :-)