Linux/AM5728: IPC examples crash on loading in DSP

Hello,

Which version of Processor SDK are you using?

I am using ti-processor-sdk-linux-am57xx-evm-04.03.00.05

I will try to reproduce this on my end. In the meantime, can you try using the images provided by Rex in the following thread?

Using the binary files that Rex provided did make the IPC example run successfully. Below is my output:

root@am57xx-evm:/sys/bus/platform/drivers/omap-rproc# echo 40800000.dsp > bind
[  878.398350] omap-rproc 40800000.dsp: assigned reserved memory node dsp1_cma@99000000
[  878.406255] remoteproc remoteproc2: 40800000.dsp is available
root@am57xx-evm:/sys/bus/platform/drivers/omap-rproc# [  878.419325] remoteproc remoteproc2: powering up 40800000.dsp
[  878.428560] remoteproc remoteproc2: Booting fw image dra7-dsp1-fw.xe66, size 4663976
[  878.443402] omap_hwmod: mmu0_dsp1: _wait_target_disable failed
[  878.449298] omap-iommu 40d01000.mmu: 40d01000.mmu: version 3.0
[  878.455243] omap-iommu 40d02000.mmu: 40d02000.mmu: version 3.0
[  878.469976] alloc_contig_range: [99600, 99700) PFNs busy
[  878.481976] virtio_rpmsg_bus virtio2: rpmsg host is online
[  878.487528] remoteproc remoteproc2: registered virtio2 (type 7)
[  878.493529] remoteproc remoteproc2: remote processor 40800000.dsp is now up
[  878.501217] virtio_rpmsg_bus virtio2: creating channel rpmsg-proto addr 0x3d
[  878.508534] omap-rproc 40800000.dsp: received echo reply from 40800000.dsp

root@am57xx-evm:~/ex02_ti_prebuilt# ./app_host DSP1
--> main:
[ 1157.500415] omap_hwmod: mmu0_dsp2: _wait_target_disable failed
[ 1157.506318] omap-iommu 41501000.mmu: 41501000.mmu: version 3.0
[ 1157.512279] omap-iommu 41502000.mmu: 41502000.mmu: version 3.0
--> Main_main:
--> App_create:
App_create: Host is ready
<-- App_create:
--> App_exec:
App_exec: sending message 1
App_exec: sending message 2
App_exec: sending message 3
App_exec: message received, sending message 4
App_exec: message received, sending message 5
App_exec: message received, sending message 6
App_exec: message received, sending message 7
App_exec: message received, sending message 8
App_exec: message received, sending message 9
App_exec: message received, sending message 10
App_exec: message received, sending message 11
App_exec: message received, sending message 12
App_exec: message received, sending message 13
App_exec: message received, sending message 14
App_exec: message received, sending message 15
App_exec: message received
App_exec: message received
App_exec: message received
<-- App_exec: 0
--> App_delete:
<-- App_delete:
<-- Main_main:
<-- main:

Is there a bug in the source code for the IPC examples for the current SDK version? If so, can you identify where it is and provide updated code?

We confirmed this is a bug in the release and will be fixed in v5.0.

The root cause is that the timer is not properly configured. To fix this, make the following modifications to Dsp1.cfg:

var Clock = xdc.useModule('ti.sysbios.knl.Clock');

Clock.tickSource = Clock.TickSource_NULL;  <--Remove

//Clock.tickSource = Clock.TickSource_USER; <--Uncomment

/* Configure BIOS clock source as GPTimer5 */

//Clock.timerId = 0;

 

var Timer = xdc.useModule('ti.sysbios.timers.dmtimer.Timer');

 

/* Skip the Timer frequency verification check. Need to remove this later */

Timer.checkFrequency = false;

 

/* Match this to the SYS_CLK frequency sourcing the dmTimers.

* Not needed once the SYS/BIOS family settings is updated. */

Timer.intFreq.hi = 0;

Timer.intFreq.lo = 19200000;

 

//var timerParams = new Timer.Params(); <--Uncomment

//timerParams.period = Clock.tickPeriod; <--Uncomment

//timerParams.periodType = Timer.PeriodType_MICROSECS; <--Uncomment

/* Switch off Software Reset to make the below settings effective */

//timerParams.tiocpCfg.softreset = 0x0;  <--Uncomment

/* Smart-idle wake-up-capable mode */

//timerParams.tiocpCfg.idlemode = 0x3; <--Uncomment

/* Wake-up generation for Overflow */

//timerParams.twer.ovf_wup_ena = 0x1; <--Uncomment

//Timer.create(Clock.timerId, Clock.doTick, timerParams); <--Uncomment

I tried editing the cfg file in this way, rebuilding, and rebinding the DSP device but I still see crash detected in the dmesg.

Thanks, that fixed it. Could you point me in the direction where I could learn about how what the purpose of that file is so that I can understand why this fixes the issue?