Sample ipc_service failed in NCS v2.3.0

RE: Sample ipc_service failed in NCS v2.3.0

Einar Thorsrud — Thu, 16 Mar 2023 14:33:56 GMT

Hi Eugene,

I referred to Synchronized RTC sample just for the description of RTC synchronization. CONFIG_IPM is not enabled in the IPC Service sample. (Though some other IPM related configs are used by the sync RTC implementation like NRF53_SYNC_RTC_IPM_OUT, but these have the default values / IPC channel assignments, and are not set explicitly in the sample).

RE: Sample ipc_service failed in NCS v2.3.0

Hiihtaja — Thu, 16 Mar 2023 11:06:19 GMT

Hi Einar !

I check my .config and sample and

# CONFIG_IPM is not set

anywhere but in synchronised RTC sample mentioned that IPM protocol is in use.

Or this is not the same ?

Regards,

Eugene

RE: Sample ipc_service failed in NCS v2.3.0

Einar Thorsrud — Thu, 16 Mar 2023 10:43:55 GMT

Hi Eugene,

I see. I have till not been able to track down what caused the issue with IPC performance in SDK 2.3.0, but I am looking into it and checking with the developers.

Regarding RTC synchronization, the point of this feature is to have the same time reference on the net core and app core, for instance for logging (which has a dependency on it). This is based on the same clock, so there is just a need to communicate and use a offset. You can see the documentation for the Synchronized RTC sample for a bit more information on that. You will need to remove more functionality in order to disable it, setting CONFIG_LOG_MODE_MINIMAL=y.

RE: Sample ipc_service failed in NCS v2.3.0

Hiihtaja — Thu, 16 Mar 2023 06:33:26 GMT

Hi Einar !

In sample you need to change timeout for demo if it expect to work out of box.

And open question is remain how-to disable RTC sync in both core in correct ways

and for what reason this sync is really need ?

Regards,

Eugene

RE: Sample ipc_service failed in NCS v2.3.0

Einar Thorsrud — Wed, 15 Mar 2023 15:33:23 GMT

Hi Eugene,

I am sorry for the late reply. Did you resolve this? If not, can you elaborate on the issue (what you are seeing, what you are doing, and what you are expecting)?

Einar

RE: Sample ipc_service failed in NCS v2.3.0

Hiihtaja — Tue, 07 Mar 2023 17:38:27 GMT

Hi Einar !

Looks like RTC_SYNC is automatically added to my custom network core automatically.

*** Bootnghyr O uld v3.2.99-ns2 ***
Hello world from net nrf5340dcpunet, data Mar 7 2023, time 14:1:10
OSF I-srvienrf540dk_nf0et started
[00:00:00.027,862]nc_rtc: Updated timetamp to synchronized RTC by 294 ticks (8972us)Δpkt: 249 (255 B/pkt) | throughput: 507960 bit/s
Δpkt: 248 (255 B/pkt) | throughput: 505920 bit/s
Δpkt: 248 (255 B/pkt) | throughput: 505920 bit/s

I have disabled it

# IPC service
CONFIG_IPC_SERVICE=y
CONFIG_HEAP_MEM_POOL_SIZE=4096
CONFIG_OPENAMP=y
CONFIG_OPENAMP_SLAVE=y
CONFIG_OPENAMP_MASTER=n
CONFIG_IPC_SERVICE_BACKEND_RPMSG=y
CONFIG_MBOX=y
CONFIG_NRF53_SYNC_RTC=n
#CONFIG_MBOX_NRFX_IPC=n
CONFIG_IPM=n
CONFIG_IPC_SERVICE_LOG_LEVEL_INF=y

I have added CONFIG_NRF53_SYNC_RTC=n to application core as well. At list build is not complain.

Regards,

Eugene

RE: Sample ipc_service failed in NCS v2.3.0

Einar Thorsrud — Tue, 07 Mar 2023 16:17:44 GMT

Hi,

You are right, the sample seems broken in nRF Connect SDK 2.3.0. I have not been able to get to the bottom of this yet, but will look into it.

Regarding RTC synchronization, CONFIG_NRF53_SYNC_RTC is set to y by default in most cases.

RE: Sample ipc_service failed in NCS v2.3.0

Hiihtaja — Tue, 07 Mar 2023 07:21:36 GMT

Hi !

I think, very short interval is set by default

with CONFIG_APP_IPC_SERVICE_SEND_INTERVAL=20000

Traces are visible from both cores:

*** Booting Zephyr OS build v3.2.99-ncs2 ***
IPC-service nrf5340dk_nrf5340_cpunet demo started
[00:00:00.520,477] <inf> sync_rtc: Updated timestamp to synchronized RTC by 8360 ticks (255126us)
Δpkt: 50 (100 B/pkt) | throughput: 40000 bit/s
Δpkt: 50 (100 B/pkt) | throughput: 40000 bit/s
Δpkt: 49 (100 B/pkt) | throughput: 39200 bit/s

*** Booting Zephyr OS build v3.2.99-ncs2 ***
IPC-service nrf5340dk_nrf5340_cpuapp demo started
Δpkt: 50 (100 B/pkt) | throughput: 40000 bit/s
Δpkt: 50 (100 B/pkt) | throughput: 40000 bit/s
Δpkt: 50 (100 B/pkt) | throughput: 40000 bit/s

But

from what component come trace

[00:00:00.520,477] <inf> sync_rtc: Updated timestamp to synchronized RTC by 8360 ticks (255126us)

RTC syncronization should be disabled by default ?

Regards, Eugene