dsplink compilation using CCS

Sateesh,

I have the following questions:

1) Did you try running the loop sample with DSP executable built using DSPLink build system?

2) The sample is crashing in PROC_load. I have a few suggestions here:

    a) Ensure that the mem variable set in Linux bootargs is correct and corresponds to DSPLink memory map

    b) Do a verbose build of loop sample using DSPLink build system to ensure that the compile options, flags that you have passed in CCS build are the same.

Deepali

hai Deepali

Thanks for replying

 I want to write an audio application using dsplink with GPP OS  linux-2.6.22 and omap3evm. I had  written a low level dsp application using ccs and loaded in omap3evm without linux. I am new in dsplink. plz give some doccument for integrating an audio application in omap3evm using dsplink. plz help..

regards

satheesh

Satheesh,

For DSPLink, please look at

http://wiki.davincidsp.com/index.php/Category:BIOSLink

For DSPLink overview, please look at

http://wiki.davincidsp.com/index.php/DSPLink_Overview

Deepali

deepali

I have installed dsplink in omap3evm for arm dsp communication with gpp os linux. my aim is to loop back speech data read from codec device and compress with ower own algorithm.

Data types used for data tansfer is signed int16. I edit the loop.c application for this purpose. while executing this application  following error is occured.

loop.c: In function 'LOOP_Create':
loop.c:348: warning: passing argument 3 of 'CHNL_allocateBuffer' from incompatible pointer type
loop.c:360: warning: assignment from incompatible pointer type
loop.c: In function 'LOOP_Execute':
loop.c:400: warning: assignment from incompatible pointer type
loop.c: In function 'LOOP_Delete':
loop.c:511: warning: passing argument 3 of 'CHNL_freeBuffer' from incompatible pointer type.

how can allocate a buffer with Int16 data types. Here CHNL_create, CHNL_allocateBuffer allocate char8 buffer.plz give necesasary information.

changes done in existing program is

STATIC Int16 * LOOP_Buffers [1] ;

regards

satheesh

Satheesh,

The change that you have done will cause a build failure.The CHNL_allocate buffer allocates a buffer of type Character.

For your use case, you can processing and consuming the Char* data as Int16 by typecasting it to Int16 while reading/writing into it.

Deepali

hai deepali

thanks for your help

I have one more question. I have to run a soft codec in dsp. Here I am using loop sample application for data transfer. Our soft codec need 480 buffer size.While trying this buffer size ,application  goes to error.I think buffer allign size is 128 and will work only for that size ,I dont know.Plz give necessary infor mation for working this much buffer size.I am using omap3530 with os linux...plz

regards

satheesh

Satheesh,

The shared memory needs to be aligned to Cache Line i.e. 128. Cache management API's on DSP work on cache aligned addresses. DSPLink mandates shared memory usage in cache aligned sizes.POOL API's fails if a non cache aligned address is passed.

I would recommend  configuring POOL buffer for size 512 and using the first 480  bytes. Will that help?

Deepali

hai deepali

thanks for your help

while I am trying LOOP_BufferSize=512 some audio data are missing .plz give any suggession to this issue..

regards

satheesh

Satheesh,

Can you give some more input? Did the application work correctly before you made the change?

Deepali

hai deepali

thanks for replying

I modified the loop sample application  for my audio data loop back. I have run the program by ./loopgpp loop.out 512 78 0. I think you are familiar with this application,512 for buffer size and 78 for number of iteration. while using this buffer size or other than 128 some amount of audio data are missing. how can I allocate buffer size of 512. I also tried with this way simply hard coded the buffer size like this

        size [0] = 512;
        poolAttrs.bufSizes      = (Uint32 *) &size ;

        poolAttrs.numBuffers    = (Uint32 *) &numBufs ;

        poolAttrs.numBufPools   = NUMBUFFERPOOLS ;

plz help me.

Satheesh,

Please see my comments inline:

>> >>I also tried with this way simply hard coded the buffer size like this

>> >>        size [0] = 512;

[Deepali]: Just hard coding this value is not enough as multiple variables need to be set with the size. (The variable LOOP_BufferSize and strBufferSize). The above witll cause a problem as there will be incorrect size being used.

>>I have run the program by ./loopgpp loop.out 512 78 0. I think you are familiar with this application,512 for buffer size and 78 for number of iteration. while using this buffer size or >> other than 128 some amount of audio data are missing.

