Other Parts Discussed in Thread: SYSCONFIG
Tool/software:
I'm trying to use IPC communication from SysConfig on the AM64x and the receive function RPMessage_recv isn't working like I expect. I'm running ThreadX on the R5F0_0 core and because it's not a supported option I used the NO RTOS BSP. When I try to block on RPMessage_recv my TCP/IP messages stop working. I suspected perhaps it was somehow starving or otherwise blocking out the IP stack, so I tried passing SystemP_NO_WAIT instead of SystemP_WAIT_FOREVER (and on returning timeout I do a ThreadX sleep call). This works to get the IP stack running, but the call constantly spams the following error:
ERROR: RPMessage_recv:371: [IPC RPMSG] Message recv @ 2 local end point failed due to invalid end point Q !!!
I could try switching to using a callback instead of the blocking call, but this raises two questions for me.
1. Shouldn't timing out not spam the console with error messages?
2. Is there a mechanism to define the NO RTOS system function calls to use ThreadX instead of the clock polling mechanism the NO RTOS option seems to use?
