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

Cannot run syslink example when built in ccs

Alexander Vasiljev
Expert 1015 points
Other Parts Discussed in Thread: SYSBIOS

Hi,

I try to make project for syslink samples in ccs accordingly to this article (http://processors.wiki.ti.com/index.php/Creating_CCS_Project_for_SysLink_samples). Now i can build messageQ sample for dsp. But i cannot run it.

I use the same sysbios, ipc, syslink, xdctools as in ezsdk 5.04.00.11. I didn't  rebuild linux side executable. Here is the trace output.

root@dm814x-evm:/usr/share/ti/syslink-examples/TI814X/messageq# ./slaveloader_debug startup DSP ./messageQ_DSP.out
Attached to slave procId 0.
Loading procId 0.
Loaded file ./messageQ_DSP.out on slave procId 0.
Started slave procId 0.
root@dm814x-evm:/usr/share/ti/syslink-examples/TI814X/messageq# ./messageqapp_debug
MessageQApp sample application
Run for all supported proc IDs
Entered MessageQApp_startup
Warning! Unsupported procID specified for running the sample application! proc I
D: [1]
Warning! Unsupported procID specified for running the sample application! proc I
D: [2]
After Ipc_loadcallback:
    status [0x0]
*** Platform_startCallback: Ipc_attach timeout
        Error [0xffffffff] at Line no: 2828 in file /swcoe/sdk/cm/netra/arago-tm
p/work/dm814x-evm-none-linux-gnueabi/ti-syslink-2_10_03_20-r1j/syslink_2_10_03_2
0/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/family/hlos/knl/ti81xx/Platform.c
*** Ipc_control: Platform_startCallback failed!
        Error [0xffffffff] at Line no: 852 in file /swcoe/sdk/cm/netra/arago-tmp
/work/dm814x-evm-none-linux-gnueabi/ti-syslink-2_10_03_20-r1j/syslink_2_10_03_20
/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/ipc/hlos/knl/Ipc.c
Assertion at Line no: 301 in /swcoe/sdk/cm/netra/arago-tmp/work/dm814x-evm-none-
linux-gnueabi/ti-syslink-2_10_03_20-r1j/syslink_2_10_03_20/packages/ti/syslink/u
tils/hlos/knl/Linux/../../../../../../ti/syslink/ipc/hlos/knl/Linux/IpcDrv.c: (status >= 0) : failed
Error in Ipc_control Ipc_CONTROLCMD_STARTCALLBACK[0xffffffff]
Leaving MessageQApp_startup ffffffff

What can i have missed in configuration?

I use dm8148 evaluation module, 2x512MB DDR3, CCS version 5.1.1.00031 (on Windows), ezsdk 5.04.00.11, bios_6_33_02_31, ipc_1_24_02_27, xdctools_3_23_01_43, syslink_2_10_03_20.

  • 0
    TI__Mastermind 18260 points

    Alexander Vasiljev said:
    root@dm814x-evm:/usr/share/ti/syslink-examples/TI814X/messageq# ./messageqapp_debug
    MessageQApp sample application
    Run for all supported proc IDs
    Entered MessageQApp_startup
    Warning! Unsupported procID specified for running the sample application! proc I
    D: [1]
    Warning! Unsupported procID specified for running the sample application! proc I
    D: [2]

    Regarding the above warnings ... when no command line arguments are passed to the Linux application, the Linux sample applications attempt to attach & load to each remote core in the system, as defined by the MultiProc module.  When built under the control of the EZSDK for the TI814X SOC, procIds 1 & 2 (VIDEO-M3 & VPSS-M3) are "hidden" from the applications.  Without any command line arguments, the Linux application attempts to load & run all processors, and since procIds 1 & 2 are hidden you get the warning.  However, it's just a warning - the application will proceed with the DSP and not attempt to load & run the other cores.

    I don't have much experience running remote core executables that were built with a CCS project, but apparently something is not right with your DSP .out file.  Can you use CCS to attach to the DSP and see where it might have gone bad?

    From your Linux-side output we can see that the DSP did not successfully sync with the Linux app during Ipc_attach(), but there is nothing to point to the problem.  I suspect that something is not right with either cache or memory settings regarding SharedRegion 0 (which is the SR used by Ipc module sync data).

    If you can post your project then I could attempt to replicate your issue and have some visibility into the situation, but for now there's not enough data to suggest the issue, nor do I know of common trip-ups when transitioning from host-based builds to CCS builds.

    Regards,

    - Rob

     

  • 0 in reply to Robert Tivy
    Expert 1015 points

    Hi, Robert.

    Thank you for reply.

    As of now i don't know how to attach CCS to the dsp in dm8148. I can attach only to A8.

    Here's my project.

    Best Regards,

    Alexander.

  • 0 in reply to Robert Tivy
    Expert 1015 points

    Hi.

    I have resolved the problem. The article http://processors.wiki.ti.com/index.php/Creating_CCS_Project_for_SysLink_samples suggests to set dmTimerFreq to 32768. But 8148 evm should use 20000000.

  • 0 in reply to Alexander Vasiljev
    TI__Mastermind 18260 points

    Alexander Vasiljev said:
    I have resolved the problem. The article http://processors.wiki.ti.com/index.php/Creating_CCS_Project_for_SysLink_samples suggests to set dmTimerFreq to 32768. But 8148 evm should use 20000000

    Hi Alexander,

    It's great to hear that you have fixed your issue, well done.

    Thankyou for pointing out that dmTimerFreq discrepency on the wiki page.  We will correct that with a pointer to another wiki page that discusses the issue:
    http://processors.wiki.ti.com/index.php/SYS/BIOS_dmtimer_configuration_for_TI81xx

    Regards,

    - Rob