Problem with remote shell over IPC

RE: Problem with remote shell over IPC

Jennifer Gibbs — Tue, 29 Jul 2025 02:05:43 GMT

Hello,

The Radio Test sample for short-range PHY testing uses the ipc shell between app and net cores and should help fill in the gap:

Radio test (short-range)

RE: Problem with remote shell over IPC

psiemek — Mon, 28 Jul 2025 14:36:30 GMT

I think I have ipc working but it is not linked to shell backends. Seems like logs from radio core getting to shell_ipc endpoint but shell instance on app core do not print it out (looks on logs above: <inf> shell_ipc: RX ring buffer full. Dropping 30 bytes) and when I'm executing a "shell backends" command I see:

Also-IoT:~$ shell backends
Active shell backends:
   0. :Also-IoT-net:~$  (shell_ipc)
   1. :Also-IoT:~$  (shell_uart)

which means that backend on app core side also working. I'm not sure what I'm missing. How to link ipc channel to app core. I think shell backend on radio is linked (looks on logs above: <inf> shell_ipc: RX ring buffer full. Dropping 30 bytes).

I do not have a possibility to execute "shell ipc" (it allows to switch between cores on shell level) command as it not appear yet. It will appear when link between cores will be completely defined end allows to exchange a data.

RE: Problem with remote shell over IPC

Jennifer Gibbs — Fri, 25 Jul 2025 22:48:20 GMT

Sorry as I should have kept digging...I found the following which does support the nRF54H20 and demonstrates remote shell IPC service: IPC service

Note that in the section for building and configuration the H20 it does expect this to be between the two domains.

RE: Problem with remote shell over IPC

psiemek — Fri, 25 Jul 2025 21:19:05 GMT

Yes. Based on this example I achieved such situation :-) Now I'm looking what I missed. From my perspective network core sending some logs and I see it on app core as a full RX ring buffer. I don't know why App core do not read it and write on his shell console and why I do not have this "shell ipc" command. How to link &ipc0 with shell on app core side ? My dts on app side has such ipc structure:

ipc0: &cpuapp_cpurad_ipc {
	status = "okay";
	mbox-names = "rx", "tx";
	tx-region = <&cpuapp_cpurad_ipc_shm>;
	rx-region = <&cpurad_cpuapp_ipc_shm>;
	tx-blocks = <32>;
	rx-blocks = <32>;

	bt_hci_ipc0: bt_hci_ipc0 {
		compatible = "zephyr,bt-hci-ipc";
		status = "okay";
	};
};

I also tried to use &cpuapp_cpurad_ipc as a subset of ipc0 but same result.

One thing:

CONFIG_IPC_SERVICE_BACKEND_RPMSG=y

Do not exist in SDK 0.17 (latest) so no chance to make it in a same way as in remote shell example.

RE: Problem with remote shell over IPC

Jennifer Gibbs — Fri, 25 Jul 2025 20:51:09 GMT

Hello, have you seen the nrf/samples/nrf5340/remote_shell sample application for the nRF5340? While written for the nRF5340, it details the overlays, kconfig, and prj.conf you will need to imitate in your setup in the nRF54H20. Please take a look, the files I think will be of most interest are exactly as I listed here, I believe they'll provide the 'Aha!' moment you're looking for. Let me know if this doesn't work out for you though.