Post Go back to editing

SHARC core 2 stuck

Hii

We are using ADSP-SC589 in my custom board &
Linux add-in 1.2.0
CCES 2.8.2

Whenever we run SHARC core 1 &2 together for the MCAPI communication with ARM, SHARC core 2 stuck/hanged.
But if run only SHARC core 2 with ARM then it's work fine .

what are the possible point to debug/ solve the issue.

NOTE: same program work fine with ADSP-SC589 EZ Board (eval board).

Parents
  • Hi, 

    Thanks for you information.

    Please refer to the attached example to run the Three-Core Communications Example with MCAPI.

    2287.MCAPI Fix and Three-Core Example for ADl-Linux-Addin-1.2.0.zip

    Please let me know if there has any question

    Best Regards

    Sullivan

  • Hi

    Thanks for the patch.
    but .... problem is the same.
    My customized board have same behavior like before.
    any other solution.

  • Hi

    Thanks for you information and Could you please try it again following the below steps:

    1. Could you please check the MCAPI status between ARM Core0 and SHARC Core1 only.
    2. Could you please double check that the attached example (three-core communication Example) could work on your customized board well or not.
    3. If it couldn't work, please enable the icc debug option in kenenl-config as below: 
           Device Drivers  --->
                 [*] Staging drivers  --->
                     [*]   icc driver  --->
                          --- icc driver
                          [*]   icc protocol
                          [*]   icc debug

                 Then type "make linux-rebuild;make" to rebuild the kernel and get the log.

            4. could you please send the log to us via email, it's will be very appreciated! 

    E-mail Address: processor.tools.support@analog.com

    Best Regards

    Sullivan

  • Hi

    Sorry for the late reply

    (It's all about customized board)
    1. I checked the status b/w ARM core0 & SHARC core1
        in all the cases status: MCAPI_SUCCESS
        I checked with SHARC core2 also & it's also have the same status i.e MCAPI_SUCCESS.
        But problem with SHARC Core2 is that it's have delay more than 30 sec during mcapi_endpoint_get()
        on  both side respectively (i.e ARM0 & SHARC2) & same delay problem during mcapi_msg_send()
        & mcapi_msg_recv() on both respective sides.
        But i expect the response immediately (like the communication b/w ARM0 & SHARC1 ).

    4. Are you talking about entire kernel build log?

    Thanks & Regards
    Parikshit

  • Hi Parikshit,

    Thanks for your information.

    I have got your test log from the Support team and try to double check to reproduce your issue following your configurations and  steps (Linux add-in 1.2.0 & CCES 2.8.2 & SC589 with Core0 ,Core1 and Core2 communication). But I am sorry I can't get your/your customer's problem in my board.

    So could you please have a try following the below steps again:

        1. Please double check the below examples that we provided can work well in your Board or not, and these tow  examples all work well in my sc589-EZ-Kit board:

              Example1. Core0 - Core2 BareMetal example: 5633.MCAPI_msg.zip, Note for this example, please run F5 to run Core0 to Core2 and the test log as the attached showing.

              Example 2. Core0-Core1&2 Linux-BareMetal example: following this document to run the three core example and get the test log, https://ez.analog.com/dsp/software-and-development-tools/linux-for-adsp-sc5xx-processors/w/documents/15009/mcapi-bug-fix-and-update-for-adi-linux-addin-v1-2-0-to-v1-3-1

         2.  Please enable the icc debuing log option in kernel-configuration as below and get the log:

    $ cd ~/sc5xx_dev/buildroot/
    $  make linux-menuconfig
    
    

                And following this PATH to enable the icc debug option.

           Device Drivers  --->
                 [*] Staging drivers  --->
                     [*]   icc driver  --->
                          --- icc driver
                          [*]   icc protocol
                          [*]   icc debug

                 Then type "make linux-rebuild;make" to rebuild the kernel and get the log.

    $  make linux-rebuild;make

                 Load the generated uImage and dtb file to target board and the icc debug will be shown when running the MCAPI example. 

         3.  Could you please share your MCAPI example and ICC driver code to us via E-mail:

             Your MCAPI example: maybe at buildroot/output/build/libmcapi-HEAD/libmcapi-2.0/tests/

             ICC driver folder for linux-addin-1.2.0:

                                         buildroot/linux/linux-kernel/drivers/staging/icc

                                         buildroot/linux/linux-kernel/arch/arm/boot/dts/sc589-ezkit.dts & sc58x.dtsi

        4. Could you please share the above test logs for us via Email:

    E-mail Address: processor.tools.support@analog.com

    Best Regards

    Sullivan

Reply
  • Hi Parikshit,

    Thanks for your information.

    I have got your test log from the Support team and try to double check to reproduce your issue following your configurations and  steps (Linux add-in 1.2.0 & CCES 2.8.2 & SC589 with Core0 ,Core1 and Core2 communication). But I am sorry I can't get your/your customer's problem in my board.

    So could you please have a try following the below steps again:

        1. Please double check the below examples that we provided can work well in your Board or not, and these tow  examples all work well in my sc589-EZ-Kit board:

              Example1. Core0 - Core2 BareMetal example: 5633.MCAPI_msg.zip, Note for this example, please run F5 to run Core0 to Core2 and the test log as the attached showing.

              Example 2. Core0-Core1&2 Linux-BareMetal example: following this document to run the three core example and get the test log, https://ez.analog.com/dsp/software-and-development-tools/linux-for-adsp-sc5xx-processors/w/documents/15009/mcapi-bug-fix-and-update-for-adi-linux-addin-v1-2-0-to-v1-3-1

         2.  Please enable the icc debuing log option in kernel-configuration as below and get the log:

    $ cd ~/sc5xx_dev/buildroot/
    $  make linux-menuconfig
    
    

                And following this PATH to enable the icc debug option.

           Device Drivers  --->
                 [*] Staging drivers  --->
                     [*]   icc driver  --->
                          --- icc driver
                          [*]   icc protocol
                          [*]   icc debug

                 Then type "make linux-rebuild;make" to rebuild the kernel and get the log.

    $  make linux-rebuild;make

                 Load the generated uImage and dtb file to target board and the icc debug will be shown when running the MCAPI example. 

         3.  Could you please share your MCAPI example and ICC driver code to us via E-mail:

             Your MCAPI example: maybe at buildroot/output/build/libmcapi-HEAD/libmcapi-2.0/tests/

             ICC driver folder for linux-addin-1.2.0:

                                         buildroot/linux/linux-kernel/drivers/staging/icc

                                         buildroot/linux/linux-kernel/arch/arm/boot/dts/sc589-ezkit.dts & sc58x.dtsi

        4. Could you please share the above test logs for us via Email:

    E-mail Address: processor.tools.support@analog.com

    Best Regards

    Sullivan

Children