Undefined reference to functions from channel manager and channel monitor.

[Allan-led]

Hi, guys, I am experiencing somethings strange. I am trying to utilize functions from channel_manager.h and channel_monitor.h. I am certain that I have the necessary headers to do so. Does anyone have any idea why these are being marked as undefined references? I have created a simple program for reference:

`
#include <zephyr/kernel.h>
#include <zephyr/logging/log.h>
#include <zephyr/drivers/uart.h>
#include <zephyr/usb/usb_device.h>
#include <zephyr/drivers/gpio.h>
#include <openthread/thread.h>
#include <openthread/instance.h>
#include <openthread/ip6.h>

#include "common_custom.h"
#include "pwm_control.h"
#include "channel_control.h"

#include <openthread/channel_manager.h>
#include <openthread/channel_monitor.h>

#include "udp_handler.h"

LOG_MODULE_REGISTER(cli_sample, CONFIG_OT_COMMAND_LINE_INTERFACE_LOG_LEVEL); // Logging module required for logs in Zephyr

otInstance *ot_instance;
// ....................................................................
int main(void)
{
// Initialize the OpenThread stack
ot_instance = otInstanceInitSingle();

// Configure Thread network parameters (implemented above but not shown here. Has been tested and works find()
setThreadNetworkParams(ot_instance);

// Configure channel mask, determine valid channels (Implemented in channel_control.c)
set_channel_mask(ot_instance);


// Bring up the IPv6 interface (equivalent to `ifconfig up`)
otError error = otIp6SetEnabled(ot_instance, true);
if (error != OT_ERROR_NONE) {
    printk("Failed to enable IPv6: %d\n", error);
    return 0;
}

// Start the OpenThread protocol (equivalent to `ot thread start`)
error = otThreadSetEnabled(ot_instance, true);
if (error != OT_ERROR_NONE) {
    printk("Failed to enable Thread protocol: %d\n", error);
    return 0;
} 


// Enable channel monitoring
error = otChannelMonitorSetEnabled(ot_instance, true);
if (error != OT_ERROR_NONE) {
    printk("Failed to enable channel monitoring: %d\n", error);
    return 0;
}
// Application's main loop or other tasks
while (1) {
    monitor_channel(ot_instance); // implemented elsewhere.
    k_sleep(K_MSEC(5000));  

}

return 0;

}
`

And my error message includes: Documents/myapps/ot-light-base/src/main.c:181: undefined reference to `otChannelMonitorSetEnabled'.

The strange thing is when I hover over the function call, I can see the description and signature of the functions, and I can even right click and select go to definition, and it would lead me to channel_monitor.h.

My prj.conf file looks as follows:
`CONFIG_SHELL=y
CONFIG_OPENTHREAD_SHELL=y
CONFIG_SHELL_ARGC_MAX=26
CONFIG_SHELL_CMD_BUFF_SIZE=416

Enable OpenThread features set

CONFIG_OPENTHREAD_NORDIC_LIBRARY_MASTER=y

CONFIG_NET_L2_OPENTHREAD=y

Generic networking options

CONFIG_NETWORKING=y

default to n if CONFIG_NET_L2_OPENTHREAD=y anyways

CONFIG_MBEDTLS_SHA1_C=n
CONFIG_FPU=y

CONFIG_GPIO_SHELL=y
CONFIG_OPENTHREAD_FTD=y

#THREAD CONFIGS
CONFIG_OPENTHREAD_COMMISSIONER=n
CONFIG_OPENTHREAD_JOINER=n
CONFIG_OPENTHREAD_SRP_CLIENT=y

#RTT CONFIG (Comment out if uart is on)
CONFIG_LOG=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_SHELL_BACKEND_RTT=y

#UART CONFIGS FOR RECEIVING COMMANDS (Comment out if rtt is on)

CONFIG_LOG=y

CONFIG_SERIAL=y

CONFIG_UART_CONSOLE=y

CONFIG_SHELL=y

CONFIG_SHELL_BACKEND_SERIAL=y

CONFIG_USE_SEGGER_RTT=n

CONFIG_RTT_CONSOLE=n

CONFIG_SHELL_BACKEND_RTT=n

CONFIG_OPENTHREAD_OPERATIONAL_DATASET_AUTO_INIT=n
CONFIG_OPENTHREAD_DEBUG=y
CONFIG_OPENTHREAD_LOG_LEVEL_DEBG=y

for nrf54L15dk only

CONFIG_SETTINGS_ZMS=y
CONFIG_ZMS=y

CONFIG_PWM=y
CONFIG_LED=y

Channel management

CONFIG_OPENTHREAD_CHANNEL_MANAGER=y
CONFIG_OPENTHREAD_CHANNEL_MONITOR=y`

I'd appreciate any help, thanks!

[LuDuda]

Hello @Allan-led

I believe the issue you’re facing is related to building your application with pre-compiled (and pre-certified) Thread libraries. If you want to enable functionality that isn’t included in those libraries, you’ll need to build OpenThread from source using the following KConfig: CONFIG_OPENTHREAD_SOURCES. I hope that helps.

You can find more information here:

• https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/thread/configuring.html
• https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/thread/prebuilt_libs.html#ug-thread-prebuilt-libs

We do plan, in the next release, to make OT KConfigs promptless when pre-compiled Thread libraries are selected. This should help in identifying the root cause more quickly in similar cases.

[Allan-led]

Thank you, I will check it out!

…

On Thu, Jan 16, 2025 at 12:39 PM Łukasz Duda ***@***.***> wrote: Hello @Allan-led <https://github.com/Allan-led> I believe the issue you’re facing is related to building your application with pre-compiled (and pre-certified) Thread libraries. If you want to enable functionality that isn’t included in those libraries, you’ll need to build OpenThread from source using the following KConfig: CONFIG_OPENTHREAD_SOURCES. I hope that helps. You can find more information here: - https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/thread/configuring.html - https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/thread/prebuilt_libs.html#ug-thread-prebuilt-libs We do plan, in the next release, to make OT KConfigs promptless when pre-compiled Thread libraries are selected. This should help in identifying the root cause more quickly in similar cases. — Reply to this email directly, view it on GitHub <#11153 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOCSXBQ2ONSKON224PJ6CJ32LAKJXAVCNFSM6AAAAABU7JRLKSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBVHEZTSMA> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>