Closed kpapak77 closed 3 years ago
Hello @kpapak77 this address translation issue should be handled by platform_patova() and platform_vatopa() functions implementation in rpmsg_platform.c source file (like this)
BTW, what SoC are you using? Have you created/ported the platform layer (rpmsg_platform.[c|h]) for this device?
Regards Michal
Hello Michal, I transferred my logic to platform_patova()/vatopa(). I am not using any known SoC. It is a system under development and I am investigating the rpmsg-lite framework.
Best Regards, Kostas
Hello,
I got a hardfault while implementing a ping-pong example between a CM33 (configured as the rpsmg-lite master) and a CM0+ (configured as the rpmsg-lite remote) core in a multicore chip. The hardfault happened on the CM0+, because the shared space memory is differently mapped by the two cores. The shared memory space starts from SH_MEM_MASTER_BASE_ADDRESS for the CM33 side and from SH_MEM_REMOTE_BASE_ADDRESS for the CM0+ side.
I added the following workaround to rpmsg-lite.c, implementing the shared memory address translation from master to remote addresses:
and
Best Regards, Kostas