Failed to enable tracking in Net subsys.

[Replay]

Hi,

I'm working on a project where we would like to track system performance using Segger Systemview.

I'm building with the following RTT configs:

CONFIG_USE_SEGGER_RTT=y

CONFIG_DEBUG_OPTIMIZATIONS=n
CONFIG_DEBUG_THREAD_INFO=y

CONFIG_TRACING=y
CONFIG_SEGGER_SYSTEMVIEW=y
CONFIG_SEGGER_SYSTEMVIEW_BOOT_ENABLE=n
CONFIG_SEGGER_SYSVIEW_POST_MORTEM_MODE=n

and I'm getting the following errors:

/home/<user>/ncs/v2.9.0/zephyr/include/zephyr/tracing/tracing_macros.h:43:9: warning: implicit declaration of function 'sys_port_trace_net_tx_time' [-Wimplicit-function-declaration]
   43 |         sys_port_trace_ ## name ## _ ## func
      |         ^~~~~~~~~~~~~~~
/home/<user>/ncs/v2.9.0/zephyr/include/zephyr/sys/util_internal.h:72:26: note: in definition of macro '__DEBRACKET'
   72 | #define __DEBRACKET(...) __VA_ARGS__
      |                          ^~~~~~~~~~~
/home/<user>/ncs/v2.9.0/zephyr/include/zephyr/sys/util_internal.h:64:9: note: in expansion of macro '__GET_ARG2_DEBRACKET'
   64 |         __GET_ARG2_DEBRACKET(one_or_two_args _if_code, _else_code)
      |         ^~~~~~~~~~~~~~~~~~~~
