Replies: 3 comments 1 reply
-
|
Path to the shared library is also in the run-time linker cache: |
Beta Was this translation helpful? Give feedback.
-
|
Found out that native 'dtc' works but 'dtc' provided in Zephyr SDK not: |
Beta Was this translation helpful? Give feedback.
-
|
I've solved the issue in a hacky way! Checking the loader of the SDK's 'dtc' showed that it uses its own runtime loader: Since 'libusb-0.1.so.4' does not exist in the SDK's library folder (~/zephyr-sdk-0.17.4/sysroots/x86_64-pokysdk-linux/usr/lib/), I've created there a symbolic link to the system 'libusb-0.1.so.4'. Finally building example application succeeds for a given board: I assume the issue is not really related to the Zephyr SDK, indeed more or less to 'libusb', which is loaded by Xilinx USB driver: BTW, I'm using the Linux Mint 21.3. Thanks @yvesll for your cross check. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Building the 'samples/basic/blinky' app fails by loading the 'libusb-0.1.so.4' shared library.
As target 'nrf5340dk/nrf5340/cpuapp' board is chosen.
Here is a part of the output message:
Inspection of required shared libraries for 'dtc' shows that 'libusb-0.1.so.4' is installed and exists:
Even an installation attempt shows that the library is actual.
What is going here wrong? Grateful for your support.
Beta Was this translation helpful? Give feedback.
All reactions