[Deepali]: Running the sample ./loopgpp loop.out 512 78 0 is correct. This will ensure the number 512 is used everywhere.

Cache coherence of buffers passed through CHNL is taken care of internally by DSPLink. It could be some other problem related to cache. Are the MAR registers set? Or are you using default DSPLink memory map? Are you also doing any manipulation of the buffer? More details will help.

Deepali

hai deepali

My aim is to transfer 512 0r 256 byte of data between ARM and DSP.I modiifed the sample loop program.Buffer size is entered through command line.plz give infromation about  what are the modification  needed to assign 512 or 256 byte buffer size.

thanks

regards

satheesh

hai deepali

thanks for your reply

I am using the defalt memory map providded with dsplink.

regards

satheesh

hai deepali

thanks for your help

My work in detail

gpp side

I have read PCM data file in filesystem to charecter buffer of size 30000 and read 128 byte from that buffer and issue it to channel throgh CHAL_Issue and loopbacked data is write in to another buffer and then to a file.It is sucessfully woking.while am trying with 512 some audio data are missing and there is no changes in dsp side and changes I have done is chnlAttrInput.endianism = Endianism_Little.There is no other change.

regards

satheesh

Satheesh,

When you modify the buffer size to 512 via command line, 512 bytes are transferred between ARM and DSP. Cache coherence is also maintained internally by DSPLink.

What other changes have you made in the application?

Deepali

hai deepali

thanks

I have given the buffer size only through command line ./loopgpp loop.out 512 280 0.

regards

satheesh

Sathhesh,

If you share your updated code, I can look through that to find the problem.

Deepali

hai deepali

Thank you very much

I have solved that issue it was my mistake. we have also real time kernel Linux 2.6.22.1-rt and is successfully running on the our platform.How ca i integrate dsplink 1.63 to our preemptive kernel while I am trying to load this it make more errors. plz give necessary information regarding to this area. Plz.....

thank for your support

regards

satheesh

Satheesh

Please give details on the errors so that I can comment on them.

Deepali

hai deepali

thanks for your help

While I am trying with latest version it works successfully .I have doubt whether a high priority task will preempt the dsplink application?

regards

satheesh

Satheesh,

In the pre-emptible kernel, a high priority task can preempt a low priority task.

The lower priority task could be running DSPLink. However, DSPLink code is written to ensure thread safe execution, if that is your concern.

Deepali

hello deepali

Thanks for your reply

what you mean by thread safe execution? can you explain?

regards

satheesh

Satheesh,

My point was that DSPLink works in a pre-emptive environment.

Deepali

hai deepali

thanks for your help

I am have one problem.while I am integrating our algorithm which has some memory hard cording is needed. while I am  trying with some memory area(0x87e00180,87ef0180) following error is occurred. plz give any suggestion regarding this area.

DSP MMU Error Fault!  MMU_IRQSTATUS = [0x1]. Virtual DSP addr reference that generated the interrupt = [0xffff0040].

regards

satheesh

Satheesh,

Please look here:

http://wiki.davincidsp.com/index.php/DSP_MMU_Faults

Deepali

hai deepali

thanks for your help

I have compile installed linux kernel 2.6.22.1 (linux-2.6.22.1 from kernel.org+patch from muru+patch fro mistral+rt patch from kernel.org).In this case patching works sucessfully. while I am trying with linux-02.01.03.11(linux psp) and  patch-2.6.29.6-rt24 make more error. I follow the doccument from rt wikki. plz give any suggession regarding this area

regards

satheesh

Satheesh,

I am not aware of Linux build error problems. Somebody else on community will have to help you.

Deepali

hai deepali

ok

thanks for your help

regards

satheesh

hai deepali

I cannot solve the mmu error.DSP MMU Error Fault!  MMU_IRQSTATUS = [0x1]. Virtual DSP addr reference that generated the interrupt = [0xffff0040].

I need a one  physical memry location OX10f07100 for our algorithm.I have changed the TCF file and CFG_OMAP3530_SHMEM.c

the changes are.

