Attachments (0)
Nordic Case Info
  • Case ID: 344412
Options

Building llext-edk with NCS 2.9 and 3.0 failing due to unknown target "llext-edk"

Colmear

I am currently trying to get LLEXTs to work on the nRF5340 Audio DK. I was able to compile an llext and load it successfully, using the cmake features, However, I would like to build the extension separately and therefore need the llext-edk to work. I tried building my app as well as the edk example with both NCS 2.9 and the NCS 3.0 preview. Both are building the app just fine, but when I call west build -t llext-edk, I get the following error:

 

I also tried to build for the qemu_cortex_r5 board just like in the example, but that didn't change anything. In my app I enabled LLEXT like this in the prj.conf:

Is the llext-edk even supported at this moment as the documentation and the example suggest? Any help is greatly appreciated. Thanks in advance

  • 0

    Hi,

    This feature is very much Zephyr and very little Nordic so I don't know how much support there is for using it with Nordic devices other than it existing in the downstream fork of Zephyr that we have in the SDK.

    Could you try to see if you're able to compile and run the steps using standalone Zephyr upstream?

    You might also want to investigate the Zephyr discord forums and see if there's any other users who's been testing LLEXT with Nordic and Non-nordic devices. Searches on the Devzone forums results in very few hits at least. 

    Kind regards,
    Andreas

  • 0 in reply to AHaug

    I did a fresh install of West in a Python venv and tried building the example with plain Zephyr. I tried it with Zephyr 4.1 and Zephyr 4.0. Building the Zephyr llext/edk/app example worked fine for both versions, even with the llext-edk target, but building the NCS example results in this error for the application build:

    I seem to only have problems with llext-edk on NCS, that's why I am asking here. Is the llext-edk supposed to work in NCS? The documentation indicates so. I also can't imagine what NCS might be doing differently than the upstream in order to not find the target at all.

    In terms of building with the standalone Zephyr upstream, is this supposed to work on NCS projects? I suppose there are quite a few changes that a NCS project expects from Zephyr in order to build correctly, especially when building an LE audio firmware.

  • 0 in reply to Colmear

    Hi,

    Colmear said:
    Building the Zephyr llext/edk/app example worked fine for both versions, even with the llext-edk target, but building the NCS example results in this error for the application build:

    That's good. Yeah, the reason for why I'm asking for testing upstream is due to NCS using a downstream fork and it has quite a few custom features that clean vanilla Zephyr does not have. 

    Colmear said:
    I seem to only have problems with llext-edk on NCS, that's why I am asking here. Is the llext-edk supposed to work in NCS?

    Yup, it seems to be a NCS issue since it works out of the box for Zephyr 4.1 and 4.0. I will check if this is something that's a known issue, report the bug and get back to you.

    Colmear said:
    In terms of building with the standalone Zephyr upstream, is this supposed to work on NCS projects? I suppose there are quite a few changes that a NCS project expects from Zephyr in order to build correctly, especially when building an LE audio firmware.

    Unfortunately that's not a guarantee. Some simple samples work out of the box, but others depend on the submodules that NCS consists of that Zephyr may not have present. The nrf5340 also has some unique features that are handled in the NCS fork that is not present in clean Zephyr.

    Kind regards,
    Andreas

Terms of service