Quantcast
Channel: Processors forum - Recent Threads
Viewing all articles
Browse latest Browse all 17527

DSP interrupt via syslink example on OMAPL138

$
0
0

Hi all,

Here is my environment.

1. mcsdk_1_01_00_02

2. bios_6_35_01_29

3. c6000_7.4.2

4. ipc_1_25_03_15

5. syslink_2_21_01_05

6. xdctools_3_25_00_48

I based on ex02_messageq (syslink example) to initialize I2C, McASP, AIC3106 and Interrupt on DSP side. Then I added LED control to make sure McASP EDMA (chunk) interrupt was generated. The behavior was normal when I exacted first run. But the interrupt was gone after I did the second run. 

Here is my test steps.

1. cd /ex02_messageq/debug

2. ./slaveloader startup DSP server_dsp.xe674 // LED is twinkling, but the second run LED is no response

Attached to slave procId 0.
Loading procId 0.
Loaded file server_dsp.xe674 on slave procId 0.
Started slave procId 0.

3. ./app_host DSP //  syslink between ARM and DSP is workable ( also include DSP McASP)

--> main:
--> 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
<-- Main_main:
<-- main:

4. ./slaveloader shutdown DSP

Stopped slave procId 0.
Unloaded slave procId 0.
Detached from slave procId 0.

Attached sample code:

https://dl.dropboxusercontent.com/u/12447225/DSP/ex02_messageq.tar.gz

My queries are:

1. Am I right to use this method to check interrupt on DSP side? Or have any better way to do such verification?

2. Which steps I miss to set in my sample code that result SW interrupt not happened at second run?

Thanks in advance.

B.R.

OC


Viewing all articles
Browse latest Browse all 17527


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>