Net core image without logging traces

RE: Net core image without logging traces

dejans — Thu, 27 Jul 2023 12:39:40 GMT

Hi Eugene,

Please have a look at this pull request.

Best regards,
Dejan

RE: Net core image without logging traces

dejans — Fri, 31 Mar 2023 12:33:20 GMT

Hi Eugene,

If you decide to keep CONFIG_NRF53_SYNC_RTC=y in your b0n.conf, you would need to ensure that you disable
CONFIG_NRF53_SYNC_RTC_LOG_TIMESTAMP=n in the same configuration file. This might be due to disabled logging CONFIG_LOG=n.

Best regards,
Dejan

RE: Net core image without logging traces

Hiihtaja — Fri, 31 Mar 2023 04:55:54 GMT

Hi Dejan !

I think RTC SYNC is used only for synchronise logging timestamps.

And it is default feature when IPC is used between core.

For my functionality I no need it for now,

But this is clear ncs code defect (?) and I report this.

Regards,

Eugene

RE: Net core image without logging traces

dejans — Thu, 30 Mar 2023 12:24:47 GMT

Hi Eugene,

I have tested your application (with added #endif in main.c) and it does not produce any build errors if you do not have CONFIG_NRF53_SYNC_RTC in your b0n.conf file. Could you provide more information about your use case and the need for CONFIG_NRF53_SYNC_RTC?

Best regards,
Dejan

RE: Net core image without logging traces

Hiihtaja — Thu, 30 Mar 2023 09:38:32 GMT

Hi Dejan !

It is in my own source code,

LOG_RAW in netcore and it is excluded by

if (IS_ENABLED(CONFIG_LOG)) {

}

if logging is disabled.

But in netcore CONFIG_NRF53_SYNC_RTC=y as usually set by default for sync RTCs and there some function from logging in use.

Regards,

Eugene

RE: Net core image without logging traces

dejans — Thu, 30 Mar 2023 09:04:15 GMT

Hi Eugene,

Where did you put your workaround?

Could you share you configuration file?

Best regards,
Dejan

RE: Net core image without logging traces

Hiihtaja — Wed, 29 Mar 2023 10:04:09 GMT

Hi Dejan !

On my side I use workaround

#if LOG_LEVEL >= LOG_LEVEL_INF
if (IS_ENABLED(CONFIG_LOG)) {
//int i;
LOG_RAW("%-6s %2u [", name, len);
for (int i = 0; i < len; i++) {
LOG_RAW("%2u,", list[i]);
}
LOG_RAW("]\n");
}

But if I enable CONFIG_NRF53_SYNC_RTC=y and disable loggging, some API is called in other component

/home/user/ncs/toolchains/v2.3.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.1.0/../../../../arm-zephyr-eabi/bin/ld.bfd: zephyr/libzephyr.a(sync_rtc.c.obj): in function `remote_callback':
/home/user/ncs/v2.3.0/zephyr/soc/arm/nordic_nrf/nrf53/sync_rtc.c:184: undefined reference to `log_set_timestamp_func'
collect2: error: ld returned 1 exit status

Regards,

Eugene

RE: Net core image without logging traces

dejans — Mon, 27 Mar 2023 14:11:01 GMT

Hi,

I have reported the issue internally. I will get back to you with new information hopefully during this week.

Best regards,
Dejan

RE: Net core image without logging traces

Hiihtaja — Mon, 27 Mar 2023 08:43:40 GMT

Hi Dejan !

Usage of LOG_RAW when CONFIG_LOG=y is not the problem.

Problem is to build image without logs CONFIG_LOG=n

when LOG_RAW is used inside own code.

Do you know any alternative of LOG_RAW ?

Regards,

Eugene

RE: Net core image without logging traces

dejans — Mon, 27 Mar 2023 08:33:16 GMT

Hi,

You should be able to build successfully when using LOG_RAW if you enable logging with CONFIG_LOG=y in cpunet\prj.conf. In addition, you can specify the default log level using CONFIG_LOG_DEFAULT_LEVEL in the same cpunet\prj.conf file.

Best regards,
Dejan

RE: Net core image without logging traces

Hiihtaja — Fri, 24 Mar 2023 16:35:41 GMT

Hi Dejon !

I need it or what can be alternative if I would like to print without automatic new line character ?

#if LOG_LEVEL >= LOG_LEVEL_INF

int i;

LOG_RAW("%-6s %2u [", name, len);

for (i = 0; i < len; i++) {

LOG_RAW("%2u,", list[i]);

}

LOG_RAW("]\n");

#endif

LOG_INF add new line to the end.

Regards,

Eugene

RE: Net core image without logging traces

dejans — Fri, 24 Mar 2023 15:07:43 GMT

Hi,

If you remove LOG_RAW from cpunet\src\main.c, build error should disappear.

Best regards,
Dejan

RE: Net core image without logging traces

Hiihtaja — Fri, 24 Mar 2023 13:32:17 GMT

Hi Dejan !

Can it be becouse of LOG_RAW usage ?

I have attached multiimage build project where LOG_RAW is in use in net core image and CONFIG_LOG=n

devzone.nordicsemi.com/.../loggingno.zip

west build -p --board nrf5340dk_nrf5340_cpuapp

loggingno/build/cpunet/zephyr/include/generated/syscalls/log_msg.h:37: undefined reference to `z_impl_z_log_msg_static_create'

Regards,

Eugene

RE: Net core image without logging traces

dejans — Fri, 24 Mar 2023 09:00:18 GMT

Hi,

[quote user="Hiihtaja"]

I'm using ncs/v2.3.0 release.

I have multi image with own net core what is already quite far away from original sample.

Net core is the child image for app core.

[/quote]

Thank you for this information.

[quote user=""]

I try to build netcore image without any logging traces and always get multiple errors:

/build/cpunet/zephyr/include/generated/syscalls/log_msg.h:37: undefined reference to `z_impl_z_log_msg_static_create'

[/quote]

Does building work when logging is enabled? Could you provide full build output for the failing case?

[quote user="Hiihtaja"]So, you think this is something unusual and CONFIG_LOG=n should be enough ?[/quote]

CONFIG_LOG is a global logging switch and it turns off log calls when set to 'n'. Therefore, if you want to turn off log calls, turning it to 'n' should be enough.

Best regards,
Dejan

RE: Net core image without logging traces

Hiihtaja — Thu, 23 Mar 2023 17:20:12 GMT

Hi !

I'm using ncs/v2.3.0 release.

I have multi image with own net core what is already quite far away from original sample.

Net core is the child image for app core.

So, you think this is something unusual and CONFIG_LOG=n should be enough ?

Regards,

Eugene

RE: Net core image without logging traces

dejans — Thu, 23 Mar 2023 14:27:28 GMT

Hi,

Which NCS version do you use? Which sample do you use? Could you provide more information about the building process?

Best regards,
Dejan