Michal Princ

Hello Sebastian, thanks for this report. The comment has been provided via the NXP community already but I agree the solution is not ideal in this case. There is no...

Hi, I think it should work in case of TCP transport, even without the arbitrator running on the server side. @Hadatko , could you confirm, please? Thanks.

There is the test code in CPP for serial communication testing in test/common folder , see [unit_test_serial_client.cpp](https://github.com/EmbeddedRPC/erpc/blob/develop/test/common/unit_test_serial_client.cpp) [unit_test_serial_server.cpp](https://github.com/EmbeddedRPC/erpc/blob/develop/test/common/unit_test_serial_server.cpp) This is not maintained but could help you.

Try to convert struct into array, i.e. use "fooStruct[0] a" instead of "fooStruct a" as the interface function parameter.

Hi, see the comment/response in #186 please.

Hello @drumairali , once both the erpc client and the server are needed to be running on the same device, the erpc arbitrator needs to be added into the project...

Hello @drumairali , it is great you got it working. Unfortunately, it is hard to judge what is the rootcause of the invalid CRC of the message received on the...

I am thinking why the CRC issue happens. We have framed transport so the header is sent first followed by the payload message(s). The serial communication bus (hw) is only...

Hello @burgerkingorama, there is no way to do it and it does not make sense either. When creating the IDL file you are specifying the remotely called function names so...

It seems to me like a nice-to-have feature, I encourage you to implement that and create the pull request if really needed. Thanks.