Device Tree overlay ipc icmsg sample

[dario.sortino]

Hello everyone.

I was trying to integrate the ipc_service sample in my application. It was working all fine and I was able to set up and link the endpoint in my code. I then tried to run a clean build, and I don't know why everything broke: when I try to execute ipc_service_register_endpoint, this happens, the board resets and keeps doing it forever.

 

Thinking that is a matter of memory position, I found out that my compiled devicetree output for the application core has a reserved-memory node like this

reserved-memory {
        #address-cells = <1>;
        #size-cells = <1>;
        ranges;
        sram0_image: image@20000000 {
                reg = <0x20000000 DT_SIZE_K(448)>;
        };

        sram0_s: image_s@20000000 {
                reg = <0x20000000 0x40000>;
        };

        sram0_ns: image_ns@20040000 {
                reg = <0x20040000 0x30000>;
        };

        sram_rx: memory@20078000 {
                reg = <0x20078000 0x8000>;
        };

};

Instead of 

reserved-memory {
        sram_tx: memory@20070000 {
                reg = <0x20070000 0x8000>;
        };

        sram_rx: memory@20078000 {
                reg = <0x20078000 0x8000>;
        };

};

Network core side instead, the devicetree seems ok, but I still encounter the error at endpoint registration time.

I am quite lost and I don't really know how to proceed, since this problem appeared point-blank when I tried to build from zero once again.

[dario.sortino]

I made some tests and I found out that by removing EVERY printing involved in real-time, I can send every message received via ESB to the application core, elaborate it and print using printk in the debug USB of the dk only the first byte of the payload (that for me represents the node ID).

Curious enough, I found out that I can also do the same processing in the work queue I set up in the network core, even though I cannot print the whole message received, but checking the first byte is fine.

I am confidant enough to say that printk is too slow for the smooth execution of the whole application. I'll try to switch to the nRF USB using CDC ACM in the application core. Any reference for that?

[Vidar Berg]

I suggest you use the Zephyr logger module in deferred mode (https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/services/logging/index.html). This will cause the log messages to be processed in a separate low priority logging thread, so it won't block your other tasks. 

You may also consider using the RTT backend instead of UART as it is considerably faster. 

To use prinkt with the logger, you can enable CONFIG_LOG_PRINTK=y.