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.

UDMA Initialization failed whiled launching msgcom



The Sysapps package is built as follows:

1. Obtained the Linaro toolchain.

2. Installed the SC-MCSDK 2_02_01_03 package to get the Linux Dev Kit.

3. Installed the Linux Dev Kit obtained from the SC-MCSDK package to get all the libraries required.

4. Obtained the Sysapps package from the repo: git://arago-project.org/git/projects/sysapps.git and checked out to the Release Version Specified in the Document provided.

5. After setting up all the Environment variables, the sysapps package is built and all the required executables are obtained.

But, there is a run time error while running the obtained executable msgrouter.out on linux.

The error is as follows:

Debug: Number of MSGCOM channels 4 Shared Address 0xa0000000
Debug: Resource Manager Size requirement is 31960 bytes (0)
Debug: Named Resource Database is mapped to address 0x0xb6e58000
Error: UDMA Initialization failed.


What, can be the reason of this failure in initialization ?

  • HI,

    Can you please let us know what command is used to run msgrouter?

    Thank you
    Cesar
  • Hi,

    I executed the command in linux on tci6614 as:

    root @ tci6614# ./msgrouter.out -n 4 -d 10 -v &

    And exucuting msgrouter.out as above gave me the following error:

    Debug: Number of MSGCOM channels 4 Shared Address 0xa0000000

    Debug: Resource Manager Size requirement is 31960 bytes (0)

    Debug: Named Resource Database is mapped to address 0x0xb6e58000

    Error: UDMA Initialization failed.


    Provided I am running linux kernel 3.3.0-00008-gead1114-dirty.

    The linux kernel was obtained from the arago repository as given in the SC-MCSDK user guide.

    http://arago-project.org/git/projects/?p=linux-tci6614.git;a=summary.

    The kernel was then built for tci6614 with the default configuration, after doing a checkout to the version specified by the RELEASE_TAG.

    Thanks.

    Ranjit.

  • Hi,

    I think you should be using the kernel binaries provided with the SC-MCSDK.

    There should not be the need to re-build the kernel.

    Thanks

    Cesar

  • Hi Cesar,

    I tried using the Kernel Binaries provided by the SC-MCSDK_02.00.00.08, which was not working. The kernel was getting halted while Uncompressing the Kernel. The boot message while booting the board with the kernel binaries obtained (uImage-tci6614-evm.bin and tci6614-evm.dtb) from SC-MCSDK_02.00.00.08 is as follows.

    ## Booting kernel from Legacy Image at 88000000 ...
       Image Name:   Arago/3.3/tci6614-evm
       Created:      2012-05-05  18:48:53 UTC
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    2268040 Bytes = 2.2 MiB
       Load Address: 80008000
       Entry Point:  80008000
       Verifying Checksum ... OK
    ## Flattened Device Tree blob at 80000200
       Booting using the fdt blob at 0x80000200
       Loading Kernel Image ... OK
    OK
       Loading Device Tree to 9fec1000, end 9fec5664 ... OK

    Starting kernel ...

    Uncompressing Linux... done, booting the kernel.

    So, for the time being, I tried building the Kernel, obtaining the Source from the Arago Repository as given in the SC-MCSDK user guide. This kernel binary worked fine for me. Provided, I was not able to run the msgrouter.out executable.

    Now, as per your last reply, I am currently using the Kernel Image obtained after installing the SC-MCSDK _ 02.00.00.08 Patch1. But, still executing the msgrouter.out gives me the Same Error as previous.

    ./msgrouter.out -n 4 -d 10 -v
    Debug: Number of MSGCOM channels 4 Shared Address 0xa0000000
    Debug: Resource Manager Size requirement is 31960 bytes (0)
    Debug: Named Resource Database is mapped to address 0x0xb6eb9000
    Error: UDMA Initialization failed

    Am I missing out something ?

  • Hi,

    Thank you for these details.

    Is there a reason for you using this SC_MCSDK version? I think this is 3 years old!

     

    Could you use the latest release? We just tried it yesterday and it works fine

     

    Please let me know if you need the link to download the latest release

     

    Thanks

    cesar

  • Hi Cesar,

    Just to help here, I am the UK Ti FAE supporting this customer.

    The customer wants an out of the box example to show IPC running between the ARM core and the C66x DSP on the TCI6614 EVM. Can we recommend which MCSDK they should be using and what set of instructions they need to follow which we have tried and know to work?

    many thanks

    Dave
  • Hi,

    Will make a short video recording to show you how to build and run the msgcom examples. We plan to send it to you by the end of the week.

    Thank you
    Cesar
  • Many thanks Cesar,

    appreciate your help here.

    regards

    Dave
  • Hi Cesar,

    The reason behind using SC_MCSDK is, with the Latest release I don't find the packages for TCI6614.

    It would be good, if you can provide the link to get the latest release for TCI6614.

    Thanks.

  • Hi many thanks for the videos.

    Question 1:

    please could you supply the links to the software which is referenced in the videos, this is not available on the Ti public links.

    E.g. SC-MCSDK 2_02_01_03  

    Question 2:

    When a new release becomes available, how will we know this and where will we get it from?

    We just need to make sure the customer can download the exact release we are recommending from our recommended server. This will help our customer to follow the videos.

    many thanks

    Dave

  • Latest sc-mcsdk release can be downloaded from this public link

     

    http://software-dl.ti.com/sdoemb/sdoemb_public_sw/sc_mcsdk/latest/index_FDS.html

     

    Thanks

    cesar

  • Hi Ranjit,
    Please help us to close this thread. Thank you.