STATIC LINKCFG_MemEntry  LINKCFG_memTable_00 [] =
{
    {
        RSTENTRYID,                        /* ENTRY          : Entry number */
        "RESETCTRL",                       /* NAME           : Name of the memory region */
        RESETCTRLADDR,                     /* ADDRPHYS       : Physical address */
        RESETCTRLADDR,                     /* ADDRDSPVIRT    : DSP virtual address */
        (Uint32) -1u,                      /* ADDRGPPVIRT    : GPP virtual address (if known) */
        RESETCTRLSIZE,                     /* SIZE           : Size of the memory region */
        TRUE,                              /* SHARED         : Shared access memory? */
        FALSE,                             /* SYNCD          : Synchornized? */
    },
    {
        CODEENTRYID,                       /* ENTRY          : Entry number */
        "DDR2",                            /* NAME           : Name of the memory region */
        CODEMEMORYADDR,                    /* ADDRPHYS       : Physical address */
        CODEMEMORYADDR,                    /* ADDRDSPVIRT    : DSP virtual address */
        (Uint32) -1u,                      /* ADDRGPPVIRT    : GPP virtual address (if known) */
        CODEMEMORYSIZE,                    /* SIZE           : Size of the memory region */
        TRUE,                              /* SHARED         : Shared access memory? */
        FALSE,                             /* SYNCD          : Synchornized? */
    },
    {
        SHAREDENTRYID0,                   /* ENTRY          : Entry number */
        "DSPLINKMEM",                     /* NAME           : Name of the memory region */
        SHAREDMEMORYADDR0,                /* ADDRPHYS       : Physical address */
        SHAREDMEMORYADDR0,                /* ADDRDSPVIRT    : DSP virtual address */
       (Uint32) -1u,                      /* ADDRGPPVIRT    : GPP virtual address (if known) */
        SHAREDMEMORYSIZE0,                /* SIZE           : Size of the memory region */
        TRUE,                             /* SHARED         : Shared access memory? */
        FALSE,                            /* SYNCD          : Synchornized? */
    },
    {
        SHAREDENTRYID1,                   /* ENTRY          : Entry number */
        "DSPLINKMEM1",                    /* NAME           : Name of the memory region */
        SHAREDMEMORYADDR1,                /* ADDRPHYS       : Physical address */
        SHAREDMEMORYADDR1,                /* ADDRDSPVIRT    : DSP virtual address */
        (Uint32) -1u,                     /* ADDRGPPVIRT    : GPP virtual address (if known) */
        SHAREDMEMORYSIZE1,                /* SIZE           : Size of the memory region */
        TRUE,                             /* SHARED         : Shared access memory? */
        FALSE,                            /* SYNCD          : Synchornized? */
    },
    {
        POOLENTRYID,                       /* ENTRY          : Entry number */
        "POOLMEM",                         /* NAME           : Name of the memory region */
        POOLMEMORYADDR,                    /* ADDRPHYS       : Physical address */
        POOLMEMORYADDR,                    /* ADDRDSPVIRT    : DSP virtual address */
        (Uint32) -1u,                      /* ADDRGPPVIRT    : GPP virtual address (if known) */
        POOLMEMORYSIZE,                    /* SIZE           : Size of the memory region */
        TRUE,                              /* SHARED         : Shared access memory? Logically */
        FALSE,                             /* SYNCD          : Synchornized? */
    },
    {
        5,                     /* ENTRY          : Entry number */
        "DSPIRAM",             /* NAME           : Name of the memory region */
        0x5c7f8000,            /* ADDRPHYS       : Physical address */
        0x107f8000,            /* ADDRDSPVIRT    : DSP virtual address */
        (Uint32) -1,           /* ADDRGPPVIRT    : GPP virtual address (if known) */
        0x00018000,            /* SIZE           : Size of the memory region */
        TRUE,                  /* SHARED         : Shared access memory? */
        FALSE                  /* SYNCD          : Synchornized? */
    },
    {
        6,                     /* ENTRY          : Entry number */
        "DSPL1PRAM",           /* NAME           : Name of the memory region */
        0x5cE00000,            /* ADDRPHYS       : Physical address */
        0x10E00000,            /* ADDRDSPVIRT    : DSP virtual address */
        (Uint32) -1,           /* ADDRGPPVIRT    : GPP virtual address (if known) */
        0x00008000,            /* SIZE           : Size of the memory region */
        TRUE,                  /* SHARED         : Shared access memory? */
        FALSE                  /* SYNCD          : Synchornized? */
    },
    {
        7,                     /* ENTRY          : Entry number */
        "DSPL1DRAM",           /* NAME           : Name of the memory region */
        0x5cF04000,            /* ADDRPHYS       : Physical address */
        0x10F04000,            /* ADDRDSPVIRT    : DSP virtual address */
        (Uint32) -1,           /* ADDRGPPVIRT    : GPP virtual address (if known) */
        0x00003000,            /* SIZE           : Size of the memory region */
        TRUE,                  /* SHARED         : Shared access memory? */
        FALSE                  /* SYNCD          : Synchornized? */
    },
    {
    8,
    "MYDATA",
    0x5cF07000,
    0x10F07000,
    (Uint32)-1,
    0x00001000,
    TRUE,
    FALSE
    },
    {
        9,                     /* ENTRY          : Entry number */
        "L4_CORE",             /* NAME           : Name of the memory region */
        0x48000000,            /* ADDRPHYS       : Physical address */
        0x48000000,            /* ADDRDSPVIRT    : DSP virtual address */
        (Uint32) -1,           /* ADDRGPPVIRT    : GPP virtual address (if known) */
        0x01000000,            /* SIZE           : Size of the memory region */
        FALSE,                 /* SHARED         : Shared access memory? */
        FALSE                  /* SYNCD          : Synchornized? */
    },
    {
        10,                     /* ENTRY          : Entry number */
        "L4_PER",              /* NAME           : Name of the memory region */
        0x49000000,            /* ADDRPHYS       : Physical address */
        0x49000000,            /* ADDRDSPVIRT    : DSP virtual address */
        (Uint32) -1,           /* ADDRGPPVIRT    : GPP virtual address (if known) */
        0x00100000,            /* SIZE           : Size of the memory region */
        FALSE,                 /* SHARED         : Shared access memory? */
        FALSE                  /* SYNCD          : Synchornized? */
    }
} ;

