• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 361 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM5728: IPC - MessageQ different address of payload

Ivan ?elehovski
Prodigy 90 points

Part Number: AM5728

Hello, I'm trying to run the changed example of MessageQApp on linux, and to get some response from messageq_single that is running on IPU1.

below is source code and built FW to bind on IPU1. Source for MessageQApp is in ti/ipc_xx_xx_xx_xx/qnx/src/tests/MessageQApp/MessageQApp.c

messQ_starter_pack_IPU1.zip

it gets stuck on MessageQApp:

sprintf(remoteQueueName, "%s_%s", SLAVE_MESSAGEQNAME, MultiProc_getName(procId));

status = MessageQ_open(remoteQueueName, &queueId);
 
as well as on slave side:
MessageQ_get(messageQ, &msg, MessageQ_FOREVER);

It seems to me like that can't find the same address (as in terminal: HOST is queueing 0x80, while SLAVE is queueing 0x10080

only possible explanation that i have for this is the custom memory map for the slave side. I had copied project from 3.7.3 IPC for AM57xx called UART_Basic_Example_evmAM572x_m4ExampleProject_with_ipc, in which we create a custom memory map. 

Mostly I'm interested to create helloWorld with IPC, without any extra addons that come with examples (server creation, UART, GPIO examples, etc)

If I start from scratch, is it possible to leave default memory map for both DSP and/or IPU with minimal .cfg, and still have IPC between processors?

Kind regards