/home/<user>/ncs/v2.9.0/zephyr/include/zephyr/sys/util_internal.h:59:9: note: in expansion of macro '__COND_CODE'
   59 |         __COND_CODE(_XXXX##_flag, _if_1_code, _else_code)
      |         ^~~~~~~~~~~
/home/<user>/ncs/v2.9.0/zephyr/include/zephyr/sys/util_macro.h:180:9: note: in expansion of macro 'Z_COND_CODE_1'
  180 |         Z_COND_CODE_1(_flag, _if_1_code, _else_code)
      |         ^~~~~~~~~~~~~
/home/<user>/ncs/v2.9.0/zephyr/include/zephyr/tracing/tracing_macros.h:211:9: note: in expansion of macro 'COND_CODE_1'
  211 |         COND_CODE_1(_SYS_PORT_TRACE_IS_DISABLED(type), (),                                         \
      |         ^~~~~~~~~~~
/home/<user>/ncs/v2.9.0/zephyr/include/zephyr/tracing/tracing_macros.h:212:22: note: in expansion of macro '_SYS_PORT_TRACE_WRAP'
  212 |                     (_SYS_PORT_TRACE_WRAP(func, __VA_ARGS__)))
      |                      ^~~~~~~~~~~~~~~~~~~~
/home/<user>/ncs/v2.9.0/zephyr/include/zephyr/tracing/tracing_macros.h:236:9: note: in expansion of macro '_SYS_PORT_TRACE_IF_NOT_DISABLED'
  236 |         _SYS_PORT_TRACE_IF_NOT_DISABLED(type, _SYS_PORT_TRACING_FUNC(type, func), __VA_ARGS__)
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/<user>/ncs/v2.9.0/zephyr/include/zephyr/tracing/tracing_macros.h:236:47: note: in expansion of macro '_SYS_PORT_TRACING_FUNC'
  236 |         _SYS_PORT_TRACE_IF_NOT_DISABLED(type, _SYS_PORT_TRACING_FUNC(type, func), __VA_ARGS__)
      |                                               ^~~~~~~~~~~~~~~~~~~~~~
/home/<user>/ncs/v2.9.0/zephyr/subsys/net/ip/net_if.c:281:25: note: in expansion of macro 'SYS_PORT_TRACING_FUNC'
  281 |                         SYS_PORT_TRACING_FUNC(net, tx_time, pkt, end_tick);
      |                         ^~~~~~~~~~~~~~~~~~~~~

I have tried to add these configs as well but without any luck:

CONFIG_TRACING_NET_CORE=n
CONFIG_TRACING_NET_SOCKETS=n

Forgot to add:
Nordic SDK: 2.9.0
SiP: nrf9160
Modem FW version: 1.3.7

[Sigurd Hellesvik]

Hi,

Check out the tracing sample and its prj_sysview.conf config. Try to build that sample with that file.

Regards,
Sigurd Hellesvik

[Replay]

Hi Sigurd,

Thank you for your suggestion.

It builds fine but I'm having a hard time to understand why the "CONFIG_TRACING is not set" in the build folder .config

BR:
Replay

[Sigurd Hellesvik]

Replay said:

It builds fine but I'm having a hard time to understand why the "CONFIG_TRACING is not set" in the build folder .config

Of your sample or the tracing sample?

[Replay]

The tracing sample from zephyr is building but "CONFIG_TRACING is not set" in the build folder .config.

[Sigurd Hellesvik]

You need to build using one of the prj_file_suffix.conf files instead of with the default prj.conf

[Replay]

Edit:
Okay just by adding CONFIG_NETWORKING=y to the tracing sample the issue is present.

Old:

My bad thought I used the correct prj.conf file.

Issue can be replicated when combining the tracing sample and azure_iot_hub sample:

Here is a snippet from the .config from the tracing sample:

#
# Tracing Configuration
#
CONFIG_TRACING_SYSCALL=y
CONFIG_TRACING_THREAD=y
CONFIG_TRACING_WORK=y
CONFIG_TRACING_ISR=y
CONFIG_TRACING_SEMAPHORE=y
CONFIG_TRACING_MUTEX=y
CONFIG_TRACING_CONDVAR=y
CONFIG_TRACING_QUEUE=y
CONFIG_TRACING_FIFO=y
CONFIG_TRACING_LIFO=y
CONFIG_TRACING_STACK=y
CONFIG_TRACING_MESSAGE_QUEUE=y
CONFIG_TRACING_MAILBOX=y
CONFIG_TRACING_PIPE=y
CONFIG_TRACING_HEAP=y
CONFIG_TRACING_MEMORY_SLAB=y
CONFIG_TRACING_TIMER=y
CONFIG_TRACING_EVENT=y
CONFIG_TRACING_POLLING=y
CONFIG_TRACING_PM=y
# CONFIG_TRACING_NETWORKING is not set
# end of Tracing Configuration

and here is for the tracing sample where azure_iot_hub sample has been merged:

#
# Tracing Configuration
#
CONFIG_TRACING_SYSCALL=y
CONFIG_TRACING_THREAD=y
CONFIG_TRACING_WORK=y
CONFIG_TRACING_ISR=y
CONFIG_TRACING_SEMAPHORE=y
CONFIG_TRACING_MUTEX=y
CONFIG_TRACING_CONDVAR=y
CONFIG_TRACING_QUEUE=y
CONFIG_TRACING_FIFO=y
CONFIG_TRACING_LIFO=y
CONFIG_TRACING_STACK=y
CONFIG_TRACING_MESSAGE_QUEUE=y
CONFIG_TRACING_MAILBOX=y
CONFIG_TRACING_PIPE=y
CONFIG_TRACING_HEAP=y
CONFIG_TRACING_MEMORY_SLAB=y
CONFIG_TRACING_TIMER=y
CONFIG_TRACING_EVENT=y
CONFIG_TRACING_POLLING=y
CONFIG_TRACING_PM=y
CONFIG_TRACING_NETWORKING=y
CONFIG_TRACING_NET_SOCKETS=y
CONFIG_TRACING_NET_CORE=y
# end of Tracing Configuration

Note the difference in network tracing in the bottom of the configs.