Segger SystemView

[Elbert]

When configuration options CONFIG_SEGGER_SYSTEMVIEW=y and CONFIG_TRACING=y are added to my prj.conf the following build errors are shown:

followed by many other errors.

Any suggestions how to solve this?

Best regards,

Elbert

[dejans]

Hi,

Which application sample did you try to build?

Best regards,
Dejan

[Elbert]

It is not a sample application but my custom development application:

nRF SDK v2.3.0

VS Code version 1.81.0

nRF Connect for VS Code v2023.7.129

Best regards,

Elbert

[dejans]

Hi Elbert,

Which board do you use?

Best regards,
Dejan

[Elbert]

Custom board based on nRF9160.

Best regards,

Elbert

[dejans]

Hi Elbert,

Have you seen the same error on nrf9160-dk?

Best regards,
Dejan

[Elbert]

Hello,

I have not tried this on nrf9160-dk, it seems to me this is not board dependent.

It looks like it is depending configurations options.

Best regards,

Elbert

[dejans]

Hi Elbert,

Could you try adding CONFIG_EVENTS=y to your project configuration?

Best regards,
Dejan

[Elbert]

dejans said:

Could you try adding CONFIG_EVENTS=y to your project configuration?

CONFIG_EVENTS=y was already included in my prj.conf file.

Best regards,

Elbert

[dejans]

Hi Elbert,

Could you please provide minimal sample for reproducing the issue on nRF9160-dk?

EDIT: Does the same issue appear in NCS v2.2.0 (as in NCS v2.3.0)?

Best regards,
Dejan

[Elbert]

Minimal sample with all my configuration options attached.

In this sample the build is not broken as in my own application, but build is finished.

I did not try NCS v2.2.0, only v2.3.0.

Best regards,systemview.zip

Elbert

[dejans]

Hi Elbert,

There is an existing issue which might be related. Could you please try using NCS v2.2.0? Is error still present?

For which build target should your sample be built?

Best regards,
Dejan

[Elbert]

Perhaps you can verify difference between v2.2.0 and v2.3.0 or newer?

The build target is nrf9160dk_nrf9160_ns.

Best regards,

Elbert