Loading procedure for Core1 and core2, after Linux booting

Hi Poornima,

This shared add-in document was based on buildroot, Have you enabled ICC in your yocto u-boot? 

icc driver & libmcapi were enabled in your yocto kernel?

For the multicore support additional details refer to the links below

https://wiki.analog.com/resources/tools-software/linuxdsp/docs/linux-kernel-and-drivers/mcapi/start

https://wiki.analog.com/resources/tools-software/linuxdsp/docs/linux-kernel-and-drivers/mcapi/mcapi_example

Hope this will help to move forward,

Thanks,

Prasanth R

Hi Prasanth,

Thanks for your support.

'icc driver & libmcapi 'were not enabled in our Yacto kernel config. We understand below is the procedure for enabling ICC and MCAPI.

We have following Method1 procedure for Enable and Disable Sharc cores. But

'ICC command to enable and disable slave cores' option is not available.

bitbake u-boot-adi -c menuconfig
ARM architecture  --->
    [*] ICC command to enable and disable slave cores  - This option is not showing in my menu config 

so I have followed Method2 also,

CONFIG_CORE_CONTROL: this option is not there in my menu config

Please support.

Hi Poornima,

1. Thanks for notifying, I could see the latest build was missing the u-boot support for ICC, You can leave this now, As it is for the u-boot side.

2. But method 2 was for the kernel side, which was available still (build$ bitbake linux-adi -c menuconfig)

I could see that in my build, Kindly try the below document and let me know, if you find any issues.

https://wiki.analog.com/resources/tools-software/linuxdsp/docs/linux-kernel-and-drivers/mcapi/mcapi_introduction

https://wiki.analog.com/resources/tools-software/linuxdsp/docs/linux-kernel-and-drivers/mcapi/mcapi_example

Thanks,

Prasanth R

Hi Prasanth,

Thank you for your continuous support.

 As you mentioned in the above, we have configured ICC.

Please find below observation.

Error - icc and corecontrol is not found.

currently, we are using just led blinking example code for verification(lnxdsp-examples-release-yocto-1.0.0\remoteproc\sharc-template-code\adsp-sc589-mini). So, we have not included below MCAPI package in the local.conf file.

However, if we include MCAPI Package, below error was observed.

vim build/conf/local.conf
IMAGE_INSTALL_append = " libmcapi sc5xx-corecontrol"

2.10.0 windows based CCES used for loading.

Please support.

Regards

Poornima T

Hi Poornima,

Apologize for the issues, I was using the older version of the release which has this support,

multicore api and ICC support seem dropped in the 3.0.0 release. 

According to the release & testing, 

rpmsg and remoteproc were the active means of communication between cores.

https://wiki.analog.com/resources/tools-software/linuxdsp/docs

https://wiki.analog.com/resources/tools-software/linuxdsp/docs/testing/release3.0.0

Kindly explore the below methods as per the release document.

https://wiki.analog.com/resources/tools-software/linuxdsp/docs/internal-cores-communication/rpmsg-lite

https://wiki.analog.com/resources/tools-software/linuxdsp/docs/linux-kernel-and-drivers/remoteproc/remoteproc

https://wiki.analog.com/resources/tools-software/linuxdsp/docs/linux-kernel-and-drivers/remoteproc/remoteproc_ldr_generate?s[]=remoteproc

Thanks,

Prasanth R

Hi Prashanth,

Thank you for your support.

In future, our Requirement is ICC and MCAPI only. So, now we are trying older version of the Linux booting procure yocto Linux2.1.0.

We have followed below procedure.

=>dhcp

=>setenv serverip 172.21.3.30

=>setenv tftpserverip 172.21.3.30

=>run nfsboot

While booting, I was structed. Please find below images

Kindly support.

Regards

Poornima T

Hi Prashanth,

Below one also failed, while booting.

[FAILED] Failed to start Generate n�…nits from Kernel command line.

Hi Prashanth,

         I am getting same observation. please support.

Regards

Poornima T

Hi Poornima,

Kindly share the build procedure and your local.conf file under the build directory,

Thanks,

Prasanth R

Hi Poornima,

Kindly share the build procedure and your local.conf file under the build directory,

Thanks,

Prasanth R