Post Go back to editing

Sigma Studio+ library usage for SHARC on ADSP-SC598-SOM + CRR-EZKIT

Category: Software
Product Number: ADSP-SC598
Software Version: 3.3

Hi, I'd like some clarification on how to use the Sigma libraries on SHARC . My end goal is to be able to use Sigma Studio+ and push schematics / update values without the USBi interface when running Linux on the Arm core.

Here is what I have achieved so far:

  • I have a Linux and SHARC code running based on the alsa-sharc example project at https://github.com/analogdevicesinc/lnxdsp-examples/tree/develop/yocto-5.0.0/icap-sharc-alsa-example
  • I have updated the project to process an exported schematic from SS+ using adi_ss_schematic_process()
  • I have implemented a Python server to which SS+ successfully connects to when using the TCP/IP communication Adaptor and that forwards data between SHARC and SS+ through Linux.
  • I have implemented the use of the Sigma library functions on Sharc.
  • I am able to "Link - Compile - Download" from SS+ and have an Active status without error on both SS+ and the SHARC.

My default exported schematic running on the SHARC is a simple Mute block between the input and output.

My issue is that after pushing the schematic I loose audio, however I do not get any error on SS+ or on the SHARC. I am wondering if the parsing of the data on the SHARC is failing or if the data is written to the wrong address in memory. I could not find examples explicitly using the function adi_ss_comm_Parse() or other functions from the lib.

Could you provide an example on how to use those functions on SHARC ?

Thanks,
Damien

Edit Notes

Updated title to add "ADSP-SC598-SOM + CRR-EZKIT"
[edited by: Littlemonster at 2:53 PM (GMT -5) on 25 Feb 2026]

Thread Notes

  • Bumping this as it has been a few days without getting an answer.

  • Hi,
     I could help you regarding SS+ library integration.
    Could you please confirm are you using generated schematic source files? or schematic download from SigmaStudio+?

    Please refer to this link for communication and target library integration,
    Target and Communication Libraries Integration [Analog Devices Wiki]

    If you are using schematic source file, then you need to regenerate the file even a single line of code change in target application.
    Microcontroller Mode Support [Analog Devices Wiki]

    The "adi_ss_comm_Parse()" function is defined in communication library to parse data received over SPI. Please refer the SPI communication related information in following link.
    SigmaStudio+ Host Controller Guide [Analog Devices Wiki]


    Thanks. 

  • Hi, thank you for helping.

    I am using a generated source file as initial schematic but then I want to be able to push an updated version of the schematics, on the fly, without having to recompile the whole LDR file. Is it something supported ? Or do I have to set bSkipInitialDownload to false in the ADI_SS_CONFIG structure when initialising ?

    I am not using SPI, I am using the TCP/IP adaptor. I know this is not the recommended way but I have written a Python script that works and acts as a bridge, on Linux, between SHARC and SS+ and I have managed to get the Sigma Studio data to / from the SHARC. I have made sure to strip the TCP/IP protocol (defined  here) before sending the SMAP data. I am also sending the response to the MIPS read request using adi_ss_comm_Packetize to properly format the backchannel.

    Please see below the SS+ data capture :

    I want an example (or even a simplified algorithm) that can confirm how to call adi_ss_comm_Parse and other functions that may be needed. I have noticed I get parse errors that magically get solved if I attempt to re-parse the same word again.

    Right now it seems the schematic processing fails as soon as I finish parsing the data transmitted by SS+.

  • The adi_ss_comm_Parse function is an internal API, so we cannot share its implementation details. However, you can call this function by providing one 32‑bit word at a time. Please refer to the header files available at:

    C:\Analog Devices\SigmaStudioPlus-Rel3.3.0\Target\Include
    

    The function prototype is:

    ADI_SS_COMM_RESULT adi_ss_comm_Parse(ADI_SS_COMM_HANDLE hSSComm, uint32_t nData);

    In our example, SPI is used to receive schematic data with the highest priority. Because of this priority scheme, the SPORT ISR will be serviced only after the code and parameter updates are completed. This means on‑the‑fly updates are supported in SigmaStudio+.

    In your case, we are not sure how fast the data is being received, so you may try disabling SPORT during the schematic code and parameter data transfer, and enabling it again after the data is fully copied into the target memory.

    We also recommend dumping the memory contents after copying the schematic code and parameter data, and comparing them with the Capture Window data to ensure they match.

    The bSkipInitialDownload flag should be set to false if your application starts with the generated schematic files.

    Note: The schematic source files must be regenerated each time you modify the target application code.

  • Thank you for your answer, I have a couple of notes:

    - "adi_ss_comm_Parse function is an internal API" : In Target\Include\adi_ss_communication.h this function (and others) are declared in a section which is stated that they are public prototypes. If thos functions are not intended to be used by external developers I suggest removing them from this public header as this brings confusion.

    - I am sending the data from Linux to the SHARC through a RPMSG endpoint.

    - Dumping the memory is a good idea, I will try this.

    - " bSkipInitialDownload flag should be set to false if your application starts with the generated schematic files": I disagree with this. The example code at https://wiki.analog.com/resources/tools-software/sigmastudiov2/targetintegration/integratecommlibrary sets bSkipInitialDownload to 0 (false) and wait for a download to be received in the init function before starting to process. On the other hand, in Target\Examples\LibraryIntegration\ADSP-SC598\LibIntegrationExample_Core1\src\LibIntegrationExample_Core1.c, bSkipInitialDownload is set to 1 (true), the code does not wait to receive an initial download and copies the schematic data to memory during the init function.

    - I was not regenerating the schematic source files when modifying the target code, thanks for pointing this out.

  • Yes you are right, the "bSkipInitialDownload" flag should be true.

Before You Switch


Switching languages will make ADI Explorer unavailable. Resume your session by switching back to English and reopening ADI Explorer.