and corresponding tcf file is

* Load generic DSP/BIOS Link configuration

* ============================================================================

*/

utils.importFile("dsplink-omap3530-base.tci");

utils.importFile("dsplink-iom.tci");

utils.importFile("dsplink-zcpydata-swi.tci");

utils.importFile("dsplink-dio.tci");

utils.importFile("loop.tci");

/* ============================================================================

* Set all code and data sections to use DDR2

* ============================================================================

*/

bios.setMemCodeSections(prog, DDR2) ;

bios.setMemDataNoHeapSections(prog, DDR2) ;

bios.setMemDataHeapSections(prog, DDR2) ;

/* ============================================================================

* MEM : Global

* ============================================================================

*/

prog.module("MEM").BIOSOBJSEG = DDR2 ;

prog.module("MEM").MALLOCSEG = DDR2 ;

/* ============================================================================

* TSK : Global

* ============================================================================

*/

prog.module("TSK").STACKSEG = DDR2 ;

/* ============================================================================

* Generate cdb file...

* ============================================================================

*/

if (config.hasReportedError == false) {

bios.MEM.create("MYDATA");

bios.MEM.instance("L1DSRAM").len = 0x00003000;

bios.MEM.instance("MYDATA").base = 0x10f07000;

bios.MEM.instance("MYDATA").len = 0x00001000;

bios.MEM.instance("MYDATA").createHeap = 0;

// !GRAPHICAL_CONFIG_TOOL_SCRIPT_INSERT_POINT!

prog.gen();

}

what are modification needed to access the physical address.plz give any suggestion to this area.

regards

satheesh

Satheesh,

The addresses that you are trying to map are fro IVA 2 sub system.

Can you explain why you are doing that? Also, why is ADDRDSPVIRT different from ADDRPHYS field? It should be the same.

Deepali

hai deepali

thanks for replying

our algorithm check the overflow status.we use physical memory address (its assembly file) for this checking overflow. Its successfully works on omap without linux (looping program without linux with low level codec driver program and loaded though jtag). I like integrate this program in linux though dsplink.For that purpose first i want to establish a audio data loop backing though dsplink. check with pcm data file(with out algorithm for compression) and algorithm need a physical address check. algorithm simply a c code with this overflow checking.while integrating this algorithm mmu error that i already mentioned will get. wether tcf memory edit only required for this purpose?. what are modification needed for implementing our requirement.how include one dsp physical address that will not make any conflict.

regards

satheesh

hai deepali

plz give any suggestion to above issue

thanks for your help

regards

satheesh

Satheesh,

Can you ensure ADDRDSPVIRT and ADDRPHYS are same. Please give the physical address as per specs for the memory entry. Can you try after this change?

Deepali