We are using ADSP-SC589 in my custom board & Linux add-in 1.2.0CCES 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).
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
Thanks for the patch.but .... problem is the same.My customized board have same behavior like before.any other solution.
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/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: email@example.com
Hi Sullivan Thanks for the support I have mailed all the files & icc-driver debug log.kindly, check the mail.
Thanks for your information and I will keep checking the mail from support team.
And just to double check that:
Thanks for your support1. Nope, I didn't checked your example at any board.2. My example/project working as expected on standard SC589-EZKIT evaluation board (core0 and core2).3. Yes, ICC & MCAPI patch has been successfully applied.4. And I don't have any changes in ICC driver at my level.
Sorry, I also have a info that -customize board has ADSP-SC587.ThanksParikshit Thakur
These days, I ported you example into my sc589-ezkit board, it works well with the three-core communication following your comments.