• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 620 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.

IPC Between C6748 and ARMv9 on an OMAP-L138 System Shows Unstable and Unpredictable Behaviour

Steve Kreyer
Intellectual 520 points
Other Parts Discussed in Thread: OMAP-L138, SYSBIOS

Hi,

I have  problems trying to setup the IPC multicore message example. I get different exceptions / errors each time I try to start the example. Sometimes it crashes on ARM, sometimes on DSP, sometimes Ipc_start already crashes with different exception (sometimes it seems to be an exception triggered by hardware (e.g. illegal Op-Code, resource conflict, etc), sometimes also by API like addrNotInSharedRegion, etc.). Sometimes Ipc_start finishes without crash on both cores but then HeapBufMP_open hangs and does not return on Core 1.... And also I got the example 1 time to work... So the error pattern like already mentioned in the subject seems to be totally unpredictable.

The only thing I've changed is the address of the SharedRegion within message_common.cfg.xs, it is 0x4150000 since my OMAP-L138 on the target hardware is connected to external SDRAM instead of DDR, like it is the case on the EVM...

My RTSC setup for the example is as follows:

  • ipc_1_23_05_40
  • bios_6_32_05_54
  • xdctools_3_22_04_46
  • xdais_7_21_01_07
Do you have any ideas what can go wrong here???
Any help on this issue would be very appreciated. If you need more information please let me know...
Kind Regards,
Steve
  • 0
    TI__Mastermind 32475 points

    Steve,

    I can't make sense of what could be wrong from your description because it seems to be all over the map.  Have you run other programs on this board and they are okay?
    Do you power cycle the board after each run? Is there any other shared memory between the cores that you can use for shared region?
    Can you try disabling the cache on both sides and see if that makes a difference?

    At this point, the only thing I can do is suggest things that you can try to see if you can consistently reproduce a fail at the same point.
    Do you get a printout from the exceptions?  If so, that could be helpful.  If not, you should be able to enable the print for the exception.

    var Exception = xdc.module("ti.sysbios.family.c64p.Exception");
    Exception.enablePrint = true;

    Judah

  • 0 in reply to judahvang
    Intellectual 520 points

    Judah,

    thanks for your response. Iam so sorry for wasting your time, but it seemed to be a hardware problem. After two days of hard try I tried a new board and with this board it worked. I almost started to lose belief. Thanks again.

    Steve