Michal Princ

Hello @stefanct , thanks for your report, it deals with known limitation. Extension and template is forced to be added into the project because we wanted - the useful extension/TAD...

Hello @stefanct , thank you for providing your inputs. As I indicted the user options definition and the way of defining components dependencies is going to be changed soon. Hope...

Hi Dusan, as for point 1, @mcuxsusan could comment that... as for point 2, this files placing inconsistency seems to be relevant just when standalone example project is downloaded, this...

Hello @amgross , the new release has been done recently: https://github.com/EmbeddedRPC/erpc/releases/tag/1.13.0 The project is in maintenance mode now due to limited capacities, will try to go through open issues and...

Hello @escherstair , yes, definitely it is possible to have multiple endpoints on each side/core and they can communicate each other. Due to the tx/rx vrings and virtqueues there is...

Hello @escherstair , it is the misunderstanding ... no, it is not the true that "on every endpoint there must be a single sender and a single receiver". When talking...

Hi @escherstair , thanks, now I understand it more ... so you have originated from this examples and updated it: https://github.com/nxp-mcuxpresso/mcuxsdk-examples/tree/release/24.12.00/multicore_examples/rpmsg_lite_str_echo_rtos/remote From the config file I can see that you...

Hi @escherstair , thanks for other details, as for you questions: > I think that this shared memory is where the vring buffers are stored. Right? correct > I think...

Nothing suspicious now, rpmsgSend is called sequentially so there should not be any collision in M7 sending. Let's wait for your testing with disabled shmem cache handling.... Regards Michal

Hello @escherstair I would focus on simplifying the app. logic and eliminate possible issues that could come from the application. I would try the simplest possible implementation that sends repeatedly...