• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 101 subscribers
  • Views 515 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Adding an HWI to messageq project

Shreeprada M S
Prodigy 40 points
Other Parts Discussed in Thread: DM3730, SYSBIOS

Hello,

I am using DM3730 torpedo module wherein I could successfully run the messageQ Application and exchange the data between ARM and IVA core.

Now I want IVA to receive data from a peripheral and send that data to ARM core. For this, I added an HWI in messageApp_common.cfg.xs file. When I execute the messageQ application, STARTCALLBACK failed and Heapmem Assertion failed error also showed up.

I tried to increase the stack and heap sizes in syslink_common.cfg file. But that did not help.

Is this error due to stack and heap size?

What modification will help to get out of this problem?

Best Regards,

Shreeprada

  • 0
    TI__Expert 3265 points

    Hi Shreeprada,

    Can you tell what messageQ application you are referring to  - software release versions of the dependent TI modules/SDK etc.,

    Also, can you share the changes you made to the configuration files?

    Best regards,

    Murat

  • 0 in reply to raormanrat
    Prodigy 40 points

    Hi Murat,

    Since I was with some other project, I could not reply in time. Sorry for a very late reply. The problem still remains unsolved.

    The software release versions are as follows:

    syslink: 2.10.08.35
    IPC: 1.24.3.32
    CCS: 5.2

    The application is the sample messageQ application.

    The following declarations are added  to  MessageQApp.cfg:

    var Hwi = xdc.useModule('ti.sysbios.hal.Hwi');
    var hwi0Params = new Hwi.Params();
    hwi0Params.instance.name = "McBSP1_RX";
    hwi0Params.eventId = 89;
    hwi0Params.priority = -1;
    hwi0Params.enableInt = true;
    Program.global.McBSP1_RX = Hwi.create(5, "&McBSP1_RX_isr", hwi0Params);
     
    var hwi1Params = new Hwi.Params();
    hwi1Params.instance.name = "McBSP4_TX";
    hwi1Params.eventId = 90;
    hwi1Params.enableInt = true;
    Program.global.McBSP4_TX = Hwi.create(6, "&McBSP4_TX_isr", hwi1Params);

    Are these static declarations of harware interrupts causing a problem?

    Kindly let me know if there is any other way of using interrupts.

    Regards,

    Shreeprada

  • 0 in reply to Shreeprada M S
    Prodigy 40 points
    Hello,
    Has anyone ever tried to add HWI to syslink project this way? Kindly reply and help us to debug the issue.

    Thanks in advance